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.
550is a permanent refusal.5.7.0is 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 Violationis 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.0is 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
- Find the server that refused it. Open the bounce (the delivery failure notice). If it has
Remote-MTA, that server issued the reply inDiagnostic-Code. If not, the server inReporting-MTAdid. Some bounces label these fields differently. If that server is your own gateway, the rule is yours. - Read everything after the code. It may name a list, a rule or a web address.
- 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.
- 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 top=noneas a test: it removes your stated preference for mail that fails DMARC. - 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.
- 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.
- 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
- If you changed DNS, run the tool again and wait until it shows the new value.
- Send a new message from the same account to the same recipient.
- 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.
- In your server logs, a
250reply from the refusing server to the message data means it accepted responsibility for delivering or relaying the message. - Ask the recipient whether it arrived and in which folder.