Prompt
My app emails are being marked as spam after a provider migration. How do I troubleshoot that?
Latest observation
Here’s a practical way to troubleshoot spam placement after an email provider migration. The goal is to figure out whether the problem is authentication, sending reputation, content, or infrastructure/configuration.
1) Compare the old provider vs new provider
Start by checking what changed during migration:
- Sending domain: same domain or new one?
- From address: same
From:or different? - IP address: shared vs dedicated, and did the IP change?
- Envelope domain / Return-Path: changed?
- DKIM domain: same selector/domain or new?
- SPF include: updated for the new provider?
- DMARC alignment: still aligned?
- Mail stream type: transactional vs marketing mixed together?
A provider migration often breaks deliverability because one or more of these changed.
2) Check authentication first
Most spam filtering starts with authentication.
Verify SPF
Make sure your SPF record authorizes the new provider.
- Example:
v=spf1 include:newprovider.example -all
Common issues:
- Too many DNS lookups
- Multiple SPF records
- Old provider still listed but new one missing
- SPF passes for the wrong domain
Verify DKIM
Make sure the new provider is signing with DKIM and that the DNS record is correct.
Check:
- Signature exists in the message headers
- Selector matches DNS
d=domain is your domain or an aligned subdomain
Verify DMARC
DMARC should pass with alignment.
Check:
- SPF or DKIM passes
- The authenticated domain aligns with the visible
From:domain
If you haven’t set DMARC yet, start with:
p=nonefor monitoring
Then move later to quarantine/reject once stable.
3) Inspect a raw message header
Send a test email to a Gmail account, then view the full headers and look for:
Authentication-ResultsReceived-SPFDKIM-SignatureReturn-PathFromMessage-IDX-headers from your provider
You want to know:
- Did SPF pass?
- Did DKIM pass?
- Did DMARC pass?
- Was there any alignment failure?
If you paste the headers into a header analyzer, it’s often obvious what’s wrong.
4) Check IP and domain reputation
After migration, you may be on a new sending IP or new pool.
If using a dedicated IP
- Was the IP warmed up gradually?
- Is it newly assigned and sending too much too soon?
- Was it previously used by someone with bad reputation?
If using a shared IP
- Is your provider putting you on a low-reputation pool?
- Are other senders on that pool hurting placement?
Check reputation tools
Look at:
- Gmail Postmaster Tools
- Microsoft SNDS
- Blocklists / RBLs
- Your provider’s reputation dashboard
You’re looking for:
- Complaint spikes
- Bounce spikes
- IP/domain reputation drops
- Authentication failures
5) Look at the content and structure of the email
Even with perfect authentication, spam filters can still flag content.
Check for:
- Subject lines with spammy wording
- Too many links
- Link shorteners
- Mismatched link domains
- HTML broken after migration
- Missing plain-text part
- Image-heavy templates
- Large attachments
- New tracking parameters or redirect chains
Also verify:
- Your links point to the correct domain
- Open/click tracking domains are set up correctly
- Unsubscribe link is present for marketing mail
A migration sometimes changes the template or tracking domain, which can hurt deliverability.
6) Confirm DNS records for tracking and sending domains
If your provider uses custom tracking domains, link domains, or branded return-paths, make sure they’re configured.
Common records:
- SPF
- DKIM
- DMARC
- Custom bounce/return-path
- Custom click tracking subdomain
- Custom open tracking pixel host
Broken or misaligned tracking domains can look suspicious to filters.
7) Check complaint and bounce behavior
Spam placement can happen if recipients interact poorly with the new mail stream.
Look for:
- Increased hard bounces
- Increased soft bounces
- User complaints
- Low opens/clicks on cold segments
- Sending to stale or purchased lists
Important:
- If this is transactional email, make sure you’re not sending it to old/inactive addresses.
- If it’s marketing, suppress inactive recipients and bad addresses.
8) Test inbox placement across providers
Send test mail to:
- Gmail
- Outlook/Hotmail
- Yahoo/AOL
- Fastmail
- iCloud
Check whether:
- It lands in inbox, promotions, updates, or spam
- It’s consistently spam only at one provider
- It’s spam only for certain recipient domains
That helps identify whether the issue is global or provider-specific.
9) Review sending patterns after migration
Spam filters can react to sudden changes.
Check:
- Volume increased too fast?
- New sender sending patterns?
- Burst sending instead of steady flow?
- Different recipient mix than before?
- New IP without warmup?
A migration often resets reputation. Even if everything is technically correct, you may need a warmup period.
10) Use provider logs and message delivery events
Look at your mail provider’s logs for:
- Accepted by recipient server
- Deferred/retried
- Rejected
- Spam complaint event
- Authentication result
- Bounces and SMTP response codes
SMTP responses can reveal:
- Policy rejection
- Reputation rejection
- Spam content filtering
- DNS/authentication issues
11) Common migration mistakes
These are the big ones I see most often:
- SPF still references the old provider only
- DKIM not enabled on the new provider
- DMARC alignment broken because
From:changed - New shared IP with poor reputation
- Missing custom tracking domain
- Broken unsubscribe or footer links
- Sending both transactional and marketing from the same domain/IP stream
- No warmup after migration
- Templates changed and now look spammy
- Old provider left in DNS, causing confusion or lookup limits
12) A quick troubleshooting checklist
If you want a fast path, do this in order:
- Send a test email to Gmail
- Inspect headers for SPF/DKIM/DMARC pass/fail
- Verify SPF includes the new provider
- Verify DKIM is signing correctly
- Confirm DMARC alignment
- Check if the sending IP changed
- Review provider reputation dashboards
- Compare new template/content to old one
- Validate tracking/link domains
- Test inbox placement across major providers
If you want, I can help you narrow it down quickly
If you share any of the following, I can tell you what to check next:
- A redacted copy of the email headers
- Your SPF/DKIM/DMARC records
- Which provider you migrated from/to
- Whether this is transactional or marketing mail
- Whether you moved to a new IP or shared pool
If you paste the headers, I can usually identify the likely cause pretty quickly.