Email

Outlook error 550 5.7.515: email rejected, how to fix it

In short. Outlook.com, Hotmail and Live.com are rejecting some of your emails: your recipients never get them, and you receive an error message in return. The cause: your domain doesn't prove well enough that these emails really come from you (three settings called SPF, DKIM and DMARC). Whoever manages your domain and email has to fix it: you, or your IT provider. Expect one to two hours of settings, then a test email to check.

The 550 5.7.515 error means Outlook.com rejected your email because your domain does not reach the required authentication level. Microsoft applies it to domains that send a lot of mail to its consumer mailboxes (Outlook.com, Hotmail, Live.com…): SPF and DKIM must pass, a DMARC record must be published, and at least one of the two must be aligned with the sender's address.

Last checked: November 18, 2026, in Microsoft's official help.

The message you receive

The non-delivery report (NDR) sent back to the sender contains this text:

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

Microsoft sums it up this way: the domain in the sender's visible address (the From, or 5322.From) does not meet the authentication requirements set for that sender.

Who is affected

According to Microsoft, high-volume senders: 5,000 messages or more sent to its consumer mailboxes, with the same domain in the sender's address. Above that threshold, all messages from that domain must follow the rules, even those of a small campaign.

In practice, a small business reaches it quickly if it sends a newsletter, invoices or notifications from its own domain.

What Microsoft requires

  1. SPF published and passing for the sending domain.
  2. DKIM published and passing: messages are signed.
  3. A published DMARC record, at least v=DMARC1; p=none. p=quarantine and p=reject are fine too.
  4. Alignment: SPF or DKIM must pass with the same domain as the visible sender address.

The fourth point is the one most often forgotten. A sending tool can pass SPF and DKIM with its own domain: that is a pass, but not aligned, and DMARC still fails.

Step 1: read a message's header

Send a test message to an Outlook.com mailbox, open it, then display its full header. In the Authentication-Results line, look at:

  • spf=pass or fail, and the domain of smtp.mailfrom;
  • dkim=pass or fail, and the domain of header.d;
  • dmarc=pass or fail, and the domain of header.from.

If smtp.mailfrom and header.d are both on a different domain from header.from, alignment is missing.

Step 2: fix the three records

  • SPF: a single record that lists all your senders. See our SPF guides, including the one for Microsoft 365.
  • DKIM: turn on signing at every service that sends with your domain (mailbox, newsletter, invoicing). See our Microsoft 365 DKIM guide.
  • DMARC: publish at least v=DMARC1; p=none; rua=mailto:…. See our DMARC guides.

Step 3: check third-party sending services

Microsoft reminds senders to check that each sending service uses your domain, both in the envelope address (MailFrom) and in the DKIM signature, and that your SPF contains what the service asks for. In the tool's interface, look for "authenticated sending domain", "custom domain" or "DKIM": most offer two or three records to add to your DNS.

Step 4: resend and check

Resend a test message to Outlook.com and check that dmarc=pass appears in the header. Our free tools SPF check, DKIM check and DMARC check check the records from the Internet.

Check your domain for free. AttackScout reads your SPF, your DKIM and your DMARC from the Internet and tells you which one is blocking your emails. In one minute, no account. Check my domain

Frequently asked questions

I send fewer than 5,000 emails. Am I safe?

Not from this error, according to Microsoft. But Gmail and Yahoo have similar rules, and a domain without SPF, DKIM or DMARC lands in spam more often everywhere. See the Gmail and Yahoo sender requirements.

Is DMARC at p=none really enough?

For Microsoft, yes: a published DMARC record, even at p=none, and successful alignment. To protect your domain against spoofing, you will need to tighten the policy afterwards.

The error only affects emails from our newsletter tool.

The tool sends without your domain in the DKIM signature or the envelope address. Set up the authenticated sending domain in the tool (step 3).

Sources

Accessed on November 18, 2026.