On Mon, Feb 20, 2006 at 09:51:20AM +0100, Christian Ferrari wrote: > A batch job has the advantage to leave all the other components at its > place without patching any well running software.
Sorry - I hadn't realised that this was a background sweep rather than a real-time action taken at delivery time. I'd be interested to see what percentage of mail storage this saves, versus the time taken to read and checksum all recent messages. In the ISP environments I've worked, I suspect this would be a small benefit for a large amount of work (i.e. finding and opening all the mail on the Netapp by itself takes severals days) You may get a better benefit by identifying all 'inactive' accounts (e.g. not accessed for 45 days) and tar/zipping their Maildir, to be untarred automatically by a .loginexec script when they next login; and/or bouncing all incoming mail for these inactive mailboxes, so they don't accumulate spam. Again, once the next login takes place, you can start accepting mail again. > You've guessed MD5 is the cornerstone of my shell script, but your idea > has a little bug: there's a little probability two completely different > files have the same MD5 hash. Replace "little" with "vanishingly small". Once you have 2^64 different E-mails stored simultaneously on your mail server, there will be a reasonable probability of a collision between two of them. That's a lot of mail to store. Regards, Brian. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
