When quotes and invoices from your company domain land in spam, the domain often cannot prove its mail is its own. What SPF, DKIM and DMARC each prove, what Gmail, Yahoo and Outlook require as of October 2026, and the order to set them up in.
On this page
A quote goes out on Monday and the client finds it in spam on Thursday. An invoice reminder never arrives. The website's enquiry form goes quiet because its notifications are filtered. When a UAE company's email runs on its own domain, the cause is often the same: the domain cannot prove that its mail is really its own.
Three DNS records do that proving: SPF, DKIM and DMARC. Here is what each one does, what Google, Yahoo and Microsoft require as of October 2026, and the order we set them up in. Hand the setup section to whoever manages your DNS.
What each record proves
- SPF is a list in your DNS of the servers allowed to send mail for your domain, checked against the domain in the message's hidden return address (Microsoft, Set up SPF).
- DKIM is a digital signature the sending service adds to each message, checked against a public key in your DNS. A pass means that domain signed it and nothing altered it on the way (Microsoft, Set up DKIM). It usually survives forwarding, which SPF does not (Microsoft, Set up DMARC).
- DMARC tells receivers what to do with mail that fails: nothing, the spam folder, or rejection, and asks them to send you reports (Google Workspace, Set up DMARC).
Why all three? SPF and DKIM can both pass for someone else's domain. A newsletter tool that sends with its own return address and signs with its own key passes both, and neither says anything about the company in the From line your client sees. DMARC passes only when SPF or DKIM passes for a domain that matches the From address, which is called alignment (Microsoft, Set up DMARC). So each service has to be set up to use your domain, not just added to a list.
What the big mailbox providers require
These rules cover consumer mailboxes: personal Gmail, Yahoo and AOL, Outlook.com and Hotmail. Google's do not apply to mail sent to Google Workspace accounts (Google, Email sender guidelines FAQ); company mailboxes run their own filters.
Every sender
- Gmail: since February 2024, SPF or DKIM, valid forward and reverse DNS, a TLS connection, correctly formatted messages, a spam rate below 0.3% in Google's Postmaster Tools, and DKIM keys of at least 1024 bits (Google, Email sender guidelines).
- Yahoo: SPF or DKIM, valid forward and reverse DNS, standards-compliant mail and a spam rate below 0.3% (Yahoo Sender Hub, Best practices).
Bulk senders
- Gmail treats a domain as a bulk sender once it sends around 5,000 or more messages to personal Gmail accounts in 24 hours, counting subdomains with the main domain, and the status is permanent. Bulk senders need SPF and DKIM, a DMARC record (p=none is enough), alignment, and one-click unsubscribe plus a visible unsubscribe link in marketing mail. Spam should stay below 0.1% and never reach 0.3%; Google recommends acting on unsubscribes within 48 hours. Since November 2025 Gmail has been stepping up enforcement, including temporary and permanent rejections (Google, Email sender guidelines FAQ).
- Yahoo sets no number, only "a significant volume". Bulk senders need SPF and DKIM, a passing DMARC record of at least p=none, alignment, one-click unsubscribe, and unsubscribes honoured within two days (Yahoo Sender Hub, Best practices; FAQs).
- Microsoft: since 5 May 2025, domains sending more than 5,000 emails a day to Outlook.com addresses must pass SPF and DKIM and publish DMARC of at least p=none, aligned with at least one of them (Outlook.com Postmaster, Policies). Microsoft's April 2025 update says failing mail is rejected, not sent to Junk (Microsoft, April 2025 update; Microsoft Support, error 550 5.7.515).
One newsletter to a large list can cross that line, and Gmail's status then sticks to the domain. Set up all three anyway: Google says alignment with both SPF and DKIM will likely become a requirement.

