On Fri, 14 Jan 2000, SoloCDM wrote:
s> 1) While downloading e-mail, formail was interrupted. After I
s> restarted formail, the files already downloaded were ignored as
s> duplicates with the formail -D. Where did I go wrong?
s>
Sounds like it worked, unless your saying that you didn't get any of the
messages. If the messageID is in the cache file and it is received a
second time, it wont be placed in your Inbox, instead its just deleted so
to speak.
s> 2) Can formail -D cache of 8192 be raised to a different value and
s> what increments are used?
s>
The 8192 can be raised to any size (size is in bytes, so 8192 is
equal to 8kb). It will create a cache file of 8kb in which it stores all
messageID's of messages received, duplicate messages (messages with same
mID) are expunged from the system. Heres the excerpt from procmailex(5)
If you are subscribed to several mailinglists and people
cross-post to some of them, you usually receive several
duplicate mails (one from every list). The following sim
ple recipe eliminates duplicate mails. It tells formail
to keep an 8KB cache file in which it will store the Mes
sage-IDs of the most recent mails you received. Since
Message-IDs are guaranteed to be unique for every new
mail, they are ideally suited to weed out duplicate mails.
Simply put the following recipe at the top of your rcfile,
and no duplicate mail will get past it.
:0 Wh: msgid.lock
| formail -D 8192 msgid.cache
s> Note: Detailed Documentation(s) and Sample(s) are more than welcome.
s> When you reply to this message, please include
s> the mailing list and my address.
s>
s> *********************************************************************
s> Signed,
s> SoloCDM
s>
s>
s>
--
S.Toms - tomas(_at_)primenet(_dot_)com - homepage is in the works
SuSE Linux v6.2+ - Kernel 2.2.13
Do what comes naturally now. Seethe and fume and throw a tantrum.