Mike Peeler <procl <at> list.z-concept.com> writes:
Assuming you've defined $EX_TEMPFAIL, looks fine. I'm not completely
sure how your mailsystem handles a tempfail error, but my guess is,
it's probably okay.
On my system, "{ EXITCODE=75 HOST }" suffices. I prefer ":0 fW", but
that only affects how it looks in my logfile.
If your spamc version is recent, it "falls back safely", instead of
failing. It outputs its input, unchanged. That is, it does for you
what procmail already does anyway when a filter exits nonzero. If so,
spamc always exits 0. The "-x" spamc option disables this behavior.
Check with "spamc -h". If you see the "-x" option, you need it.
HTH,
Mike
Thanks Mike:
So how does this look?
EX_TEMPFAIL = 75
:0
* ! ^X-Spam-Checker-Version: SpamAssassin .* on $host
{
:0
* > 256000
{
:0fhw
| formail -A "X-VMC: BIG"
}
:0 E
* ! ^TO_spamassassin-users(_at_)incubator(_dot_)apache(_dot_)org
* ! ^TO_postfix-users@(postfix.org|cloud9.net)
* ! ^X-Spam-Checker-Version: SpamAssassin .* on $host
{
:0 fw
| /usr/bin/spamc
:0 e ## If previous errors, run this
* ! ^X-Spam-Checker-Version: SpamAssassin .* on $host
{
EXITCODE = $EX_TEMPFAIL
HOST = "_spamc_failed_"
}
}
____________________________________________________________
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