Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Email delivery

Outlook.com bounces your mail with 550 5.7.515

Error550 5.7.515 Access denied, sending domain example.com does not meet the required authentication level.

Short answer

550 5.7.515 means Outlook.com counts your From domain as a high-volume sender (5,000 or more messages a day to Microsoft consumer addresses) and the message failed its authentication rules. Since 5 May 2025 such domains need SPF and DKIM to both pass, plus a DMARC record of at least p=none that passes through SPF or DKIM aligned with the From domain.

  • Applies to Outlook.com sender rules (May 2025), dig (BIND 9.18), Postfix 3.8, Ubuntu 24.04
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Microsoft's announcement first described sending failing mail to Junk, with rejection to follow; a 5.7.515 bounce is the rejection, and the fix is the same either way. Find the bounces in your mail log, then read the two records Outlook.com checks before anything else.

    sudo grep "5.7.515" /var/log/mail.log | tail -n 5
    dig +short TXT example.com | grep spf1
    dig +short TXT _dmarc.example.com
  2. 2Match what you see, then jump to its fix

    1. 1dig prints nothing for _dmarc.example.com, or prints two v=DMARC1 recordsThere is no DMARC record, or Outlook.com can't read itFix
    2. 2Outlook's headers show spf=pass with smtp.mailfrom on the provider's domain and dmarc=fail, or spf=none for your domainSPF passes on the provider's bounce domain, not on yoursFix
    3. 3dkim=none, or dkim=pass with header.d set to the provider's domain while header.from is yoursDKIM is missing, or signed with the provider's domainFix
    4. 4Newsletters get through, but password resets or invoices from the app server bounce with 5.7.515Another system sends with the same From domain and failsFix

What does the error look like?

  • 550 5.7.515 Access denied, sending domain example.com does not meet the required authentication level.
  • status=bounced (host hotmail-com.olc.protection.outlook.com[...] said: 550 5.7.515 Access denied
  • Mail to Gmail is delivered, but mail to hotmail.com, live.com and outlook.com addresses bounces

Cause 1 of 4

There is no DMARC record, or Outlook.com can't read it

1Check

Microsoft looks for a TXT record at _dmarc under the From domain. DNS panels that add the zone name for you often turn a host typed as _dmarc.example.com into _dmarc.example.com.example.com. A domain with two DMARC records is treated as having none.

dig +short TXT _dmarc.example.com
dig +short TXT _dmarc.example.com.example.com

2Fix

Publish exactly one record. p=none is enough for this rule; add a report address so you learn which senders still fail before you tighten the policy.

Host:  _dmarc
Type:  TXT
Value: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com

3Verify

Ask a public resolver, so a cached answer on your own network can't mislead you.

dig +short TXT _dmarc.example.com @8.8.8.8
Did this fix it?

Cause 2 of 4

SPF passes on the provider's bounce domain, not on yours

1Check

SPF is judged on the envelope sender (5321.MailFrom, which shows up as Return-Path), and many sending platforms fill that in with their own domain. Microsoft's guidance for third-party senders is that this address should contain your domain. Look at the Return-Path of a copy that was delivered to a mailbox you control.

grep -iE '^Return-Path:|smtp.mailfrom=' delivered-copy.eml

2Fix

Turn on the provider's custom return path (also called custom MAIL FROM or bounce domain). You publish the records it gives you for a subdomain such as bounce.example.com, usually a CNAME or an MX plus a TXT, and the provider starts using that subdomain as the envelope sender.

; values come from your provider's dashboard
bounce.example.com.  3600  IN  CNAME  <host given by the provider>.

3Verify

The subdomain resolves to the provider's SPF policy, and new messages carry a Return-Path at bounce.example.com.

dig +short TXT bounce.example.com
Did this fix it?

Cause 3 of 4

DKIM is missing, or signed with the provider's domain

1Check

Microsoft wants DKIM to pass, and for DMARC the signing domain (the d= tag) should be yours. Read d= and s= from the DKIM-Signature header, then fetch the key at that selector.

grep -i '^DKIM-Signature:' -A4 delivered-copy.eml | grep -oE '\b(d|s)=[^;]+'
dig +short TXT s1._domainkey.example.com

2Fix

Enable custom DKIM at every provider that sends as you; each one hands you two or three records under _domainkey. Mail that your own servers send straight out needs its own signer, for example OpenDKIM next to Postfix.

; typical shape, exact names come from the provider
s1._domainkey.example.com.  3600  IN  CNAME  <s1 target from the provider>.
s2._domainkey.example.com.  3600  IN  CNAME  <s2 target from the provider>.

3Verify

Send to an Outlook.com test mailbox and open the message headers: dkim=pass with header.d=example.com and dmarc=pass with header.from=example.com.

grep -i '^Authentication-Results:' -A3 outlook-copy.eml
Did this fix it?

Cause 4 of 4

Another system sends with the same From domain and fails

1Check

Microsoft applies the threshold and the rules to the From domain as a whole, not to each platform. A web server that sends straight out with no DKIM, from an IP that is missing in SPF, fails even when the newsletter platform is set up perfectly. Count bounces to Microsoft's consumer domains from each server, and list every system that uses your domain in From.

sudo grep -E 'to=<[^>]*@(outlook|hotmail|live)\.com>' /var/log/mail.log | grep -c 'status=bounced'

2Fix

Send application mail through a provider that signs for your domain, or give that server DKIM signing and an SPF entry of its own. Moving bulk mail to a subdomain such as news.example.com also keeps its volume and reputation apart from transactional mail.

# Postfix on the app server: hand every message to an authenticated relay
sudo postconf -e 'relayhost = [smtp.your-provider.example]:587' \
  'smtp_sasl_auth_enable = yes' \
  'smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd' \
  'smtp_sasl_security_options = noanonymous' \
  'smtp_tls_security_level = encrypt'
# /etc/postfix/sasl_passwd holds one line:  [smtp.your-provider.example]:587  user:password
sudo chmod 600 /etc/postfix/sasl_passwd
sudo postmap /etc/postfix/sasl_passwd
sudo systemctl reload postfix

3Verify

New messages to Microsoft addresses from that server show status=sent.

sudo tail -f /var/log/mail.log | grep -E '@(outlook|hotmail|live)\.com'
Did this fix it?

How do I stop it coming back?

  • Treat SPF pass, DKIM pass and aligned DMARC as the minimum for every platform that sends as your domain, not only the main one.
  • Register your sending IPs with Microsoft SNDS to see how Outlook.com rates them.
  • Keep a test mailbox at outlook.com and read its headers after every change to DNS or to a sending provider.
  • Read DMARC aggregate reports: a new source showing dmarc=fail there is the next 5.7.515 bounce.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Related fixes

Email

Mail from your own domain keeps landing in the spam folder

dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=example.com

Open a message that went to spam and read its Authentication-Results header: it shows whether SPF, DKIM and DMARC passed, and for which domain.

5 causes, each with a fix

Email

Postfix refuses to send with "Relay access denied"

454 4.7.1 <user@example.net>: Relay access denied

Postfix says Relay access denied when a client asks it to deliver to a domain it does not host, and the client is neither listed in mynetworks nor logged in with SASL.

5 causes, each with a fix

Email

PHP mail() returns true but the email never arrives

Warning: mail(): "sendmail_from" not set in php.ini or custom "From:" header missing

mail() returning true only means the message was accepted for delivery, not that it arrived.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.