Skip to main content
Tutorials

Outlook rejected email from domains without DMARC for four days. It was a bug, the next one might not be (and how to set it up properly with Resend)

From Nov 5 to 9, Outlook bounced email from domains with no DMARC record. It was a bug, but it shows which record to add with Resend and how to check it.

Israel Palma Sebastià

This blog belongs to CREA.MBA, a Next.js boilerplate with auth, payments and an admin panel already set up. See what's included

A user signs up with a Hotmail address, forgets their password and asks for a reset link. It never arrives. Resend accepts the send, your app logs no error, and you have no idea anything went wrong.

That's what happened to a lot of SaaS products between November 5 and 9. Outlook.com, Hotmail and Live rejected email from domains that had no DMARC record, even if they only sent a handful of emails. The server answered with this:

550 5.7.1 Message rejected: Message lacks SPF/DKIM/DMARC Auth Records (AS9031519)

Microsoft acknowledged it on its service health dashboard (EX1545193): an update to its anti-spam rules was flagging and blocking mail by mistake. It was rolled back around midday on November 9. So this isn't a new rule, and if it hit you during those days, resend anything important: a 550 is a permanent rejection and nobody retries it.

But the fact that it was a bug doesn't mean you can skip it. Since May 2025 Microsoft requires SPF, DKIM and DMARC from anyone sending more than 5,000 emails a day, and Gmail and Yahoo have done the same since February 2024. What the incident did, for four days, was show how many domains were only half set up.

If your SaaS sends verification emails, password resets or team invitations, these are the ones that matter, because without them the user is locked out.

What each record checks

Three DNS records, and it's worth keeping them apart:

  • SPF lists which servers are allowed to send email on behalf of your domain.
  • DKIM signs every message with a key whose public half lives in your DNS. If anyone tampers with the message in transit, the signature no longer matches.
  • DMARC ties both to the address the user sees in the From field. A message passes DMARC if SPF or DKIM passes and is aligned with the From domain. It also tells the receiver what to do with messages that fail.

The detail almost everyone misses: verifying your domain in Resend gets SPF and DKIM working, but it doesn't create a DMARC record. You have to add that one yourself, and it's the one missing from nearly every domain that bounced those days.

Step 1: verify the domain in Resend

If it's already verified, skip this. If not, go to Domains in the Resend dashboard, add your domain, and it gives you the records for your DNS: a DKIM record at resend._domainkey, plus the SPF and MX records on a sending subdomain. Copy them exactly as shown, because the values depend on the region.

With that in place, Resend signs your email with DKIM for your domain, and that signature is what DMARC will align against.

Step 2: make sure the From uses that domain

Sounds obvious, but this is where alignment breaks. If you verify yourapp.com and send from hello@another-domain.com, DKIM passes for one domain while the From says another.

In the CREA.MBA boilerplate the sender comes from an environment variable:

// src/lib/email/config.ts
export const emailConfig = {
  from: process.env.EMAIL_FROM || 'noreply@localhost',
  replyTo: process.env.EMAIL_REPLY_TO,
  resend: {
    apiKey: process.env.RESEND_API_KEY || '',
  },
} as const;

So in production it has to be an address on the domain you verified:

EMAIL_FROM="YourApp "
RESEND_API_KEY=re_...

If it's left as noreply@localhost, isEmailConfigured() returns false and nothing gets sent, which is at least a failure you can see.

Step 3: the DMARC record

A TXT record at _dmarc.yourapp.com:

v=DMARC1; p=none; rua=mailto:dmarc@yourapp.com
  • p=none tells the receiver not to do anything special with messages that fail. It's the safe starting point: it doesn't change how Gmail or anyone else treats you, and it takes you out of the "domains without DMARC" group, which is the one that got rejected in November.
  • rua= is the address where receivers send you daily reports on who is sending email as your domain and whether it passes. It has to be a mailbox that actually receives mail.

rua is the part people forget most. Without it you do have DMARC, but you're flying blind: if a service you use (your invoicing tool, your CRM, your contact form) sends email as your domain and fails, you'll never know. We know because it was happening to us: until this week, crea.mba's DNS had v=DMARC1; p=none; with no rua. Compliant, and silent. We noticed while writing this post and added the rua.

Step 4: check it

From the terminal:

dig TXT _dmarc.yourapp.com +short

And the check that really counts: send an email from your app to an Outlook or Hotmail account, open the raw message (View message source) and look for the Authentication-Results header. You want all three:

spf=pass ... dkim=pass ... dmarc=pass

If you see dkim=pass but dmarc=fail, the problem is alignment: go back to step 2.

Step 5: tighten it once you have data

p=none is just the start. After a couple of weeks of rua reports you'll know which services send email as your domain. Once everything legitimate passes DMARC:

v=DMARC1; p=quarantine; rua=mailto:dmarc@yourapp.com

Later, if nothing legitimate lands in quarantine, move to p=reject. That's the step that actually stops people from sending email pretending to be your domain. There's no rush, and doing it without reading the reports is the fastest way to block your own invoices.

The takeaway

Three records you set up once and never think about again, until a user writes in to say the email never arrived. Checking today takes ten minutes. Finding out through a support ticket can cost you days of users who couldn't log in.

CREA.MBA ships with email already wired up through Resend and React Email: verification, password reset, organization invites and notifications. What the code can't do for you is touch your DNS, so this checklist is your part of the job on deploy day.

Have you checked whether your emails are actually reaching Hotmail?

EmailResendDMARCNext.jsDeliverability

Enjoyed this article?

Subscribe for more tutorials and tips on building products with AI