Mailing List Archive: 49091 messages
  • Home
  • Script library
  • AltME Archive
  • Mailing list
  • Articles Index
  • Site search
 

[REBOL] Re: Server error: tcp 553

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