Fran Fabrizio wrote:
The setup: Thunderbird email client, courier-imap 3.0.8, this problem
happens from both windows and linux clients, running various recent
versions of Thunderbird. No firewall or router between client and
server, all on same subnet.
3.0.8 is anciently old, strongly consider you investigate upgrading to
the latest version and see if it fixes the issue.
The symptoms are that for folders with large numbers of messages
(around > 2000) the operations timeout after exactly 60 seconds. By
operations I mean if I click on a folder to open it, exactly 60
seconds after the Thunderbird status bar reports Opening Folder... it
will report "connection to server timed out". If I do have a large
folder opened successfully and I select all messages and attempt to
drag to Trash, again, exactly 60 seconds after Thunderbird reports
"Moving messages to INBOX.Trash" it will time out.
I would not consider 2000 all that large of a folder, I've used TB with
folders of 100,000 messages and it's worked once I resolved some
ENHANCED_IDLE issues (or else completely compiled Courier w/o FAM/Gamin
support). If you're not using ENHANCED_IDLE, you might consider
recompiling without FAM support, the only way to do this is to remove
and fam-devel or gamin-devel packages from your install and recompile.
With logging on, nothing at all appears in the courier-imap log at the
moment of timeout, and there are no TIMEOUT or DISCONNECTED messages
from these clients in the log. The server appears to be continuing to
complete the task, since I still see that the processes are active in
the output of 'top' even after the timeout. In the case of the moving
of messages, the size of Trash is growing, but the size of the
original folder is not shrinking.
Yes, TB probably is marking the messages with a deleted flag but won't
actually purge the folder till later, this is generally quicker and
keeps your data safe also.
Settings that might be related:
In courier-imap's imapd config file
MAXDAEMONS=100 (only in the mid-20s during the testing, so this isn't
coming into play)
MAXPERIP=10 (with Thunderbird set at max of 5 cached connections this
isn't coming into play either)
IMAP_IDLE_TIMEOUT=180 IMAP_ENHANCEDIDLE=0
Thunderbird has no timeout settings and the best I can discover online
is that "it has been reported that the default Thunderbird timeout
should be sufficient." So, I have no idea what that means but I do
know that in other setups Thunderbird can perform operations that last
longer than 60 seconds. I have max cached connections in Thunderbird
currently set to 3 but have tried with 1 and 5 with the same results.
Are you using the latest TB 1.5? If you're running TB on a machine with
a Dual Core processor have you read this page?:
http://kb.mozillazine.org/Timeout_on_dual_core
and applied the update? (I don't think this is your issue, I had the
issue with 1.5 but the timeout message appears immediately for this
issue, not after 60 seconds, really wish Mozilla would push out 1.5.0.2
to resolve this issue permanently but the updated .dll from the website
fixes the issue for now)
I have tried this with logging turned off to see if logging itself was
causing the timeouts but there was no change in behavior.
A good step, in general, how is the server running? What is the
resource usage at, how much memory does the imapd process consume? Have
you tried running a tcpdump and see if Courier is still sending data, I
don't think TB would timeout unless the server is no longer saying
anything at all...
Anyone have any thoughts as to what is happening here? I'm rather
stumped as to what to try next.
10 bucks says moving to TB 1.5 and Courier 4.1 will resolve the issue...
Thanks,
Fran
-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Courier-imap mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
