SMTP Response Codes, Deferrals and Throttling

Every time your server hands a message to a receiving mail server, it gets a reply. That reply is a short code followed by text, and it is the most direct feedback a mailbox provider gives. Senders who read these responses can see reputation problems forming days before inbox placement suffers.

How to Read a Response

An SMTP response has up to three parts:

550 5.7.1 Message rejected due to policy

• The three-digit reply code, here 550
• The enhanced status code, here 5.7.1
• Free text explaining the reason

Reply Code Classes

• 2xx means success. The server accepted the message.
• 4xx means temporary failure. The message was not accepted now, and the sender should try again later.
• 5xx means permanent failure. The message was rejected and should not be retried.

Enhanced Status Codes

The enhanced code has the form class.subject.detail. The middle number shows the category:

• x.1.x relates to addresses, such as an unknown recipient.
• x.2.x relates to the mailbox, such as one that is full.
• x.4.x relates to network and routing.
• x.7.x relates to security and policy. This is the category that matters most for deliverability.

Deferrals

A deferral is a 4xx response. The receiving server is declining the message for now. Your mail server queues it and retries on a schedule, typically for up to several days, before giving up and treating it as a bounce.

Deferrals happen for ordinary reasons, such as a busy server or a full mailbox. They also happen when a provider is uncertain about a sender and wants to slow them down.

A low deferral rate that clears on retry is normal, especially during warm-up. Deferrals that persist, grow or cite reputation are a warning.

Throttling and Rate Limiting

Mailbox providers limit how much mail they accept from a sender in a given period. The limits are not fixed. They depend on the reputation of your IP and domain, your history and how recipients are reacting.

When you exceed what a provider will accept, it responds with deferrals. Typical examples include:

• Gmail responses in the 421 4.7.x range, indicating that mail is being rate limited because of unusual volume or suspicious content
• Yahoo responses containing TSS04, indicating that messages are temporarily deferred because of unexpected volume or user complaints
• Microsoft responses in the 451 4.7.x range, indicating throttling linked to IP reputation

The exact wording changes over time, and each provider documents its current codes on its postmaster site.

Common Permanent Failures

• 550 5.1.1 means the recipient address does not exist. Remove it immediately.
• 552 5.2.2 means the mailbox is over quota. Some providers return this as a temporary 452 4.2.2.
• 550 5.7.1 is a general policy rejection, often tied to reputation, content or a blocklist.
• 550 5.7.26 is used by Gmail when a message fails authentication.
• 550 5.7.515 is used by Microsoft when a high-volume sender does not meet its authentication requirements.

The free text usually includes a link or keyword pointing to the specific cause. Read it. Two rejections with the same numeric code can have entirely different reasons.

How to Respond to Deferrals

Let Retries Work

Do not resend deferred messages manually or switch to another IP to force them through. Your mail server will retry. Forcing volume through a throttle confirms the provider's suspicion.

Slow Down

If deferrals from one provider are rising:

• Reduce sending speed and concurrent connections to that provider.
• Lower daily volume to that provider until deferrals clear.
• Prioritize your most engaged recipients.

Find the Cause

Throttling is a symptom. Look for what changed:

• A jump in volume
• A new or reactivated list segment
• A rise in spam complaints
• A new template or new link domain
• An authentication change

Know When to Give Up

Messages have a shelf life. A flash sale email delivered three days late does more harm than good. Set a sensible retry window for time-sensitive campaigns, so that stale messages expire instead of arriving late.

Bounce Classification

Your email platform turns SMTP responses into bounce categories. Check how it classifies them.

• Address failures such as 5.1.1 should suppress the address at once.
• Policy rejections such as 5.7.1 are about the sender, not the recipient. Suppressing those addresses is the wrong reaction. The fix is on your side.
• Repeated temporary failures to the same address over several sends may justify suppression.

A common mistake is treating every 5xx as a bad address. After a blocklisting, that can wipe out a large part of a healthy list.

Monitoring

Track these by mailbox provider, not only in total:

• Deferral rate
• Rejection rate and the most common reasons
• Time to delivery
• Queue size

A healthy program sees most mail accepted on the first attempt within seconds. Longer delivery times and growing queues at a single provider are often the first sign of a developing reputation problem.

Key Point

SMTP responses are the one channel through which mailbox providers tell you directly what they think of your mail. Keep the logs, review them by provider, and treat a pattern of policy-related 4.7.x and 5.7.x codes as an instruction to slow down and investigate.