Sign-up codes arriving an hour late? It may be greylisting
Short answer: If some customers get your sign-up codes, password resets or booking confirmations 20 minutes to an hour late, while most get them instantly, the receiving mail server may be greylisting you: it temporarily rejects mail from senders it hasn't seen before and only accepts the retry. You can't switch greylisting off on someone else's server, but you can make sure your sending service retries quickly and from consistent addresses, check your delivery logs for temporary 4xx responses, and design login flows so a delayed email isn't a dead end.
What greylisting is
Greylisting is an anti-spam technique described in RFC 6647. The receiving server records details of an incoming delivery attempt, typically the sending IP address, the sender address and the recipient. If it hasn't seen that combination before, or the record hasn't reached a minimum age, it answers with a temporary failure (a 4xx SMTP reply) and invites a later retry. The RFC gives "30 minutes since the initial connection attempt" as an example of such a minimum age.
The theory is that spam software often doesn't retry, while legitimate mail servers do. A proper retry arrives later and is accepted.
The RFC is frank about the cost: the most obvious drawback is delay on legitimate mail. It notes that some popular mail servers don't retry failed deliveries for an hour or more, which causes expensive delays when mail is time-critical, and that some legitimate senders don't retry at all.
Why it hits verification emails hardest
Most of your email can wait an hour. Codes and links can't:
- A customer signing up waits on the "check your email" screen, then gives up.
- A one-time code expires before it arrives.
- A password reset arrives after the customer has already requested three more, and the first link no longer works.
- A booking confirmation arrives after the customer has phoned you to check.
Greylisting is more common at smaller mail providers, company mail servers and some regional internet providers than at the big free webmail services, which is why the problem often appears for "only some customers".
How to confirm it's greylisting
Look at the delivery events in your email sending service or server logs for an affected message:
- A temporary failure first. You'll see a 4xx response such as 421 or 450 from the recipient's server, often with words like "greylisted", "try again later" or "please retry".
- Then a successful retry. A later attempt to the same recipient is accepted with a 250 response.
- A pattern by domain. Delays cluster on particular recipient domains, not across everyone.
If you see permanent 5xx failures instead, that's a different problem: a block or a bad address, not greylisting.
What you can do as the sender
You can't change the recipient's policy, but you can shorten the delay and avoid triggering it repeatedly.
Retry promptly. RFC 5321, the core email standard, says a sender must wait after a failed attempt and that the retry interval should generally be at least 30 minutes, with smarter strategies beneficial when the sender can tell why delivery failed. Many sending services retry greylisted mail sooner than that. If you run your own mail server, check its retry schedule; if you use a sending service, check its documentation on deferrals.
Send from consistent infrastructure. Greylisting remembers sender combinations. If your mail goes out from a large, rotating pool of IP addresses, each attempt can look new. A transactional email service with a stable sending pool, or a dedicated address for your login mail, can help.
Keep the sender address stable. Don't put random strings in the envelope sender for every message unless your sending service handles that for bounce tracking and is known to cope with greylisting.
Separate login mail from marketing. Send codes and resets through a transactional stream, not a bulk newsletter system that may queue and throttle.
Design so a delay isn't fatal
Even with a good sender, some delays will happen. Make the experience survive them:
- Tell people what to expect. "It can take a few minutes. Check spam or promotions too."
- Give a resend button with a sensible wait, and make sure the latest code is accepted alongside a recent earlier one, or say clearly that only the newest works.
- Use reasonable code lifetimes. A code that expires in two minutes guarantees failures for greylisted recipients.
- Offer another route, such as a passkey, a sign-in with an existing provider, or an SMS code if you already collect numbers.
- Let support resend or check delivery status instead of guessing.
Watch it over time
Add a simple check to your monitoring: the share of verification emails delivered within five minutes, broken down by recipient domain. A sudden drop for one domain usually means a new filtering rule there; a drop across all domains points at your own sending setup. Review it monthly, and after any change of email provider, sending domain or DNS records, since each of those can make your mail look new to greylisting servers again.
An illustrative example
A hypothetical Galway accountancy software firm's trial sign-ups from some business email domains stalled at "verify your email". Delivery logs showed 450 "greylisted, try again later" replies, then successful deliveries 35 to 60 minutes later. The firm moved verification mail to a transactional sending service with prompt retries, extended the link's validity, added "still waiting? resend" after a minute, and let users continue setting up their account while verification was pending.
FAQ
Can I ask the recipient's IT team to allowlist us?
For a business customer, yes. Many greylisting setups have allowlists for known senders. Give them your sending domain and IPs.
Does SPF or DKIM stop greylisting?
Not necessarily. Some servers skip greylisting for well-authenticated senders, but it depends on their configuration.
Is a 4xx response a bounce?
No. It's a temporary failure. Your system should retry, not mark the address as bad.
Will this affect my newsletter too?
Yes, but a delay there rarely matters.
If customers say your codes or reset emails arrive late, and you'd like your sending setup and login flow checked, tell us which email service you use.