A question regarding formail's Message-Id cache:
I have a procmail recipe utilizing 'formail -D <n> <f>'
to detect and process duplicate messages. Being somewhat
curious about what happens when the cache file hits it's
maximum size, I did a quick perusal of the appropriate
source code. It appears that once the file has hit it's
max size, further Message-Id keys will all be written
at offset 0 in the cache file, which rather limits the
usefulness of the cache for this type of use. It seems
like it should work fine when all messages pass through
a single invocation of formail - i.e. when using 'formail -s',
but when individual messages are getting fed to individual
invocations of formail, there seems to be a certain deficiency
in the cache handling. Maybe that's because I'm using the
cache for something it wasn't really intended for?
Regardless, I'm wondering what kind of effort would be
required to make this work the way I'm trying to make it work.
It would involve (at least) storing information about where
the last key was written either in the cache file itself or
in another auxiliary file, so that that information is available
between invocations of 'formail -D <n> <f>'.
In the mean time, are there any recommendations for alternative
ways of addressing this issue? Other packages, recipes that don't
use formail, etc.?
tw
--
+---------------------------------------+-------------------------------------+
| Tim Walberg | Phone: (847) 632-3407 |
| Motorola CE/ITS | Pager: (800) SKY-TEL2 PIN:1384689 |
| 1475 W Shure Dr. IL75-2H14 | FAX: (847) 632-5769 |
| Arlington Heights, IL 60004 | |
+---------------------------------------+-------------------------------------+
| http://www.cig.mot.com/~walberg | E-mail:
walberg(_at_)cig(_dot_)mot(_dot_)com, |
| http://www.skytel.com/Paging (pager) | 1384689(_at_)skytel(_dot_)com
(pager) |
+---------------------------------------+-------------------------------------+