Skip to content

550 5.7.509 Access Denied: Causes and How to Fix It

What the Microsoft 365 bounce 550 5.7.509 Access denied, sending domain does not pass DMARC verification means, why it happens and how to fix SPF and DKIM.

Nov 19, 2026 5 min read 1,201 words
550 5.7.509 Access Denied: Causes and How to Fix It
550 5.7.509 access denied DMARC reject error
550 5.7.509 access denied DMARC reject error

You send an email to someone on Outlook or Microsoft 365, and it bounces. The report says "550 5.7.509 Access denied, sending domain example.com does not pass DMARC verification and has a DMARC policy of reject". Most of your other mail may still arrive. Only some messages fail, and often only to Microsoft.

This bounce is about your own domain, not the person you wrote to. This guide explains what the 550 5.7.509 error means, why it happens, and how to fix it for good.

What 550 5.7.509 means#

The bounce has two parts. 550 is the SMTP reply for a permanent failure. Sending the same message again will fail the same way.

5.7.509 is the enhanced status code. The 7 class covers security and policy, and 509 is Microsoft's own detail code.

Microsoft's list of Exchange Online bounce codes is clear. The domain in the From address did not pass DMARC, and that domain asks receivers to reject mail that fails. Microsoft did what your DMARC record told it to do.

So the message looked like it came from your domain, but Microsoft could not prove it. Neither SPF nor DKIM passed in a way that matched your From domain.

How DMARC decides pass or fail#

DMARC is defined in RFC 7489. A message passes when at least one of two checks works:

  • SPF passes and aligns. The server that sent the mail is listed in the SPF record of the domain in the From address.
  • DKIM passes and aligns. The message carries a valid DKIM signature from the same domain as the From address.

"Aligns" is the part most people miss. A message can pass SPF for your email tool's domain and still fail DMARC for yours. Our guide to DMARC alignment shows how this works with real headers.

When both checks fail and your record says p=reject, Microsoft rejects the mail. That is the 5.7.509 bounce.

Common causes#

The same few cases come up again and again.

  • A tool sends as your domain. A CRM, help desk, invoice app or newsletter service sends mail with your address in From. If it is not in your SPF record and does not sign with DKIM for your domain, it fails.
  • DKIM is not turned on. Many Microsoft 365 and Google Workspace domains have SPF but never turned on DKIM signing.
  • The SPF record is broken. More than 10 DNS lookups, two SPF records, or a typo makes SPF fail for every message.
  • Forwarding or a mailing list. A forward changes the sending server, so SPF fails. A list that edits the subject or footer breaks DKIM.
  • Someone spoofed your domain. If you did not send the message, the bounce shows your policy doing its job.

How to fix 550 5.7.509 step by step#

You fix this on the sending domain. The recipient cannot fix it for you, and they should not have to.

Step 1: Read the full bounce and headers#

Open the bounce and find the original message headers. Look for the Authentication-Results line. It shows spf=, dkim= and dmarc= results and the domains checked. Note which server sent the message and which app sent it.

Step 2: Find every service that sends as you#

List each tool that uses your domain in From: your mailbox host, CRM, support desk, billing and marketing tools. DMARC aggregate reports help here. They list each source IP that sent mail for your domain and whether it passed.

Step 3: Fix your SPF record#

Add each real sending service to one SPF record with its include:. Keep the record under 10 DNS lookups. Remove services you no longer use. Then check that the record has no syntax errors.

Step 4: Turn on DKIM for each sender#

DKIM is the stronger fix, because it survives forwarding. Turn on DKIM signing in Microsoft 365 or Google Workspace. For each other tool, add the DKIM records it gives you so it signs as your domain, not its own. Our guide to SPF, DKIM and DMARC in Office 365 walks through each record.

Step 5: Send a test and check the result#

Send a test from each tool to an Outlook.com or Microsoft 365 mailbox. Open the headers and confirm that dmarc=pass appears. Then send the bounced message again.

Step 6: Handle forwarding with care#

If the bounce comes after a forward, DKIM is your best protection, since SPF breaks on every forward. A recipient admin on Microsoft 365 can also add the forwarding service as a trusted ARC sealer. That is their setting, not yours.

Should you lower your DMARC policy?#

Moving from p=reject to p=quarantine or p=none stops the bounce. It also lets anyone spoof your domain more easily. Use it only for a short time, while you fix a sender you cannot fix fast. Watch your reports, then go back to reject. Our post on DMARC reject covers the trade-offs.

Can the recipient change it?#

Yes, but it is not the right fix. In Microsoft's anti-phishing policies, the recipient admin chooses whether to honor sender DMARC policies. They can quarantine instead of reject. That only hides the problem, and other providers will still reject your mail.

How it compares with nearby codes#

Code Who sends it What failed
550 5.7.509 (this error) Microsoft 365, Outlook.com DMARC, with the sender's policy set to reject
550 5.7.26 Gmail The message was not authenticated
554 5.7.9 Yahoo, AOL A policy check, often DMARC
550 5.7.1 Many servers A general policy or relay block

All four point at how the mail was sent, not at the address. For Gmail's version, see 550 5.7.26 unauthenticated email.

550 5.7.509 Checklist#

  • Full bounce and headers saved
  • Every service that sends as your domain listed
  • One SPF record, under 10 lookups, with each sender included
  • DKIM signing on for each sender, with your own domain
  • Test sent to Outlook with dmarc=pass in the headers
  • DMARC reports checked each week

FAQ#

What does 550 5.7.509 mean?#

It means Microsoft rejected your message because your domain failed DMARC and your DMARC policy is set to reject. The fix is on your side, the sender.

Why do only some of my emails bounce?#

Different tools send your mail. Your mailbox may pass DMARC while a CRM or form tool does not. Find the tool in the headers and fix its SPF or DKIM.

Why does it happen when I forward an email?#

Forwarding sends the message from a new server, so SPF fails. If the message has no aligned DKIM signature, DMARC fails too.

Is my domain being spoofed?#

Maybe. If you did not send the message, someone else used your domain. The bounce shows that your reject policy is working.

How long does it take to fix?#

DNS changes often apply within an hour, but some take up to a day or two. Send a test after each change before you resend.

Once your domain passes DMARC, clean your list too. The Tomba Email Verifier catches dead addresses before they bounce.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
AU

// about the author

Tomba Editorial Team

Was this helpful?