Bugzilla

Hi Richard,
I think what you observe in your two use cases is pretty much expected behavior. Say the computer sleeps or hibernates. After a while (30 minutes per imap spec, but some servers quicker) the server times out the connection due to inactivity. When the computer then wakes up, the connections are all half-closed since TB doesn't know they are closed (but the server does). So TB does nothing until the next biff time (check for new mail time) occurs. I think the biff time is measured as TB operating time and not based on actual wall time, but not sure. So then at first biff after wake up, TB tries to check for new mail (typically just sends NOOP) and receives an error that there is no connection. So only now does TB know the connection is closed and then creates a new one to retry the NOOP command and normal checks for new mail cycles resume.

So if biff time is set to, say, 25m, you might not receive new mail until 25m after the computer wakes up (unless you click get messages or re-select inbox, as you describe).
Note: I recommended to set biff time to no more than 30m so the server doesn't close/timeout the Inbox imap connection while computer is awake. This will still allow the imap IDLE command to signal there are new messages immediately when they arrive, provided the server supports IDLE and it is enabled with TB's server setting "allow immediate notification when new mail arrives.

Edit: Some of this is just WRONG. See next comment 14.
Hi Richard,
I think what you observe in your two use cases is pretty much expected behavior. Say the computer sleeps or hibernates. After a while (30 minutes per imap spec, but some servers quicker) the server times out the connection due to inactivity. When the computer then wakes up, the connections are all half-closed since TB doesn't know they are closed (but the server does). So TB does nothing until the next biff time (check for new mail time) occurs. I think the biff time is measured as TB operating time and not based on actual wall time, but not sure. So then at first biff after wake up, TB tries to check for new mail (typically just sends NOOP) and receives an error that there is no connection. So only now does TB know the connection is closed and then creates a new one to retry the NOOP command and normal checks for new mail cycles resume.

So if biff time is set to, say, 25m, you might not receive new mail until 25m after the computer wakes up (unless you click get messages or re-select inbox, as you describe).
Note: I recommended to set biff time to no more than 30m so the server doesn't close/timeout the Inbox imap connection while computer is awake. This will still allow the imap IDLE command to signal there are new messages immediately when they arrive, provided the server supports IDLE and it is enabled with TB's server setting "allow immediate notification when new mail arrives.