If someone tries to email you and their message bounces back with this error, our mail server refused the message because of a rule that blocks that sender. This article explains what the error means, why adding the sender to your whitelist won't fix it, and what to send our support team so we can resolve it.
What the bounce message looks like
The sender will receive a bounce (an "Undelivered Mail Returned to Sender" email) with a line similar to this:
<you@yourdomain.com>: host mail.yourdomain.com[203.0.113.10] said: 554 5.7.1 <sender@example.com>: Sender address rejected: Access denied (in reply to RCPT TO command)
(These addresses are examples. Your bounce will show the real sender, recipient and server.)
What each part means
| Part of the message | What it means |
|---|---|
host mail.yourdomain.com[...] said: | The rejection came from your mail server (ours), not the sender's. |
554 5.7.1 | A permanent rejection, based on a security or policy rule. The sender's server won't retry. |
<sender@example.com>: Sender address rejected | The sender's address or domain is what was blocked. |
Access denied | A rule on the server specifically doesn't allow that sender. |
in reply to RCPT TO command | The message was refused at the very start of delivery, before the email's content was even sent. |
In plain terms: the sender's email account is fine. Our mail server turned the message away at the door because of a sender rule.
What it is not: this error isn't caused by spam content, attachments, a full mailbox, or the sender's SPF or DKIM settings. Those problems produce different error messages.
Why adding the sender to my whitelist doesn't fix it
You may have already added the sender (for example, sender@example.com or *@example.com) to your spam filter whitelist in your control panel, and the emails still bounce. That's expected, and here's why.
Incoming email passes through several checks, in this order:
- Connection and sender rules (server level). The server first checks who the message is from. If a server-level rule blocks the sender, the message is rejected here, with "Sender address rejected: Access denied."
- Spam filtering (SpamAssassin). Only messages that pass step 1 are scanned for spam. Your whitelist and blacklist work at this step. They adjust a message's spam score and decide whether it goes to your inbox or spam folder.
- Delivery to your mailbox.
Because this error happens at step 1, the message never reaches the spam filter, so your whitelist never gets a chance to apply. Only our hosting team can change a server-level sender rule.
What to do
1. Don't change your settings. Your whitelist entries don't hurt anything, but they won't fix this error, so there's no need to keep adjusting them.
2. Send our support team the bounce message.
The best thing to send is the full bounce message, in its original form. Please ask the sender to send it in one of these ways, in order of preference:
As an .EML file (the original message file):
- Gmail: open the bounce, click ⋮ (More) → Download message.
- Outlook (desktop): open the bounce, then File → Save As, and save it as Outlook Message Format, or drag the email onto the desktop.
- Outlook on the web / new Outlook: open the bounce, click ⋯ (More actions) → Save as.
- Apple Mail: select the bounce, then File → Save As, and choose Raw Message Source.
Forwarded as an attachment, not as a regular forward. In most email apps, this is under More → Forward as attachment. A regular forward can change or remove the technical details we need.
- The full text of the bounce, copied and pasted into an email, including everything below "This is the mail system…" and the technical details at the bottom.
Please don't send a screenshot. Our team needs the exact text to search the server logs.
If the sender can't send the bounce message in any of these ways, please send us at least:
- The sender's email address (for example, sender@example.com).
- Your email address, the one the message was sent to.
- The date and time of the bounce, including the time zone if possible.
3. We'll escalate it to our hosting team, who will check the server-level sender rules and remove the block, or add an exception for your domain.
4. Ask the sender to resend once we confirm it's fixed. Rejected messages aren't stored or delivered later, so the original email won't arrive on its own.
Frequently asked questions
Is the problem on the sender's side?
No. This error comes from the receiving server, which is ours. The sender doesn't need to change anything.
Why would a sender be blocked in the first place?
Mail servers use sender rules to block sources that are often linked to spam or fraud. Occasionally, a rule can also catch legitimate senders. When that happens, our hosting team can review the rule and make an exception.
Will other people be able to email me?
Yes. This only affects the specific sender, or sending domain, that the rule matches. Everyone else can still reach you normally.
I'm getting a different 554 error. Is this article for me?
Only if the message says "Sender address rejected: Access denied." Other 554 errors, such as "Recipient address rejected," "Client host rejected," or messages mentioning SPF, DMARC or blocklists, have different causes. Send us the full bounce message, and we'll tell you what it means.
How long does it take to fix?
Once we have the original bounce message (ideally as an .EML file), or at least the sender, recipient and time of the bounce, we escalate the request to our hosting team right away. We'll update you as soon as the block is removed, so the sender can try again.
If you have any questions, please contact our support team.
Comments
0 comments
Please sign in to leave a comment.