Small-business operations
Why your business emails land in spam: SPF, DKIM, DMARC and Gmail’s sender rules
Some businesses find out about email authentication the day a campaign vanishes. The mail went out, the tool says delivered, and almost nobody saw it. Since February 2024 Gmail and Yahoo have set written rules for anyone sending to their users, and Gmail began tightening enforcement in November 2025. This guide explains those rules from the providers’ own pages, and the three DNS records that decide most of it.
A Diwali email that nobody sees
Picture a home-décor brand in Nashik with 9,000 customer email addresses from three years of orders. For the Diwali sale its marketing executive signs up for a bulk email tool, sets the From address to the brand’s old gmail.com account because that is the address customers know, and sends. The tool reports the send as complete. Sales do not move. A week later someone checks a customer’s inbox and finds the email in spam, if it arrived at all.
Nothing about the offer was wrong. The email failed on rules the brand did not know existed, and one of them is in Google’s own list of what not to do. The good news is that most of these rules come down to a few records on your domain and a few habits, and you can check all of them yourself.
What Gmail now requires from every sender
Google’s email sender guidelines say that “Starting February 1, 2024, all email senders who send email to Gmail accounts must meet the requirements in this section.” The rules cover delivery to personal Gmail addresses, those ending in @gmail.com or @googlemail.com. For every sender, however small, they include:
- “Set up SPF or DKIM email authentication for your sending domains.”
- Valid forward and reverse DNS for the sending servers. It matters most if you run your own mail server; if you send through Google Workspace, Zoho or an email tool, ask them to confirm it.
- “Use a TLS connection for transmitting email.”
- Keep the spam rate reported in Postmaster Tools below 0.3 per cent.
Mail that is not authenticated with SPF, DKIM and DMARC “might be marked as spam or rejected with a 5.7.26 error.” Google’s sender FAQ adds that “Starting November 2025, Gmail is ramping up its enforcement on non-compliant traffic”, with “temporary and permanent rejections.”
When does a business count as a bulk sender?
Above a certain volume the rules get stricter. Google’s FAQ defines a bulk sender as “any email sender that sends close to 5,000 messages or more to personal Gmail accounts within a 24-hour period”, and says “Messages sent from the same primary domain count toward the 5,000 limit.” Two details catch people out:
- It is one day that counts. “Senders who meet the above criteria at least once are permanently considered bulk senders.” A brand whose one big festive campaign reaches close to 5,000 Gmail addresses in a day is a bulk sender for good.
- Subdomains add up. Mail from offers.yourbrand.in and from yourbrand.in counts towards the same primary domain.
Bulk senders must also do the following, per Google’s guidelines:
- Set up both SPF and DKIM, not one or the other.
- Publish a DMARC record. “Your DMARC enforcement policy can be set to none.”
- Align the From address: “the domain in the sender’s From: header must be aligned with either the SPF domain or the DKIM domain.”
- Give marketing messages one-click unsubscribe, plus “a clearly visible unsubscribe link in the message body.”
Yahoo’s sender best practices set nearly the same floor and the same bulk duties, including a DMARC policy of “at least p=none” that must pass, and “Honor unsubscribes within 2 days”. Unlike Google, Yahoo’s FAQ says “We will not specify a volume threshold.” Microsoft followed for Outlook.com, Hotmail and Live addresses: its postmaster policy page says that from 5 May 2025 domains sending more than 5,000 emails a day to Outlook.com “must fully be compliant with SPF, DKIM, and DMARC”, that non-compliant mail goes to junk, and that it “may be rejected” if issues remain.
What do SPF, DKIM and DMARC actually do?
| Record | What it says | Where it lives | The mistake to avoid |
|---|---|---|---|
| SPF | Which servers may send mail for your domain. | One TXT record on your domain, starting v=spf1. | Two SPF records, or more than 10 DNS lookups. Either gives a permanent error, so SPF cannot pass. |
| DKIM | A signature that proves the message came from your domain and was not altered. | A public key in DNS; your mail service signs each message. | Letting a tool sign with its own domain instead of yours, or using a short key. |
| DMARC | What receivers should do when SPF and DKIM do not line up with your From address, and where to send reports. | A TXT record at _dmarc.yourdomain. | Publishing p=none and never reading the reports. |
SPF: one record, ten lookups
Most businesses add a tool, then another, and paste a fresh SPF record for each. The standard, RFC 7208, says that if a domain has more than one SPF record, the check “produces the ‘permerror’ result”. It also caps the DNS lookups SPF can trigger at 10, counting include, a, mx, ptr, exists and redirect; beyond that the result is again ‘permerror’. The include lines your tools ask for can each contain more includes, so a record with six include lines can still exceed the limit. Microsoft’s SPF guide says it directly: “having fewer than 10 include: statements doesn’t guarantee fewer than 10 DNS lookups.” Merge everything into one record and count. To count, start with every include, a, mx, ptr, exists and redirect in your own record, then look up each include’s TXT record (for example, nslookup -type=txt _spf.google.com) and add the same terms inside it, and inside any include it contains; ip4 and ip6 entries cost nothing.
DKIM: sign as yourself
Google says sending to Gmail “requires a DKIM key of 1024 bits or longer” and recommends 2048 bits “if your domain provider supports this”. Google Workspace and Zoho Mail let you choose 2048 when you create the key; Microsoft 365’s PowerShell setting lists 1024 as the default, so ask for 2048. Every email tool that sends for you should sign with your domain, not its own. If Gmail shows “via” and another domain next to your name, its help page explains why: “The domain it was sent from doesn’t match the domain in the ‘From:’ address.”
DMARC: start at none, then move
DMARC ties the two together. It checks that the domain which passed SPF or DKIM matches the domain in your From address (for SPF, the domain checked is the hidden bounce or Return-Path address, not the From address), and tells receivers what to do when it does not: nothing (p=none), treat as suspicious (p=quarantine) or refuse (p=reject). Google, Microsoft and Zoho all describe the same path. Google’s Workspace DMARC page recommends starting at none and, “Over time, change the receiver policy to quarantine (or reject).” Microsoft’s Outlook.com announcement advises “moving gradually (none → quarantine → reject) to avoid unintended mail loss.”
p=none satisfies all three providers, but on its own it stops nobody from sending mail in your name. Its value is the reports you receive at the rua address. Read them for a few weeks, fix the senders that fail, then tighten. The DMARC standard itself was updated in May 2026: RFC 9989 replaces RFC 7489, removes the pct tag and adds np and t. Most provider help pages still show the older tags, so you will see both for a while. RFC 9989 also says that domains whose users might post to mailing lists should not publish p=reject. If such a domain still wants it, the RFC asks for at least a month at none and an equally long period at quarantine, reading the reports, and says any domain that publishes p=reject must DKIM-sign its mail. One workable pattern is to stop at quarantine on the main domain and use reject only on a domain kept for marketing.
Do not send bulk mail from a gmail.com address
Back to the brand in Nashik. Google’s guidelines say: “Don’t impersonate Gmail From: headers. Gmail will begin using a DMARC quarantine enforcement policy, and impersonating Gmail From: headers might impact your email delivery.” A bulk tool sending as yourbrand@gmail.com is doing exactly that, because the tool is not Gmail. Send from your own domain, set up through the tool with SPF, DKIM and DMARC, and keep the gmail.com account for one-to-one mail.
One-click unsubscribe is a header, not a footer link
This is where many setups fall short. Google’s FAQ says “Including a mailto link in the body of your messages doesn’t meet our one-click unsubscribe requirement”, and that a link to “a landing or other type of web page” does not comply either. What Google wants are two headers defined in RFC 8058: a List-Unsubscribe header with an https address, and “List-Unsubscribe-Post: List-Unsubscribe=One-Click”. The RFC also requires a DKIM signature covering both headers. Gmail may then show its own unsubscribe link next to your name, but Google says only for messages that pass “Google’s automated eligibility checks”.
Many email tools can add these headers, but check rather than assume: open a sent campaign in Gmail, choose “Show original” and look for both lines. The rule applies to marketing messages; Google says “Transactional messages are excluded”, such as password resets and order confirmations. Google recommends honouring an unsubscribe “within 48 hours”, Yahoo says two days, and your list should drop the address in that time without anyone touching a spreadsheet.
What spam rate does Gmail allow?
Google’s guidelines say to keep spam rates reported in Postmaster Tools below 0.10 per cent and never to reach a spam rate of 0.30 per cent or higher. The FAQ explains why both numbers matter: rates above 0.1 per cent already “have a negative impact on email inbox delivery for bulk senders”, and a bulk sender above 0.3 per cent is “ineligible for mitigation” until it stays below that for “7 consecutive days”. One complaint in a thousand is the target. A list bought from a data seller, or a list nobody has emailed in two years, can blow through that in one send.
Google’s guidelines are plain about where those complaints come from: “Don’t purchase email addresses from other companies”, and “Avoid opt-in forms that are checked by default”. They also warn against “sudden volume spikes”, so a brand that mails 300 people a week should not send to 9,000 on Dhanteras without building up first. Google also says “Google doesn’t track open rates”, so do not judge reputation by opens.
To see the numbers Google sees, add your domain to Postmaster Tools. Its Compliance status dashboard shows whether you meet each requirement. Small senders may see gaps: Google says data “might not include all data on days when outgoing email volume is low.”
Setting it up on Google Workspace, Microsoft 365 or Zoho Mail
Each provider publishes the exact records. The pattern is the same everywhere:
- SPF. Google’s SPF page gives v=spf1 include:_spf.google.com ~all for a domain that sends only through Workspace. Zoho’s SPF page gives v=spf1 include:zohomail.com -all. Zoho also runs an India data centre (you sign in at mail.zoho.in); if your account is there, copy the exact SPF value your own Zoho admin console shows rather than one from any guide, this one included. Either way, “There should be only a single SPF record for the domain.” Add a tool’s include only if its set-up guide asks for it, usually because it sends with a bounce (Return-Path) address on your domain. For most email tools, DKIM signing as your domain is what makes DMARC pass, so do that first.
- DKIM. Generate the key in the admin console (Google’s DKIM page; Zoho’s DKIM page), choose 2048 bits, publish it in DNS, and switch signing on. Google says it “can take up to 48 hours” to start working. Do the same inside every email tool, so each signs as your domain.
- DMARC. Google says to “Allow 48 hours after setting up SPF and/or DKIM before setting up DMARC.” Then publish a record such as Zoho’s example: v=DMARC1; p=none; rua=mailto: followed by an address someone actually reads.
- Test. Send to someone else’s Gmail address, such as a colleague’s personal account (Google says you “can’t verify DKIM is on by sending yourself a test message”), open “Show original”, and check that SPF, DKIM and DMARC all say PASS.
Whoever manages your domain’s DNS, often the person who built your website, needs to add these records. If you are not sure who that is, our guide to choosing a marketing agency explains why the domain should be registered in your name.
What about Indian rules?
There is no Indian law that sets SPF, DKIM or DMARC for private businesses, as far as we could find. CERT-In recommends them: its baseline controls for MSMEs (1 September 2025) say “Protect email and messaging systems from phishing and spoofing using SPF, DKIM, DMARC.” TRAI’s commercial communication rules, which our guide to business SMS and calls covers, appear to be written for messages and voice calls on telecom networks: the February 2025 amendment ties commercial communication to registered headers and number series, and mentions email only as a way to complain.
Consent is the bigger Indian question. Under the Digital Personal Data Protection Act, 2023, consent must be “free, specific, informed, unconditional and unambiguous with a clear affirmative action”, and the ease of withdrawing it must be “comparable to the ease with which such consent was given”. These provisions commence on 13 May 2027. Whether a given marketing email needs fresh consent is a legal question; a pre-ticked box will not meet that standard, and Gmail’s guidelines already tell senders to avoid it. Our DPDP guide covers the rest. This is general information, not legal advice.
One last warning, from CERT-In’s August 2026 advisory on attacks against Microsoft 365: attackers who take over a mailbox can send from “authenticated email accounts that successfully pass SPF, DKIM, and DMARC validation.” These records stop others pretending to be you. They do not stop someone who has got into your account, and the same advisory describes attackers getting past two-step verification, including by tricking staff into authorising attacker-controlled device codes. Turn on two-step verification for every mailbox, and teach staff never to approve a sign-in or enter a code they did not start.
A checklist for your domain
- Bulk email goes out from your own domain, never from a gmail.com address.
- The domain has exactly one SPF record, covering every service that sends with a Return-Path on your domain, within 10 lookups.
- DKIM is on, at 2048 bits where possible, in your mailbox provider and in every email tool.
- A DMARC record exists, its reports go to someone who reads them, and there is a date to move from none to quarantine.
- A test email to an outside Gmail address shows SPF, DKIM and DMARC as PASS, with no “via”.
- Marketing emails carry both one-click unsubscribe headers and a visible unsubscribe link, and unsubscribes take effect within 48 hours.
- The domain is in Postmaster Tools, and someone checks the spam rate and compliance status after each big send.
- No bought lists, no pre-ticked boxes, and volume built up gradually before festive campaigns.
- Every mailbox has two-step verification, and staff know never to approve a sign-in they did not start.
QUESTIONS
Common questions
What are Gmail’s bulk sender requirements?
A sender that sends close to 5,000 or more messages to personal Gmail accounts in 24 hours, counted across its primary domain, must set up SPF and DKIM, publish a DMARC record (p=none is enough), align the From domain, support one-click unsubscribe on marketing mail, and keep its spam rate below 0.3 per cent. Once a bulk sender, always one.
Why are my business emails going to spam?
The usual causes are missing or broken SPF, DKIM or DMARC records, sending bulk mail from a gmail.com address through another tool, a high complaint rate from old or bought lists, or a sudden jump in volume. Send a test to an outside Gmail address, open “Show original”, and check that SPF, DKIM and DMARC say PASS.
Is DMARC p=none enough?
It meets the minimum for Gmail, Yahoo and Outlook.com, but it does not stop anyone sending mail in your name. Use the reports to fix your real senders, then move to p=quarantine and, on domains not used for everyday staff mail, p=reject. Google, Microsoft and Zoho all describe that gradual path.
Can I have two SPF records?
No. Under RFC 7208 two SPF records give a permanent error (‘permerror’), so SPF cannot pass. Merge into one record the services that need SPF (your mailbox provider and any tool whose set-up guide asks for an include), and keep the total DNS lookups at 10 or fewer, counting the includes inside each include.
Do Indian laws require SPF, DKIM and DMARC?
We found no Indian law that requires them for private businesses. CERT-In recommends all three in its baseline controls for MSMEs. The practical requirement comes from Gmail, Yahoo and Outlook.com, which apply their rules to anyone sending to their users, including Indian businesses.
REFERENCES
Sources and further reading
Each link was opened and checked on .
- Google: Email sender guidelines
- Google: Email sender guidelines FAQ
- Google: Set up Postmaster Tools
- Google: Postmaster Tools dashboards (Compliance status)
- Google: Why a message shows “via” another domain
- Google Workspace: Set up SPF
- Google Workspace: Set up DKIM
- Google Workspace: Set up DMARC
- Yahoo Sender Hub: Sender best practices
- Yahoo Sender Hub: FAQs
- Microsoft: Outlook.com postmaster policies
- Microsoft Tech Community: Outlook’s new requirements for high-volume senders (2 April 2025, updated 30 April 2025)
- Microsoft Learn: Set up SPF for Microsoft 365
- Microsoft Learn: Set up DKIM for Microsoft 365
- Zoho Mail: SPF configuration
- Zoho Mail: GDPR compliance (data centre locations)
- Zoho Mail: DKIM configuration
- Zoho Mail: DMARC policy
- IETF RFC 7208: Sender Policy Framework (April 2014)
- IETF RFC 8058: One-click unsubscribe (January 2017)
- IETF RFC 9989: DMARC (May 2026)
- TRAI: Telecom Commercial Communications Customer Preference (Second Amendment) Regulations (12 February 2025)
- CERT-In: 15 Elemental Cyber Defense Controls for MSMEs (1 September 2025)
- CERT-In: Advisory CIAD-2026-0037 (7 August 2026)
- Digital Personal Data Protection Act, 2023 (India Code)