Setting it up, in order
- List every service that sends as your domain: the mail provider, the website's contact form, the CRM, the newsletter tool, the invoicing or accounting software, the booking system. Note the From address each uses.
- Find who controls the DNS. A .ae domain is registered through a registrar accredited by TDRA's .ae Domain Administration (UAE Government portal, .ae domain names; TDRA, Accredited registrars). Records are changed there, or at whichever DNS host the nameservers point to.
- Publish one SPF record that includes them all. Two records make SPF fail with a permanent error (Microsoft, Set up SPF). Each service's help pages give the value to include. SPF allows at most 10 DNS lookups, and nested includes count (Google Workspace, Troubleshoot SPF issues). Google's guide ends the record with a soft fail, ~all (Google Workspace, Set up SPF); Microsoft recommends a hard fail, -all.
- Turn on DKIM for each service, with your domain. In Google Workspace, generate a key in the Admin console (2048-bit if your DNS host supports it), publish it as a TXT record and click Start authentication; allow up to 48 hours (Google Workspace, Set up DKIM). Microsoft 365 does not sign with your custom domain until you publish two CNAME records and switch signing on in the Defender portal (Microsoft, Set up DKIM). Other platforms have their own domain authentication setting.
- Publish DMARC at p=none with a reporting address. Google suggests waiting 48 hours after SPF and DKIM, and sending reports to a dedicated mailbox, not a person's inbox (Google Workspace, Set up DMARC).
- Read the reports, fix what fails, then tighten. Google's rollout guide says a week at p=none usually shows all your mail streams (Google Workspace, Recommended DMARC rollout); we prefer a full month, so monthly invoice runs appear. Then quarantine, then reject, which Microsoft names as the goal. Phase in by time: RFC 9989, the current DMARC standard, removed the percentage tag some guides still show (RFC Editor, RFC 9989).
- Consider a subdomain for marketing mail, as Microsoft recommends, so its problems do not touch staff mail (Microsoft, Set up SPF). Gmail still counts it towards the main domain's volume.
Mistakes we see
- Two SPF records, usually because a new tool's setup added its own. Merge them.
- A website form sending "from" the visitor. The notification claims a visitor's Gmail or Yahoo address but leaves from your web server, so it fails their checks; Google's guidelines tell senders not to impersonate Gmail From addresses. Send from your own domain through an authenticated service, with the visitor in Reply-To.
- A forgotten sender under p=reject. Nobody set up the accounting software, and at reject, receivers that honour the policy turn its invoices away. Microsoft 365 rejects them outright when its recommended setting to honour DMARC is on (Microsoft, Set up DMARC).
- DNS nobody can log into, registered by a former agency or an employee who has left. Nothing above happens until the account is back in the company's name.
- Parked domains left open. A domain you never send from can still be forged. M3AAWG's best practice is an SPF record that authorises no server, no DKIM key, a DMARC policy of reject and a null MX record (M3AAWG, Protecting parked domains); Microsoft gives the same SPF and DMARC advice.
How to check it works
- Send a message from each service to a personal Gmail address. On a computer, click the arrow under the sender's name: "signed by" should show your domain, and ideally "mailed by" as well (Gmail Help, Check if your Gmail message is authenticated).
- For detail, click More, then Show original (Gmail Help, Trace an email with its full header). SPF, DKIM and DMARC each appear on their own line (Google for Developers, Gmail security requirements); you want a pass on all three, for your domain. Google's Admin Toolbox can analyse pasted headers (Google Workspace, Troubleshoot DMARC issues).
- Read the DMARC aggregate reports: XML files, usually daily, from receiving servers, listing who sent as your domain, how many messages, and the SPF, DKIM and DMARC results (Google Workspace, About DMARC reports). A familiar service failing needs fixing; an unknown source failing in volume may be someone forging your domain.
What authentication does not do
It does not put mail in the inbox. Gmail's guidelines say some legitimate messages may be marked as spam (Google, Email sender guidelines), and the spam-rate limits above show that complaints still count. Once DMARC is at quarantine or reject you can optionally add BIMI, which shows your logo beside your mail in Gmail; it needs a Verified Mark Certificate for a trademarked logo, or a Common Mark Certificate, from a certificate authority (Google Workspace, Set up BIMI).
Start with the list of senders: it is the part the DNS person cannot do alone. As part of a website or hosting project, we can check a domain's SPF, DKIM and DMARC records.
Sources
- Google, Email sender guidelines and FAQ: Gmail requirements.
- Yahoo Sender Hub, Best practices and FAQs: Yahoo requirements.
- Outlook.com Postmaster, Policies, Microsoft Tech Community, April 2025 update and Microsoft Support, error 550 5.7.515: Outlook.com high-volume requirements.
- Microsoft Learn, SPF, DKIM and DMARC: Microsoft 365 setup.
- Google Workspace Help, SPF, SPF troubleshooting, DKIM, DMARC, rollout, reports, troubleshooting and BIMI: Workspace setup and checks.
- Gmail Help, authenticated messages and full headers, and Google for Developers, Gmail security requirements: checking a message.
- RFC Editor, RFC 9989: the current DMARC standard.
- M3AAWG, Protecting Parked Domains Best Common Practices: non-sending domains.
- UAE Government portal, .ae domain names and TDRA, Accredited registrars: .ae registration.
- email deliverability
- SPF
- DKIM
- DMARC
- Google Workspace
- Microsoft 365



