If legitimate email is landing in spam, start by identifying the recipient provider and the exact outcome: spam-folder placement, delay, rejection, or a message that never appears. Then inspect the message’s authentication results, sender reputation, provider requirements, and any delivery error. Passing SPF, DKIM, and DMARC helps, but no single setting guarantees inbox placement.
First, identify what “going to spam” means
Check the affected recipient account and provider—such as Gmail, Outlook.com, Microsoft 365, Yahoo, or another service—and distinguish among these outcomes:
- Spam placement: the message arrived, but the recipient’s service classified it as junk.
- Deferral or throttling: the server temporarily delayed acceptance, often with an SMTP response.
- Hard rejection: the recipient server refused the message and may have returned a non-delivery report (NDR).
- Missing message: the message is not visible in the inbox or spam folder; investigate delivery status and recipient-side filtering.
These outcomes point to different investigations. Save the recipient domain, time sent, sending service, and complete SMTP error or NDR if one exists. Follow the receiving provider’s specific error guidance rather than treating every problem as a spam-filter issue. See Microsoft’s mail-flow troubleshooting guidance and Google’s sender guidelines.
10 deliverability problems to check first
1. SPF does not authorize every sending service
SPF tells a receiving service which sources are authorized to send for a domain. Check the SPF record for the domain used by your mail route and confirm that every service sending on its behalf is accounted for. A third-party sender omitted from the record can contribute to spam placement; Microsoft also documents missing or misconfigured SPF as a cause of authentication-related NDRs. Use the sending provider’s domain-specific setup instructions rather than guessing at record syntax. Google sender guidelines and Microsoft authentication troubleshooting explain the provider-side concerns.
#1 Best Overall
2. DKIM signing is missing or failing on the actual route
DKIM adds a cryptographic signature that a receiving service can validate. Send a test through the same platform and route that is having trouble, then inspect the delivered message’s Authentication-Results header for the DKIM result and signing domain. A setting enabled in a dashboard does not by itself show that the message recipients receive passes validation. Google recommends DKIM and requires it alongside SPF for bulk senders to Gmail; its guidance also specifies key-length requirements for personal Gmail delivery. Google’s current sender guidance and Google Workspace DMARC troubleshooting provide further context.
3. DMARC is missing or authentication is not aligned with the From domain
DMARC checks whether SPF or DKIM passes in alignment with the domain visible in the message’s From address. The visible From domain, the envelope sender (MAIL FROM), and the DKIM signing domain can be different; authentication can pass while alignment fails. Inspect the actual Authentication-Results header for the DMARC result and alignment rather than relying on a configuration screen. Microsoft describes misalignment cases, and Google requires alignment for direct mail from bulk senders. Microsoft’s authentication troubleshooting and Google’s sender guidelines cover these requirements.
Rank #2
4. The domain or sending IP has a reputation problem
Authentication is not a guarantee of inbox placement. A domain or IP can still be filtered because of reputation, prior complaints, or blocklisting. Review diagnostics from the recipient provider and look for recent changes to the sending service, domain, or infrastructure. If you use a shared sending IP, the reputation of that shared infrastructure may be relevant; Google identifies poor shared-IP reputation as one possible explanation for rejection. Changing IPs is not a guaranteed fix for a domain-level or other reputation issue. See Microsoft’s anti-spam guidance and Google’s sender guidance.
5. Recipients are reporting the messages as spam
Complaint signals can damage delivery reputation. For Gmail, Google recommends keeping its reported spam rate below 0.10% and avoiding 0.30% or higher; these are Google’s provider-specific recommendations, not universal thresholds for every mailbox service. Monitor the rate in Google Postmaster Tools when available. A spam complaint rate is not the same metric as a bounce rate. Microsoft also identifies junk complaints as a reputation factor. See Google’s sender guidelines and Microsoft’s mail-flow troubleshooting.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors6. Sending volume or infrastructure changed abruptly
Compare the timing of the problem with changes in message volume, sending IP, domain, or mail service. Check provider error and reputation data to see whether the change coincided with filtering or deferrals. Provider rules can differ by volume, but there is no universal safe ramp schedule or fixed recovery period established by the cited guidance. Google’s requirements depend in part on sender volume, while Microsoft identifies sender reputation as a delivery factor. Google’s guidelines and Microsoft’s anti-spam FAQ are relevant starting points.
7. Applicable bulk marketing mail lacks unsubscribe support
For applicable bulk senders to Gmail, Google requires marketing and subscribed messages to support one-click unsubscribe and to include a clearly visible unsubscribe link in the message body. Check both the message headers and what the recipient can see. This requirement is specific to the covered bulk-mail context; it is not a general explanation for every personal message that lands in spam. See Google’s sender guidelines.
Rank #4
8. The message or transport fails provider requirements
Check the delivery route for requirements such as TLS, valid RFC 5322 message formatting, and DNS/PTR configuration. Google’s guidance covers these points. However, if a message arrives in the spam folder, do not assume a transport-format failure without evidence in its headers or provider diagnostics; transport problems may instead produce a rejection or other explicit delivery error. See Google’s sender guidelines and Microsoft’s mail-flow troubleshooting.
9. The recipient provider is rejecting, throttling, or filtering the route
Read the complete SMTP response or NDR, including its code and explanation, and use the remedy specified for that recipient service. Record the affected recipient domain, timestamp, and sending service so you can compare failures with successful deliveries. Microsoft documents IP-blocking and removal-request paths; Google’s sender guidance lists delivery error conditions and points to troubleshooting resources. An error from the destination server is more actionable than a general impression that “email is going to spam.” See Microsoft’s mail-flow troubleshooting and Google’s sender guidelines.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
10. The diagnosis relies on open rates instead of provider evidence
Low reported opens do not prove that messages are in spam. Google says it does not track open rates and cannot verify the accuracy of third-party open-rate data; it also cautions that low open rates are not necessarily an accurate indicator of deliverability or spam classification issues. Prefer Postmaster Tools data for Gmail, authentication results from the delivered message, recipient-provider error codes, and confirmation from affected recipients. See Google’s sender guidelines.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use evidence that matches the recipient provider
Rules and diagnostics vary by destination, sender volume, and message type. Google’s requirements distinguish baseline senders from bulk senders; Microsoft’s guidance also varies by mail service and context. Outlook.com documents requirements for high-volume consumer senders, while Yahoo maintains its own sender guidance. Check the current rules for the service actually receiving the message rather than assuming one provider’s threshold applies everywhere.
- For Gmail: Google Postmaster Tools can show spam-rate, authentication, reputation, and delivery information. Google says it cannot guarantee messages sent by email providers will pass Gmail’s spam filters. Google sender guidelines
- For Microsoft destinations: use the full NDR, authentication results, and Microsoft’s relevant troubleshooting steps. Consumer Outlook.com requirements should not automatically be treated as identical to Microsoft 365 policies. Outlook.com support · Authentication troubleshooting
- For Yahoo: consult its current sender best practices for the applicable requirements. Yahoo Sender Hub
A practical order for troubleshooting
- Classify the symptom: confirm spam placement, deferral, rejection, or missing mail, and note which recipient provider is involved.
- Capture provider evidence: save the full NDR or SMTP response, or inspect the headers of a delivered message.
- Verify authentication on the affected route: check SPF, DKIM, DMARC, and alignment in the received message.
- Check provider-specific rules and reputation signals: review Gmail Postmaster Tools when Gmail is involved, and use the destination provider’s diagnostics for other services.
- Compare with recent changes: investigate new sending services, volume shifts, infrastructure changes, complaint patterns, and missing unsubscribe support where applicable.
Make one evidence-based change at a time, then test delivery to the affected provider and review the resulting headers or response. Inbox placement cannot be guaranteed by a checklist, and no universal recovery time or sending ramp can be inferred from the provider guidance cited here.
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.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →
