Outlook/Hotmail error 550 5.7.515: what does it mean and how do I fix it?
The 550 5.7.515 error means Outlook, Hotmail or Live rejected your email because your domain didn't pass Microsoft's authentication. Fix SPF, DKIM and DMARC, align the From address and send again.
The 550 5.7.515 Outlook error means Microsoft (Outlook, Hotmail or Live) rejected your email because your domain didn't pass the authentication it requires. To fix it, your domain needs a passing SPF, a valid DKIM signature and a DMARC record (at least p=none) aligned with the sender's domain. Once you fix those DNS records and they propagate, delivery resumes.
Below you'll find the steps in order, a table of causes and what to do depending on the type of sending.
What the bounce says and why it appears
The error message usually looks like this:
550 5.7.515 Access denied, sending domain [tudominio.com] doesn't meet the required authentication level.This bounce comes from Microsoft's consumer mailboxes: outlook.com, hotmail.com and live.com. Since 2025, Microsoft has enforced stricter rules for high-volume senders, meaning those who send more than 5,000 emails a day to its mailboxes. Those senders must have:
- SPF passing for the sending domain.
- DKIM passing, with a valid signature from the domain.
- DMARC published, at minimum with
p=none, and aligned with SPF or DKIM. Ideally, aligned with both.
It can happen to you even if you send few emails. If your domain lacks authentication or has it misconfigured, Microsoft may reject your messages with this same code or send them to the junk folder. That's why it's worth fixing even if you don't send newsletters.
Step 1: read the full bounce
Open the bounce email (“Mail Delivery Failed” or “Undeliverable”) and check three things:
- The domain in square brackets. That's the domain Microsoft evaluated. Sometimes it isn't your main domain but a subdomain or an external service's domain.
- The recipient. Confirm the destination is outlook.com, hotmail.com or live.com.
- Whether all your emails are rejected or only some. If only messages sent from your website or CRM bounce, the problem is in that service, not in your mailbox.
Step 2: check SPF, DKIM and DMARC
Send a test email to a Gmail account and open the message with the “Show original” option. There you'll see whether SPF, DKIM and DMARC show PASS or FAIL. The step-by-step is in this guide to check SPF, DKIM and DMARC with Gmail's “Show original”.
Run one test for each system that sends email with your domain, not just your email program. If a form on your website shows FAIL and your Outlook shows PASS, you've found the culprit.
Step 3: fix the DNS records
Open your domain's DNS zone and adjust the three records. If you don't know where to edit them, follow this guide on how to add DNS records to your domain.
SPF: a single TXT record
Your domain must have only one SPF record. If it has two, both fail. An example of the structure:
v=spf1 +a +mx include:servicio-que-envia.example ~allReplace the includes with the ones each provider gives you. If you use hosting email in cPanel, the email deliverability section shows the suggested SPF record for your domain.
DKIM: turn on signing
Every service that sends email must sign with DKIM using your domain. In cPanel, the same deliverability section tells you whether DKIM is valid and which TXT record to publish if your DNS is hosted elsewhere.
DMARC: start with p=none
_dmarc.tudominio.com TXT "v=DMARC1; p=none; rua=mailto:reportes@tudominio.com"With p=none you meet Microsoft's minimum and start receiving reports. Once everything passes consistently, you can move to quarantine or reject.
Step 4: align the From address with your domain
DMARC doesn't just require SPF or DKIM to pass. It also requires the validating domain to match the visible sender domain (the From field). A typical mistake is a form plugin that sends as info@yourdomain.com but signs with the server's domain or an external service's domain. In that case, DKIM passes but DMARC fails. The fix is to have the service sign with your domain, or to have your website send via authenticated SMTP with a real account on your domain, on port 587 (STARTTLS) or 465 (SSL/TLS).
Step 5: review everything that sends on behalf of your domain
Make a list of everything that sends email with your domain and check each one:
- Your mailboxes (Outlook, Thunderbird, your phone's mail app).
- Your website: forms, online store, WordPress notifications.
- Your CRM or billing system.
- Your newsletter platform.
Each one must appear in your SPF and sign with DKIM using your domain. To understand how an intermediate server delivers your email, read what an SMTP relay is.
Step 6: wait for propagation and send again
DNS changes can take anywhere from minutes to a few hours, depending on each record's TTL. Repeat the test with “Show original”. When SPF, DKIM and DMARC all show PASS, send one test email to an Outlook or Hotmail account before resending everything that bounced.
Table: cause and fix
| Cause | How to spot it | Fix |
|---|---|---|
| No DMARC record | “Show original” says DMARC doesn't exist | Publish _dmarc with p=none |
| Two SPF records | SPF shows PermError | Merge them into a single TXT |
| A service isn't included in SPF | SPF fails only on that service's emails | Add its include |
| DKIM is off or published incorrectly | DKIM shows FAIL or neutral | Turn on DKIM and publish the correct key |
| The From isn't aligned | SPF or DKIM pass, but DMARC shows FAIL | Have the service sign with your domain or send via authenticated SMTP |
| Bulk email from the hosting mailbox | Bounces on large sends | Use a dedicated bulk email service |
What not to do
- Don't resend in a loop. Insisting with an unauthenticated domain hurts your domain's reputation with Microsoft.
- Don't change the From to a Gmail account. If you send as @gmail.com from a server that isn't Google's, the email fails DMARC and the problem repeats, just with another domain.
- Don't publish
p=rejectright away. If you still have unaligned services, you'd be blocking them yourself.
How it differs from the MagicSpam 550 error
Both errors start with 550, but 5.7.515 is generated by the recipient's server (Microsoft) because of an authentication problem with your domain. The MagicSpam one is returned by an antispam filter on a cPanel mail server at connection time, usually because the sending wasn't authenticated, because of the IP it comes from or because of sending behavior. If your bounce mentions MagicSpam, follow this guide on the MagicSpam 550 error when sending email.
Dongee options for your case
| Option | Authentication | Ideal for |
|---|---|---|
| Shared hosting email | Email goes out through MailChannels with SPF and DKIM | A business's daily email alongside its website |
| Dongee Prime Email | DKIM and antispam on every mailbox | Teams that need email to keep working even if the website goes down |
| Dedicated bulk email service | Depends on the provider you choose | High-volume newsletters and campaigns |
With Dongee shared hosting (Dongee Startup at 10 USD/month with 50 mailboxes of 1 GB, or Dongee Quantum at 19 USD/month with 50 mailboxes of 2 GB), outbound email goes through MailChannels, a relay with SPF and DKIM. Check in cPanel's email deliverability section that SPF and DKIM show as valid for your domain, and publish your DMARC record. If you'd rather keep email separate from your website, Dongee Prime Email costs from 2 USD/month per mailbox on the Basic tier, with 8 GB (expandable) and DKIM. Keep in mind you can't mix hosting mailboxes and Prime Email mailboxes on the same domain.
For bulk campaigns, the honest recommendation is a dedicated bulk email service. Set it up with its own include in your SPF and its DKIM signature using your domain. That way you protect the reputation of the mailboxes you use every day.
Frequently asked questions
Does error 5.7.515 only affect senders of more than 5,000 emails a day?
Microsoft's strict rules are aimed at high-volume senders. Even so, a domain without SPF, DKIM or DMARC can get rejections or land in junk at any volume.
Is SPF enough?
No. Microsoft requires SPF and DKIM to pass, plus an aligned DMARC. If you only have SPF, you don't meet the full requirement.
How long does it take to fix?
It depends on your DNS records' TTL. It can take minutes or several hours. Before resending, use “Show original” to confirm everything shows PASS.
Why does my Outlook send fine but my website's emails bounce?
Because your website probably sends without authenticating or signs with another domain. Configure it to send via authenticated SMTP with an account on your domain, on port 587 or 465.
Can I get help reviewing my records?
Yes. Dongee's 24/7 human support in your language (the platform translates on the fly) can help you review them by chat or WhatsApp.
In summary
Error 550 5.7.515 is an authentication problem, not a permanent block. To solve it: read the bounce, check SPF, DKIM and DMARC, align the From with your domain and make sure every service sending with your domain is authenticated. Then wait for propagation and run a test before resending. Once all three records show PASS, Outlook and Hotmail accept your emails again.
Comenta lo que quieras
Unete a la charla
Solo ingresa tu email