Skip to content
Glossary · SMTP

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.

Sources

What this definition rests on. The wording is ours; the facts are theirs.

All 432 terms in the glossaryThe wiki: blocklists and bounce codes

Beat · paid monitoring

A heartbeat for your email.

Beat runs every check on this site on a schedule: 41 checks, 25 blacklists and real inbox placement. The moment something breaks, it tells you what broke, why it matters, and the exact fix.

example.comWatching
  • SPFpass
  • DKIMpass
  • DMARCp=none
  • Blacklists0 of 25

Illustrative. Your domain, every few hours.

Also from us:Pulse: your own sending infrastructureConsulting: $65/hr, no retainer