# Outlook 550 5.7.515: How to Fix DMARC Rejections

> Outlook bouncing your mail with 550 5.7.515? What the error means, why small senders saw it in November 2026, and the DMARC, SPF and DKIM fix.

Canonical: https://www.cresca.xyz/blog/outlook-550-5-7-515-dmarc-fix
Author: Lalit Kumar Jangid
Published: 2026-11-22
Last updated: 2026-11-22

If mail you send to Outlook.com, Hotmail or Live addresses comes back with **550 5.7.515**, Microsoft is telling you that your domain does not meet its sender authentication rules. The fix for the Outlook DMARC rejection is almost always the same: publish a DMARC record, make sure SPF and DKIM pass, and make at least one of them line up with your From domain. This guide explains what the error means, why small senders started seeing it in November 2026, and how to fix it step by step.

*Microsoft's rules and error text below come from its Outlook.com support page and its April 2025 Tech Community announcement, both checked on November 22, 2026. The November incident details come from published reporting and Microsoft's statements, checked the same day.*

## What 550 5.7.515 means

The bounce reads like this:

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

Microsoft's support page says the rule applies when you send 5,000 or more messages to its consumer email services (Outlook.com, Hotmail, Live and MSN) using the same domain in the From address. Once you reach that volume, Microsoft expects every message to meet three requirements:

1. **SPF passes** for the sending domain.
2. **DKIM passes.**
3. **A DMARC record is published** with a valid policy (p=none, p=quarantine or p=reject), and DMARC passes: SPF or DKIM, at least one of them, must align with the domain in the From address.

Microsoft announced these rules in April 2025. Non-compliant mail first went to the Junk folder from May 5, 2025. The support page now says Microsoft enforces the requirements, and non-compliant mail is rejected with 550 5.7.515.

## Why small senders saw Outlook DMARC rejections in November 2026

Late in the week before November 9, 2026, people sending far fewer than 5,000 emails a day started reporting rejections from Outlook.com, Hotmail and Live addresses. Some bounces cited a missing DMARC record, others a failed SPF check, and in some reports a single one-line email was refused.

Microsoft tracked it as incident EX1545193. Its incident report said a recent update to its spam enforcement rules had caused messages to be incorrectly marked and blocked. On November 11, Microsoft said it had fixed the bug and was continuing to monitor.

Two lessons came out of it:

- **The volume threshold is not a safety net.** Filters change, and a domain without DMARC is the first to get caught when they do.
- **Senders with complete, aligned records had far fewer problems.** Publishing DMARC takes a few minutes and removes one reason to reject your mail.

## The Outlook DMARC fix, step by step

### 1\. Find the domain you send from

Look at the From address of the email that bounced. If it is news@example.com, the domain is example.com. If you send from a subdomain such as mail.example.com, DMARC is looked up there first and then on the parent domain.

### 2\. Check whether you have a DMARC record

Run this in a terminal, with your own domain:

> dig TXT \_dmarc.example.com +short

If the answer starts with v=DMARC1, you have a record. If it is empty, that is very likely your problem.

### 3\. Publish a DMARC record if you don't have one

Add a TXT record in your DNS:

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

p=none tells receivers to report problems without blocking anything, and Microsoft lists it as a valid policy. The rua address receives daily aggregate reports, so you can see which services send mail as your domain. Use a mailbox you actually read, or one you set up just for these reports.

Publish exactly one DMARC record. Two records on \_dmarc are treated as an error.

### 4\. Make sure SPF passes

- Your domain must have exactly one TXT record that starts with v=spf1.
- It must include every service that sends as your domain: your mailbox provider, your email platform, your help desk, your CRM.
- SPF allows at most 10 DNS lookups. Every include counts, and so do the includes inside it. Go over 10 and SPF fails for all of your mail.

### 5\. Make sure DKIM passes and is signed with your domain

DKIM must be set up separately in each tool that sends for you. The detail that catches people is the signing domain. If a tool signs with its own domain (d=the-tool.com) instead of yours, DKIM can pass but it does not align with your From domain, so it does not help DMARC. Most email platforms let you add CNAME or TXT records so they sign as your domain. Do that for every tool.

