|
SMTP protocol specific response code design provides some useful (numeric) codes used for reporting mail (delivery status) system errors (Protocol–a method of sending and receiving data). SMTP is a simple ASCII protocol. SMTP is a protocol governing electronic mail transmission and reception (sending and receiving emails between mail servers). Operational Sequent
of: How two MTAs (Message Transfer Agent) communicate with each other using a single TCP connection.
*If not--There are no standard mechanism for reporting mail system errors except for the limited codes consisting of three numbers offered by SMTP with specific text descriptions sent in mail messages. Because of its limitations, the majority of each code delivery report may indicate several other error conditions as well as different mail server using their own text description. The first number generally tells whether the server accepted the command and if it could manage it. 2 The server has completed the task successfully. 3 The server has
understood the request, 4 The server has
encountered a temporary failure. 5 The server has encountered an error. The second number gives more
information. 0 A syntax error has
occurred. The third number shows more graduations of the mail transfer status to return a more detailed report as detailed in the ESMTP server response codes defined in RFC 821 and later extensions. Example of an older SMTP response text
description for the first number. 4.x.x Persistent Transient Failure 5.x.x Permanent Failure
(The
server has encountered an
error).
Example of
a new ESMTP response 501 5.5.4 Syntax error 501 Syntax error represent the enhanced SMTP (ESMTP) status code 5.5.4 represent the old SMTP status code
|
|
|
|
New enhanced ESMTP Status/Error
Codes rfc 821 for the basic specification of SMTP
200 Nonstandard success
response 211 System status or system help reply 214 Help message 220 <domain> Service
ready 221 <domain> Service
closing transmission channel 250 Requested mail action taken,
completed
251 User not local, will forward
to <forward-path> 252 Recipient cannot be
verified 354 Start mail input and end with
<CRLF> <CRLF> 421 <domain>
Service
not available, closing transmission channel This may be a reply to any
command if the service knows it must shut down. 450 Requested mail action not
taken: mailbox unavailable 451 Requested action aborted:
local error in processing 452 Requested action not taken:
insufficient system storage 452 too
many messages' error
|
|
|
|
500
Syntax error, command unrecognized 501
Syntax error in parameters or
arguments 502 Command not
implemented 503 Server encountered bad
sequence of commands 504 Command
parameter not implemented 521 <domain does
not accept mail or closing transmission channel You must be
pop-authenticated before you can use this SMTP server and you must use
your mail address for the Sender/From field. 530 Access denied
(???a Sendmailism) 550 Requested action not taken,
mailbox unavailable 550 Relaying prohibited or Not
local host… not a gateway 550
This address is not allowed or Requested action not taken: mailbox
unavailable 551 User not local, please try
<forward-path> or
Invalid
Address: Relay request denied 552 Requested mail action
aborted: exceeded storage allocation ISP mail server
indicates, probable overloading from too many
messages. 553 Denied. Requested action not
taken: mailbox name not allowed or bad command
format 554 Transaction failed or
Permanent Failure 557 Too many duplicate messages:
Resource temporarily unavailable Indicates (probable) that
there is some kind of anti-spam system on the mail
server. 572 Relay not authorized or Not
local host… not a gateway |
|
|
|
Request For Comment
(RFC) rfc 821 for the basic specification of SMTP rfc1123 for important
additional information. For
information about enhanced status codes. RFC index for further
mail-related RFCs rfc2821 for the basic specification of
SMTP RFC
821 Simple
Mail Transfer Protocol (SMTP) RFC
822 Standard for the format of ARPA Internet text
messages RFC
1123 Internet Host Requirements RFC 1854 SMTP
Service Extension for Command Pipelining RFC
1891 SMTP
Service Extension for Delivery Status Notifications RFC
1892 Multipart/Report RFC
1893 Mail System Status Codes (about enhanced status
codes) RFC
1894 Delivery Status Notifications RFC
1939 Post Office Protocol – Version 3 RFC 2045 MIME Part One: Format of Internet Message Bodies RFC 1985 SMTP Service Extension for Remote Message Queue Starting www.urz.uni-heidelberg.de/Netzdienste/Mail/rfc/rfc1985.txt RFC 2034 SMTP Service Extension for Returning Enhanced Error Codes www.urz.uni-heidelberg.de/Netzdienste/Mail/rfc/rfc2034.txt RFC
2045 MIME RFC 2046 MIME
Part Two: Media Types RFC 2060 IMAP Version 4 rev 1 RFC
2476 Message
Submission RFC
2505 Anti
Spam Recommendations RFC
2554 SMTP Service Extension for
Authentication RFC 2635 Guidelines for Mass Unsolicited Mailings and Postings (Spam) www.urz.uni-heidelberg.de/Netzdienste/Mail/rfc/rfc2635.txt
References RFC: Request For Comments, the 'laws' of the Internet. http://www.faqs.org/rfcs/ RFC791 -- http://www.faqs.org/rfcs/rfc791.html RFC1122 -- http://www.faqs.org/rfcs/rfc1122.html RFC1918 -- http://www.faqs.org/rfcs/rfc1918.html Technical tutorial |