Microsoft 365 5.7.512
Access denied, message must be RFC 5322 section 3.6.2 compliant
Microsoft 365 5.7.512 means: access denied, message must be RFC 5322 section 3.6.2 compliant. It is a permanent failure, so do not retry it unchanged. The fix is in the sending or receiving configuration named above, not in the list. Fix that, then resend.
Microsoft 365’s exact wording
Quoted from Microsoft Learn: Email non-delivery reports and SMTP errors in Exchange Online, checked 2026-11-05. Placeholders are Microsoft 365’s own.
Provider's description
Access denied, message must be RFC 5322 section 3.6.2 compliant
Possible cause
Message was sent without a valid "From" email address.
Provider's advice
Office 365 only. Each message must contain a valid email address in the "From" header field. Proper formatting of this address includes angle brackets around the email address. For example: <[email protected]>. Without an address in this format, Microsoft 365 or Office 365 rejects the message.
| Who sends it | Microsoft 365, Exchange Online and Outlook.com |
|---|---|
| Basic code | Microsoft 365 lists the enhanced code only |
| Enhanced code | 5.7.512: Microsoft 365-specific, not in the IANA registry. Its subject digit puts it under 5.7.0 other or undefined security status. |
| Permanent or temporary | Permanent (5xx) |
| Verifying the list prevents it | No |
What the sender should do
The fix is in the sending or receiving configuration named above, not in the list. Fix that, then resend.
Would verifying the list have prevented Microsoft 365 5.7.512?
No
This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Common questions
- What does Microsoft 365 5.7.512 mean?
- Microsoft 365 5.7.512 means: access denied, message must be RFC 5322 section 3.6.2 compliant. It is a permanent failure, so do not retry it unchanged. The fix is in the sending or receiving configuration named above, not in the list. Fix that, then resend.
- Should I retry after Microsoft 365 5.7.512?
- No. It is a permanent (5xx) failure, so the same message to the same address will fail again. Fix the cause first. The fix is in the sending or receiving configuration named above, not in the list. Fix that, then resend.
- Would verifying my list have prevented Microsoft 365 5.7.512?
- No. This reply is about your sending setup, the message or the receiving system, not about whether the address exists, so verifying the list will not prevent it.
Sources
- Microsoft Learn: Email non-delivery reports and SMTP errors in Exchange Online (checked 2026-11-05)
Registry and provider wording is quoted exactly; guidance is written by the SimpleVerifier Team.
SimpleVerifier Team · Last checked against the sources 2026-11-05