Retry schedule
The timing a sending server follows to re-attempt a temporarily failed delivery, from the first retry to the moment it gives up and bounces the message.
What it means
RFC 5321 sets the frame. After a failed attempt the sender must wait before trying the same destination again; the retry interval should generally be at least 30 minutes, and the overall give-up time generally at least 4 to 5 days. It observes that two attempts in the first hour, then one every two or three hours, suits typical transient failures. MTAs make this configurable; Postfix, for example, sets the range of waits with minimal_backoff_time and maximal_backoff_time.
Retry timing interacts with receivers' defences. Greylisting refuses a new sender until a minimum delay has passed, so a sender that never retries never gets through, and providers that throttle expect senders to slow down rather than reconnect at once. Gmail's guidance after a 4.7.28 rate limit is to stop sending for at least 10 minutes, then resume on a single connection.
Related terms
Sources
What this definition rests on. The wording is ours; the facts are theirs.
- RFC 5321, section 4.5.4.1: Sending Strategyrfc-editor.org
- Postfix configuration parameters, postconf(5)postfix.org
- Google, Gmail Help: Email sender guidelinessupport.google.com
All 432 terms in the glossaryThe wiki: blocklists and bounce codes