SMTP Error Code 554
The transaction failed permanently. The server will not try to send the message again.
Providers
Barracuda · Comcast · Exchange Online Protection · Free · GoDaddy · Infomaniak · Mimecast · Outlook.com · Proofpoint · Rackspace · Rambler · Trend Micro · Yahoo · Yandex · ZeroSpam · Zoho · iCloud
- Barracuda↑
554 rejected due to spam URL in content
A URL in your message content may be on a public or private block list. Some recipients may also filter URLs based on their geo-location. Check all of the domains, subdomains, and full URLs in your content against as many public lists as you can to narrow-down the culprit.
554 rejecting banned content
Check your content, phrasing, and links for any potentially suspicious characteristics. Even something as simple as an unfortunate typo or a link to an exploited webpage can block a message from delivering.
- Comcast↑
host xx.comcast.net [x.xx.xx.xx] SMTP error from remote mail server after initial connection: 554 xx.comcast.net comcast x.xx.xx.xx Comcast requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mail server does not fill that requirement. For more information, refer to: http://postmaster.comcast.net/smtp-error-codes.php#554
554 xx.comcast.net comcast x.xx.xx.xx Comcast block for spam. Please see http://postmaster.comcast.net/smtp-error-codes.php#BL000000
- Exchange Online Protection↑
554 5.4.14 Hop count exceeded - possible mail loop ATTR34
That means the message is being passed around like a hot potato between servers. Possible reasons include: A misconfigured hybrid environment; internal M365 wonkiness; they are forwarding it somewhere, and it's being sent back to 365 multiple times; a mailbox is being migrated between clusters, or the mailbox was corrupted/misconfigured. There is nothing you as the sender can do; if it's an important email, try contacting the recipient via alternate means.
- Free↑
554 5.2.2 <example@free.fr>: Recipient address rejected: Quota exceeded (mailbox for user is full)
The recepients email mailbox is full and currently unable to accept messages.
- GoDaddy↑
554 $(_ipsrc) has been temporarily blocked for attempting to mail too many invalid recipients. IB112
The connecting IP has attempted to send to a number of invalid recipients, and has been blocked for at least an hour. Please check to ensure you aren't sending to lists containing invalid recipients. If you are, please remove those addresses from your list and try again later.
554 $(_ipsrc) has been blocked for the day, for attempting to mail too many invalid recipients. IB113
The connecting IP has attempted to send to a number of invalid recipients, over the course of multiple hours and has been blocked for at least a day. Please check to ensure you aren't sending to lists containing invalid recipients. If you are, please remove those addresses from your list and try again later.
554 $(_ipsrc) has been temporarily blocked for attempting to send too many messages containing content judged to be spam by the internet community. IB110
The connecting IP has attempted to send too many messages considered spam, and has been blocked for at least an hour. Please check to ensure you aren't sending messages considered as spam, and try again later.
554 $(_ipsrc) has been blocked for the day, for attempting to send too many messages containing content judged to be spam by the internet community. IB111
The connecting IP has attempted to send too many messages considered spam over the course of multiple hours, and has been blocked for at least a day. Please check to ensure you aren't sending messages considered as spam, and try again later.
554 RBL Reject -Please submit an unblock request
The connecting IP address exists on an internal block list. Please check to ensure you aren't sending messages considered as spam, to valid recipients and please submit an unblock request.
554 IB103. Connection refused. $(_ipsrc) has a poor reputation on Cloudmark Sender Intelligence (CSI).
The connecting IP address exists on Cloudmark Sender Intelligence (CSI) block list. Please check to ensure you aren't sending messages considered as spam, to valid recipients and please submit an unblock request.
554 IB104. Connection refused. $(_ipsrc) is listed on the Spamhaus Block List (SBL). Please visit http://www.spamhaus.org/sbl for more information or to request a delisting.
The connecting IP address exists on Spamhaus' (SBL) block list. Please check to ensure you aren't sending messages considered as spam, to valid recipients and please submit an unblock request.
554 IB105. Connection refused. $(_ipsrc) is listed on the Exploits Block List (XBL). Please visit http://www.spamhaus.org/xblfor more information.
The connecting IP address exists on Spamhaus' (XBL) block list. Please check to ensure you aren't sending messages considered as spam, to valid recipients and please submit an unblock request.
554 IB106. Connection refused. $(_ipsrc) is listed on the Spamhaus Block List (PBL). Please visit http://www.spamhaus.org/pbl for more information or to request a delisting.
The connecting IP address exists on Spamhaus' (PBL) block list. Please check to ensure you aren't sending messages considered as spam, to valid recipients and please submit an unblock request.
- Infomaniak↑
554 5.7.1 Relay access denied
You are sending an email to a server that has not been configured to receive email for that domain.
- Mimecast↑
554 Email rejected due to security policies (e.g., MCSpamSignature.x.x).
A signature could be a virus or a spam score over the maximum threshold. The spam score isn't available in the Administration Console. If you aren't a Mimecast customer but have emails rejected with this error code, contact the recipient to adjust their configuration and permit your address. If unsuccessful, your IT department can- submit a request to review these email rejections via our Sender Feedback form linked below.
554 Mail loop detected.
The message has too many Received Headers as it has been forwarded across multiple hops. Once 25 hops have been reached; the email is rejected.
554 Host network not allowed.
The message has triggered a Geographical Restriction policy set by the administrator.
- Outlook.com↑
554 5.2.122 The recipient has exceeded their limit for the number of messages they can receive per hour. For more information go to http://go.microsoft.com/fwlink/?LinkId=526653. (#) [outlook.com]
The Microsoft 365 or Office 365 recipient has exceeded the number of messages they can receive per hour from all senders.
554 5.2.121 The sender has exceeded the limit for the number of messages they can send to this recipient per hour. For more information go to http://go.microsoft.com/fwlink/?LinkId=526653. [#.prod.outlook.com #]
The sender has exceeded the maximum number of messages they're allowed to send per hour to a specific recipient in Exchange Online.
- Proofpoint↑
554 5.7.1 <email@example>: Relay access denied
- Rackspace↑
554 5.7.1 user@example.com: Sender address rejected: Blocked by this recipient (GE)
You have been manually added to the recipient's block list.
554 5.7.1 ACL dns_rbl; Client host {IP} blocked using Senderscore. Please visit Senderscore for more information on why this message could not be delivered (G31)
Your IP has bad reputation with Validity's SenderScore. Use the link below to get more information.
554 5.7.1 ACL dns_rbl; Client host {IP} blocked using Spamhaus XBL. Please visit Spamhaus for more information on why this message could not be delivered (G31)
Your IP is listed in the Spamhaus XBL. Use the link below to get more information.
- Rambler↑
554 5.7.1 Spam message rejected; If this is not spam contact abuse
After reviewing your messages to ensure they follow sender best practices, you can contact Rambler's support team for review.
- Trend Micro↑
554 5.7.1 <example@example.com>: Recipient address rejected: BLOCK-SEND-ER.
There's certain criteria in the message itself that this recipient is blocking, which could include a block on the sender's domain/IP by an admin of the recipient's domain.
- 554 5.7.1 <example@example.com>: Recipient address rejected: Invalid-Recipient.
554 5.7.1 <example@example.com>: Recipient address rejected: NO-DOMAIN.
The recipient is permanently undeliverable unless manual changes are made on the recipient's end to allow the sender's domain and/or sending IP. This doesn't necessarily mean the message was purposefully blocked, just that routing of the message through Trend Micro is not yet allowed.
- 554 5.7.1 <example@example.com>: Recipient address rejected: BLOCK-RCPT.
- Yahoo↑
554 delivery error: dd This user doesn't have a example.com account (example@example.com) [-9] - example.yahoo.com
554 delivery error: dd Sorry, your message to example@example.com cannot be delivered. This mailbox is disabled (554.30). - example.yahoo.com
Yahoo email addresses are used for lots of different services -- not just for receiving email. This bounce means that while this recipient is not using Yahoo's email service, the address itself exists for login purposes for other services. The best option is suppress this email address from your lists, as it hasn't used its inbox in a very long time (if ever).
554 delivery error: dd Requested mail action aborted - example.yahoo.com
554 5.7.9 Message not accepted for policy reasons.
554 Message not allowed - [PH01] Email not accepted for policy reasons. Please visit https://postmaster.yahooinc.com/error-codes
This rejection occurs out of suspicion that the message or sender is phishing. Review the URLs and images in your content. Once investigated and you can verify your messages are safe, you can request a review from Verizon's support team.
554 Message not allowed - Headers are not RFC compliant [291]
Your message headers are not compliant. Double check your sending settings and parameters or ask your email provider for assistance.
554 Message not allowed - [299]
554 delivery error: dd example@example.com is no longer valid. [-20] - example.yahoo.com
- Yandex↑
554 5.7.1 [1] Message rejected under suspicion of SPAM; https://ya.cc/1IrBc ##
While a message being rejected as spam isn't good news for anyone, this bounce response is especially helpful for those who don't typically send to Russian domains. In those cases, you'll see this bounce when online forms are being exploited by spam bots repeatedly victimizing Yandex recipients. Please check all of your online forms to be sure that they are properly protected.
- ZeroSpam↑
- 554 5.7.1 <email@example.com>: Recipient address rejected: Not in recipient list
- Zoho↑
554 5.2.3 MailPolicy violation Error delivering to mailboxes,mx.zoho.com
Reasons for this response vary significantly, so the best place to start is the Zoho Community forum.
554 5.7.1 Email cannot be delivered. Reason: Email flagged as Spam.
- iCloud↑
554 5.7.1 <example@icloud.com>: Relay access denied
The recipient domain has not been correctly setup in iCloud+
554 5.7.1 [CS01] Message rejected due to local policy.
Apple Mail is blocking the email because of an email filter policy on their end. Usually due to to the sender domain / IP reputation. If you're following Apple's suggested best practices, you can also contact Apple's postmaster team with mail logs for delivery support.
554 5.7.1 [HM08] Message rejected due to local policy.
Apple Mail is blocking the email because of an email filter policy on their end. Usually due to to the sender domain / IP reputation. If you're following Apple's suggested best practices, you can also contact Apple's postmaster team with mail logs for delivery support.
554 5.7.1 [BS01] Message rejected due to local policy.
Apple Mail is blocking the email because of an email filter policy on their end. Please make sure that affected customers have valid SPF, DKIM and DMARC to remediate them. If you're following Apple's suggested best practices, you can also contact Apple's postmaster team with mail logs for delivery support.