The below is a quick reference to common Mail Delivery Errors, often known as SMTP status or SMTP error codes for SMTP mail servers such as AA Mail Server, GMS Mail, Lotus Notes, Microsoft Exchange, PowerMTA, SendMail, WinMail, Zimbra or any other SMTP/ESMTP standards compliant e-mail MTA.
These codes are not a definitive golden rule but more of a guideline as each mail server and mail transfer agent (MTA) have their own classification that they report back to our Send system.
Important note: Sometimes it can seem as if the errors delivered do not correspond to the actual error occurring. For example, the report delivers an error "bounced: invalid email" when you have verified the email address is correct. In these situations it is important to note that Concep Send pulls through the errors directly from the email client or inbox vendor. Sometimes they will deliver an error that is not a perfect description of the error in order to simply convey the message that the email has not been delivered.
Example SMTP Mail Delivery Errors
|SMTP Status Code
|Alternative Code Name
|Cannot open connection
|Cannot verify the user - the server will accept the message and attempt to deliver it
|Service not available - the sending email program should try again later
The SMTP service/server you use has a limit on the number of concurrent SMTP streams your server can use
|The recipient's mailbox is over it's storage limit
The size of the message exceeds the recipient's size limits for incoming emails
|The recipient's mail server is experiencing Disk Full condition
|The recipient's Exchange Server incoming mail queue has been stopped
|The recipient's server is not responding
|The connection was dropped during transmission
|The maximum hop count was exceeded for the message
|Your outgoing message timed out
|Requested action not taken - The mailbox was unavailable at the remote end
|Requested action aborted - Local error in processing
Requested action delayed - Local problem or <IP address> has recently sent spam
|Requested action not taken - Insufficient storage
|Code Page unavailable on the recipient server
|This is a local error with the sending server and is often followed with 'Please try again later'
|Syntax error command not recognized
|Syntax error in parameters or arguments (e.g. email address)
|Command not implemented
|Bad sequence of commands
This mail server requires authentication
|Command parameter not implemented
|Bad email address
|Bad email address
|The host server for the recipient's domain name cannot be found (DNS error)
|Address type is incorrect (most mail servers)
Authentication required (a small percentage of mail servers)
|The recipient's mailbox cannot receive messages this big
|Authentication is required
Your server has been blocklisted by the recipient's server
The recipient's mailbox does not exist
|Recipient address rejected - access denied
|Requested actions not taken as the mailbox is unavailable
|User not local or invalid address - relay denied
|Requested mail actions aborted - exceeded storage allocation
Size of the incoming message exceeds the incoming size limit
|Requested actions not taken - mailbox name invalid
You are attempting to send emails through a specific ISP's SMTP server without authentication and without being connected to the Internet through that ISP's service
You are sending from an Exchange Server configured to send via DNS and you do not have a public reverse DNS record pointing back to your exchange server
|Transaction failed - most cases where the recipient server believes your email is spam or your IP address or ISP server has been blocklisted on one or more Internet blocklists
Yahoo - email address does not exist or is disabled
IBM Lotus Domino - either a Domino bug or a Disk Full error
|Your server is not permitted
If you wish for further details please take a look at this SMTP codes document.
That response occurs when the email server sending us the bounceback message does not provide a reason - meaning all it reports back to our servers is that the email is not deliverable, and will never be. This could be due to a spam filter or other corporate email filter setting.
In these cases, we recommend switching the contact to plain text format and resending the campaign to see if it can be delivered. Plain text, while not as visually appealing, is the simplest form of email and is almost always not a problem with spam and corporate email filters.