The five usual causes are missing email authentication (SPF, DKIM and DMARC), a sending server with a poor reputation, a website or tool sending email in your name without permission, sending habits that look like spam, and content that triggers filters. Start with the first three: they're the most common for small businesses, and you can check them in minutes with the free domain checker.
1. Check whether it's really spam
Before changing anything, find out what the receiving server actually decided. Ask someone who uses Gmail to find your message, open it, choose Show original from the three-dot menu, and send you a screenshot of the top of the page.
It shows three lines: SPF, DKIM and DMARC, each marked PASS or FAIL. If any of them fails, the problem is technical and fixable. If all three pass and the message still lands in spam, the cause is more likely reputation, content or sending habits.
2. SPF: the list of servers allowed to send
SPF (Sender Policy Framework) is a TXT record in your domain's DNS. It lists every server that may send email using your domain. When a message arrives, the receiver checks whether the sending server is on that list.
v=spf1 include:_spf.google.com include:servers.mcsv.net ~all
This example allows Google Workspace and Mailchimp, and marks everything else as suspicious.
Common mistakes:
- Two SPF records. A domain may have only one. Adding a second one when you sign up for a new tool breaks both.
- A missing sender. Your invoicing software, booking system or website sends email too, and each one needs to be in the record.
- More than 10 lookups. Each
include:costs at least one DNS lookup. Past 10, SPF fails for everyone. - Ending in +all. This allows any server in the world to send as you, which makes the record pointless.
3. DKIM: a digital signature on every message
DKIM (DomainKeys Identified Mail) adds an invisible signature to each email. The receiver checks it against a public key published in your DNS. A valid signature proves the message came from your domain and wasn't changed in transit.
Each platform signs with its own key, so DKIM has to be turned on separately in Google Workspace, Microsoft 365, Mailchimp, Brevo, your cPanel mail and anything else that sends for you. The key lives at an address such as google._domainkey.yourcompany.lk.
4. DMARC: the rule for messages that fail
DMARC tells receivers what to do when a message claims to come from your domain but fails SPF and DKIM. It also sends you daily reports listing every server that sent email using your name, which is how you discover forgotten tools and spoofing.
v=DMARC1; p=none; rua=mailto:[email protected]
Roll it out in three steps:
- Start with
p=none. Nothing is blocked; you just collect reports. - After two to four weeks, once every real sender passes, change to
p=quarantine. Failing messages go to spam. - When you're confident, change to
p=reject. Fake emails in your name are refused outright.
Jumping straight to reject before checking reports is a common way to block your own invoices.
5. Alignment: why records can exist and still fail
DMARC doesn't only ask whether SPF or DKIM passed. It asks whether they passed for the same domain the reader sees in the From address. That match is called alignment, and it's the most misunderstood part of email authentication.
A common example: you send a newsletter from [email protected] through a marketing platform. SPF passes, but for the platform's own bounce domain, not yours. DKIM is signed with the platform's domain too. Both checks pass, yet neither is aligned with yourshop.lk, so DMARC fails.
The fix is usually to set up the platform's "domain authentication" or "custom DKIM" option, which signs your mail with your own domain. Mailchimp, Brevo, SendGrid and most others offer it. Only one of SPF or DKIM needs to align for DMARC to pass, and DKIM is the more reliable of the two because it survives forwarding.
6. Shared hosting and blocklists
Many Sri Lankan businesses run email on cPanel shared hosting. Your messages then leave from a server shared with hundreds of other websites. If one of those sites is hacked and starts sending spam, the server's IP address can be added to a blocklist, and your mail is treated with suspicion too.
Signs of this: emails to some providers bounce with messages mentioning "blocked", "listed" or "reputation", while your authentication records are fine. The fixes are to ask your host to clean the server and request delisting, to move business email to Google Workspace or Microsoft 365, or to send website email through an authenticated email service. The cPanel guide covers the setup.
7. Website contact forms sending as you
WordPress and other website forms often send notifications using the server's basic mail function, with your business address in the From field. Those messages aren't authenticated, so they fail DMARC and land in spam, or vanish. The WordPress email guide shows the fix step by step.
8. Sending habits and content
Authentication proves who you are. It doesn't make people want your email. Filters also watch how recipients react, and these habits hurt:
- Sending to bought, scraped or very old lists
- Newsletters without a clear unsubscribe link
- Sudden jumps in volume, such as 50 emails a week, then 5,000 in a day
- Emails that are one large image with almost no text
- Link shorteners, and attachments people didn't expect
- Sending business mail from a free Gmail address with your company's name
9. What Gmail, Yahoo and Outlook now require
Since February 2024, Gmail and Yahoo have required anyone who sends 5,000 or more emails a day to their users to have SPF, DKIM and DMARC, a one-click unsubscribe for marketing email, and a spam complaint rate below 0.3%. Microsoft began enforcing similar rules for Outlook.com in May 2025. Every sender, at any volume, needs at least SPF or DKIM. Google lists its current requirements in its email sender guidelines FAQ.
One-click unsubscribe means two hidden headers in every marketing email, defined in a standard called RFC 8058. They let Gmail show its own Unsubscribe button and remove the person without them visiting a web page:
List-Unsubscribe: <https://yourshop.lk/unsubscribe?id=8f3a>
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Newsletter platforms such as Mailchimp and Brevo add these automatically. If you send newsletters from your own server or a plugin, check that they're present by viewing the message source.
Checklist
- Exactly one SPF record, listing every service that sends for you, ending in
~allor-all - DKIM turned on in every sending platform, using your own domain
- A DMARC record with a report address, moving from none to quarantine to reject
- SPF or DKIM aligned with your From domain for every sender
- Website forms sending through authenticated SMTP
- Sending server not on a major blocklist
- A one-click unsubscribe in every newsletter
- Business email sent from your own domain, not a free address
Questions
Do I need DMARC if I only send a few emails a day?
It isn't required at low volume, but it's the only record that stops other people sending fake emails in your name, so every business domain should have one.
Will changing DNS records break my email?
A wrong SPF or MX change can. Make one change at a time, keep a copy of the old record, and test after each change.
How do I see why Gmail sent my email to spam?
Ask the recipient to open the message, choose Show original from the three-dot menu, and send you the SPF, DKIM and DMARC results at the top.
Want me to check yours?
Send me your domain and I'll reply within 24 hours with what's wrong and what it would cost to fix. The check is free.
Get a free domain check