On this page
Mail that lands in junk is usually a problem with authentication, the sending IP, or the message itself—not a missing plugin. Start with SPF, DKIM, and DMARC so receivers can trust who you are. After those pass, check HELO and reverse DNS, then look at content and list hygiene. There is no inbox-placement product that replaces clean auth and a good sending reputation.
Confirm what the receiver actually saw
Send a test to a mailbox you control at Gmail or a work account. Open the message even if it is in junk, and read the Authentication-Results header. You want spf=pass, dkim=pass, and a DMARC pass with proper alignment. A fail or permerror means you still have a DNS problem, not a design problem. Warming an IP by blasting more unsigned mail does not help. Warm up by sending mail people asked for, with authentication already working.
If authentication already passes and the message still goes to junk, review the From display name, shortened URLs, and urgent or deceptive wording. Purchased lists and lookalike “voice message” copy hurt reputation quickly. On shared hosting the outbound IP is shared, so a noisy neighbor can affect you; we step in when we see that pattern. Campaign mail is often kinder on a proper ESP. Transactional mail such as receipts and password resets can stay on your account when auth is clean.
HELO, reverse DNS, and the sending IP
On shared hosting, HELO and PTR are already set for you. On a VPS you configured yourself, a name like localhost.localdomain is a common reason banks and large providers bin the mail. Make sure the name you announce in HELO resolves to the sending IP and that the PTR record matches. Only after that should you worry about blocklists. If you are not listed and auth passes, the template or the list is usually the remaining issue.
What to do in the first hour
Do not move MX records or change the sending IP because one recipient junked a password reset. Fix the record that failed, then send again to the same test mailbox. If Gmail still files it as junk with full passes, review the content and how clean your recipient list is. The first hour belongs to headers and DNS, not a new ESP account you will misconfigure by lunch.
- Confirm SPF, DKIM, and DMARC all pass with alignment.
- On a VPS, verify HELO and PTR match the sending IP.
- Keep transactional mail on the server only when auth is solid.
- Move true campaigns to an ESP so shared neighbors stay healthier.
Tagged
Was this article helpful?
Be the first to rate this article.
