Skip to content
DMARC Pulse

Email errors

550 5.7.0 Local Policy Violation: meaning and how to fix it

550 5.7.0 local policy violation means a mail server refused your email under its own rule. See which rule it might be and what you can fix.

What this means

550 5.7.0 local policy violation means a mail server permanently refused your message because it broke a rule set by whoever runs that server. Those words do not say which rule.

  • 550 is a permanent refusal.
  • 5.7.0 is the generic security and policy status. RFC 3463 says it applies when no other code fits, or when "security policies in force" prevent a fuller explanation.
  • Local Policy Violation is text the server chose. None of the RFCs or provider documents cited here define this wording. RFC 5321 says reply text can vary by receiver.

The same code covers unrelated cases. Google's Gmail table lists 550 5.7.0 for SMTP relay refusals such as Email sending denied. and 552 5.7.0 for content that "presents a potential security issue."

Why it happens

Only the refusing server's operator knows the exact rule. Providers document these causes, often under neighboring codes:

  • A restriction at the recipient. Microsoft's first examples: you lack permission to send to that recipient or group.
  • A rule on your side. Microsoft also names settings in your own organization and servers along the path that you may not send through.
  • The sending IP. Proofpoint blocks IPs it receives spam or viruses from.
  • DNS and authentication. Microsoft mentions an incomplete SPF record. Gmail requires SPF or DKIM, plus valid forward and reverse DNS (PTR records).
  • The content. Gmail's 552 5.7.0 is one example.

Authentication failures have their own codes: RFC 7372 registers 5.7.23 for SPF and 5.7.25 for reverse DNS. A bare 5.7.0 neither confirms nor rules them out.

How to fix it

  1. Find the server that refused it. Open the bounce (the delivery failure notice). If it has Remote-MTA, that server issued the reply in Diagnostic-Code. If not, the server in Reporting-MTA did. Some bounces label these fields differently. If that server is your own gateway, the rule is yours.
  2. Read everything after the code. It may name a list, a rule or a web address.
  3. Check the sending IP with the Blacklist Check. If the bounce does not show the IP, ask your network administrator or ISP, as Proofpoint suggests. On shared webmail the IP belongs to your provider, so send it the bounce. A listing is only a lead, because the refusing server may not use that list. If the bounce names that list, fix the cause and follow its removal process.
  4. Check your domain with the Email Security Score and the IP with the Reverse DNS Lookup. Caution: changing SPF can stop legitimate mail. List every service that sends as your domain first, add any missing one to your existing record, and keep a single SPF record. Stay within SPF's limit of 10 DNS lookups, because going over it returns permerror. If the PTR is missing, ask whoever runs that IP to add it. Do not lower DMARC to p=none as a test: it removes your stated preference for mail that fails DMARC.
  5. Test the content. Send the same recipient a new, plain-text message without links or attachments. If it arrives, the first message probably matched a content rule.
  6. Ask the recipient's admin. For Exchange Online, Microsoft's guidance for codes 5.7.0 through 5.7.999 says you typically cannot fix this yourself. Reach the recipient by phone or in person, and pass their admin the full reply text, the date and time with time zone, both addresses and the sending IP.
  7. If the server is yours, see in your logs which rule refused the message. Change only that rule, only if the refusal was wrong, and never open relaying to let a message through.

Confirm the fix

  1. If you changed DNS, run the tool again and wait until it shows the new value.
  2. Send a new message from the same account to the same recipient.
  3. If another bounce arrives, compare its text with the old one. A different code, such as 550 5.7.26, points to a more specific problem.
  4. In your server logs, a 250 reply from the refusing server to the message data means it accepted responsibility for delivering or relaying the message.
  5. Ask the recipient whether it arrived and in which folder.

Check it now

Check an IP or domain on ~30 blocklists

Frequently asked questions

Is 550 5.7.0 local policy violation a spam block?
It can be, but the code does not say so. Proofpoint documents IP blocks for spam under 5.7.1, while Gmail uses 5.7.0 for a content block and for SMTP relay refusals. The text after the code, or the server's operator, tells you which case is yours.
Can I fix 550 5.7.0 myself?
Only the parts you control, such as a listed IP, an incomplete SPF record or a missing PTR record. When a recipient's settings in Exchange Online cause the refusal, Microsoft says you typically need the recipient or their email admin to change the configuration.
Why does only one recipient reject my email?
Local policy belongs to one server or organization, so another recipient's server can accept the same message. Microsoft also lists permissions on a single recipient or group among the causes of 5.7.x refusals in Exchange Online.
Is 550 5.7.0 the same as 550 5.7.1?
They are different codes that can describe similar refusals. RFC 3463 defines 5.7.0 as other or undefined security status and 5.7.1 as delivery not authorized, message refused. Microsoft gives the same guidance for both in Exchange Online.
Will the message go through if I send it again?
Sending it unchanged is unlikely to help. RFC 3463 says a permanent failure is not likely to be resolved by resending the message in its current form, and RFC 5321 says the client should not repeat the exact request. Send a new message after you change what caused the refusal.
Does a DMARC failure cause this error?
The code alone does not show that. RFC 9989 says a receiver might name DMARC in the reply text, and its example uses 5.7.1. If your reply mentions only local policy, treat authentication as one possibility and check the sending IP as well.

Sources consulted

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.