SMTP Server Status and Error Codes
SMTP Server Status and Error Codes
There comes a time in the life of a Computer Consultant where, one day, he/she will have to
deal with email server problems. It is inevitable. Sometimes these problems will be with the
interfacing of the mail server with the ISP, in particular an inability to send mail. After checking
the usual suspects such as lack of connection (your broadband line is dead), faulty router,
firewall problems, DNS problems, or an incorrect SMTP server name (thanks to some clever
ISP changing its SMTP server name without informing anyone – it happens!!), you will likely
start delving a little deeper by checking if your email server reports any errors.
Depending on the actual problem it is encountering, your mail server may not be able to
provide detailed help on how to resolve the problem, and may instead only be able to provide
you with an SMTP Status Code in your server’s log (these codes are also known as SMTP
Error Codes or SMTP Reply Codes), or emails will be returned to the sender with error text.
A classic reply might be, for example, “SMTP error from remote mail server after end of data -
<host ip-address> : 550 Error: Message content rejected”, or “SMTP error from remote mail
server after RCPT TO <email-address>, 550 5.1.1 User unknown”. It is just for such cases
that we have produced this document (we use it too !! J ). What does 550 mean ? What
does 550 5.1.1 mean (or, shortened, what does 511 mean ?) ?
So, use this document as a quick reference to common SMTP status codes or SMTP error
codes for SMTP mail servers such as AA Mail Server, Alt-N MDaemon, ArGoSoft Mail Server,
Axigen Mail Server, Barracuda Spam Firewall, CMail, CMailServer, E-Mail Anywhere, FTGate,
GMS Mail, Internet Anywhere, Kerio MailServer (KMS), Lotus Notes, MailEnable, MailMax,
Mailtraq, Merak Mail Server, Microsoft Exchange (Exchange Server 2003 NDR, Non-Delivery
Report, error codes), Novell GroupWise, Qmail, PostCast Server, PostConf, PostFix,
PowerMTA, QK SMTP Server, Rockliffe MailSite, SendMail, SurgeMail, TFS Secure Message
Server, VisNetic Mail Server, WinMail, Zimbra, or any other SMTP / ESMTP standards
compliant e-mail MTA.
Note : the following list of SMTP reply codes can also be used to troubleshoot Eudora
or FoxMail email problems, Outlook error codes, Outlook Express error codes
(Windows 2000/XP), Windows Mail Error Codes (Vista), Thunderbird problems, or other
email program problems when those programs send and collect emails directly to and
from the Internet as opposed to through a corporate email system. The error codes
returned are the same.
Finally, there are no better tools for resolving complex SMTP error situations than the
WHOIS, Name Server Lookup, Trace Route, and PING tools of our own
The Ultimate Troubleshooter available on our AnswersThatWork.com website – that is
how we ourselves quickly solve complex SMTP error situations.
Page 1 of 18
101 – Cannot open SMTP Error 101 : Typically your SMTP server or email
connection program is unable to even start an SMTP session. Typical
replies will be “SMTP Error 101, Error opening connection”
or “SMTP Error 101, cannot open SMTP stream”.
(also called SMTP Error 1.0.1)
All SMTP Error 101 errors usually point to a configuration
problem, such as an incorrectly spelt SMTP server, or an
IP address that does not exist, or an SMTP port that does
not exist or which the recipient will not accept SMTP
connections on, or some other process is already using the
default SMTP port, port 25.
211 – System Status SMTP Error 211 : SMTP status 211 prefaces a message
message or System about the Mail Server status or a System Help reply to the
Help Reply user requesting help information. You might for example
issue a command to the mail server to display a list of
(also called SMTP Error 2.1.1) commands you can use and the server replies with an
SMTP Reply 211 followed by the list you requested.
214 – Help Reply message SMTP Error 214 : SMTP status 214 is usually in reply to
the “HELP” command. It displays information about the
(also called SMTP Error 2.1.4) server, usually a URL to the FAQ page of the SMTP
software running on the server. As a result this “error” is
normally called a reply, as in SMTP Reply 214.
220 – <Server Name> SMTP Status 220 : This is normally the first message you
service is running will get back from the server. It means the mail service is
running (ie. your mail server is running). It will normally
contain a welcome message and/or the title of the SMTP
software and, sometimes, the version number of the mail
(also called SMTP Error 2.2.0)
server software. SMTP Reply 220 is effectively a “Hi
There, I have just this second finished starting up – I
am ready to go and at your command” informational
message.
Page 2 of 18
221 – The domain service is SMTP Error 221 : The server is ending the mail session –
closing the it is closing the conversation with the ISP as it has no more
transmission channel mail to send in this sending session.
250 – Requested mail SMTP Status 250 : The mail server has successfully
action OK completed delivered the message! This is the best SMTP reply (250)
to receive - your message has been accepted and
transmitted OK ! J Yippee.
(also called SMTP Error 2.5.0)
250 is effectively a status code rather than an error code –
there is no such thing as an SMTP error 250.
251 – User not local will SMTP Status 251 : The email account is not local to the
forward ISP server but the ISP server will accept the email and will
forward it (the server will RELAY your message, this is the
most common action for ISP Mail servers – the recipient
(also called SMTP Error 2.5.1) will see your ISP in the mail header as one of the first hops
on the way to the recipient’s email system).
Page 3 of 18
252 – Cannot VRFY (verify) SMTP Status 252 : The user account appears to be valid
the user – the server but could not be verified, however the server will try do
will accept the deliver the message.
message and attempt
to deliver it There are sometimes circumstances where an email
address appears to be valid but cannot be verified as
definitely valid during the SMTP session between the
(also called SMTP Error 2.5.2) sending server (your server) and the next server to accept
your message. This can happen for example in very large
corporation where the first email receiving server might
only be an email exchanger server, a gateway server to
the eventual server which holds the user mailboxes and
which can verify if the intended recipient exists in that
organization. When this happens the gateway server will
reply with an SMTP Error 252 telling your sending server
that it cannot verify the user part of the email address, that
the domain part is OK, and that it will forward your email to
a server which can do the checking and eventually deliver
to the user mailbox if it exists.
354 – Start mail input end SMTP Error 354 : This is normally in response to the
with <CRLF>.<CRLF>, DATA command. The server has received the From and
or, as a less cryptic To information and is now asking for the “Message
description – “FROM Body”, the main part of the message which should be
and TO information ended by two blank lines separated by a dot (period).
received, now please
provide message Therefore, on receiving an SMTP Reply 354 the sending
body and mark its server should send the body of the message to the
end with receiving server and indicate the end of the message body
<CRLF>.<CRLF>” with <CRLF>.<CRLF> (note the full stop between the two
Carriage_Return-Line_Feed’s).
421 – <Server name> SMTP Error 421 : The Mail transfer service is unavailable
Service not available because of a transient event. SMTP reply 451 can be
– the sending email caused by many things but generally indicates that the mail
program should try server which returns this status code is currently
again later unavailable but may be available later.
Page 4 of 18
422 – The recipient’s SMTP Error 422 : Either the recipient’s mailbox is over its
mailbox is over its storage limit or the message delivery directory (folder) on
storage limit the recipient’s mail server is currently over a size limit
imposed by the Network Administrator (e.g. possibly as a
result of the mail server having been down for some time,
(also called SMTP Error 4.2.2) having been repaired, and currently in the process of
collecting thousands of queued up messages).
431 – The recipient’s mail SMTP Error 431 : The recipient’s mail server is
server is experiencing experiencing a Disk Full error condition, or an Out of
a Disk Full condition Memory (too many file handles) error condition (Microsoft
Exchange).
(also called SMTP Error 4.3.1)
432 – The recipient’s SMTP Error 432 : This is an SMTP status response
Exchange Server specific to Microsoft Exchange Server. It indicates that the
incoming mail queue recipient’s mail queue on their Exchange Server has been
has been stopped stopped (frozen), probably while the Network Administrator
troubleshoots some problem.
(also called SMTP Error 4.3.2)
441 – The recipient’s server SMTP Error 441 : This is an error emanating from your
is not responding server indicating that the recipient’s server is not
responding. Your server will automatically try again a
(also called SMTP Error 4.4.1) number of times – how many depends on how your server
has been configured.
442 – The connection was SMTP Error 442 : Your server started delivering the
dropped during message but the connection was broken during
transmission. transmission. This may be an unusual transient error –
however, if it keeps happening you should investigate
possible problems with your server’s network card, your
Internet routers, processes hogging the resources of your
(also called SMTP Error 4.4.2)
server, and anything else which could result in a network
connection being broken.
446 – The maximum hop SMTP Error 446 : The maximum hop count was
count was exceeded exceeded for your message. The most likely cause of this
for the message error status code is that your message is looping internally
on your server, internally between two of your
(also called SMTP Error 4.4.6) organisation’s servers, or, sometimes, looping between
your server and the recipient’s server.
447 – Your outgoing SMTP Error 447 : Your outgoing message timed out
message timed out. because of problems with the receiving server who
objected to your message. Typically there is a problem
with the message header (such as too many recipients, in
(also called SMTP Error 4.4.7) most cases, or a protocol timeout between the two
servers).
Page 5 of 18
449 – Routing error SMTP Error 449 : This is a Microsoft Exchange Server
specific error code. As per Microsoft’s documentation this
error code is returned when either of the following
(also called SMTP Error 4.4.9) conditions occurs : an SMTP connector is configured to
use DNS without a smart host and also uses a non-SMTP
address space (e.g. X.400), or A message was sent to a
recipient who was identified as a member of a routing
group that was deleted.
450 – Requested action not SMTP Error 450 : The server could not access the
taken – The mailbox mailbox to deliver the message. This could be caused by
was unavailable at the a process on the remote server tidying up the mailbox, or
remote end. A the remote mailbox could be corrupt, or the remote mailbox
secondary SMTP may be stored on another server which is currently offline,
error code may follow or the network connection went down while sending, or the
“450” to refine the remote mail server does not want to accept mail from your
reason for the failure server for some reason (IP address, blacklisting, etc..).
to transmit the
message, e.g. In general SMTP Error 450 is a transient error at the
“SMTP Error 450 remote end (the destination), or at one of the servers
en route to the remote end, and should induce your
mail server to retry after it’s preset retry interval.
Example of an SMTP Error 450 reply message : “450
(also called SMTP Error 4.5.0)
Please try again later”.
Page 6 of 18
451 – Requested action SMTP Error 451 : The action has been aborted by the
aborted – Local error ISP’s server. “Local” refers to the ISP’s server. This
in processing. error is usually due to overloading at the ISP from too
many messages or transient failures. Typically some
[hopefully] temporary event prevents the successful
(also called SMTP Error 4.5.1) sending of the message. The next attempt to send by your
server may prove successful.
Page 7 of 18
452 – Requested action not SMTP Error 452 : The ISP server’s disk system has run
taken – Insufficient out of storage space, so the action had to be cancelled.
storage. Unless you are with an ISP which is so slack that they
have not implemented Disk Full Alerts, this error usually
indicates that your ISP’s mail server is overloaded from too
(also called SMTP Error 4.5.2) many messages. This can happen even to the best ISPs
when, for example, there have been problems and none of
the ISP’s customers could send mail; as soon as the
problems are fixed there is almost always a situation where
thousands of users and organizations are trying to send
mail all at the same time, and those numbers can
occasionally result in the ISP’s mail servers’ hard disks
temporarily filling up, with SMTP Error 452 being the result.
The next attempt to send by your server may prove
successful.
471 – This is a local error SMTP Error 471 : This is always a local error with your
with the sending own mail server. SMTP Error 471 (or 4.7.1) is usually
server and is often tagged onto a primary SMTP error code, for example
followed with “Please “SMTP Error 450 4.7.1”, or “SMTP Error 451 4.7.1”, or
try again later” “SMTP Error 550 4.7.1”. In all the cases that we have
seen SMTP Error 471 is usually caused by anti-spam or
virus scanning software on your server (the sending
(also called SMTP Error 4.7.1) server) getting into problems through a bug in the software,
or because of a bad automatic update from the
antivirus/anti-spam manufacturer, because of lack of
memory on your server, or because of hard disk problems.
Page 8 of 18
500 – Syntax error SMTP Error 500 : The last command sent by your server
command not was not recognized as a valid SMTP or ESMTP command,
recognized. or is not formatted in the way the server expected. This
includes situations where the command is too long.
(also called SMTP Error 5.0.0) Note that commands that are recognized, but not
implemented, are handled by different status messages
(see 502 and 504).
501 – Syntax error in SMTP Error 501 : The command was correct and
parameters or recognised, but the parameters (the arguments, e.g. email
arguments (e.g. address) were not valid.
invalid email address)
For example, the following email address will definitely give
Can sometimes also an SMTP Error 501 with most mail servers,
be indicative of happy\_larry@hotmail.com, as “\” is not allowed in email
communication addresses, which makes this email address invalid.
problems
In the vast majority of cases SMTP Error 501 is caused
by invalid email addresses. For example, a typical return
error message might be : “<remote-server-ip-address>
(also called SMTP Error 5.0.1)
does not like recipient. Remote host said: 501 Invalid
Address”.
502 – Command not SMTP Error 502 : The command or function issued by
implemented. your mail server is valid but has not been activated
(typically, it is not supported on this particular server).
(also called SMTP Error 5.0.2)
Page 9 of 18
503 – Bad sequence of SMTP Error 503 : In the original standards SMTP Status
commands. 503 indicates that the commands have been sent in the
wrong order, for example your mail server has sent the
or “Hello” command before sending the “Mail” command.
This can often be caused by a drop in network connection
This mail server just as your server was sending a command, resulting in
requires the ISP’s server not receiving it and consequently not
authentication understanding the command that followed it.
------------------------------
504 – Command parameter SMTP Error 504 : The command and parameter are both
not implemented. valid, but the parameter is not implemented on the ISP
server, or an additional parameter or action is missing.
(also called SMTP Error 5.0.4) For example, an often encountered SMTP Error 504 is :
“504 Need to authenticate first”.
510 – Bad Email Address SMTP Error 510 : Bad email address. This status code
is generated by the sender’s local mail server.
511 – Bad Email Address SMTP Error 511 : Bad email address. This error is
similar to error 510 and as with error 510, this status code
is generated by the sender’s local mail server.
(also called SMTP Error 5.1.1)
If the email was addressed internally, then it means that
the addressee, as written in the email’s TO, CC, or BCC
fields, does not exist in your organization’s email system.
Page 10 of 18
512 – The host server for SMTP Error 512 : This SMTP reply code is received
the recipient’s when one of the servers on the way to the destination is
domain name cannot unable to resolve the domain name of a recipient email
be found (DNS error) address. Said differently : one of the servers on the way
to the destination, including your server or your ISP, has a
DNS problem or, possibly correctly, does not like one of
the email addresses in the message’s TO, CC, and BCC
(also called SMTP Error 5.1.2)
fields.
--------------
Page 11 of 18
513 – Address type is SMTP Error 513 : This status code (from the sender’s
incorrect (most mail mail server) is usually symptomatic, in an Exchange +
servers) Outlook environment, of the user’s Outlook Contacts
having been imported from another system or PST and
or where some of the addresses are not defined correctly.
Or, in any environment it is simply that the end-user simply
Relaying denied or did enter the email address completely wrongly, such as
Authentication copying it from a website and not replacing “at” with “@”,
required (a small e.g. : John.DoeatUCLA.edu (which should have been
percentage of mail John.Doe@UCLA.edu), or John.Doe@UCLA.edu” (“,
servers) quotes, is not allowed in email addresses and is often
included in error as a result of copying and pasting an
email from somewhere).
(also called SMTP Error 5.1.3)
The user should check all the recipient addresses in the
email, including those that were inserted from Contacts.
--------------
523 – The Recipient’s SMTP Status 523 : This error will be received when the
mailbox cannot total size of the message you have sent (ie: message + all
receive messages of its attachments) exceeds the size limits on the
this big Recipient’s server. Many companies implement the good
practice of configuring their servers with limits on the size
of emails they can receive to prevent their systems running
out of space as a result of a spam attack where the spam
(also called SMTP Error 5.2.3)
emails contain large attachments, or as a result of valid but
not very technically savvy senders sending enormous
scans (through not knowing that scanning at 1200dpi
rather than the usually perfectly usable and acceptable
300dpi, will create humongous attachments).
Check the size of the email you sent, and, specifically, the
size of the attachments you included, and consider splitting
your email into smaller emails. If that does not work, check
with the Recipient the maximum size of email they can
receive, and if that is still prohibitive then consider FTP
arrangements between you and the recipient.
550 – Requested actions SMTP Error 550 : This response can be caused by quite
not taken as the a few situations.
mailbox is
unavailable. --------------
--------------
Page 13 of 18
--------------
--------------
--------------
--------------
--------------
--------------
Page 14 of 18
--------------
--------------
551 – User not local or SMTP Error 551 : If neither the sending mail address nor
invalid address – the recipient’s address are locally hosted by the server,
Relay denied. then the ISP’s servers may refuse to relay the message
on.
(also called SMTP Error 5.5.1) Some ISPs implement this restriction to thwart spammers.
In our view, here at AnswersThatWork, this is a lazy and
incompetent method of fighting spam as most of the time it
does nothing but inconvenience no-one other than the
ISP’s vast majority of considerate and law abiding users.
In our experience this usually goes hand in hand with
barely competent technical support. At the time of writing,
14-Sep-2008, a typical culprit for this is BT, British
Telecom, in the UK. The way in which it manifests itself is
as follows : you have a domain that is hosted by
CrystalTech.com but your ISP is DodgyISP.com and
you try to send emails from your domain to
WhatANiceBunchOfPeopleYouAre@yahoo.usa.
Neither your domain nor Yahoo.usa are hosted by
DodgyISP.com, as a result your email is not accepted by
DodgyISP’s mail servers and your mail server is returned
an SMTP Error 551. To correct the problem you have to
call DodgyISP.com and ask them to enter your domain
name as an allowed sender.
Page 15 of 18
552 – Requested mail SMTP Error 552 : The recipient’s mailbox has reached its
actions aborted – maximum allowed size (this is often accompanied by a
Exceeded storage return mail from your ISP or mail server informing the
allocation. sender of the email of just that situation).
553 – Requested action not SMTP Error 553 : There is an invalid email address in the
taken – Mailbox name “To“, “CC”, or “BCC” field of the email message.
invalid.
Here is a typical SMTP Error 553 response :
(also called SMTP Error 5.5.3) ”Hi. This is the QMAIL-send program at <ip-address>. I'm
afraid I wasn't able to deliver your message to the following
addresses. This is a permanent error; I've given up. Sorry
it didn't work out. <Email-address-you’re-sending-to> :
<remote-mail-server-ip> does not like recipient. Remote
host said: 553 5.3.0 <Email-address-you’re-sending-to>.
Addressee unknown. Giving up.”.
--------------
554 – Transaction failed. SMTP Error 554 : There was a permanent error trying to
complete the mail transaction which will not be resolved by
Nowadays SMTP resending the message in its current form. Some change
status 554 is in most to the message and/or destination must be made for
cases returned when successful delivery.
the recipient server
believes your email is For instance, Yahoo often returns the following if the
spam or your IP recipient email address does not exist on the Yahoo
address or ISP server systems : “554 delivery error: This user doesn't have a
has been blacklisted Yahoo.com account”. Another typical Yahoo SMTP Error
on one or more 554 reply is : “554 delivery error: Sorry your message to
Page 16 of 18
Note that SMTP Error 554 can also often be buried in the
middle of SMTP Error 550 errors. Here is an example of a
recipient mail server returning an SMTP Error 554 because
its Barracuda anti-spam firewall appliance rejected the
email (the cause, as shown below, is Barracuda
Reputation which means your IP address or your ISP’s
server is blacklisted on Barracuda’s RBL) :
Page 17 of 18
The following addresses had “The following addresses had permanent delivery
permanent delivery errors errors” / “The following address had permanent
delivery errors” : Either of these sentences are usually
followed by one or more email address(es).
oooooooOOOOOOOooooooo
Page 18 of 18