2 messages in net.sourceforge.lists.courier-maildrop[maildropl] Re: How Crazy is That ?
FromSent OnAttachments
Ramy M. HassanAug 18, 2002 7:25 am 
George GeorgalisAug 23, 2002 6:35 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[maildropl] Re: How Crazy is That ?Actions...
From:George Georgalis (geo@galis.org)
Date:Aug 23, 2002 6:35:41 pm
List:net.sourceforge.lists.courier-maildrop

This, from the procmailex man page might be helpfull...

:0 Whc: msgid.lock | formail -D 8192 msgid.cache :0 a: duplicates/

Using formail -D, it creates a message id database from distinct emails.

Yours was, 2002@aast.edu If I were to get that one again it would be filtered into my duplicates/ maildir. (carefully be sure procmail has permission to write msgid.lock and msgid.cache)

maybe you can use this somehow? post your results!

// George

On Sun, Aug 18, 2002 at 02:21:03PM +0000, Ramy M. Hassan wrote:

Well, I am facing storage problem. The main reason for that is mailing lists that sends huge attachments. Don't you have same problem ? Ok, I thought of solving my problem in a new way using qmail + maildrop + maildir++. Let me know what do you think of that. The idea is simple and only a local delivery agent will be modified ( possibly maildrop ). Here are the steps.

1- Maildrop search of a mailing list header and if exists continue to step 2 otherwise deliver the message normally. 2- Calculate the MD5 sum of the message. 3- Check for the existance of a file at a path like /shared/some/direcotory/hasing/path/using/md5sum/ 4- If the file does not exist then create it and write the email message to this file, otherwise leave it as it is. 5- Locate the maildir of the user and apply the filtering rules as usual , but instead of writing the mail in the maildir just link the file in of step 3 to a file in the maildir where the link follows the naming convention of maildir++. 6- That's it :)

Ok, This way we will have a single copy of each email and hard links in the users maildirs, isn't it great ? The problems I see in this technique are : 1- All maildirs should be on same device to be able to use hardlinks. This is the case with me , but to make it general we can create a shared spool for each partition and modify the algorithm to copy the message when we deliver to a maildir that exists on a different device.

2- What about if user modified the message ?! .. A problem .. we can solve this by making the message read only for the user.

What do you think ? Let me know your comments as I am willing to start hacking maildrop source to make it work like that..

Best regards

============================================ Ramy M. Hassan AAST , College of Engineering and Technology. Teaching Assistant ============================================

============================================================ Arab Academy for Science & Technology and Maritime Transport Visit us at : http://www.aast.edu Any sugesstion , please send to webm@aast.edu ============================================================