Bugzilla

(In reply to Wayne Mery (:wsmwk) from comment #9)
> Could the change to serializing pop accounts have side effects with these symptoms?

I tested with 3 pop3 account with one being unreachable (a POP3 test server is down) and several IMAP accounts. Don't see a problem.
Maybe the reporter macus could "disable" his POP3 accounts and restart TB and see if the the problem(s), at least with IMAP, still occur.

Reporter macus, to "disable" your POP3 account, go to the Server settings for each account and un-select ```Check for new messages at startup``` and disable ```Check for new messages every X minutes```. Then select Inbox on an imap account and restart TB. After restart, don't attempt to access or check for new messages on POP3 account. Just access other non-POP3 accounts as you normally would.

If you do this, do you still see problems?
Once this test is finished you can returned the POP3 server configurations back the way they were.

(In reply to Wayne Mery (:wsmwk) from comment #9)
> Could the change to serializing pop accounts have side effects with these symptoms?

I tested with 3 pop3 account with one being unreachable (a POP3 test server is down) and several IMAP accounts. Don't see a problem.
Maybe the reporter macus could "disable" his POP3 accounts and restart TB and see if the the problem(s), at least with IMAP, still occur.

Reporter macus, to "disable" your POP3 accounts, go to the Server settings for each account and un-select ```Check for new messages at startup``` and disable ```Check for new messages every X minutes```. Then select Inbox on an imap account and restart TB. After restart, don't attempt to access or check for new messages on POP3 account. Just access other non-POP3 accounts as you normally would.

If you do this, do you still see problems?
Once this test is finished you can returned the POP3 server configurations back the way they were.