### 6\. Send a test to an Outlook.com address and read the headers

Send a normal email to an Outlook.com or Hotmail address you control, open it, and view the message source. Find the Authentication-Results line. A healthy one looks like this:

> spf=pass smtp.mailfrom=bounce.example.com; dkim=pass header.d=example.com; dmarc=pass action=none header.from=example.com

You want dmarc=pass. If DMARC fails, compare the domains: header.from is your From domain, smtp.mailfrom is the domain SPF checked, and header.d is the domain DKIM signed with. At least one of the last two must be your From domain or one of its subdomains.

## Common mistakes that keep 550 5.7.515 coming back

| Mistake | What happens | Fix |
| --- | --- | --- |
| Two SPF records | SPF returns a permanent error for every message | Merge them into one v=spf1 record |
| DKIM signed with the tool's domain | DKIM passes but doesn't align, so DMARC can fail | Set up the tool's custom DKIM records for your domain |
| DMARC record on the wrong host | Receivers find no DMARC record | The host must be \_dmarc (or \_dmarc.yourdomain.com in full) |
| Jumping straight to p=reject | Legitimate mail from a forgotten tool gets rejected | Start at p=none, read the reports, then tighten |
| Fixing the main domain only | Mail from a subdomain still fails | Check every domain and subdomain in your From addresses |

## After p=none: when to tighten your DMARC policy

p=none is enough to meet Microsoft's requirement, but it does not stop anyone from spoofing your domain. Once your reports show that all your real mail passes for two to four weeks, move to p=quarantine, and later to p=reject. Our [study of DMARC records across the top 10,000 domains](https://www.cresca.xyz/research/email-authentication) shows how many large companies still stop at p=none.

## Gmail and Yahoo ask for the same thing

Microsoft's rules match what Gmail and Yahoo have required from bulk senders since February 2024: SPF, DKIM, an aligned DMARC record, a one-click unsubscribe and a low spam rate. If you fix your records for Outlook, you fix them for all three. The details are in our guide to [Gmail and Yahoo sender requirements](https://www.cresca.xyz/blog/gmail-yahoo-sender-requirements).

## How Cresca sets up authentication for you

When you add a sending domain in [Cresca](https://www.cresca.xyz/), the app lists every DNS record you need: DKIM records so your mail is signed with your own domain, a custom MAIL FROM subdomain with its own SPF record so SPF aligns too, and a suggested DMARC record if you don't have one yet. Cresca then checks the records and shows when the domain is ready to send.

Marketing campaigns and transactional email (password resets, receipts) go out from the same verified domain, and a marketing unsubscribe never blocks a password reset.

**[Try Cresca free for 30 days](https://app.cresca.xyz/signup)**: 250 contacts, 1,000 emails and 20 AI-designed emails, no credit card required.

## Outlook DMARC and 550 5.7.515: frequently asked questions

### Is p=none enough for Outlook?

Yes. Microsoft's support page lists p=none, p=quarantine and p=reject as valid policies. What matters is that the record exists and that DMARC passes, which needs SPF or DKIM to align with your From domain.

### Do I need both SPF and DKIM?

Microsoft's requirements say both SPF and DKIM must pass. DMARC itself needs only one of them to pass and align, but set up both so one broken record can't take down all your mail.

### I send fewer than 5,000 emails a day. Does this apply to me?

The written rule targets senders of 5,000 or more messages a day. In practice, the November 2026 incident showed that small senders can be caught when filters change, and Gmail asks every sender for SPF or DKIM. Publishing DMARC is quick and worth doing at any volume.

### How long does the fix take to work?

The DNS change usually takes effect within minutes to an hour, depending on your provider and the record's TTL. Send a fresh test after that. Mail that already bounced is not retried, so resend anything important.

### Was my bounce caused by Microsoft's November bug?

Possibly. Microsoft confirmed that a spam rule update incorrectly blocked some mail and said it fixed the bug on November 11, 2026. If you still see 550 5.7.515 after that date, treat it as a real authentication problem and work through the steps above.
