Built this week · That's something I need
Who else can send email as your business?

Did you know anyone can send an email that says it's from your business?
What I set out to fix
Plain email lets the sender type whatever they like in the "from" line, the same way you can write any return address on an envelope.
Scammers use that. An email that looks like it's from you, asking your client to pay or to send something, is more likely to be believed.
There's a setting that tells other mail systems what to do with those fakes. It's called DMARC, and it's a short line of text on your web address. This morning, mine went to the strictest setting: reject.
How I did it
When I set up Microsoft 365 for my business email on 30 September, the domain came with a ready-made email security setting from my domain company, already on reject. I took it off so Microsoft's mail would work, and built it back up step by step. Here's why.
DMARC leans on two other checks. One checks the mail came from a server you've allowed (SPF). The other checks a signature your mail system puts on each email (DKIM). Your real mail passes if either one checks out for your address. If something sending in your name passes neither when you switch on reject, your own real mail can get bounced.
So I followed Microsoft's own advice and did it in three steps:
| When | Setting | What it asks other systems to do with a fake |
|---|---|---|
| 1 October | None, with reports | Nothing. Just report what's being sent as me |
| 30 October | Quarantine | Mark it, usually into junk |
| 13 November | Reject | Turn it away |
The reports are the key part. Google and Microsoft send a small file listing the mail they've seen from my address and whether it passed. They go to their own address, and a rule files them in their own folder.
What went wrong, and the fix
Two things.
First, I moved to quarantine too soon. On 30 October I read one report, from Google, covering one email. It passed, so I stepped up. Three earlier reports sat unread. Nothing broke, but one email isn't much proof, and I knew it.
So this time I read every report before touching anything. That's where the second problem came in. The reports arrive as attachments, and the tool Claude uses to read my Outlook couldn't open them. So Claude downloaded all seven through Outlook in my browser and added them up.
Seven reports, 20 emails, every one passed both checks, and every one came from Microsoft's own servers. Nothing else turned up in the reports sending as me. Then I changed the line and checked it was live.
What I learnt
The change itself is one line. The work before it is reading the reports, to be sure my own mail would still get through.
One good result isn't enough to step up on. I'd tell a client that, and I didn't do it myself the first time.
The thing to watch when you step up is your own real mail. A booking system, an invoicing app or a website form that sends in your name, and isn't set up for these checks, can start landing in junk or bouncing. I only had Microsoft sending for me, so mine was simple.
DMARC also has limits. It works on your exact address. It doesn't stop a scammer who sets up a look-alike address, or one who gets into your real email account. The Australian Signals Directorate's own example of invoice fraud is the second kind: a supplier's email account broken into, and real invoices sent out with the bank details changed.
What it could mean for you
If your business email is on your own web address, it's worth knowing three things.
Have you got DMARC, and what's it set to? Set to "none", it only watches, and other systems aren't asked to do anything about fakes. Ask whoever looks after your email.
Who can get into your email? A strong password and a second step at sign-in, like a code on your phone, make it much harder for someone to get into your real account.
How does your business check a change of bank details? The Australian Signals Directorate's advice is to check with the person separately, on contact details you already know are right.
The first is a line of text. The other two are about people and habits.
When I do a Workflow Audit, part of the day is an AI and email check, done with whoever looks after your email, including who can get into it.
The workings
- What DMARC does and doesn't do: Microsoft Learn, "Set up DMARC to validate email in Microsoft 365" and "How email authentication works in Microsoft 365", and the Australian Signals Directorate's "How to combat fake emails" and "Protecting against business email compromise" (cyber.gov.au), read 13 Nov 2026.
- 1 Oct: DKIM signing on, DMARC set to none with reports to their own address. A test email showed SPF, DKIM and DMARC all passing.
- 30 Oct: quarantine, on Google's 28 Oct report (one email, passed). The 15, 18 and 27 Oct reports weren't read.
- 13 Nov: 7 reports since 30 Oct (six from Google, for 29, 30, 31 Oct and 2, 9, 11 Nov, and one from Microsoft, for 29 Oct, report dates in UTC). 20 emails, all passed DKIM and SPF, none failing, all from Microsoft's servers. Reject live the same morning.
Newsletter
A short email from me now and then about AI changes that matter to small businesses.
Sign up to the newsletter