What is greylisting delay?

A greylisting delay is the wait time between when a mail server temporarily rejects your email and when it tries again. It's part of a spam-fighting technique called greylisting, where the receiving server says "come back in 5-15 minutes" to any sender it doesn't recognize.

Here's what actually happens. Your mail server tries to deliver an email. The receiving server checks if it recognizes your sending server (your IP address and domain). If not, it responds with a temporary error code (typically 4.x.x) and tells your server to retry later. Legitimate mail servers (like SendGrid, Postmark, or your company's mail server) are configured to retry automatically. They'll wait a few minutes and try again. When they do, the receiving server says "okay, you came back, you're legit" and accepts the message.

Spammers typically don't retry. They're sending millions of messages from compromised servers or scripts that move on immediately if the first attempt fails. That's the whole point of greylisting. It filters out bulk spam while letting real mail through with a short delay.

The delay is usually 5-15 minutes, sometimes up to an hour depending on the server's configuration. That means if you send a password reset email to someone whose mail server uses greylisting, and you're sending from a new IP or domain they haven't seen before, that email might arrive 10 minutes late instead of instantly. For newsletters and marketing emails, no one notices. For transactional emails like password resets or two-factor codes, it can cause confusion.

What determines if your emails hit a greylisting delay? The receiving server keeps a list of senders it trusts (called a whitelist or greylist pass). If your sending IP has successfully retried before, you're on that list and future emails pass through immediately. If you're new, or if you're sending from a new IP, you'll trigger the delay once. After that, you're trusted.

So most modern ESPs handle this automatically. They retry failed deliveries without you needing to do anything. But if you're running your own mail server or using a custom SMTP setup, make sure your system is configured to retry temporary failures. If it doesn't retry, your emails won't deliver at all to servers using greylisting.

One common mistake: changing your sending IP address frequently. If you rotate IPs or send from a pool of IPs that aren't warmed up, you'll trigger greylisting delays more often because the receiving servers don't recognize any of your IPs. Consistent sending from the same IP (or IP pool) reduces greylisting delays over time.

Greylisting is less common now than it was 10-15 years ago. Most major mailbox providers (Gmail, Outlook, Yahoo) don't use it. Smaller organizations, universities, and some corporate mail servers still do. You can't avoid it entirely, but you can minimize how often it affects you by maintaining good sender reputation, warming up new IPs properly, and making sure your mail server retries temporary failures.

Want to see if greylisting is affecting your deliverability? Check your mail server logs for 4.x.x temporary error codes followed by successful retries. That's greylisting in action.