1. Authenticate your domain (SPF, DKIM, DMARC)
Unauthenticated mail is the most common reason for the spam folder, and Gmail and Yahoo now reject a lot of it outright.
- SPF lists the servers allowed to send for your domain. Every service that sends as you (mailbox, newsletter tool, CRM, website) must be included. Check SPF.
- DKIM signs each message. Turn it on in every sending service, using your own domain. Check DKIM.
- DMARC ties them to the From address and tells receivers what to do with failures. Start with
p=none. Check DMARC.
The From domain must align with SPF or DKIM. Sending “from” [email protected] through your own server, or from your domain through a tool that signs with its own domain, fails DMARC.
2. Meet the Gmail and Yahoo sender rules
Since February 2024, Gmail and Yahoo require every sender to have SPF or DKIM, valid forward and reverse DNS for the sending IP, TLS for delivery, and a spam complaint rate below 0.3%. If you send 5,000 or more messages a day to Gmail, you also need:
- SPF and DKIM, plus a DMARC record (
p=noneis enough), with the From domain aligned; - one-click unsubscribe (the
List-UnsubscribeandList-Unsubscribe-Postheaders) on marketing mail, with unsubscribes processed within two days; - a complaint rate kept well below 0.3%, ideally under 0.1%. Gmail’s Postmaster Tools shows yours.
3. Check your sending IP and domain reputation
- Blocklists: run a blacklist check. A Spamhaus or Barracuda listing sends mail to spam or gets it rejected.
- Reverse DNS: the sending IP should have a PTR record that resolves back to the same IP. Shared hosting and sending services handle this; self-hosted servers often don’t.
- Shared IPs: on cheap hosting or a free sending plan you share an IP with other senders and their reputation. Consider a reputable sending service, or a dedicated IP once your volume is steady.
- New domains and IPs have no history. Start with low volume to engaged recipients and increase gradually over a few weeks.
4. Review the message itself
- Send a plain-text part along with HTML. Avoid image-only emails.
- Avoid link shorteners and links to domains with a poor reputation. Link to your own domain.
- Keep the From name and address consistent, and use a real Reply-To that someone reads.
- Make the subject match the content. Misleading subjects drive complaints.
- Large attachments, especially .zip or Office files with macros, are treated with suspicion. Link to files instead.
Content matters less than most people think. Authentication and reputation decide most cases.
5. Clean up who you send to
- Only email people who asked for it. Bought or scraped lists contain spam traps that damage your reputation.
- Remove addresses that bounce, and people who haven’t opened or clicked in six to twelve months.
- Make unsubscribing easy. Someone who can’t unsubscribe clicks “Report spam” instead, which hurts much more.
6. Separate transactional and marketing mail
Send receipts, password resets and notifications from a different subdomain (for example mail.example.com) or a different sending service from newsletters. A bad campaign then can’t drag your password resets into spam.
7. Diagnose a specific message
Open a message that landed in spam, copy its full headers and paste them into the email header analyzer. It shows whether SPF, DKIM and DMARC passed, whether the domains aligned and which server handled each hop. That usually points straight at the problem.
Frequently asked questions
Each provider uses its own filters and reputation data. Gmail weighs authentication, alignment and recipient engagement heavily. Check that SPF, DKIM and DMARC all pass and align, and look at Gmail Postmaster Tools for your domain’s reputation and complaint rate.
They are required, but not enough on their own. They prove who sent the message; reputation, complaint rate and list quality decide whether receivers want it.
Usually a few weeks of consistent, wanted mail. Fix authentication, stop sending to unengaged or bought addresses, keep complaints low, and reputation recovers gradually.
Most forms send from the web server without SPF or DKIM, often using the visitor’s address as From. Send through an authenticated SMTP account using your own address as From and the visitor’s as Reply-To. See the WordPress SMTP guide.