Salve, David!
Well, let's see what you have. (Actions are single lines in Garvin's
rcfiles, broken only in these posts.)
[...examples cut...]
No wonder. I'll bet you get "couldn't determine implicit lockfile"
errors in your log too. (You *are* using a logfile, aren't you, and you
do have VERBOSE turned on when you're trying to track down a problem,
don't you?)
Yes, I did use the logfile and also see that flag. Because I read in the
FAQ that implicit lockfiles aren't that bad (at least that was the thing I
drew out of it) and I should rather put a colon too much than too little.
My first guess was that my mails got kicked too fast and procmail would
stumble on an empty mail to process.
The `f' flag says to run the command on the text and replace it with the
output of the command; since those commands have no stdout (the pipe to
$SENDMAIL sucks it all up), you're replacing the message, head and body,
with nothingness. Procmail always wants a closing blank line, so
procmail puts back one blank line. My take is that you don't want the
`f' flag, nor `w' either.
Darn, that makes a good sense. I just changed my file and it seems to work
now. Thanks a lot!
--
Bye, ...[ icq #21392242 |
Garvin ...[ www.supergarv.de |
... *Du stehst auf heiligem Boden!*
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail