=- Michael J Wise wrote on Sat 9.Dec'06 at 8:54:01 -1000 -=
a) does this happen even with : locking?
I <3 Maildir....
That's fine for your mailfolders not to get corrupted, but the
logfile is not protected this way. Try explicit : locking to avoid
concurrent processing of procmailrc and henceforth log writing.
(if this is possible/ makes sense with maildir)
b) I use a "digest" awk-script that converts the abstract to my
liking. Given the logfile's simple form it's easy to figure out.
If interested reply in private.
I use this:
TRAP='/usr/bin/sed -n ...
Uh well, not sure what your TRAP does there... but what do you
want your logfile to look like anyway?
My way doesn't put load on procmail processing, but rather takes
the "natural" LOGABSTRACT=yes logfile and filters it to a final
destination one when I call it manually from cmd-line.
awk-script < ORGLOG > FINALLOG
--
© Rado S. -- You must provide YOUR effort for your goal!
Even if it seems insignificant, in fact EVERY effort counts
for a shared task, at least to show your deserving attitude.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail