
Outlook error 550 5.7.515 is a hard bounce from Outlook.com and Microsoft's consumer email services (Hotmail, Live.com, MSN). The full message reads "550 5.7.515 Access denied, sending domain [domain] does not meet the required authentication level." It means the domain in your visible From address failed the authentication rules Microsoft applies to high-volume senders. It is not a password, port or Outlook-app problem — which is where many forum threads go wrong. This guide explains exactly what triggers the error, how to read the authentication results in the bounce, and the step-by-step fix for Google Workspace, Microsoft 365 and third-party sending tools.
Outlook Error 550 5.7.515: The Short Answer
Microsoft rejects your mail with 550 5.7.515 when your From domain sends a high volume of email to Outlook.com consumer addresses and doesn't meet its authentication requirements. To fix it: make sure SPF and DKIM are published and pass for your domain, publish a DMARC record (p=none or stricter), and make sure DMARC passes with SPF and/or DKIM aligned to the From domain. Then check every service that sends as your domain.
Requirement (per Microsoft) | What it means | Common failure |
|---|---|---|
SPF published and passing | Your sending servers are authorised | Missing include for a sending tool |
DKIM published and passing | Messages are signed by your domain | DKIM not enabled or signing with the provider's domain |
DMARC record published | At least v=DMARC1; p=none | No _dmarc record |
DMARC passes with alignment | SPF or DKIM domain matches the From domain | Third-party tool sending without alignment |
Source: Microsoft's support article Fix NDR error "550 5.7.515" in Outlook.com. Our SPF, DKIM and DMARC guide shows how to set each record.
Who Gets Error 550 5.7.515 — and Why Now
Microsoft announced requirements for high-volume senders to Outlook.com in 2025, matching the direction Google and Yahoo took in 2024. Microsoft's article says the requirements apply once a domain sends 5,000 or more messages to its consumer services using the same domain in the From address; after that threshold, messages from the domain are expected to meet the authentication requirements. That is why domains that used to deliver fine suddenly see 100% rejections to Hotmail and Outlook.com addresses.
Note that this error concerns consumer Outlook.com mailboxes. Problems sending to business Microsoft 365 tenants usually show different codes. For general Outlook troubleshooting see Outlook cold email troubleshooting: 9 fixes; for why Outlook audiences matter, see why Microsoft 365 for outbound sales and Microsoft 365 pros and cons.
Step 1: Read the Bounce and Headers
Many 5.7.515 bounces include the authentication results at the end, for example Spf=Pass, Dkim=Fail, DMARC=Pass. That line tells you what to fix. If it isn't there:
Send a test message to an Outlook.com address you control.
Open the message, view message details / internet headers, and find
Authentication-Results.Note the results for
spf,dkimanddmarc, and compare the domains insmtp.mailfrom(return-path),header.d(DKIM signing domain) andheader.from.Any FAIL, or a signing/return-path domain that doesn't match your From domain, is the problem. (For Gmail-side checks, set up Postmaster Tools too.)
Step 2: Fix SPF, DKIM and DMARC
Fix SPF
Make sure your domain has exactly one SPF TXT record that includes every service that sends as you. For Google Workspace that includes Google's servers; for Microsoft 365, Microsoft's. Keep under the 10-DNS-lookup limit. See SPF, DKIM and DMARC setup guide.
Fix DKIM
DKIM failing is the most common cause reported in Microsoft's community threads. In Google Workspace (see domain setup guide), generate the DKIM key in the Admin console, publish the TXT record, then click Start authentication. In Microsoft 365, publish the two CNAME records and enable DKIM signing in the Defender portal — a step people often miss; see Microsoft 365 cold email setup and Microsoft 365 setup mistakes.
Fix DMARC
Publish a TXT record at _dmarc.yourdomain.com, for example v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com. Microsoft accepts p=none, p=quarantine or p=reject; DMARC must pass via aligned SPF and/or DKIM.
Fix alignment
Alignment means the domain that SPF or DKIM authenticates matches the From domain. A tool that signs with its own domain or uses its own return-path will pass SPF/DKIM for its domain but fail DMARC for yours.
Step 3: Check Every Service That Sends as Your Domain
If your mailbox passes but some mail still bounces, a different service is sending as your domain. Microsoft's checklist for third-party senders:
📤Return-path uses your domain
The service's MAIL FROM / return-path should be on your domain (often a subdomain you set up).
✍️DKIM signs with your domain
Set up the service's custom DKIM so header.d matches your domain.
🧾SPF includes the service
Add the service's include or IPs to your SPF record.
✅DMARC validates your domain
DMARC should pass for your domain, not the service's.
Typical culprits: CRMs, newsletter tools, help desks, website forms and invoice systems. Cold email should run on separate secondary domains anyway — see cold email domain setup.
Step 4: Verify the Fix and Resume Carefully
Wait for DNS changes to propagate, then send new test messages to an Outlook.com address and confirm SPF, DKIM and DMARC all pass with aligned domains.
Re-send a small batch; don't blast the full queue at once — sudden spikes can trigger Microsoft throttling.
Check that your domain isn't also on a blocklist (how to check).
Monitor bounces for a week. If rejections continue with a different code, read the new code carefully; our recovery guide helps if reputation also dropped.
If Outlook placement is poor even after authentication passes, see why are my emails going to spam and Microsoft 365 troubleshooting for agencies.
Related Microsoft Error Codes
Code | Meaning | Where it comes from |
|---|---|---|
550 5.7.515 | From domain failed required authentication level | Outlook.com consumer services |
550 5.7.233 | Tenant exceeded daily limit for external recipients (TERRL) | Your Microsoft 365 tenant |
550 5.1.8 | Sender restricted, often after suspected outbound spam | Your Microsoft 365 tenant |
5.7.233 and 5.1.8 relate to Microsoft 365's own sending limits, covered in Microsoft 365 email throttling and Microsoft's sending limits troubleshooting page.
Common Outlook Error 550 5.7.515 Scenarios
Scenario | Typical cause | Fix |
|---|---|---|
Bounce shows Spf=Pass, Dkim=Fail | DKIM not enabled or broken key | Enable/repair DKIM for the From domain |
Only newsletter emails bounce | Newsletter tool signs with its own domain | Set up custom DKIM and return-path in the tool |
Website form emails bounce | Form plugin sends via an unauthorised server | Route through an authenticated service or add to SPF with DKIM |
Free webmail address in From | You can't control that domain's DNS | Send from your own domain with full authentication |
Started after moving providers | Old SPF/DKIM records left behind | Update SPF include and DKIM for the new provider |
Agencies seeing outlook error 550 5.7.515 across many client domains should standardise setup — see Microsoft 365 tips for agencies, agency troubleshooting and Microsoft 365 risks for SDR teams. If your outreach targets Outlook users heavily, LiteMail's Microsoft 365 inboxes explained and pre-warmed vs DIY Outlook compare setup routes. Healthy authentication also helps you stop cold emails going to spam and avoid general spam placement.
Avoid 5.7.515 with Pre-Configured Authentication
LiteMail | Authentication handled for you
Fresh from $2.50/inbox
SPF, DKIM and DMARC configured automatically on every domain
LiteMail sets up Microsoft 365 and Google Workspace inboxes with SPF, DKIM and DMARC configured automatically on your secondary domains, including the Microsoft 365 DKIM step, on dedicated US and EU IPs. The API can check DNS records and add DMARC records programmatically. For Outlook-heavy audiences, pre-warmed Microsoft 365 accounts are also available.
Strengths | Keep in mind |
|
|
See Plans → Send to Outlook with authentication configured correctly from day one. Get Pre-Warmed Inboxes →
Frequently Asked Questions
What does Outlook error 550 5.7.515 mean?
It means Outlook.com rejected your message because the domain in your From address did not meet Microsoft's required authentication level for high-volume senders.
How do I fix 550 5.7.515 Access denied?
Publish passing SPF and DKIM for your domain, publish a DMARC record (p=none or stricter), make sure DMARC passes with SPF and/or DKIM aligned to your From domain, and fix any third-party service sending as your domain.
Is 550 5.7.515 caused by my password or SMTP port?
No. It is a sender-domain authentication rejection. Changing ports or passwords won't fix it. See Microsoft 365 setup mistakes for related errors.
Which domains does 5.7.515 apply to?
Outlook.com and related Microsoft consumer services such as Hotmail, Live.com and MSN.
Does DMARC p=none satisfy Microsoft?
Microsoft's article lists p=none, p=quarantine and p=reject as acceptable policies, as long as DMARC passes with alignment.
Why does SPF pass but I still get 5.7.515?
Usually because DKIM fails or isn't aligned, or because SPF passes for a different domain than your From address. Check the Authentication-Results header.
How long after fixing DNS will Outlook accept my mail?
Once DNS changes propagate and new messages pass authentication, they should be accepted. Resume gradually and monitor bounces (mid-campaign drop guide).
How do I enable DKIM in Microsoft 365?
Publish the two DKIM CNAME records and enable signing in the Microsoft Defender portal. See our Microsoft 365 setup guide.
Send to Outlook Without Authentication Bounces
Google Workspace and Microsoft 365 inboxes with SPF, DKIM and DMARC configured automatically, on dedicated US and EU IPs.
Automated DNS · Microsoft 365 DKIM handled · Bulk OAuth export
About LiteMail — LiteMail provides fresh and pre-warmed Google Workspace and Microsoft 365 inboxes for cold email outreach, with automated SPF, DKIM and DMARC setup, dedicated US and EU IPs, separate client workspaces and one-click OAuth export to Instantly, Smartlead, Lemlist and other sending tools. View pre-warmed inbox plans →
Related reading: SPF, DKIM and DMARC Setup · Microsoft 365 Cold Email Setup · Outlook Cold Email Troubleshooting · Microsoft 365 Setup Mistakes · Why Microsoft 365 for Outbound · Microsoft 365 Inboxes


