Topic · Deliverability
Greylisting
Greylisting is a receiver-side technique that temporarily defers unfamiliar mail and expects the sender to retry.
How it works
The receiver initially issues a temporary SMTP failure based on sender and recipient characteristics before later acceptance.
What can go wrong
Poorly configured retry queues can turn an intended delay into message loss or long delivery latency.
What to check or do
Confirm MTAs retry correctly and distinguish expected greylisting from persistent rate-limit or reputation blocks.
How to investigate Greylisting
- Signal to investigate
- A first-time sender sees 451 or 4xx deferral but later succeeds.
- Evidence to collect
- Track the same sending IP, envelope identities and destination across multiple retries.
- Common wrong conclusion
- Greylisting usually expects a retry; immediately removing the recipient is the wrong response.
How to interpret the evidence
Receivers can defer unfamiliar sender tuples to distinguish normal MTAs from scripts that do not retry. Modern filtering may combine this with rate limits, so not every 4xx is greylisting.
What to change and how to verify it
Ensure the MTA has sane retry intervals and consistent outbound identity; investigate if delivery never succeeds.
Put this into practice
Run a focused check, then explore protection if your domain needs it.