User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/20070501 Firefox/188.8.131.52 Build Identifier: version 184.108.40.206 (20070326) I connect to a Merak mail server with the following capability: CAPABILITY IMAP4rev1 AUTH=NTLM AUTH=CRAM-MD5 AUTH=DIGEST-MD5 AUTH=LOGIN AUTH=PLAIN SORT THREAD-ORDEREDSUBJECT UIDPLUS QUOTA ACL NAMESPACE STARTTLS If I use TB2 constantly the IMAP connection will not timeout. But when I leave the client running for more than 1 hr, sometimes more, the connection to the server becomes broken. The server sometimes still shows the connection activate, but when you try an get mail or read mail it will not connect. The only way to restore the connection is to exit TB2 and go back in. This is happening about 2-3 times a day. This did not happen to TB 1.5.10. There is a firewall between the client and server, but nothing has changed, excpet for the TB upgrade to TB2. Reproducible: Always Steps to Reproduce: 1. Open TB2, read mail 2. Leave TB2 open for more than 1-2 hours 3. Get new mail or read mail, just get the scrolling progress bar. Connection broken I have been recording logs which I can send. Using standard TB2 theme
(In reply to comment #0) > If I use TB2 constantly the IMAP connection will not timeout. > But when I leave the client running for more than 1 hr, sometimes more, the connection to the server becomes broken. > The server sometimes still shows the connection activate, but when you try an get mail or read mail it will not connect. Sound similar situation to Bug 380342. To Master Abi(bug opener): Same asking as 378708 Comment #1 (for IMAP protocol log). > I have been recording logs which I can send Is it NSPR log by Tb? Log of network traffic by such as eathereal is not suitable for analysis of higher IMAP protocol level flow.
It is a NSPR log file.
(In reply to comment #2) > It is a NSPR log file. Please attach two NSPR log for IMAP as I asked in Bug 380342 Comment #1. (1) Normal flow (2) Around last normal access and first failure if log file is big. Can you find first error and split log file? How large is the log file?
Oh, it was Bug 378708 Comment #1. Sorry for mistake and spam.
OK, I will redo the logs and attach. Bug 378708 is an exact match to what I am experiencing. It once also stayed connected for up to 2 days.
This problem is now finally solved. I switched off the 'Show an alert' email notification. Now TB 2 does not timeout. But there is still an issue where it can and has happened. If I have more the one IMAP account, and I switch between the accounts, when I switch to the Merak IMAP account, it has happened that TB will not read anymore. So the popup email notification is causing the timeout to a Merak Server 8.0.3. I have not tried with other versions of Merak.
(In reply to comment #6) > So the popup email notification is causing the timeout to a Merak Server 8.0.3. > I have not tried with other versions of Merak. does your log show this? If not, please attach.
Very strange - I don't think the show alert notification really makes TB2 time out, but there might be some strange side effect, like our effort to fetch the body text snippet might be causing a server error or the server to return invalid protocol, causing a syntax error. A protocol log would help, but we don't have one. I'd suggest marking this incomplete unless we can get a log...
incomplete per comment 8. Master Abi, if you still see this please update the bug