
Summary: Company emails land in spam mainly because of missing or broken domain authentication (SPF, DKIM and DMARC), poor reputation of the sending IP or domain, misconfigured infrastructure (reverse DNS, TLS) and content or volume that looks like advertising. Since February 2024, Gmail requires SPF or DKIM from all senders and SPF, DKIM and DMARC from bulk senders.
A customer says they never got the quote. You resend. Nothing. They check spam and there it is. That costs sales. The good news: in most cases the problem is technical and has an objective diagnosis.
Step 1: diagnose with "Show original"
Send an email from your account to a Gmail address. Open the message, click the three dots and Show original. Gmail shows the SPF, DKIM and DMARC results (PASS or FAIL) at the top. The full headers show the sending IP and which domain signed the message. In Outlook, the equivalent is "View source" or "Message properties".
Step 2: understand and configure the three records
SPF: who may send for your domain
A TXT record on the domain listing the servers authorized to send email using your domain (RFC 7208). Example for sending through the hosting server and Google Workspace:
yourcompany.com. TXT "v=spf1 a mx include:_spf.google.com ~all"
- Only one SPF record per domain may exist. Two records make SPF fail.
- SPF allows at most 10 DNS lookups (each
include,a,mxcounts). Too many included services cause an error. - Include every service that sends for the domain: mail server, email marketing tool, invoicing system, online store.
DKIM: a signature that proves origin
The sending server signs each message with a private key, and the public key is published in DNS (RFC 6376). The email provider generates the record; you just publish it. Google requires keys of at least 1024 bits and recommends 2048.
default._domainkey.yourcompany.com. TXT "v=DKIM1; k=rsa; p=MIIBIjANBgkqh..."
DMARC: policy and reports
Tells receiving servers what to do when SPF and DKIM aren't aligned with the sender's domain (what appears in "From:") and where to send reports (RFC 7489). Start by monitoring:
_dmarc.yourcompany.com. TXT "v=DMARC1; p=none; rua=mailto:dmarc@yourcompany.com; adkim=r; aspf=r"
After analyzing reports and making sure all legitimate mail passes, move to p=quarantine and, if possible, p=reject. This also makes it harder for scammers to use your domain.
Gmail's requirements
Per Google's email sender guidelines, in force since February 1, 2024:
| All senders | Senders of more than 5,000 messages a day |
|---|---|
| SPF or DKIM configured | SPF and DKIM, plus a published DMARC record (can be p=none) |
| Valid forward and reverse DNS (PTR) for the sending IP | "From:" domain aligned with the SPF or DKIM domain |
| TLS connection | One-click unsubscribe on marketing messages, plus a visible link in the body |
| Spam rate in Postmaster Tools below 0.3% | Same rate; Google recommends staying below 0.1% |
| Messages formatted per RFC 5322 | - |
Other major providers, such as Yahoo and Microsoft (Outlook.com), have adopted similar requirements for high-volume senders.
Other common causes
IP or domain reputation
On shared hosting, the sending IP is shared with other customers. If one of them sends spam, the IP may land on blocklists. Look up the sending IP (shown in the headers) on public blocklists and ask the provider to change it or request delisting. Google Postmaster Tools shows your domain's reputation at Gmail, for those sending meaningful volume.
Bulk sending from a regular mailbox
Sending a newsletter to hundreds of contacts from a regular mailbox is asking for spam and can exceed hosting limits. Use an email marketing tool with unsubscribe, send only to people who consented (as data protection laws require) and clean invalid addresses.
Content
- All-caps subject lines full of exclamation points.
- A message that's just one image, with no text.
- Shortened links or links to domains other than yours.
- Executable attachments or password-protected archives.
Forwarding
Auto-forwarded messages can fail SPF. DKIM usually survives forwarding, which is why it's so important to have it.
Resolution checklist
- Check in "Show original" that SPF, DKIM and DMARC pass.
- Make sure there's a single SPF record with every sending service.
- Turn on DKIM for each service that sends for the domain.
- Publish DMARC with
p=noneand follow the reports. - Confirm the sending IP's PTR with the provider.
- Separate email marketing from transactional and sales email.
- Ask key customers to add you to their contacts.
Our business email comes with authentication already configured on the domain. If your email is elsewhere and keeps landing in spam, we diagnose it. Configuration details are in the Help Center.
Sources and references
- Google: email sender guidelines
- RFC 7208: SPF
- RFC 6376: DKIM
- RFC 7489: DMARC
- RFC 8058: one-click unsubscribe
- Google Postmaster Tools
Frequently asked questions
Can I have two SPF records?
No. The standard allows a single SPF record per domain. Combine every service into one record.
Does DMARC with p=none protect my domain?
It doesn't block anything yet; it only generates reports. It's the first step; after fixing legitimate senders, move to quarantine or reject.
Why did my emails start landing in Gmail spam in 2024?
Because since February 2024 Gmail requires authentication (SPF or DKIM for everyone, plus DMARC for bulk senders), valid reverse DNS and TLS.
How do I know if the sending IP is on a blocklist?
Get the IP from the message headers (Show original) and check it on public blocklists. If it's listed, ask the provider for delisting or another IP.
Can email marketing use the same domain?
Yes, as long as the tool is authorized in SPF, signs with your domain's DKIM and respects consent and unsubscribe. Many companies use a subdomain to isolate reputation.
Are your emails going to spam?
We configure your company's domain and email so messages land in the inbox.
Read also
- Business email with your own domain: why it still matters
- Is there such a thing as free business email?
- How to transfer a domain without taking your website offline
Written by Mário Moreno, founder of Agência hetsi, which has been building websites and handling digital marketing for businesses in Brazil and abroad since 2000. Mário Moreno on LinkedIn