
"Who Can Send Email as You?"
Imagine receiving an email from someone you've trusted for twenty years. Their name is familiar. Their email address looks right. They ask you to change the bank account for your next payment.
Would you question it?
Most of us want to believe the people we've built relationships with. Unfortunately, someone else can sometimes put a familiar name and domain on an email they never sent.
Now picture that email appearing to come from your practice or nonprofit. The damage isn't only a misdirected payment. It's the trust you've spent years building.
This is not simply about email security. It's about protecting the trust behind every message. Three small pieces of technology (SPF, DKIM and DMARC) can help protect that trust.
The weeks ahead bring holiday newsletters, year-end invoices and donation appeals before GivingTuesday on December 1. These are exactly the messages impersonators like to copy.
Mailbox providers increasingly expect these records. Google's sender guidelines ask every sender to Gmail to use SPF or DKIM, and require SPF, DKIM and DMARC from senders of 5,000 or more messages a day to personal Gmail accounts. Microsoft set similar requirements for high-volume senders to Outlook.com, Hotmail and Live addresses from May 5, 2025. For smaller senders, the same records help receiving systems recognize genuine mail from you. They don't guarantee inbox placement; spam filtering and sender reputation still play a part.
A guest list, a wax seal and a house rule
SPF is the guest list. It's a record in your domain's settings that identifies the servers and services authorized to send mail for your domain. It checks the behind-the-scenes sending address, which isn't always the address people see in Outlook.
DKIM is the wax seal. It adds a digital signature tied to your domain. The receiving system checks the seal to confirm which domain signed the message and that the signed content wasn't changed. Like a real seal, it shows where a letter came from, not whether the writer is trustworthy.
DMARC is the house rule. It connects the other two to the name people actually see. DMARC checks that SPF or DKIM passes and lines up with the domain in the visible From address; at least one aligned result is needed. It also tells receivers what to do with messages that fail, and sends you reports. A policy of "none" only watches. It's a starting point; the Cyber Centre recommends moving toward enforcement (quarantine, then reject) once legitimate senders are verified, as does Microsoft.
What these records can't do
They can't stop someone from registering a look-alike domain. And if a staff member's real email account is compromised, mail sent from it can pass all three checks. SPF, DKIM and DMARC don't replace multi-factor authentication, good account security, or an independent call-back before any payment or banking change.
Where this fits in your Cyber Armor
In the Seven Layers of Cyber Armor, email authentication most directly strengthens Identity, helping receivers confirm that mail carrying your domain is really yours. It also strengthens Proactive, because DMARC reports show who is sending as you before a client is fooled. As a secondary benefit, it gives you a clearer answer if a cyber Insurance application asks about email security.
For the curious
One SPF record per domain. Two SPF records cause errors, and SPF allows only 10 DNS lookups, which a long list of add-on services can exceed (Microsoft Learn).
Microsoft 365 and DKIM. Mail from the starter onmicrosoft.com address is signed automatically, but custom domains need DKIM configured and verified (Microsoft Learn). A message signed only with onmicrosoft.com may not satisfy DMARC alignment for your own domain.
Third-party senders. Newsletter, billing and booking platforms that send "as you" may need their own setup.
Unused domains. After confirming that no legitimate system sends from a domain, you can publish SPF "-all" and DMARC "p=reject" for it (Cyber Centre ITSP.40.065).
The trust behind every message
Every email carries more than information. It carries a little of the trust we've spent years building.
SPF, DKIM and DMARC may sound technical, but their purpose is deeply human: helping protect our identity, our relationships and the people who trust us.
Start by discovering who is allowed to send email on your behalf. You don't have to solve everything today.
And if you'd appreciate a second pair of eyes, MicroAge Richmond Team Jahan is always happy to help.
Real People • Real Solutions.
One practical action this week
Make a "who sends as us" list. Ten minutes to get started.
Write down who manages your domain name and its settings (often your registrar or web host), and who in your office can sign in.
List every service that sends email using your domain: your main email system, plus any newsletter, billing, booking, website-form or donor tools.
Ask whoever manages your email whether SPF, DKIM and DMARC are in place, and what your DMARC policy is today.
And if you'd appreciate a second pair of eyes, MicroAge Richmond where Team Jahan is always happy to help. Real People • Real Solutions.
Sources
Canadian Centre for Cyber Security, Implementation guidance: email domain protection (ITSP.40.065 v1.1), August 2021
Microsoft Learn, Email authentication in Microsoft 365, updated July 3, 2026
Microsoft Learn, Set up SPF for your Microsoft 365 domain, updated July 3, 2026
Microsoft Learn, Set up DKIM to sign mail from your Microsoft 365 domain, updated July 3, 2026
Microsoft Learn, Set up DMARC to validate the From address domain, updated July 17, 2026
Microsoft Defender for Office 365 blog, Outlook's new requirements for high-volume senders, April 2025 (updated April 29, 2025)
Google, Email sender guidelines
