Prompt
My emails are bouncing after a provider migration, what should I look at?
Latest observation
Nov 6, 2026
OpenAI APIWeb search: off
After a provider migration, email bounces are usually caused by a few common things. Here’s a practical checklist of what to inspect first:
1) DNS records for the domain
Make sure the new provider’s records are correct and fully propagated:
- MX records point to the right mail server
- A/AAAA records for mail hostnames are correct, if used
- SPF includes the new sending servers
- DKIM keys are published correctly
- DMARC policy isn’t blocking legitimate mail during transition
- If you use a custom mail subdomain (like
mail.example.com), verify it too
2) Reverse DNS / PTR
If you send mail from your own server or a new IP:
- The sending IP should have a valid PTR record
- The PTR should resolve to a hostname that matches your mail setup
- Some providers reject mail if PTR is missing or inconsistent
3) Mail server configuration
Check the new provider’s SMTP/IMAP settings:
- Correct SMTP hostname
- Correct port and encryption (587/TLS, 465/SSL, etc.)
- Authentication is enabled and working
- The server is allowed to relay mail for your domain
4) SPF alignment
If SPF is too strict or outdated:
- Add the new provider’s sending IPs/include mechanisms
- Remove old provider entries if no longer used
- Make sure you stay within the SPF lookup limit
5) DKIM signing
If messages aren’t being signed:
- Confirm your mail system is signing outgoing messages
- Verify the selector and public key in DNS match
- Test with a message to a mailbox that shows authentication results
6) DMARC alignment
Bounces or rejections can happen if:
- SPF or DKIM pass but don’t align with the visible
From:domain - DMARC policy is set to
quarantineorreject - Your migration changed the envelope sender or From domain behavior
7) Old server still referenced
Sometimes mail is still going to the old provider because:
- DNS cache hasn’t expired
- Applications/scripts still use the old SMTP host
- Stored MX records on third-party services are stale
- Hosted services like forms, billing systems, or CRMs still send via the old server
8) Blacklists / reputation
If you moved to a new IP:
- Check whether the new IP is on blocklists
- New IPs often have poor reputation until warmed up
- Some providers rate-limit or reject new sending IPs temporarily
9) Bounce codes / SMTP response
The exact bounce text is very useful. Look for:
550,553,554errorsSPF fail,DKIM fail,DMARC failrelay denied,user unknown,mailbox unavailabletemporarily deferred,greylisted,connection timed out
10) TLS / certificate issues
Some servers reject mail if:
- The SMTP server certificate is invalid or expired
- Hostname doesn’t match the cert
- STARTTLS negotiation fails
Quick triage steps
- Check the bounce message
- Verify MX/SPF/DKIM/DMARC
- Confirm the new provider’s SMTP settings
- Test sending to a Gmail/Outlook mailbox and inspect headers
- Check whether mail is still being sent via the old provider
- Review logs on the sending server and the new provider
If you want, paste a bounce message or the SMTP error code, and I can help identify the likely cause quickly.