IMAP IDLE connection dropped: no push notifications / "connection lost" after idle (NAT or firewall timeout)
IMAP IDLE connections silently die after minutes, so new mail doesn't arrive instantly or the client reconnects constantly.
IMAP IDLE connection droppedIMAP IDLE timeout push notifications not workingConnection lost after idle Thunderbird IMAPIDLE connection closed by server Meaning
NAT/firewalls drop idle TCP connections after their timeout (often 5-30 minutes). Clients should re-issue IDLE every 10-29 minutes or use shorter keepalives; servers can set imap_idle_notify_interval. Enable TCP keepalive and raise the device's idle timeout where possible.
Common causes
- Firewall/NAT idle timeout
- Mobile network switching
- Client not refreshing IDLE
- Server
imap_idle_notify_intervaltoo high - Proxy/load balancer timeouts
⚡ Quick fix
- Send IDLE keepalives every ~10 min (
imap_idle_notify_interval = 2 mins) - Enable TCP keepalive
- Raise the NAT/LB idle timeout
Detailed fix by platform
Dovecot
- bash
imap_idle_notify_interval = 2 mins # kernel: net.ipv4.tcp_keepalive_time = 240
How to diagnose
- Drop time — Constant?
- Keepalive — Enabled?
- Timeout — Device?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- Idle connections silently dropped by firewall/NAT Networking: Connection works, then fails after being idle — firewall/NAT idle timeout dropped the TCP session (use keepalive)
- IMAP: [AUTHENTICATIONFAILED] Invalid credentials IMAP: NO [AUTHENTICATIONFAILED] Invalid credentials (Failure)
- IMAP: Too many simultaneous connections IMAP: NO [ALERT] Too many simultaneous connections. (Failure)
Most viewed in Email / SMTP
- 550 5.7.1 550 5.7.1 Relaying denied / Message rejected as spam / Unauthenticated email not accepted
- Laravel: Connection could not be established with host Laravel: Symfony\Component\Mailer\Exception\TransportException: Connection could not be established with host "smtp.mailtrap.io:2525": stream_socket_client(): Unable to connect
- SES: Maximum sending rate exceeded Amazon SES: Throttling — Maximum sending rate exceeded (454 Throttling failure)
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 18 Nov 2026