// how to fix
Bounce "550 5.7.1": message rejected or blocked by policy
A 5.7.1 bounce means the receiving server refused your email on purpose. Learn to read bounce messages, find the real reason and fix it.
What it means
When an email cannot be delivered, your provider sends you back an error message, called a bounce or "non-delivery report". It contains a code and a short text from the receiving server. For example:
550 5.7.1 Service unavailable, Client host [203.0.113.10] blocked using zen.spamhaus.org
The code 5.7.1 means "refused for security or policy reasons". It is generic: the real reason is in the text after the code.
How to read a bounce
- The first digit:
4means temporary (the server will try again),5means permanent (the email is lost). - The middle part:
5.1.xis an address problem (the mailbox does not exist),5.2.xa mailbox problem (full),5.7.xa security or policy refusal. - The text: the most useful part. Look for the name of a blacklist, an IP address, a link to a help page, or words like SPF, DKIM, DMARC, policy, reputation.
- The server name: shows who refused the email (Gmail, Outlook, a company's filter).
Common reasons behind a 5.7.1
- Blacklisted IP: the text names a list such as Spamhaus, Barracuda or SpamCop.
- Authentication: SPF fails, or DMARC refuses the email.
- Reputation: "poor reputation", "blocked for spam", "banned sending IP".
- Company rules: the recipient's company only accepts certain senders, blocks attachments or blocks your country.
- Relaying denied: your own server refuses to send because you are not logged in. Check your SMTP username and password.
How to check
- Send a test email: on the home page, copy your unique test address, send it a normal email from the mailbox or tool you want to check, then open the report. It shows authentication, blacklists, reverse DNS and spam score.
- Look up the IP named in the bounce on
/blacklists.
How to fix it
- Copy the full bounce text and find the reason in it.
- If a blacklist is named, follow the blacklist guides: fix the cause, then request removal. Blacklist removal help is available in the paid Delivmail dashboard.
- If authentication is mentioned, fix SPF, DKIM and DMARC for the tool that sent the email.
- If reputation is mentioned, slow down, clean your list and contact the receiver's sender support page if the bounce gives a link.
- If it looks like a company rule, contact the recipient another way and ask their IT team to allow your domain.
Check that it is fixed
Send a new test email from the home page: the report should be clean. Then resend to the recipient who bounced. If the same bounce comes back, read the text again: the reason may have changed.
Check that it is fixed
DNS changes can take from a few minutes to a few hours. Then send a new test email or scan your domain again.
Related guides
- Your sending IP address is on a blacklistA blacklist is a public list of IP addresses known for sending spam. Find out if the IP is yours, fix the cause, then ask for removal.
- Your domain is on a blacklist (Spamhaus DBL, SURBL, URIBL)Domain blacklists list domain names seen in spam. They follow your domain wherever you send from. Find the cause, clean up, then request removal.
- Your emails land in Gmail's spam folderWhen Gmail sends your emails to spam, the cause is almost always authentication, reputation or content. Here is how to find which one and fix it.
- Your emails land in Outlook or Hotmail junkOutlook.com, Hotmail and Live send many new senders to Junk. Check your setup, then use Microsoft's free sender tools: SNDS, JMRP and the delist portal.
- Gmail bounce "550 5.7.26": unauthenticated emailGmail refused your email because it could not confirm it comes from your domain. SPF, DKIM or DMARC is missing or failing. Here is how to fix it.