On Friday 18 January 2008, Александър Л. Димитров wrote: > Quoth David Baron: > > On Wednesday 16 January 2008, Александър Л. Димитров wrote: > > > Quoth David Baron: > > > > Would there be any script, option, or such to solve this problem in a > > > > more elegant manner and leave things alone when the network is doing > > > > what it is supposed to do? > > > > > > Depends. Are you using procmail, too? If so, you might be interested in > > > the following rule I have in my .procmailrc: > > > > > > # Dupes? Nuke'em! > > > > > > :0 Wh: msgid.lock > > > : > > > | $FORMAIL -D 8192 msgid.cache > > > > > > That's it. All there is to it. Just put that little beast in and all > > > duplicate massages will get deleted. > > > > Great. Just put it in. > > $FORMAIL, I assume is a predefined macro for procmail? > > msgid -- do I need to install this? > > No, $FORMAIL holds the location of the 'formail' program, most likely > /usr/bin/formail (just type `which formail', to find out). > msgid is nothing more than a name for the file the already-retrieved > message-ids will get stored in, nothingadditional
>Thanks. I replaced $FORMAIL with /usr/bin/formail. >Locate msgid | grep cache only yields something connected with opera. Their >are a bunch of msgid thingies connected with kde and some other things but >these two items are not found. Oooh! It created that cache on my home directory. Is this where it belongs? Seem to be this stuff belongs somewhere on /var...
