I have a simple optimisation suggestion for the new courierpop3dsizelist mechanism.
At the moment it is written out as soon as the mailbox is opened. I suggest delaying writing it out until the mailbox is closed (excluding any DELEted items) or the session dropped. The benefit of this is that in the normal case where a client downloads and deletes all messages, no courierpop3dsizelist file needs to be written at all - thus there is no overhead in terms of disk space, inodes, and disk operations to maintain it. As an additional optimisation it could be not written out if no changes have been made (i.e. for repeated polls of a mailbox when no new items have arrived) Regards, Brian. ------------------------------------------------------- This SF.NET email is sponsored by: FREE SSL Guide from Thawte are you planning your Web Server Security? Click here to get a FREE Thawte SSL guide and find the answers to all your SSL security issues. http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
