SMTP Error Code 554
The transaction failed permanently. The server will not try to send the message again.
Providers
Barracuda · Comcast · Free · Infomaniak · Mimecast · Outlook · Proofpoint · Rambler · Trend Micro · Yahoo Inc · 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
- 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.
- 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 - https://community.mimecast.com/docs/DOC-1369#554 [#]
- Outlook↑
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
- 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 Inc↑
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. See https://postmaster.yahooinc.com/error-codes
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]
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
554 5.7.1 [CS01] Message rejected due to local policy. Please visit https://support.apple.com/en-us/HT204137
Apple Mail is blocking the email because of an email filter policy on their end. If this is happening for a specific recipient, ask them to save the From address for the message as an iCloud contact, specifically marking them as a "VIP" there. This VIP status should at least temporarily override the block. If you're following Apple's suggested best practices, you can also contact Apple's postmaster team with mail logs for delivery support.