Internet How the web works under the address bar
How long does Gmail retry sending an email?
About two days: what Gmail's Delivery incomplete notice says, why a typo bounces at once, and how Outlook, Exchange and Postfix retry times compare.
The short answer
- Gmail keeps retrying an email that hit a temporary problem for about two days. Its "Delivery incomplete" notice says "Gmail will retry for 46 more hours", and a later notice counts down.
- Google's own help page on bounced email gives no hour count, so the notices themselves are the best public evidence of Gmail's window.
- Only temporary errors, which mail servers mark with a code starting with 4, are retried. A permanent error starting with 5, such as an address that does not exist, bounces right away with no retry.
- Other senders use other clocks: Microsoft 365 gives up after 24 hours by default, Exchange Server after 2 days, and Postfix after 5 days. The email standard says at least 4 to 5 days.
- The clock that counts belongs to the sender's mail service, not the recipient's, so the same broken inbox can bounce a Microsoft 365 email after one day and a Postfix email after five.
Gmail keeps trying for about two days. When an email hits a temporary problem, Gmail sends you a notice headed "Delivery incomplete". A real one, kept in a public mailing list archive, reads: "There was a temporary problem delivering your message. Gmail will retry for 46 more hours. You'll be notified if the delivery fails permanently." If the problem is still there when that time runs out, the email bounces for good. But that only applies to temporary problems. If the address does not exist, the email bounces right away, with no retry at all. And if you are sending from Outlook, a work account or your own server, a different clock applies.
What retrying and bouncing mean
When you press Send, your email does not go straight to the other person's inbox. It goes to your provider's mail server first. That server looks up where the recipient's mail is handled, using the MX record that DNS keeps for every mail domain. Then it connects to the recipient's mail server and offers the message.
The recipient's server answers with a three-digit reply code. The email standard, RFC 5321, sorts those answers by their first digit.
- A code starting with 2 means the message was accepted.
- A code starting with 4 is a temporary failure. The standard says the error "is temporary, and the action may be requested again." Code 450, for example, means the mailbox is busy or temporarily blocked.
- A code starting with 5 is a permanent failure. The sender "SHOULD NOT repeat the exact request." Code 550 covers a mailbox that was not found.
A retry is your server trying again after a temporary failure. It keeps the email in a waiting line called the queue and tries every so often. A bounce is the message your server sends back to you to say it has given up. People call the permanent kind a hard bounce and the temporary kind a soft bounce.
So the question "how long before it bounces" has two answers. A hard bounce comes back as soon as the receiving server refuses the message. A soft bounce comes back only when the sender's retry window runs out.
What Gmail's notice actually says
Google does not publish its retry window. Its help page "Fix bounced or rejected emails" explains the two kinds of failure. For a temporary problem, it says the recipient's server may be "busy, offline, or experiences a temporary technical issue." Its advice is to "send the message again at a later time." It gives no number of hours or days, and Google publishes no setting to change the window.
The number comes from Gmail's own notices. Two of them sit in the public archive of a RIPE NCC mailing list. Both are about the same Gmail address. The one filed on June 9, 2017 says "Gmail will retry for 46 more hours." The one filed the next day says "Gmail will retry for 23 more hours." Neither shows an error code or a server name.
Two things follow from that wording. First, the figure is a countdown, not a fixed promise. A later notice shows fewer hours left. Second, both notices fit a total window of roughly two days. Google does not say when in that window the first notice goes out, so treat "about 48 hours" as the shape of it, not an exact figure.
One email, walked through two ways
Take an email you send from Gmail at 9 a.m. on a Monday to a small company. Suppose the company's mail server has crashed over the weekend.
Gmail's server connects, and the company's server either does not answer or replies with a temporary error. Gmail puts the email in its queue. Some time later you get a Delivery incomplete notice saying Gmail will retry for 46 more hours. Gmail keeps trying in the background. Suppose the company fixes its server on Tuesday afternoon. The next retry gets through, and the email lands in the inbox about a day late. You get no message telling you it worked. The notice only promises to tell you if delivery "fails permanently."
Now suppose the server stays down until Thursday. About two days after you pressed Send, around Wednesday morning, the window runs out. Gmail stops trying and sends you a final failure notice. The email is never delivered, and you have to send it again once the server is back.
Now change one letter. Suppose you typed the address with a mistake in the name before the @. The company's server is working fine. It replies with a 550 code, mailbox not found. That is permanent, so Gmail does not queue the email at all. The bounce reaches you right away, and waiting two days would not have changed it.
How long other email services keep trying
Gmail's two days is shorter than the email standard suggests. RFC 5321, section 4.5.4.1, says retries continue "until the message is transmitted or the sender gives up; the give-up time generally needs to be at least 4-5 days." It also says the gap between tries "SHOULD be at least 30 minutes," and that the settings "MUST be configurable." Each mail system picks its own numbers.
| Sending service | Gives up after | Can it be changed? | Where the figure comes from |
|---|---|---|---|
| Gmail | About 2 days (notice says "46 more hours") | No published setting | Gmail's Delivery incomplete notices. Google's help page gives no number. |
| Microsoft 365 (Exchange Online) | 24 hours | Yes, from 12 to 24 hours for the whole organization | Microsoft Learn, queued messages report and Set-TransportConfig |
| Exchange Server 2016, 2019 and Subscription Edition | 2 days, with a delay warning after 4 hours | Yes, by the administrator | Microsoft Learn, message expiration interval |
| Postfix | 5 days | Yes, by the administrator | Postfix maximal_queue_lifetime default |
| The email standard (RFC 5321) | "At least 4-5 days" in general | Must be configurable | RFC 5321 section 4.5.4.1 |
A few details sit behind those rows. Microsoft says that for messages queued in Microsoft 365, it "continues to retry to delivery for 24 hours." After that, the messages "will expire and will be returned to the senders" as bounces. Its MessageExpiration setting defaults to one day and accepts 12 hours to 24 hours, so an organization can only make the window shorter.
Exchange Server, the version a company runs on its own machines, retries a message every 15 minutes by default. It warns the sender after 4 hours and gives up after 2 days. Postfix, a mail server common on Linux machines, waits between 300 and 4,000 seconds between tries by default. It gives up when a message has sat in the queue for 5 days. The administrator can change all of these.
Whose clock counts
The retry window belongs to the sender's mail service, not the recipient's. The recipient's server only says "not now." It is the sending server that keeps the email, decides when to try again and decides when to quit.
That settles the most common confusion. Many pages quote the 4 to 5 days from the email standard as if every email gets that long. It does not. If a Gmail user's inbox is unreachable, an email sent to it from a Microsoft 365 work account gets 24 hours. One sent from a server running Postfix on its defaults gets 5 days. One sent from another Gmail account gets about two. The 4 to 5 days survives because it is the only number in the standard, and the standard is what people quote.
The same logic tells you which number applies to you. Look at the account you sent from, not the address you sent to. A school or work account may run on Microsoft 365, Exchange Server or something else entirely, and its administrator may have changed the default.
What this answer does not cover
Gmail's figure comes from its own notices, and the archived ones date from 2017. Google has published no number, so it can change the window without saying so. The table gives defaults, and any administrator can change them. A message the receiving server accepted and then filed as spam is not a bounce and is never retried, so none of these clocks applies to it. The standard itself admits that two servers may not agree on what counts as temporary. So a problem marked with a 4 can last the whole window and still end in a bounce. Google Workspace accounts are run by Google, but Google publishes no separate figure for them.
What to do when you get a delivery notice
- Read which kind it is. "Delivery incomplete" and "will retry" mean a temporary problem, and Gmail is still trying. A notice saying the address was not found is a hard bounce, and nothing more will happen.
- For a hard bounce, check the address. Look hardest at the part after the @, the domain, the same part that decides where a web link really goes. If the address was right, the account may have been closed, which is what happens to email accounts left unused too long.
- For a soft bounce, do not resend straight away. Gmail still has the message. If you send it again, both copies may arrive once the server recovers.
- If it is urgent, use another channel. Call or text the person while Gmail keeps trying. A crashed company server is often fixed within the window.
- Be wary of delivery notices you did not expect. A message dressed up as a delivery notice can be a scam. Check that it refers to an email you really sent, and learn how fake messages get past careful people. The red flags in scam emails apply to fake system notices too.
- Keep your own account safe. If bounces arrive for emails you never sent, someone may have sent mail in your name. Check your account's recent activity, and start with locking down your email account.
Common questions
Should I resend an email after a Delivery incomplete notice?
Not straight away. The notice means Gmail still holds the message and is still trying. If you send it again and the recipient's server recovers, both copies can arrive. Wait for either silence, which usually means it got through, or a final failure notice. If the message is urgent, reach the person another way, such as a call or a text, while Gmail keeps trying.
Does Gmail tell you when the retried email finally gets through?
No. The notice promises the opposite case only: "You'll be notified if the delivery fails permanently." A successful delivery after a delay sends you nothing. So if a Delivery incomplete notice is the last thing you heard, and the retry window has passed with no failure notice, the message most likely arrived. Ask the recipient to check, including their spam folder.
What is the difference between a soft bounce and a hard bounce?
A soft bounce is a temporary failure, such as a server that is down or busy. Mail servers mark it with a reply code starting with 4, and the sender keeps trying. A hard bounce is a permanent failure, such as an address that does not exist, marked with a code starting with 5. The email standard says the sender should not repeat that request, so it comes straight back.
Can I make Gmail retry for longer or shorter?
Google publishes no setting for a personal Gmail account, and its help page on bounced email gives no retry figure at all. The window is part of how Google runs its mail servers. Administrators of other systems can change theirs: Postfix and Exchange Server allow any value, and Microsoft 365 lets an organization pick from 12 to 24 hours.
Why did my email bounce instantly instead of being retried?
Because the receiving server gave a permanent answer. The most common one is that the mailbox does not exist, often because of a typo or because the account was closed. Retrying cannot fix that, so the sender stops at once. Check every letter of the address, especially the part after the @, which names the domain.
Sources
- Gmail Delivery incomplete notice, "Gmail will retry for 46 more hours" (routing-wg list archive, 9 June 2017), RIPE NCC
- Gmail Delivery incomplete notice, "Gmail will retry for 23 more hours" (routing-wg list archive, 10 June 2017), RIPE NCC
- Fix bounced or rejected emails, Gmail Help
- RFC 5321: Simple Mail Transfer Protocol (sections 4.2.1, 4.2.3 and 4.5.4.1), IETF / RFC Editor
- Postfix configuration parameters (maximal_queue_lifetime, minimal_backoff_time, maximal_backoff_time), Postfix
- Message retry, resubmit, and expiration intervals, Microsoft Learn
- Queued messages report in the new EAC in Exchange Online, Microsoft Learn
- Set-TransportConfig (MessageExpiration parameter), Microsoft Learn