From David's comment 26: > The try build only opens one connection to the server. This is a sensible thing to do. IMAP clients need to open multiple connections. NNTP clients don't. I didn't do anything in the patch that changed the number of connections to the server. Currently the default number of connections per nntp server is 2. (It can be changed in the prefs / Config Editor.) What I observer is if I have two groups subscribed on an nntp server and if I have "check for new messages at startup" selected, two connection will be created and both groups will be accessed in parallel using the their own connection after the first startup. If "check for new message at startup" is not selected and you are not selected on a group for that server at the last shutdown, on first startup no connection will occur until a group is selected and the one connection will be used to obtain new messages for that selected group. Then at the first biff interval (assuming biff is enabled) after startup (e.g., 50m point) you will have 2 connections. The original connection will probably be timed out after 50m so there will usually be two new connections created, one to replace the original timed out connection and one for the other group.
Bug 1901338 Comment 34 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
From David's comment 26: > The try build only opens one connection to the server. This is a sensible thing to do. IMAP clients need to open multiple connections. NNTP clients don't. I didn't do anything in the patch that changed the number of connections to the server. Currently the default number of connections per nntp server is 2. (It can be changed in the prefs / Config Editor.) What I observe is if I have two groups subscribed on an nntp server and if I have "check for new messages at startup" selected, two connection will be created and both groups will be accessed in parallel using their own connection after the first startup. If "check for new message at startup" is not selected and you are not selected on a group for that server at the last shutdown, on next startup no connection will occur until a group is selected and the one connection will be used to obtain new messages for that selected group. Then at the first biff interval (assuming biff is enabled) after startup (e.g., 50m point) you will have 2 connections. The original connection will probably be timed out after 50m so there will usually be two new connections created, one to replace the original timed out connection and one for the other group.