Recommended Free Tools
If legitimate email is landing in spam, being delayed, or rejected, start by checking authentication, recipient consent, complaint and bounce signals, and recent sending-volume changes. Set up SPF, DKIM, and DMARC; mail only people who opted in; make marketing email easy to unsubscribe from; and investigate provider-specific errors. These steps improve the conditions for delivery, but no single setting guarantees inbox placement.
Why are my emails going to spam?
Inbox placement depends on more than whether an SPF or DKIM record exists. Mail providers also consider whether recipients want the messages, how they respond, whether the sending domain and infrastructure are trustworthy, and whether traffic patterns look stable. A message can pass authentication and still be filtered if people report it as spam or the sender’s reputation is poor.
As an Amazon Associate I earn from qualifying purchases.
Begin with the provider where the problem occurs. Read the SMTP bounce or deferral response, check whether the issue affects Gmail, Yahoo, or another service, and compare recent changes in list sources, message type, volume, or sending platform. Gmail and Yahoo have their own published requirements; their numeric thresholds and enforcement should not be treated as universal rules for every mailbox provider.
Authenticate your sending domain
Configure SPF, DKIM, and DMARC for every domain used to send mail. Google requires senders to personal Gmail accounts to use SPF or DKIM, and requires bulk senders to use both plus DMARC. Yahoo likewise requires at least SPF or DKIM for all senders and both SPF and DKIM, plus DMARC, for bulk senders. Google recommends all three even when a sender is not subject to its bulk requirements. See Google’s email sender guidelines and Yahoo’s sender best practices.
#1 Best Overall
- SPF: List every legitimate service that sends mail for your domain. Add a new email platform before it sends, and update the record when providers change. An SPF record that omits a newsletter or transactional service can cause its mail to fail authentication.
- DKIM: Ensure each sending service signs messages with a key for your domain. Google says DKIM keys must be at least 1024 bits for delivery to personal Gmail accounts and recommends 2048 bits when supported.
- DMARC: Publish a DMARC record and use reports to identify legitimate and unauthorized senders. Google says its bulk senders may use a policy of
p=none; Yahoo requires a valid policy of at least that level for bulk senders.
For Gmail bulk mail, the visible From domain must align with the domain authenticated by SPF or DKIM. A third-party platform should be included in SPF and configured to DKIM-sign for your domain. Confirm results using message headers and provider diagnostics—not simply the presence of DNS records. Microsoft Learn provides background on how Microsoft 365 evaluates SPF, DKIM, and DMARC, but the requirements below are specifically the cited Gmail and Yahoo guidance, not a claim that their rules apply unchanged to Outlook: Microsoft 365 email authentication.
Meet the published Gmail and Yahoo requirements
The following requirements concern personal Gmail accounts and Yahoo-managed consumer mail, respectively. Google defines its bulk-sender threshold; Yahoo’s cited sender guidance does not publish a numeric volume trigger, so do not apply Gmail’s threshold to Yahoo.
| Provider and scope | Authentication and infrastructure | Bulk-mail and unsubscribe rules | Complaint-rate guidance |
|---|---|---|---|
| Google: mail to personal Gmail accounts | All senders: SPF or DKIM, valid forward and reverse DNS, TLS, and RFC 5322-compliant formatting. Bulk senders: SPF and DKIM, DMARC, and From-domain alignment with SPF or DKIM. | Bulk senders must support one-click unsubscribe for marketing and subscribed messages. Google defines a bulk sender as sending close to 5,000 or more messages to personal Gmail accounts in 24 hours; messages from subdomains under the same primary domain are aggregated. Once classified as bulk, that status does not expire. | Google advises keeping the spam rate reported in Postmaster Tools below 0.1% and avoiding 0.3% or higher. It says rates above 0.1% can hurt bulk-sender inbox delivery; at 0.3% or higher, the negative impact is greater. Bulk senders above 0.3% are ineligible for mitigation until the rate stays below that level for seven consecutive days. |
| Yahoo: Yahoo-managed consumer mail | All senders: SPF or DKIM, valid forward and reverse DNS, and RFC 5321 and RFC 5322 compliance. Bulk senders: SPF and DKIM, a valid DMARC policy of at least p=none, and DMARC alignment with SPF or DKIM. |
Bulk marketing or subscribed mail must support one-click unsubscribe and include a visible body link. Yahoo says to honor opt-outs within two days. Its cited guidance does not state a numeric bulk-volume threshold. | Yahoo’s bulk-sender guidance says to keep the complaint rate below 0.3%. |
Google’s bulk definition applies to personal Gmail accounts, not Google Workspace inbound or mail exchanged within a Workspace domain. Google’s FAQ and sender guidelines are maintained documentation, so check the current pages when configuring a sending setup: Google’s sender guidelines FAQ. Google’s spam-rate figures are its own Postmaster Tools guidance, while Yahoo’s complaint-rate figure is Yahoo’s; they are not interchangeable measurements or a cross-provider deliverability guarantee. Yahoo’s consumer-mail requirements are detailed in its Sender Best Practices and Sender FAQ.
The Tool Desk
Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Send only to people who want your email
Build and maintain an opted-in list. Google advises: “Don’t send messages to people who didn’t sign up to get messages from you.” Purchased lists and addresses with no reliable permission are especially risky: unwanted mail can generate complaints, damage domain reputation, and make future messages more likely to be classified as spam. Google’s guidance also emphasizes engaged recipients: Email sender guidelines.
Rank #3
- Use signup sources where people clearly choose to receive the messages you send.
- Prioritize recipients who have engaged recently; do not keep mailing stale or unresponsive addresses simply to preserve list size.
- Process hard bounces and unsubscribe requests rather than repeatedly trying the same addresses.
- Keep message categories distinct. Use consistent From addresses for each category and, where practical, separate promotional traffic from transactional messages such as receipts or password resets.
Make promotional email easy to unsubscribe from
For applicable bulk promotional or subscribed mail, Gmail and Yahoo require one-click unsubscribe support as well as a visible unsubscribe link in the message body. A link in the body alone does not satisfy the one-click-header requirement. Test the mechanism end to end so that a recipient’s opt-out is actually honored. Yahoo says bulk senders should process opt-outs within two days. These requirements do not apply identically to transactional mail: Yahoo’s FAQ distinguishes promotional messages from transactional messages such as order confirmations and password resets.
Keep the unsubscribe experience clear rather than making recipients search, sign in, or contact support to stop marketing messages. Separating promotional and transactional sending streams where practical can also help keep their purposes and operational handling distinct. See Google’s sender guidelines, Yahoo’s sender best practices, and Yahoo’s sender FAQ.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Keep sending volume steady and diagnose changes
Sudden increases can coincide with more deferrals, bounces, or complaints. Send at a consistent pace, ramp gradually when starting or resuming a program, and begin with recipients most likely to engage. If SMTP errors, deferrals, or bounces rise, reduce or pause sending while you investigate rather than continuing to increase traffic. Google also cautions that shared IP reputation can affect every sender using that IP.
When choosing an email platform or evaluating a current setup, check whether it supports custom-domain SPF and DKIM, DMARC alignment diagnostics, unsubscribe headers and preference handling, bounce and complaint processing, reputation visibility, volume controls, and separation of transactional from promotional mail. Ask whether sending uses shared or dedicated IP infrastructure and what reputation information is available; neither arrangement by itself guarantees inbox placement.
Use provider diagnostics to find the cause
Google Postmaster Tools
Google Postmaster Tools can report Gmail spam rates, authentication, domain and IP reputation, and delivery errors. Its dashboards may show no data when traffic is too low. A blank dashboard therefore does not establish that mail is healthy or that a particular authentication check passed; inspect message headers and delivery responses as well.
Yahoo Complaint Feedback Loop
Yahoo’s Complaint Feedback Loop provides complaint information for reports from Yahoo domains. Use it alongside bounce and unsubscribe data to identify campaigns or audience segments that trigger unwanted-mail reports. Yahoo recommends meaningful PTR records and separating bulk or marketing traffic from user or transactional mail by IP or DKIM domain where practical. See the Yahoo Sender FAQ.
A practical troubleshooting sequence
- Identify the affected mailbox provider. Record whether messages are rejected, deferred, or accepted into spam. Save the full SMTP response and compare results across providers instead of assuming one provider’s rule applies to all.
- Verify authentication and alignment. Check that SPF includes each legitimate sender, DKIM passes for the sending domain, and DMARC is published. For Gmail bulk mail, confirm the visible From domain aligns with SPF or DKIM. Review actual headers and DMARC reports.
- Check infrastructure. Verify forward and reverse DNS for sending domains or IPs and confirm TLS is used. If the service uses shared IPs, ask the provider how it handles reputation and whether the affected traffic shares an IP with other senders.
- Audit the audience. Stop sending to purchased, stale, or nonconsenting lists. Remove bounced addresses, respect opt-outs, and focus on people who opted in and have recently engaged.
- Test marketing opt-out. Confirm one-click unsubscribe headers and a visible body link are present where required, then verify that an unsubscribe actually suppresses further promotional mail.
- Stabilize traffic. Reduce volume when bounces or deferrals rise. Diagnose the source before resuming, then increase gradually from engaged recipients.
- Review provider signals. Check Google Postmaster Tools and Yahoo’s Complaint Feedback Loop when available. Monitor responses over time; classification changes can take time, and Google dashboards may lack data at low traffic volumes.
Google’s detailed operating guidance is at Email sender guidelines; its FAQ explains bulk classification and spam-rate treatment at Email sender guidelines FAQ. Yahoo’s current sender-facing guidance is at Sender Best Practices and Sender FAQ. Provider documentation can change, and laws governing consent and opt-outs vary by jurisdiction; these operational guidelines are not jurisdiction-specific legal advice.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
