550 5.7.515 Access denied, sending domain example.com does not meet the
required authentication level.
Since May 2025, Outlook.com (which also handles hotmail.com and live.com addresses) requires domains that send more than 5,000 messages a day to its users to authenticate their mail. Messages that don't meet the bar are rejected with this code.
What Microsoft requires
- SPF must pass for the sending domain.
- DKIM must pass for the sending domain.
- DMARC must be published with at least
p=none, and it must pass: SPF or DKIM has to align with the domain in the From address.
Microsoft also recommends a working unsubscribe link, valid From and Reply-To addresses, and keeping your list clean, but the three checks above are what trigger this rejection.
How to fix it
- Check which of the three fails by sending a message to an Outlook.com address and reading the Authentication-Results header, or use a tester.
- If there is no DMARC record, publish one. Starting with
p=noneis enough to meet the requirement. - Enable DKIM signing with your own domain in every service that sends bulk mail for you.
- Make sure SPF passes too: the envelope sender (Return-Path) domain needs an SPF record that includes the sending service. Many platforms let you set a custom return-path subdomain for this.
This applies to consumer Outlook.com mailboxes. Mail to businesses on Microsoft 365 follows the recipient organisation's own policies, but meeting the same bar helps there too. The requirements closely match what Gmail and Yahoo ask.