Greylisting
What is Greylisting?
Greylisting is a spam-reduction technique where a mail server temporarily rejects an unfamiliar sender with an SMTP 4xx code, then accepts the message once it retries, relying on RFC 5321's retry requirement. Spam infrastructure of the era often never retried. AdminKit's MX lookup tool shows which mail server handles a domain's inbound mail so a greylisting setup can be reviewed.
By AdminKit team, Netbase JSC · Updated
Greylisting is a spam-reduction technique where a receiving mail server temporarily rejects an unfamiliar sender/recipient/IP combination with a standard SMTP 4xx temporary-failure code, then accepts the message once the same sender retries after a short delay. The technique, described by Evan Harris in 2003, relies on RFC 5321’s requirement, documented at its IETF Datatracker entry, that a compliant SMTP server must queue and retry temporary failures — the same mechanism Postgrey, a widely deployed greylisting policy server, implements for Postfix: well-behaved mail servers retry automatically, while much of the spam-sending infrastructure of the time fired messages once and moved on. OpenBSD’s spamd(8) is another implementation: in its default mode it greylists connections from new hosts, giving them a temporary failure message when they try to deliver mail until they pass its checks and are whitelisted. Greylisting adds delivery latency, typically minutes, to first-time senders, its main downside for time-sensitive mail. It’s largely a legacy technique now, since modern filtering leans more on SPF, DKIM, DMARC and sender reputation, but many mail servers still layer it on as one more low-cost check. AdminKit’s MX lookup tool shows which mail server handles a domain’s inbound mail so its configuration can be reviewed.
Greylisting is part of AdminKit’s email authentication cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
Why does greylisting actually reduce spam?
Because it relies on RFC 5321's requirement that a compliant SMTP server must queue and retry temporary failures -- well-behaved mail servers retry automatically, while much of the spam-sending infrastructure of the time fired messages once and moved on.
What's the main downside of greylisting?
Delivery latency for first-time senders, typically minutes, since the message isn't accepted until the sending server's retry -- a real cost for time-sensitive mail even though it's otherwise a low-cost spam check.
Is greylisting still widely used today?
It's largely a legacy technique now, since modern filtering leans more on SPF, DKIM, DMARC and sender reputation, but many mail servers still layer it on as one more low-cost check.
What software commonly implements greylisting?
Postgrey is a widely deployed greylisting policy server for Postfix, implementing the same temporarily-reject-then-accept-on-retry mechanism the technique relies on.