The e-securemail interface, at the message tracking level, allows you to retrieve the SMTP code that is returned by the server in front of you.
This is usually related to problems with email delivery (e.g. after a bounceback), your SMTP server returns a particular error message.
The problem is that it will probably be cryptic, like "550 Requested action not taken: mailbox unavailable" or "421 Try again later".
What do these numbers mean? And how can they help the confused user to solve the problem?
Secuserve, offers a list of the main SMTP errors or response messages, with an explanation and advice on what to do.
|
CODE |
WHAT DOES IT MEAN |
WHAT TO DO |
|
101 |
The server is unable to connect. |
Try changing the server name (perhaps misspelled) or the connection port. |
|
111 |
Connection refused or inability to open an SMTP stream. |
This kind of error normally refers to a problem with the connection to the remote SMTP server, caused by a firewall or misspelled domains. Check all configurations or ask your provider. |
|
211 |
System status message or help response. |
It comes with more information about the server. |
|
214 |
A response to the HELP command. |
It contains information about your server, normally pointing to a FAQ page. |
|
220 |
The server is ready. |
This is just a welcome message. Be happy that everything works (for now)! |
|
221 |
The server closes its transmission channel. It may come with messages such as "Goodbye" or "Closing connection". |
The mailing session will end, which simply means that all messages have been delivered. |
|
250 |
Its typical side message is "Requested mail action okay completed": which means that the server has transmitted a message. |
The exact opposite of an error: everything worked and your email was delivered. |
|
251 |
"User not local will forward": the recipient's account is not present on the server, so it will be relayed to another. |
This is a normal transfer action. |
|
252 |
The server cannot verify the user, but it will try to transmit the message anyway. |
The recipient's email address is valid, but not verifiable. Normally, the server forwards the message to another server that will be able to verify it. |
|
354 |
The message can be very cryptic ("Start mail input end <CRLF>.<CRLF>"). This is the typical response to the DATA command. |
The server has received the "From" and "To" details of the email, and is ready to pass the body of the message. |
|
420 |
"Timeout connection problem: there were problems with the transfer of messages. |
This error message is only produced by GroupWise servers. Either your email has been blocked by the recipient's firewall, or there is a hardware problem. Check with your provider. |
|
421 |
The service is unavailable due to a connection problem: it may refer to an overflow of simultaneous connections, or to a more general temporary problem. |
The server (yours or the recipient's) is not available at the moment, so the sending will be tried later. |
|
422 |
The recipient's box has exceeded its storage limit. |
It is best to contact the user through another channel to alert them and ask them to create free space in their box. |
|
431 |
Not enough space on the disk, or an "out of memory" condition due to file overload. |
You should try again to send smaller sets of emails instead of one big one-off. |
|
432 |
"The recipient's Exchange Server incoming mail queue has been stopped. |
This is the SMTP error code for Microsoft Exchange. You should contact him for more information: usually it is due to a connection problem. |
|
441 |
The recipient's server does not respond. |
There is a problem with the user's incoming server: yours will try to contact him again. |
|
442 |
The connection was interrupted during transmission. |
A typical network connection problem, due to your router: check immediately. |
|
446 |
"The maximum hop count was exceeded for the message: an internal loop has occurred. |
Ask your SMTP provider to check what happened. |
|
447 |
Your outgoing message has expired due to problems with the incoming server. |
This usually happens when you have exceeded your server's limit on the number of recipients for a message. Try sending again by segmenting the list into smaller shares. |
|
449 |
A routing error. |
Like error 432, it is related only to Microsoft Exchange. Use WinRoute. |
|
450 |
"Requested action not taken - The user's mailbox is unavailable. The mailbox has been corrupted or placed on a server that is not online, or your email has not been accepted due to IP or blacklisting issues. |
The server will try to send the message again after a while. In any case, check that it is working on a reliable IP address. |
|
451 |
"Requested action aborted - Local error in processing". Your ISP's server or the server that first relayed from you has encountered a connection problem. |
This is normally a temporary error due to message overload, but it may also refer to a rejection due to a spam filter. If it keeps recurring, ask your SMTP provider to check the situation. |
|
452 |
Too many emails sent or too many recipients: More generally, a server storage limit exceeded. |
Again, the typical cause is a message overload. Usually the next attempt will succeed: if there are problems on your server, it will come with a side message like "Out of memory". |
|
471 |
An error in your mail server, often due to a local spam filter problem. |
Contact your SMTP service provider to correct the situation. |
|
500 |
A syntax error: the server could not recognise the command. |
It can be caused by a bad interaction between the server and your firewall or antivirus. Check the instructions carefully to solve it. |
|
501 |
Another syntax error, not in the command, but in its parameters or arguments. |
In most cases it is due to a valid e-mail address, but it can also be associated with connection problems (or an issue with your antivirus settings). |
|
502 |
The command is not implemented. |
The order has not yet been activated on your own server. Contact your supplier for more information. |
|
503 |
The server has encountered a wrong command sequence, or it requires authentication. |
In the case of a "bad sequence", the server has withdrawn its orders in the wrong order, usually due to a connection failure. If authentication is required, you must insert your username and password. |
|
504 |
The command is not implemented. |
A syntax error; contact your supplier. |
|
510/511 |
"Bad email address. |
One of the addresses in your A, CC or CCI line does not exist. Check again and correct any possible spelling mistakes. |
|
512 |
A DNS error: the host server for the recipient's domain name cannot be found. |
Check all your recipients' addresses again: there will probably be an error in a domain name (like mail@domain.coom instead of mail@domain.com). |
|
513 |
"Address type is incorrect": another problem with writing addresses. In some cases, however, it is related to an authentication problem. |
Check the addresses of your recipients and correct any errors. If everything is OK and the error persists, it is caused by a configuration problem (simply, the server needs authentication). |
|
523 |
The total weight of your shipments exceeds the limits of the server recipient. |
Resend your message by dividing the list into smaller subsets. |
|
530 |
Normally an authentication problem. But sometimes the recipient's server is blacklisting yours, or there is an invalid email address. |
Configure your settings by providing a username and password authentication. If the error persists, check all your recipients' addresses and whether you have been blacklisted. |
|
541 |
The recipient's address has rejected your message: normally, this is an error caused by a spam filter. |
Your message has been detected and identified as spam. You must ask the recipient to whitelist you. |
|
550 |
It usually sets a non-existent email address on the remote side. |
Although it can also be returned by the recipient's firewall (or when the incoming server is down), the vast majority of 550 errors simply say that the recipient's email address does not exist. You need to contact the recipient in another way and get the correct address. |
|
551 |
"User not local or invalid address - Relay denied. If both your address and the recipient's address are not locally hosted by the server, a relay may be interrupted. |
This is a (not very clever) strategy to avoid spamming. You should contact your ISP and ask them to label you as a registered sender. |
|
552 |
"Requested mail actions aborted - Exceeded storage allocation": quite simply, the recipient's mailbox has exceeded its limits. |
Try sending a lighter message: this error usually occurs when you send emails with large attachments. |
|
553 |
"Requested action not taken - Mailbox name invalid. In other words, there is an incorrect email address in the recipient line. |
Check all addresses in the TO, CC and CCI fields. There should be a mistake or misspelling somewhere. |
|
554 |
This means that the operation has failed. This is a permanent error and the server will not try to send the message again. |
Usually the incoming server thinks your email is spam or an IP address has been blacklisted. Check carefully if you end up in some spam lists |