After a migration, mail may go to spam because the sending IP changed, DNS authentication records were not updated, or the website started sending from a form without proper alignment.
Common symptoms
- Spam placement begins immediately after a move
- Messages fail only from website forms
- Authentication checks changed from pass to fail
Troubleshooting steps
- Confirm SPF, DKIM, and DMARC records still reflect the current mail sender after the migration.
- Verify the website contact forms send using authenticated SMTP instead of insecure local mail where possible.
- Check that reverse DNS and hostname settings match the sending environment if mail is sent directly from the server.
- Review message content for spam triggers, especially if templates changed during migration.
- Warm up sending gradually if the migration introduced a new dedicated sending IP.
Additional notes
- Website migrations often move the web files but leave external mail routing unchanged; confirm both layers.
- A contact form can fail reputation checks even when mailbox-to-mailbox sending looks normal.
When to contact support
Contact support if authentication passes but inbox placement dropped sharply after the move.