3.0.8 is anciently old, strongly consider you investigate upgrading to
the latest version and see if it fixes the issue.
I will try this next, and see if it helps.
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.
What exactly does ENHANCED_IDLE do? I would not mind turning it on if
it might help.
I don't consider 2000 to be all that large either, just pointing out
that 2000 seems to be the break point for when the timeouts occur. In
the past, I've used TB successfully up to 35,000 messages per folder.
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.
That makes sense. The key point I was trying to say but that I failed
to word properly is that the messages are not being marked deleted,
because they are still in the original folder as well as Trash.
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?:
Yes, this is definitely occurring with 1.5 under single-core fedora. I
did come across the DLL issue with dual-core; so far, none of our users
are in that category so we can safely eliminate that.
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...
I have been looking at top output, and the CPU on the server is
generally > 90% idle, loads are in the 0.1 range, and such. I have not
yet gone as deep as tcpdump to see if traffic is still flowing. Would I
expect traffic to be flowing -during- the mass delete (i.e. does the
server ping the client with a message after each message is moved to
trash?) or would it be normal for there to be silence between server and
client while the 2000 messages are being copied to Trash and marked deleted?
10 bucks says moving to TB 1.5 and Courier 4.1 will resolve the issue...
I am already at the former, so I will try the latter as my first pass,
and report back. I also will try to learn more about ENHANCED_IDLE to
see if that would help. Thanks!
--
Fran Fabrizio
Senior Systems Analyst
Department of Computer and Information Sciences
University of Alabama at Birmingham
http://www.cis.uab.edu/
205.934.0653
-------------------------------------------------------
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
