V K wrote:
VK> > fix it, try adding a : on the end of the second procmail recipe:
VK> >
VK> > :0:# All messages
VK> > ! etcetcetc
VK>
VK> Don't waste your time. That'll just give you one more line in your
VK> $LOGFILE saying that the useless lock has been ignored. The "!" pipes
VK> the mail i
> fix it, try adding a : on the end of the second procmail recipe:
>
> :0:# All messages
> ! etcetcetc
Don't waste your time. That'll just give you one more line in your
$LOGFILE saying that the useless lock has been ignored. The "!" pipes
the mail into $SENDMAIL - what the &*^@&*! do you wa
Hmm, strange. Shouldn't be a locking issue if you're just forwarding
the mail on... Have you tried -F1 instead of -F0? And if that doesn't
fix it, try adding a : on the end of the second procmail recipe:
:0:# All messages
! etcetcetc
and see if that fixes it (though I doubt it).
C
On We
This message (and a few others) have been mangled by SpamAssassin 2.11.
(1000 others were processed perfectly.) I thought adding -F 0 would fix
it, but I'm still occasionally getting the same problem. Here are my
.procmailrc and .spamassassinrc/user_prefs:
:0fw
| /usr/bin/spamassassin -Pa
