Cold Email Soft Bounce Fix Guide (2026)

A soft bounce is a temporary SMTP delivery failure reported with a 4xx response code (4.x.x enhanced status code). The receiving server is saying "not now, try later." The message is not necessarily lost: most sequencers retry soft bounces 3-5 times over 24-72 hours.

A hard bounce is a permanent failure with a 5xx code (5.x.x enhanced). The mailbox does not exist, the domain has no MX record, or the receiving server explicitly rejected the sender. Hard bounces should not be retried, retrying them damages reputation and can trigger blacklisting.

The critical mistake most cold emailers make: treating repeated soft bounces as "no big deal" because the sequencer retries automatically. A single soft bounce is noise. Repeat soft bounces at > 3% of volume are a warning sign that receiving servers are rate-limiting or temporarily de-prioritizing your sender, and that signal tends to precede a hard-bounce wave by 48-72 hours. Fix them early.

This guide decodes the most common SMTP 4xx codes and walks through the fix for each cause.

Your sequencer logs the SMTP error string when a soft bounce happens. Open the campaign's bounce log and grab the full error. It looks like:

421 4.7.0 [IP] Our system has detected an unusual rate of unsolicited mail originating from your IP address. To protect our users from spam, mail sent from your IP address has been temporarily rate limited. Please visit https://support.google.com/mail/?p=UnsolicitedRateLimitError

The important parts:

The most common cold email soft bounce codes and their causes:

Whatever code you see, check the URL in the error message. Gmail and Microsoft both link to an explanation page that tells you exactly why the message was rate limited. Read it before making any config changes, the fix depends on the specific code.

The single most common cold email soft bounce. SMTP 421 4.7.0 and 421 4.7.28 are both rate-limit responses from Gmail. Microsoft's equivalent is 421 4.7.500 or 451 4.7.28.

What triggers rate limiting:

The fix is throttling, not retrying harder:

1. 1Lower per-mailbox daily volume. Drop from 40/day to 25/day on affected mailboxes. Stay there for a week, then ramp slowly.
2. 2Add delay between sends. Most sequencers let you set "send interval" or "delay between messages." Set to 60-120 seconds per mailbox. This spreads sends out and avoids triggering receiver-side rate windows.
3. 3Stagger across mailboxes. If you're sending 200/day across 5 mailboxes, don't have them all fire at 9:00 AM. Stagger starts by 15-30 minutes.
4. 4Respect receiver-specific limits. Gmail tolerates roughly 5-10 msg/minute per sender-receiver IP pair. Microsoft is similar. Going above triggers 421 instantly.

The math: for cold email, 30-35 sends/mailbox/day at 90-second intervals is the steady-state sweet spot. That maps to ~5-6 sends per hour per mailbox, well below any provider's rate threshold. Full send-limit reference in email-sending-limits-google-microsoft.

Greylisting is a spam defense where the receiving server temporarily rejects the first delivery attempt from an unknown sender and waits to see if the sender retries. Legitimate mail servers retry automatically; most spam bots don't bother, so greylisting filters them out.

What you see: one 451 4.7.1 Greylisted per new recipient, followed by successful delivery on the retry (usually 10-30 minutes later). This is working as intended and is not a deliverability problem. Most corporate and small-business mail servers use greylisting.

When it becomes a problem:

1. 1Your sequencer's retry window is too short. Some sequencers retry in 2-5 minutes and give up after 3 attempts, which misses the greylisting release window. Set retry intervals to 15 min, 30 min, 1 hour, 4 hours (exponential backoff).
2. 2High-volume campaigns hit greylisting in a visible cluster. A 500-recipient campaign to corporate domains will log hundreds of 451s in the first hour, normal, resolves on retry. Your sequencer should track the final delivery state, not just the initial 451.
3. 3Repeated greylisting on the same recipient. If the same recipient greylists you on every send, the recipient's server is actually whitelisting trusted senders and not you. This is rare and usually needs the recipient to add you to an address book.

How to verify greylisting vs a real problem: wait 30 minutes after the 451, then check the sequencer. If the message delivered on retry, it was greylisting. If it's still bouncing, move to Fix 3 or Fix 4.

When Microsoft 365 or Gmail issues a sender-reputation soft bounce, it's a warning that your IP or domain is being temporarily de-prioritized. Repeat offenders get hard-blocked.

What these codes look like:

451 4.7.500 Server busy, please try again later [Microsoft 365]
550 5.7.520 Access denied, please try again later [Microsoft 365 - harder]
421-4.7.28 Gmail will not accept your message. Unusual traffic [Gmail]

Root causes in cold email setups:

Stop-the-bleed protocol for reputation-flagged soft bounces:

1. 1Pause the affected campaigns for 24-48 hours. Every additional rejected send compounds the reputation signal.
2. 2Keep warmup running. Warmup activity generates positive engagement that offsets the soft-bounce signal.
3. 3Check Postmaster Tools and blacklist status. If Domain Reputation is dropping, move to the full diagnosis in domain-blacklisted-diagnosis-guide.
4. 4Resume at 30-50% of previous volume after the pause window.

Some soft bounces have nothing to do with your sending setup, the recipient's mailbox or server is the problem. These codes are usually safe to ignore on the first occurrence:

When a soft bounce should be treated as a hard bounce: after 5 retry attempts over 72 hours, a persistent soft bounce is effectively a hard bounce for deliverability purposes. Remove the address from your list, further retries damage reputation.

Most sequencers have configurable "maximum retry attempts": set to 5-7 and "maximum retry duration" to 72 hours. Anything longer wastes capacity and compounds reputation issues. Reference bounce rate targets in cold-email-bounce-rate-benchmarks.

Soft bounces below 2% are normal background noise. Above that threshold, they start predicting hard bounces and reputation damage:

Track soft and hard bounces separately. A sequencer dashboard that combines them into a single "bounce rate" hides the signal. If your sequencer only shows combined bounces, export the raw SMTP logs weekly and compute the split manually, or use a tool that does it automatically.

One more pattern to watch: soft-to-hard conversion rate. If soft bounces are increasing and hard bounces are also increasing two days later, you're in an active reputation decay cycle. Pause, audit, and rebuild. This pattern is visible in email-deliverability-monitoring-setup.

InboxKit's soft bounce defense is baked into the infrastructure and monitoring layer:

Pricing: $39/mo for 10 slots ($3.50 extra) Professional, $99/mo for 30 slots ($3.25 extra) Agency. Warmup is a separate $3/mailbox/mo add-on. Full breakdown in inboxkit-pricing.

Most cold emailers discover too late that the soft bounce rate on shared-IP providers is structurally higher than on real mailboxes, not because of your behavior, but because the shared IP absorbs noise from every other customer. Migrating to real accounts typically drops soft bounce rate from 4-6% to under 2% without any other change.