Email greylisting in 2026: what it is and how it affects cold-email delivery
Greylisting is a 20-year-old spam-prevention trick that some receivers still use. It introduces a 5-30 minute delay on first delivery and shows up in your logs as a soft bounce.
Rejwan Nirob·May 23, 2026·5 min readGreylisting is a spam-prevention technique invented in 2003 that some receivers still use in 2026. When a sender unknown to the receiving server attempts delivery, the server temporarily rejects with an SMTP 4xx code, expecting the sender to retry within a few minutes. Real mail servers retry; many spam bots do not. The technique reduces spam by filtering out non-compliant senders.
What you see when it happens
In your sending tool's logs, greylisting shows up as a soft bounce with a 4xx code (typically 421, 450, or 451) and a message like "Greylisting in effect, please try again." Standard SMTP clients (Gmail, M365 outbound, the major sending tools) automatically retry after a few minutes and the message delivers on the second attempt.
Who still uses greylisting
Gmail and Microsoft 365 do not use greylisting by default. Some self-hosted mail servers (Postfix with Postgrey, Exim with greylistd) still do, particularly at smaller hosting providers and universities. The percentage of receivers using greylisting in 2026 is small but non-zero - maybe 1-2 percent of B2B recipients in our partner-program telemetry.
Why it matters for cold email
Three things to know. (1) The 5-30 minute delay can affect time-sensitive outreach (event invitations, time-bound offers). (2) Greylisting soft bounces look like deliverability problems in dashboards that do not distinguish between greylisting and genuine issues - the bounce gets logged but the message eventually delivers. (3) A surge of greylisting bounces is sometimes mistaken for sender-reputation problems and triggers unnecessary "remediation."
How sending tools handle it
Smartlead, Instantly, Lemlist, and Apollo all handle greylisting automatically - they treat the 4xx response as "retry later," queue the message, and re-attempt after a configurable delay (typically 5-15 minutes). The user does not have to do anything. The bounce shows up briefly in the log and disappears on retry success.
“Greylisting is a rare-enough phenomenon in 2026 that you can mostly ignore it. The sending tool handles the retry, the message delivers, and your dashboard self-corrects within minutes.”
When greylisting is actually a problem
If your sending tool does not retry on 4xx responses, the message stays "soft bounced" forever and you incorrectly suppress the recipient. Modern tools handle this correctly; older or self-built SMTP integrations sometimes do not. Verify behaviour by sending a test to an address known to greylist and confirming the retry-success log entry.
What greylisting does NOT do
Greylisting does not reflect your sender reputation. It triggers on novelty (the receiving server has not seen mail from your sending IP recently), not on quality. A clean reputation-perfect cold-email sender hits greylisting at the same rate as a spam botnet on the first delivery attempt. The difference is the retry behaviour, not the trigger.
Inboxlee distinguishes greylisting from real soft bounces in the dashboard - a 4xx that resolves on retry is not flagged as a deliverability problem. Real soft bounces (consecutive failures, quota-exceeded patterns) still surface for action.
See deliverability monitoringFrequently asked
What is email greylisting?
A spam-prevention technique where the receiving server temporarily rejects mail from unknown senders with an SMTP 4xx code (typically 421, 450, or 451), expecting the sender to retry within a few minutes. Real mail servers retry and the message delivers on the second attempt; many spam bots do not retry. Invented in 2003 and still used by some receivers in 2026.
Does Gmail or Microsoft 365 use greylisting?
No, neither uses greylisting by default. Greylisting is most common at self-hosted mail servers (Postfix with Postgrey, Exim with greylistd) and at smaller hosting providers or universities. In 2026, roughly 1-2 percent of B2B recipients sit behind greylisting servers - small but non-zero.
Does greylisting affect cold-email deliverability?
Slightly. Greylisting introduces a 5-30 minute delay on first delivery and shows up as a soft bounce in sending-tool logs before the retry succeeds. The delay can affect time-sensitive outreach. Surge of greylisting bounces is sometimes misread as a sender-reputation problem when it is just normal first-contact behaviour from a greylisting receiver.
Do I have to manually retry greylisted messages?
No. Smartlead, Instantly, Lemlist, and Apollo all retry automatically on 4xx responses (typically 5-15 minutes later). The user does not have to do anything. The bounce shows up briefly in the log and disappears on retry success. Only older or self-built SMTP integrations require manual retry logic.
Is greylisting a sender-reputation signal?
No. Greylisting triggers on novelty (the receiving server has not seen mail from your sending IP recently), not on sender quality. A clean reputation-perfect cold-email sender hits greylisting at the same rate as a spam botnet on the first delivery attempt. The difference is the retry behaviour, not the trigger.