Outlook Is Blocking Email Without DMARC. Does Your Software Send Any?
Outlook.com has started rejecting email from domains without a DMARC record. If any of your custom software sends email on your behalf, it's worth checking before messages start quietly disappearing.
Outlook.com has started rejecting email from domains that don't have a DMARC record set up. Most coverage of this has been aimed at marketing teams worried about newsletters landing in spam. But DMARC doesn't care whether an email came from Mailchimp or from a script you had written three years ago that quietly emails invoices every month. If your domain sends mail and that domain has no DMARC policy, some of it is now going to bounce or vanish.
This matters more for business owners than the headlines suggest, because a lot of the email your business sends isn't sent by a person at all. It's sent by software.
What DMARC actually does, in plain terms
Three bits of DNS configuration decide whether an email claiming to be from your domain gets trusted:
- SPF lists which servers are allowed to send mail for your domain.
- DKIM adds a signature to each message so the receiving server can check it wasn't altered in transit.
- DMARC is the policy that tells receiving servers what to do if SPF or DKIM checks fail, reject it, quarantine it, or let it through anyway.
Without a DMARC record, there's no instruction. Outlook's change means that gap is no longer treated as neutral. No policy is now closer to "treat with suspicion" than "ignore".
Where this quietly affects custom software
Think about everything in your business that sends email without a human clicking send:
- An invoicing system emailing PDFs to clients
- A booking tool sending confirmations and reminders
- A password reset or account verification email from a customer portal
- An internal tool emailing a daily report to a manager
- A webhook handler that fires off an alert when something fails
Every one of these typically sends "as" your domain, often through a transactional email service like Postmark, SES or SendGrid rather than your normal office email. That's fine, and it's the right way to do it. But it only works reliably if SPF, DKIM and DMARC are all configured correctly for that sending domain or subdomain, and kept up to date whenever you add a new service that sends email on your behalf.
The failure mode nobody notices straight away
The nasty part of this isn't a dramatic outage. It's silence. A client doesn't get their invoice. A customer never receives their password reset link and assumes your site is broken. A manager stops getting the daily report and doesn't mention it for three weeks because they didn't know to expect it. Nothing in your software throws an error, because as far as your system is concerned, the email was sent. What happens to it after it leaves your server is a separate problem, and it's one that doesn't show up in your logs unless you're specifically watching for bounces and rejections.
I've written before about automation nobody remembers building, and email sending is a classic example. It gets set up once, it works for years, and then a receiving provider changes its policy and it stops working with no obvious trigger. The code hasn't changed. The outside world has.
What to actually check
You don't need to become an email infrastructure expert to get this right, but it's worth running through a short list:
- Does your main domain have a DMARC record at all? A quick DNS lookup for
_dmarc.yourdomain.co.ukwill tell you. - If you send transactional email through a service like Postmark, SES, SendGrid or Resend, do you know which domain or subdomain it sends from, and is that one properly authenticated too?
- Is your DMARC policy actually enforcing anything, or is it set to
p=none, which reports problems but doesn't stop them? A lot of domains have a DMARC record that technically exists but doesn't do much. - Has anyone added a new email tool, CRM, or marketing platform in the last year without updating SPF? Each new sender needs to be included or it can break the others.
- Do you have any way of seeing bounced or rejected transactional email, or does it just disappear?
If the honest answer to most of these is "I don't know", that's not unusual. This sits in the gap between "who manages the website" and "who manages email", and it's rarely anyone's clear job once the original setup is done.
Why this is worth fixing properly, not just patching
The temptation when something like this breaks is to find the one setting that's wrong and move on. But DMARC problems tend to be a symptom of email sending being bolted onto a domain over time without anyone keeping a map of what's sending from where. If your invoicing tool, your booking system, your CRM and your marketing platform are all sending as your domain, each one needs to be accounted for in SPF and authenticated with DKIM, and the DMARC policy needs to actually reflect that setup rather than guess at it.
This is the kind of thing that's quick to check and genuinely satisfying to get right once, rather than something to revisit every time a provider changes its rules. If you're not sure whether the software sending email on your behalf is set up to survive changes like Outlook's, it's worth a proper look before a client tells you their invoice never arrived.