Gmail spam delivery guide
If Gmail marks your email as spam, fix authentication and sending habits before changing the message design
Ask one recipient to mark a legitimate message as not spam, then correct the sender-side cause. Send through authenticated SMTP, publish SPF, enable DKIM, add DMARC, keep recipients clean and study the full Gmail rejection or message headers. No provider can guarantee placement in the inbox.
What can the Gmail recipient do?
- 1Open Spam
Select the genuine message and choose Not spam. This gives Gmail useful feedback.
- 2Add the sender to contacts
Save the exact From address when it is a person or business you recognise.
- 3Check for forwarding
If another address forwards into Gmail, test direct delivery to separate forwarding from sender problems.
- 4Report suspicious mail correctly
Do not mark unwanted or unsafe messages as legitimate just to force delivery.
What should the sender fix?
Use authenticated SMTP
Send through the mailbox service assigned to the address. Do not use an unrelated server with your domain in the From field.
Publish one correct SPF record
Authorise every legitimate platform that sends for the domain. Multiple separate SPF records cause failure.
Enable DKIM
DKIM gives Gmail a cryptographic signature connected to the sending domain and is especially useful when mail is forwarded.
Add DMARC carefully
DMARC checks alignment and provides reporting. Start with a monitoring policy while confirming every valid sender.
Use clear sender details
Keep the From name, address, subject and links honest and consistent. Do not imitate replies or trusted brands.
Protect list quality
Send only to people who expect the message, remove bounces and complaints, and never use purchased address lists.
Google’s current Email sender guidelines require all senders to personal Gmail accounts to use SPF or DKIM, valid forward and reverse DNS, TLS and correctly formatted messages. Google recommends using SPF, DKIM and DMARC together.
What changes for bulk or marketing email?
Google applies additional requirements when a sender delivers more than 5,000 messages per day to personal Gmail accounts. These include SPF, DKIM, DMARC, alignment and one-click unsubscribe for marketing and subscribed messages. Keep the Gmail Postmaster Tools spam rate below 0.3%, with a lower rate preferable.
Use a mailing platform
A normal mailbox is not designed for bulk campaigns. Use a reputable service configured to authenticate your domain.
Make consent clear
Use confirmed, relevant recipients and an obvious unsubscribe process. Do not preselect marketing consent.
Increase volume gradually
A sudden spike from a new domain or IP can look suspicious. Start with engaged recipients and monitor responses.
Separate message types
Keep receipts and account notices distinct from promotions so complaints about marketing do not affect essential mail.
How do I find the real cause?
- 1Keep the Gmail response
Copy the full bounce, including a code such as 5.7.25 or 5.7.26.
- 2Inspect Show original
In Gmail, open the message menu and use Show original to review SPF, DKIM and DMARC results.
- 3List every sending service
Include your mailbox, website forms, invoices, CRM and newsletter platform.
- 4Change one cause at a time
Retest after DNS has updated and avoid repeated bursts to the same recipient.
Gmail spam questions
Can UKC ask Gmail to allowlist my domain?
No. Google does not accept allowlist requests from email providers and does not guarantee that provider mail will pass its filters.
Is SPF alone enough?
It can meet Google’s minimum authentication requirement for some low-volume senders, but UKC recommends SPF, DKIM and DMARC together.
Why does direct mail work but forwarded mail fail?
Forwarding changes the delivery path and can affect SPF. A surviving DKIM signature can help, but the original sender controls it.
Will changing a few words fix spam placement?
Sometimes content contributes, but authentication, reputation, consent, complaints and sending behaviour are usually more important.
Need a setup check?
Bring the error, headers and sending-service details
Specific evidence lets UKC separate DNS, mailbox, website and recipient-filtering problems.