Greylisting is a spam-filtering technique where a receiving mail server temporarily rejects a message from an unrecognized sender, expecting a legitimate mail server to retry after a delay, since most spam-sending software doesn't bother.
Greylisting is a bet that spammers won't retry. When a message arrives from an unfamiliar combination of sending IP, envelope sender and recipient, the receiving server answers with a temporary failure, a 4xx code, instead of accepting it. RFC 6647 says the only reasonable choices are 421 and 450. A real mail server queues the message and tries again. Greylisting assumes bulk spam software often doesn't, so the message disappears.
On the retry, the server recognizes the combination and lets the message through, then usually allows further mail from that IP. The RFC describes a default retry window of one minute to 24 hours, with records kept at least a week. A retry after the window counts as a new message and gets delayed again.
Delay, mostly. The RFC notes that some popular mail transfer agents don't retry for an hour or more, so a first email to a greylisting domain can land late. Sending through several outbound servers can trip it repeatedly, because a retry that leaves from a different IP looks like a new sender. And a sender that never retries, or reads a 4xx as final, loses the message. The RFC says such clients aren't fully SMTP-capable.
Worked example. An email goes out at 9:00 and gets a 450. The sequencer retries at 9:30, which is the RFC's own example delay, and the message lands. Depending on the tool, that half hour is invisible, or the 450 gets logged as a bounce and a good address ends up suppressed.
Greylisting rarely shows up as a campaign problem. It shows up as odd delays: the same message arrives late at one company and instantly at another. Check the logs for 4xx codes before calling anything a bounce, since a soft failure that later succeeds isn't a bad address. If a sequencer treats every 4xx as permanent, it will quietly drop good contacts from the list.
People read greylisting as a block, or as a sign the sender has a bad reputation. It's neither. It's applied to unfamiliar sender and recipient combinations whatever their quality, and a message that retries properly is accepted. It isn't foolproof either, as the RFC itself says. Treat a 4xx as a delay to watch, not a verdict on the sender.
Tell us how your motion runs today. We'll show you what we'd engineer.
Contact us