Fix emails from your server going to spam
Self-hosted email absolutely can hit the inbox — mail providers just hold it to a high bar. Work down this list in order; the top items matter most.
1. Authenticate (non-negotiable)
Set up SPF, DKIM, and DMARC. Without these, major providers distrust your mail by default. → DKIM, SPF & DMARC
2. Reverse DNS (PTR)
Your server’s IP should resolve back to your mail hostname (e.g.
mail.yourdomain.com). This PTR record is set at your hosting/VPS provider,
not in your own DNS. Mismatched or generic reverse DNS is a common spam trigger.
3. Check your IP isn’t blacklisted
A fresh server IP can carry a previous tenant’s bad reputation. Look it up on a blacklist checker. If listed, follow the delisting process for that blocklist.
4. Get the basics of the message right
- Send from a real, monitored address (not
noreply@only). - Include a plain-text part, not just HTML.
- Avoid spammy subject lines, all-caps, and link shorteners.
- Include a real unsubscribe link for bulk mail.
5. Warm up gradually
A brand-new domain/IP with no history should ramp up slowly — a burst of hundreds of emails on day one looks exactly like spam. Start with real, low-volume mail and build reputation.
6. Test your score
Send to a mail-tester service and to a Gmail account (Show original → check SPF/DKIM/DMARC all PASS). Fix whatever it flags.
When to use a relay instead
If you must send high volume and deliverability is business-critical, consider routing outbound mail through a reputable SMTP relay while keeping inboxes on your server. For most sites, proper authentication (steps 1–2) is enough.
Running OrbixPanel? DKIM and mail services are set up at install. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.