Server error: tcp 553
[1/11] from: hijim::pronet::net at: 16-Apr-2003 20:16
** User Error: Server error: tcp 553 sorry, that domain isn't in my list of allowed rcp
thosts (#5=2E7=2E1)
** Near: insert port reduce data
That's the error message I get when I send email to some addresses=2E What causes this?
One list I belong to now gives me this message, though my emails used to go through fine=2E
Here's the code I use:
butt "Send" red [
write %email=2Etxt my-area/text
write clipboard:// my-area/text
a: request/confirm "Are you connected to the Internet?"
if not a [return]
send to-email m-field/text my-area/text
]
The error message says:
Near: insert port reduce data
but that's not part of my code=2E
I can't get through to rebol-list with this code either=2E So why does it work with certain
addresses and not with others?
Thanks,
Jim Clatfelter
[2/11] from: gschwarz:netconnect:au at: 17-Apr-2003 14:24
Some mail servers have black list.
If they see many e-mails from one mail server, they may put that server on a
black list for 3 days.
Hence now any mail you send though your mail server is now blocked.
Regards,
Greg
----- Original Message -----
From: "Jim Clatfelter" <[hijim--pronet--net]>
To: <[rebol-list--rebol--com]>
Sent: Thursday, April 17, 2003 1:16 PM
Subject: [REBOL] Server error: tcp 553
** User Error: Server error: tcp 553 sorry, that domain isn't in my list of
allowed rcp
thosts (#5.7.1)
** Near: insert port reduce data
That's the error message I get when I send email to some addresses. What
causes this? One list I belong to now gives me this message, though my
emails used to go through fine.
Here's the code I use:
butt "Send" red [
write %email.txt my-area/text
write clipboard:// my-area/text
a: request/confirm "Are you connected to the Internet?"
if not a [return]
send to-email m-field/text my-area/text
]
The error message says:
Near: insert port reduce data
but that's not part of my code.
I can't get through to rebol-list with this code either. So why does it work
with certain addresses and not with others?
Thanks,
Jim Clatfelter
[3/11] from: antonr:iinet:au at: 17-Apr-2003 14:18
Looks like a blacklist is in effect on your
mail server ? It could be that a server has
been blacklisted because of spam. I would
imagine that the condition should be temporary...
By the way, asking the user if they are connected
to the internet is not a very reliable way of
avoiding network errors.
I would rather catch the errors:
if error? set/any 'err try [
; send mail here
][
; I usually pop open a new window here, but anyway...
print [
"oh no, there was an error, not connected?"
mold disarm err
; extra details of the message here
]
]
And you are not interrupting the user with another
useless dialog box (unless there is a problem).
Anton Rolls.
[4/11] from: gscottjones:mchsi at: 17-Apr-2003 5:45
Hi, Jim,
From: "Jim Clatfelter"
> ** User Error: Server error: tcp 553 sorry,
> that domain isn't in my list of allowed rcp thosts (#5.7.1)
> ** Near: insert port reduce data
...
> That's the error message I get when I send email to some addresses. ...
Others have suggested that your server has been blacklisted, which may be
true and account for why only some emails bounce. Your statement here
suggests that this *may* be the case.
> What causes this? One list I belong to now gives me this message,
> though my emails used to go through fine.
There are other causes for 553 errors. 553 is the general smtp bounce code.
Bounces can occur for a number of reasons that are configurable by the smtp
server administrator. A fairly common cause is using an smtp server that
requires authentication prior to accepting email for forwarding. Some
servers require authentication before accepting any email. Others may
require authentication before accepting email that has a disimilar domain
root ([joe--mypersonaldomain--com] being sent through smtp.acompany.com). After
authentication, the server can be configured to allow email to be sent for a
period of time, like 15 minutes.
Checking email before sending is the "simplest" way to authenticate.
read pop://myusername:[myuserpass--mail--mydomain--com]
send [myusername--mydomain--com] "test"
If your smtp server has been blacklisted, then sending email through any
email client will bounce when routed through that server. In theory an smtp
server may also bounce emails that have disimilar roots (identified email
address is disimilar to the root of the original smtp server), but this
would bounce many, many emails, so I suspect few actually do this form of
blocking.
> The error message says:
> Near: insert port reduce data
> but that's not part of my code.
That code is in the SEND command, viewable, of course, by typing "source
send".
> I can't get through to rebol-list with this code either. So why does it
> work with certain addresses and not with others?
This was the part that caught my attention. It seems unlikely that you have
been blocked by rebol-list; after all, your email through a different email
client did get through. If this client has been configured to authenticate
prior to sending, then you may have your answer. As a side note, the
rebol-list will only automatically post email that uses an address that has
been signed up. Other email addresses require manual approval, which can be
slow when RT is busy. To my knowledge their server does not
block/blacklist.
So, before you throw in the towel, I would suggest using very simply code to
check the authentication issue (see above). If authentication is *not* the
issue, there may be other issues going on with your code; however, it is not
possibly to access this possibility without further information (for
example, I am unclear why you have supplied 3 arguments for SEND when only 2
are required by default).
--Scott Jones
[5/11] from: gscottjones:mchsi at: 18-Apr-2003 11:11
Hi, Jim,
...
SJ> I am unclear why you have supplied 3 arguments for SEND
SJ> when only 2 are required by default.
JC> send to-email m-field/text my-area/text
JC> to-email m-field/text is the first argument; it doesn't work without
to-email
My apologies. Poor excuse but I was tired yesterday and totally spaced it
that "to-email" was a REBOL command. Apologies.
JC> I can send anywhere without being bounced EXCEPT
JC> when I use REBOL. Then I get bounced sending to some
JC> addresses. My server isn't blacklisted. I figure it's my error.
<link to script removed>
JC> And thanks to everyone who responded.
First, the good news is that your script seems to work unchanged through my
smtp server. Looking at the header that is sent, I see one possible issue.
REBOL includes:
X-REBOL: View 1.2.8.3.1 http://WWW.REBOL.COM
as a part of its standard header. There is a chance that your smtp server
blocks on this header. Easiest way to check is to modify REBOL's header
template to get rid of this marker.
system/standard/email: make system/standard/email [
To: none
CC: none
BCC: none
From: none
Reply-To: none
Date: none
Subject: none
Return-Path: none
Organization: none
Message-Id: none
Comment: none
MIME-Version: none
Content-Type: none
Content: none
]
Place this at the begiining of your script and then rerun your script.
If messages still bounce, then there may be another problem with the header.
Are you sending HTML email? If so then the header may be malformed for this
purpose. Compliant email clients send a mutipart email that includes a text
version and the html email version. The email client is then configured to
select which version to show. Email can be sent as HTML email only, but
there is a chance that this is not compliant with the standard, depending on
what is sent, and therefore getting bounced. Just thinking out loud. It
will be interesting to see exactly what is casuing the bounce, so be sure
and let me/us know.
--Scott Jones
[6/11] from: hijim::pronet::net at: 18-Apr-2003 16:55
Bouncing
Hi Scott,
I added your code to the top of my script, but it still bounces. I'm trying this with
Outlook Express. I want to see if it bounces with that program. I seem to remember messages
bouncing in the past. If you get this message, it didn't bounce.
Thanks for all your efforts,
Jim
[7/11] from: hijim:pronet at: 18-Apr-2003 17:11
Server error: tcp 553
Hi Scott,
You seem to have received my email, since you quote it and say you tried the script=2E
But I didn't get it back on my machine=2E And it doesn't appear on rebol-list http://www=2Eescribe=2Ecom/internet/rebol/index=2Ehtml
archives=2E That's pretty strange=2E
I tried your code but my mail still bounces=2E I'm glad it worked for you=2E I think
this message may be sent to the list, but it won't be sent back to me, and it won't appear
in the archives=2E
This must be a problem with my server=2E I'm going to give them a call=2E Then I'll test
your new code=2E
Thanks,
Jim
[8/11] from: gscottjones:mchsi at: 19-Apr-2003 5:45
From: "Jim Clatfelter"
> You seem to have received my email, since you quote
> it and say you tried the script. But I didn't get it back
> on my machine. And it doesn't appear on rebol-list
> http://www.escribe.com/internet/rebol/index.html
> archives. That's pretty strange.
Like a good magic trick, it is less strange once you know what happened.
That email you sent was sent directly to me instead of the list. I assumed
that had happened because you were changing clients as you were figuring out
this problem. If so, then it is very easy to accidently send it to the
wrong address. I probably should have explained this, but I didn't want to
draw light to that issue. Now look what I've done! :-)
> I tried your code but my mail still bounces.
My code snippet only got rid of the evidence that REBOL was sending the
email. So it seems as though that was not the issue. There still may be
some sort of authentication issue, a header mismatch or content encoding
issue.
I looked through pronet's support pages, and I do not see that
authentication is required before sending email. I am assuming that your
domain name on your email address is the same as that of the server (both
are pronet.net).
Inorder to separate whether your smtp server is choking on something REBOL
is doing versus your value-added client, I would next check by sending a
very basic message from the REBOL's command line.
send [personofmychoosing--theirdomain--com] "This is a test message"
If this message does not bounce, then it is likely something in your
program. If it does bounce, then, just to be compulsively sure, I would get
rid of the header line that identifies REBOL:
X-REBOL: "View 1.2.8.3.1 http://WWW.REBOL.COM"
as shown in the code sample yesterday. (BTW, as you probably already know,
there are of course other ways to do that.) If this message bounces, then
the problem gets *really* interesting, in my opinion, because it suggests at
least one of two possibilities: 1) REBOL's smtp scheme may have a bug, 2)
pronet's smtp server is non-standard, 3) pronet's smtp server screens for
the most common kind of clients before sending on email.
Given that your email to the list does not show a client type in the
headers, I do not think #3 is very likely, *unless* you are using pronet's
webmail interface (in which case they know you are validated). If you have
been using their web-based email to respond to the list, then, from REBOL
you may wish to send a spoofed head along with you email to see if they are
indeed screening for "bonified email clients (note that some localities may
have laws which prohibit header spoofing). One option would be to add the
following to the header:
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
Assuming that the above issue is not proving productive, I would next screen
the conversation between REBOL and your smtp server. The easiest way to do
this is to turn on tracing:
trace/net on
then resend your test message from the console:
send [personofmychoosing--theirdomain--com] "This is a test message"
This conversation will look something like this (email addresses obscured to
reduce spam harvesting):
Net-log: ["Opening" "tcp" "for" "smtp"]
Net-log: [none "220"]
Net-log: {220 sccmmhc01.mydomain.com - Maillennium ESMTP/MULTIBOX sccmmhc01
#3}
Net-log: [["HELO" system/network/host] "250"]
Net-log: "250 sccmmhc01.mydomain.com"
Net-log: "MAIL FROM: <[myname--mydomain--com]>"
Net-log: [none "250"]
Net-log: "250 ok"
Net-log: "RCPT TO: <[anothername--anotherdomain--com]>"
Net-log: [none "250"]
Net-log: "250 ok"
Net-log: ["DATA" "354"]
Net-log: "354 ok"
Net-log: [none "250"]
Net-log: "250 ok ; id=20030419102205mm1008qqooe"
Net-log: ["QUIT" "221"]
Net-log: "221 sccmmhc01.mydomain.com"
The bracketed responses are what REBOL is doing. The unbracketed responses
are what your smtp server is sending. If pronet's smtp server is
noncompliant, then one of these responses will look different. If you will
share that difference, then we will know what is going on. (BTW, given your
earlier messages, my assumption is that the message is not being accepted by
the server, instead of actually being accepted but then returned as
undeliverable.)
Let us know what you find when you have time.
--Scott Jones
[9/11] from: hijim:pronet at: 19-Apr-2003 7:36
Hi Scott,
Error message below comes from REBOL console=2E I've called pronet, and they are looking
into it=2E They were recently bought out by impulse=2Enet=2E They may be causing the
problem=2E I get this message sending mail to anyone=2E I may have to change servers
if they can't fix this=2E I can send email with any program but REBOL=2E
Sorry about sending to you instead of list=2E DeltaMail reply button does that=2E Gotta
watch that=2E
Thanks for all your help=2E I'll let you know if they fix it=2E
Thanks to Anton too=2E I've added your error trapping lines=2E No more pop up message=2E
Jim
*** REBOL/View license only=2E No REBOL/View/Pro features=2E
*** Obtain REBOL/View/Pro from http://www=2Erebol=2Ecom/view-sales=2Ehtml
>> send [rebol-list--rebol]=2Ecom "Hi Scott, This is a test message sent from the REBOL
cons
ole=2E"
** User Error: Server error: tcp 553 sorry, that domain isn't in my list of allowed rcp
thosts (#5=2E7=2E1)
** Near: insert port reduce data
>>
----- Original Message -----
From: G=2E Scott Jones
To: [rebol-list--rebol]=2Ecom
Date: Sat, 19 Apr 2003 05:45:23 -0500
[10/11] from: gscottjones:mchsi at: 19-Apr-2003 10:47
Hi, Jim,
From: "Jim Clatfelter"
> Sorry about sending to you instead of list.
No problem.
> Thanks for all your help. I'll let you know if they fix it.
If they don't (or "can't"), try sending the same email from the console but
with trace/net set to on just out of curiosity.
Hope they fix it soon for you. Good luck.
--Scott Jones
[11/11] from: g:santilli:tiscalinet:it at: 19-Apr-2003 21:15
Hi Jim,
On Saturday, April 19, 2003, 4:36:32 PM, you wrote:
JC> Error message below comes from REBOL console. I've called
JC> pronet, and they are looking into it. They were recently
JC> bought out by impulse.net. They may be causing the problem. I
JC> get this message sending mail to anyone. I may have to change
JC> servers if they can't fix this. I can send email with any
JC> program but REBOL.
Did you compare the configuration of your email clients versus
that of REBOL (i.e. the SET-NET line of your user.r file)? There
has to be some difference...
Regards,
Gabriele.
--
Gabriele Santilli <[g--santilli--tiscalinet--it]> -- REBOL Programmer
Amigan -- AGI L'Aquila -- REB: http://web.tiscali.it/rebol/index.r