REBRAND ANNOUNCEMENT

From 1 July 2026 Metrofile Cloud is back to IronTree. Same team. Same service. A name we’ve originally built and have carried with pride for over 20 years.

Cyber Security

•

What the Outlook email incident tells us about DMARC

What the Outlook email incident tells us about DMARC

You send a quote, follow up on a customer enquiry, or email an invoice. When that email doesn’t reach the right person, it can delay payments, hold up decisions, and leave customers waiting. You also need customers to be able to trust emails sent in your business’s name. Email authentication helps with both, but it needs to be set up correctly and maintained as your systems change. 

The Outlook incident was rolled back 

In early November 2026, MailRoute reported that Microsoft’s consumer email services were rejecting some legitimate messages from domains without a DMARC record. In its 10 November update, MailRoute said Microsoft had traced the problem to an incorrect spam-filtering rule and rolled back the change. The impact ended on 9 November. 

The rejections were caused by a filtering error, rather than a new DMARC requirement for every business. If important messages bounced during the incident, check the delivery failure details and resend them where appropriate. 

Authentication is already a requirement for some senders 

Microsoft already requires domains sending more than 5,000 emails a day to its consumer services to meet SPF, DKIM, and DMARC requirements. Google requires SPF or DKIM for all senders to personal Gmail accounts, and SPF, DKIM, and DMARC for bulk senders. These rules still apply. 

There is no confirmed new Microsoft deadline for every small sender. Even so, the requirements already in place are a good reason to check your own setup. Doing this before you have a delivery problem gives your team time to identify issues and fix them carefully. 

What does DMARC actually do? 

DMARC (Domain-based Message Authentication, Reporting, and Conformance) helps receiving email systems check whether an email is authorised to use the domain in its visible “From” address. It works with two other authentication methods:  

  • SPF (Sender Policy Framework), which identifies the servers authorised to send email for a domain.  
  • DKIM (DomainKeys Identified Mail), which adds a digital signature that lets receiving systems verify the signing domain and whether signed content has changed.  

For DMARC to pass, at least one of these checks must pass and align with the domain the recipient sees as the sender. DMARC also lets a domain owner specify how receiving systems should handle messages that fail.  

This matters because criminals can forge a sender address to make an email look as though it came from your business. Properly enforced DMARC helps receiving systems reject those attempts to use your domain.  

A basic record is a starting point 

A policy of p=none asks receivers to take no action based on a DMARC failure. It is useful during setup, but it does not instruct them to block someone spoofing your domain. Reporting also needs to be configured, because a basic record alone does not tell reports where to go. 

Before moving towards quarantine or reject, identify legitimate sending services, correct any authentication problems, and check the results. Include your accounting platform, CRM, website forms, marketing tools, and support system. An overlooked service could have genuine emails rejected when you tighten the policy. Keep reviewing reports as those services change. 

Managing DMARC yourself vs getting support 

Your IT team can manage DMARC if it has the skills, access, and time. The work continues after setup: someone needs to review reports, investigate failures, and check new sending services before they go live. 

For example, your team’s Microsoft 365 email may authenticate correctly while your invoicing platform uses different settings. Tightening the policy without checking that platform could stop invoices reaching your customers. 

IronTree offers Sendmarc to help businesses implement and manage DMARC, SPF, and DKIM, with reports to show who is sending emails using your domain and help identify issues that need attention. Sendmarc also supports ongoing monitoring and a gradual move towards stronger enforcement, so you have support with both the initial setup and the work that follows.  

Trusting someone with your business email 

It’s understandable to be cautious about letting a new provider make changes that could affect your email. Setting up DMARC does not require you to move your mailboxes or replace your email platform. It involves checking your domain records, sending services, and authentication results.  

IronTree has spent more than 20 years helping South African businesses protect their data and keep business-critical systems running. Our Sendmarc offering brings that local support to managing your email authentication, with people you can turn to when your setup changes or something needs attention.  

Not sure where your domain stands? Speak to IronTree about Sendmarc and getting your business’s email authentication in order. 

Share This Article

LinkedIn
X/Twitter
Facebook
WhatsApp

Related Articles

business email compromise. the scam hiding inside ordinary work
Cyber Security
Business Email Compromise: The Scam Hiding Inside Ordinary Work
AI Is Making Server Hardware More Expensive. Is Cloud Hosting a Smarter Option for South African SMBs
All
AI Is Making Server Hardware More Expensive. Is Cloud Hosting a Smarter Option for South African SMBs?
How IronTree VPS Hosting is Powering South Africas SMBs to Scale Smarter
Hosting
How IronTree VPS Hosting is Powering South Africa’s SMBs to Scale Smarter