Permanent failure — do not retry
SMTP 541
message rejected by the recipient's filter
SMTP 541 is not defined in RFC 5321. Some spam-filtering appliances and hosted filters use it to say the recipient's system refused the message, usually as spam or because of a sender rule. Treat it as a permanent policy rejection and read the text that follows for the reason.
How it appears
541 The recipient address rejected your message
541 5.4.1 Recipient address rejected: Access denied
What causes it
- A spam filter in front of the recipient's mail server scored the message as spam.
- The recipient organisation has blocked your sending domain or IP.
- Your sending IP or domain is on a blocklist the filter checks.
- Authentication (SPF, DKIM or DMARC) failed.
How to fix it
In order — try the first one first.
- Read the text after the code. Filter vendors normally name the rule or blocklist that matched.
- Check SPF, DKIM and DMARC alignment on your sending domain.
- Check your sending IP and domain against the major blocklists.
- If one organisation blocks you, ask them to allowlist you or reach them another way.
Common questions
- What does SMTP 541 mean?
- SMTP 541 is not defined in RFC 5321. Some spam-filtering appliances and hosted filters use it to say the recipient's system refused the message, usually as spam or because of a sender rule. Treat it as a permanent policy rejection and read the text that follows for the reason.
- Should I retry a 541 error?
- No. 541 is a permanent failure, so the message will never be delivered no matter how many times you try. Remove the address — repeated sends to permanent failures are one of the main signals mailbox providers use to throttle a sender.
- How do I fix SMTP 541?
- Read the text after the code. Filter vendors normally name the rule or blocklist that matched.
Last reviewed 2026-09-11