Kelsey Cummings writes:
On Wed, Jun 24, 2009 at 05:48:55PM -0400, Sam Varshavchik wrote:> More description of issue:> The server runs fine for small moves (i.e. <100 messages at a time.) and > general message access. however when moving many messages, from the > client side it just endlessly says "Moving messages to INBOX.Trash" (or > whatever the destination folder is.)More than likely that the message copy, especially over NFS, takes a long time and the IMAP client is too impatient, and breaks the connection and tries it again. Lather, rinse, repeat.This is true of course but it doesn't help solve the problem. Any suggestions as to how to improve performance or mitigate the problem?
Fix the client. It's a client problem.
I've considered hacking so moves are a little less safe (just renames) - I'm not entirely sure why they aren't already.
Because that's what IMAP specifies. There is no move message operation in IMAP, just a COPY operation that creates another copy of the message in another folder. IMAP clients effect a message move by copying messages, then deleting the copy in the original folder.
(Shared folders?) But
it brings up another issue to. Courier has no way of limiting
connections by user
Of course it does. Courier's default configuration limits four connections from the same IP address.
pgpqbZnr0EuDI.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
