Common Email Bouncebacks

Below are some of the most common SMTP responses that Mailprotector observes. If you run into an issue that isn't specified here, you may want to start troubleshooting with a web search of the SMTP response. Mailprotector's Partner Success team is more than happy to assist if you are stuck.

The majority of the time, the Logs of the Console will be the source of information to review the bounceback error.


SMTP Response Problem Solution

EX: "Message not delivered. Reason: host[] said: 421 4.4.2 Message submission rate for this client has exceeded the configured limit (in reply to MAIL FROM command)"
The recipient's server is unavailable due to a connection issue.

This can be because Mailprotector is on a blacklist, a message size limit, internet issues, power issues, a connection time out, etc....
  • If you notice that the error message says Mailprotector's servers are on a blacklist, please contact Mailprotector. The user can resend the email if it is urgent, and it will go through another server.
  • If there is a message size limit issue, you'll have to reduce the email size or contact the recipient/sender.
  • If it is a power or internet issue, please wait until power or internet is restored. If you need assistance routing email to our Continuity product, XtraMail, feel free to reach out to Mailprotector.
  • If there is a connection timeout, try to send the email again in 15 minutes. If that fails, you'll need to figure out why the server is timing out (power, internet, parameter tables, the account doesn't exist, etc...).

EX: Message not delivered. Reason: host *Host*[*IP ADDRESS*] said: 450 4.2.0 <*SERVER*>: Recipient address rejected: Greylisted, see *Helpful Website*(in reply to RCPT TO command)
The email was undelivered because the user's mailbox was unavailable. The reason will be stated in the error.

Common responses are "user is over mailbox quota," "recipient address greylisted," "Domain not found," "Email was rejected due to spam policy," etc... 
  • If you have received a bounceback for any reason that is related to security policy, you will need to reach out to the recipient and ask them to resolve their blacklist/spam policy.
  • If a mailbox's quota has been reached, the mailbox size would need to be increased or the user needs to remove old emails.
  • If the domain cannot be found, the domain isn't routable on the exchange server, and the exchange server would need to be checked to find problems.

EX: host *IP ADDRESS*[*IP ADDRESS*] said: 452 4.3.1 Insufficient system resources (UsedDiskSpace[C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\data\Queue]) (in reply to end of DATA command)
Server resources have reached their limit. This is a common error that's seen when an exchange server has run out of memory, disk space, or can't process the number of emails it is receiving.  

  • In these cases, you'll want to go to your local exchange server and review the specified directory and resolve the issue. The most common problem is disk space, in which case, you'll need to add more storage on the server or clean out the older data.

EX: <*Email Address*>: host[*IP ADDRESS*] said:
530 5.7.57 SMTP; Client was not authenticated to send anonymous mail during
This is most commonly seen when there is a misconfigured inbound connector or the exchange server is restricting non-authenticated traffic
  • If you have a misconfigured inbound connector or mail route, please view the G-Suite Mail Routes article or O365 Inbound Connector article to check for any misconfiguration. 
  • If there is an exchange server issue, please contact the owner of the server and provide them the bounceback.


EX:[]:25, delay=0.39, delays=0.01/0/0.33/0.05, dsn=5.0.0, status=bounced (host[] said: 550 SPF Hard Fail: Domain does not designate as permitted sender. (in reply to MAIL FROM command)) 

This bounceback is commonly caused by a missing mailbox, firewall block, or antispam filter. The most common culprits here are "Invalid Mailprotector Sender," Century Link SPF Hard Fail," and "Invalid Mailprotector Recipient."
  • To resolve any Mailprotector related bounces, you'll need to add the user into the console under the "Users" tab.
  • Century Link issues have to be resolved with Century Link. They don't allow non-customers to interact with their filters
  • If you see a bounceback due to a policy of a different service, that service will need to be contracted to whitelist the domain/user.

EX: <*Email Address*>: host *IP ADDRESS*[*IP ADDRESS*] said: 552 5.3.4
Message size exceeds fixed maximum message size (in reply to MAIL FROM
This bounceback is only related to maximum message size, attachment size, or other size limitations 
  •  Mailprotector's Exchange services limit message size at 150MB, so you'll need to send a smaller email in this case
  • For any other issues, you'll need to contact the owner of the exchange server, send a smaller email, or increase the size limits on your own exchange server

EX: <*Email Address*>: host[] said:
553 5.3.0 flph839 DNSBL:RBL 521< >_is_blocked.For assistance
forward this error to *Abuse Address*(in reply to MAIL FROM
A 553 bounceback is commonly caused by an invalid destination or a block rule being in place. Issues include: DNS records not updated in Mailprotector, Mailprotector's server is on a block list, or the domain/user is on a blocklist 
  • If you notice that the error message says Mailprotector's servers are on a blacklist, please contact Mailprotector. The user can resend the email if it is urgent, and it will go through another server.
  • If there is an issue where the system says "mail is not allowed," check the "Inbound SMTP Host Address" in Mailprotector, remove the address, wait 5 minutes, and re-add it. This will update the DNS tables on our end.
  • If the user/domain is on a block list, contact the recipient/service and have them removed.


EX: <*Email Address*>: host[*IP ADDRESS*] said: 554 5.4.12 SMTP; Hop count exceeded - possible mail loop detected on

The 554 SMTP response could be any type of error listed before, but it indicates that the email will not be resent. Common situations are policy violations, hop count met, or other hard bounces. 
  • If it is a hop count issue, you'll need to look for any type of mail loop or email misconfiguration that can cause multiple attempts.
  • If it is a policy violation, you will need to contact the domain that rejected the email. 


Have more questions? Submit a request