On Mar 23, 2006, at 11:37 AM, Jim C. Nasby wrote:
On Thu, Mar 23, 2006 at 10:54:10AM +0100, Klaus Johannes Rusch wrote:
Jim Nasby wrote:
I just ended up with a bunch of spam in my inbox because
Spamassassin
went belly-up for some reason. In my procmail log I see:
procmail: Program failure (-25) of "spamassassin"
What I don't understand is why procmail continued delivering the
email instead of bouncing back to the mailer/exiting with an error.
I'm calling spamassassin like this:
:0fw : spamassassin.lck
| spamassassin
You can check if the spamassassin step was successful by looking
for the
SpamAssassin headers, e.g.
:0fw: spamassassin.lck
| spamassassin
:0
* !^X-Spam-Status:
{
EXITCODE=75
}
Ahh, outstanding! I new there had to be an easy way to do that.
Actually, that doesn't seem to be doing what I'd want... namely,
delivery still continues after that rule. Is there a way to make
procmail 'pull the plug' at that point? Or would I need to do
something like wrap everything else in another rule?
--
Jim C. Nasby, Database Architect decibel(_at_)decibel(_dot_)org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
____________________________________________________________
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