ONLINE
Bento

Landing in Spam: Recovery Guide

Your emails were landing in the inbox and now they are not. This is the runbook. Confirm the problem is real, find the cause in a fixed order, then rebuild placement with a controlled recovery sequence. Skipping steps usually extends the recovery, not shortens it.

Confirm It Is Actually Spam Placement

Before changing anything, confirm your mail is really landing in spam. Open rate drops alone are not proof. Apple Mail Privacy Protection, Gmail image proxying, and bot filtering all distort opens. See Open and Click Tracking for why.

Test with real seed addresses:

  1. Create or use real mailboxes at Gmail, Outlook, and Yahoo. Use addresses that have no history with your domain if possible.
  2. Add them to a small test segment in Bento.
  3. Send your actual campaign template, not a stripped-down test. Filtering decisions depend on the real content, links, and headers.
  4. Check each mailbox. Note whether the email landed in the inbox, Promotions or another tab, or the spam folder.
  5. Repeat across two or three sends. A single placement result can be noise.

Also check the supporting signals:

  • Clicks, replies, and conversions dropped alongside opens. A tracking artifact only hits opens.
  • The drop is provider-specific. A Gmail-only drop points at Gmail reputation. A broad drop points at authentication or a shared cause.
  • Google Postmaster Tools shows a spam rate or reputation change for your domain. See Google Postmaster Tools.
  • Bento's Deliverability Monitor shows reputation or placement changes.

If seeds land in the inbox and conversions are stable, you likely have a tracking measurement issue, not a placement issue. Stop here and review tracking instead.

Diagnose in Order

Work through these causes in order. Most spam placement incidents are one of the first three.

1. Authentication broke

The most common sudden cause. A website migration, DNS cleanup, or registrar change silently removed an SPF, DKIM, or DMARC record. When authentication fails, providers junk or reject mail immediately.

  1. Check Deliverability -> DNS Records in Bento for any record that is no longer verified.
  2. Confirm nothing changed at your DNS host or registrar recently.
  3. Fix and re-verify using DNS Setup. If you publish a DMARC policy, see the DMARC guide.

If DNS broke, fixing it usually restores placement within a few days. Do not proceed to drastic changes until DNS is verified again.

2. Reputation took a hit

Complaints, spam trap hits, or a blocklist entry damaged your sending reputation.

3. List quality changed

A new import or a send to a cold segment introduced low-quality recipients.

  • Review recent imports. A list with unclear consent or old addresses drags placement down for your whole domain. See the Import Guide.
  • Check whether the drop started after a send to a segment that had not been emailed in months.
  • Review list hygiene for the affected segments.

4. Content or links got flagged

Less common than people assume, but worth checking once the above are clear.

  • Test every link in the email, including the tracking domain and final destinations. See Gmail Link Warnings.
  • Remove URL shorteners, stacked redirects, and links to third-party domains with poor reputation.
  • Check that subject lines match the email content and the sender name is recognizable.

5. Volume spiked

A sudden jump in daily volume looks like a compromised account or a spammer to providers, even from an established domain.

  • Compare recent daily volume against your normal baseline.
  • If you ramped too fast, return to a gradual pace using the Domain Warmup guidance.
  • If your domain went quiet for weeks and then resumed at full volume, follow the Rewarming guide instead.

The Recovery Sequence

Once you know the cause and have fixed it, rebuild placement like a warmup:

  1. Pause broad sends. Stop all campaigns to large or mixed segments. Keep transactional email running.
  2. Send only to your most engaged recipients. Build a segment of people who clicked or purchased in the last 30 days. These recipients open, click, and never complain, which is exactly the signal providers need to see.
  3. Keep volume low and consistent. Daily sends at a modest, steady volume beat occasional large blasts. Consistency is itself a positive signal.
  4. Expand gradually. Once placement to the engaged segment is stable for several sends, widen to 60-day engagement, then 90-day. Treat it like the ramp in the warmup guide.
  5. Hold the line on quality. No cold segments, no new imports, no re-engagement blasts until you are fully back in the inbox.
  6. Monitor daily. Watch Google Postmaster Tools for spam rate and domain reputation, and Bento's Deliverability Monitor for reputation and placement signals. Re-test your seed addresses every few sends.

Timeline Expectations

Recovery takes days to weeks, not hours. Plan for it.

ScenarioTypical recovery window
Broken DNS, fixed quickly2 to 7 days after records verify
Moderate complaint spike, one bad campaign1 to 3 weeks of engaged-only sending
Sustained complaints or spam trap hits3 to 6 weeks or longer
Major blocklist entry (Spamhaus)Days after delisting, plus reputation rebuild

Providers weight recent behavior most heavily, so every clean, engaged send moves you forward. But they also remember the bad period, which is why placement returns gradually rather than all at once. If you are still in spam after four weeks of disciplined recovery sending, contact Bento support with your seed test results and Postmaster Tools data.

Provider-Specific Notes

Each major provider filters differently. Use the provider guides and SMTP error references when the problem is concentrated at one of them.

ProviderKey behaviorGuideSMTP errors
GmailDomain reputation driven. Spam rate visible only in Postmaster Tools. Requires authentication and one-click unsubscribe for bulk senders.Google Postmaster ToolsGmail SMTP errors
OutlookThe strictest filtering of the big three. Weighs IP reputation heavily and is slow to forgive.Outlook DeliverabilityMicrosoft SMTP errors
YahooComplaint sensitive. Enforces the same bulk sender rules as Gmail, with per-user feedback loops.Yahoo DeliverabilityYahoo SMTP errors

For Apple inboxes, placement generally follows your Gmail-style domain reputation, but opens are heavily distorted by Mail Privacy Protection. See Apple Mail.

For the full operating checklist, return to the Deliverability Guide.

Was this page useful?

Your answer helps us find docs that need work.