At 10:25 2003-10-29 -0800, Jim Osborn wrote:
I suppose it's generally unwise to mix versions of things, but I
thought I'd ask here for confirmation that these two don't play
well together. I think my ISP must have kept the procmail v3.10
because of something in SmartList, but I don't know what.
Q: what happens when you pipe a message to formail right on the commandline
with that invocation?
Well, they don't say much, as they stop at that point. :)
Surely procmail indicates delivery or program failure or something. You
ARE running with VERBOSE logging, right?
Is the formail/procmail actually COMPILED for the machine in question?
debug (s20-post-happy) (mx1): Wed Oct 29 08:00:06 PST 2003
about to filter header x-debug line
procmail: [25930] Wed Oct 29 08:00:06 2003
procmail: Executing "formail,-I,X-Debug"
-------------end of log file---------------------------------
That's it; there's nothing in the log after the formail -I statement.
That's the first formail -I statement in the rc file.
I'd check the system logs and verify that the procmail isn't coredumping.
If you have a shell account elsewhere, you should try running your recipe -
you'll see that it runs properly.
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
_______________________________________________
procmail mailing list
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)DE
http://MailMan.RWTH-Aachen.DE/mailman/listinfo/procmail