Bug 1911950 Comment 25 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

I'm now using your python server and it's working better than my own. It's producing the same network and imap log activity as your attachments.

Your pcap trace attachment took over 24 hours to cause TB to lock up. At another place (comment 10) you said the lock up occurs in 92 minutes.

In comment 12 you said:
>I have found another way to have the server greet with * BYE, and the network package sequence results are similar. Just this server is requested, no other servers (imap or pop3). There was no hang in this situation. I cannot keep the server running in this state, I need mail to work.

So I'm wondering how long and under what server setup the lockup/hang occurs? Does it only occur with your "real" (PM?) server and will it also happen with the python (only sends BYE) server? What is the "another way".

Possibly I need to go into the TB "biff" code and set the check for new mail timer down to something very short, like maybe 10 or 5 seconds, since in "server setting" you can only set it to X minutes.
I'm now using your python server and it's working better than my own. It's producing the same network and imap log activity as your attachments.

Your pcap trace attachment took over 24 hours to cause TB to lock up. At another place (comment 10) you said the lock up occurs in 92 minutes.

In comment 12 you said:
>I have found another way to have the server greet with * BYE, and the network package sequence results are similar. Just this server is requested, no other servers (imap or pop3). There was no hang in this situation. I cannot keep the server running in this state, I need mail to work.

So I'm wondering how long and under what server setup the lockup/hang occurs? Does it only occur with your "real" (PM?) server and will it also happen with the python (only sends BYE) server? What is the "another way".

Possibly I need to go into the TB "biff" code and set the check for new mail timer down to something very short, like maybe 10 or 5 seconds, since in "server setting" you can only set it to X minutes.
**Edit:** I hardcoded the "biff" time to 1 sec. So far, still running. Hitting the "bye" server every second on the 2 connections.

Back to Bug 1911950 Comment 25