On Mon, 16 Sep 2002, Bart Schaefer wrote: > The procmail bug happens when the filter program does something that > procmail doesn't expect. Exactly what that something is, hasn't been > confirmed by anyone on the procmail list. It might be exiting with a > nonzero status, or it might be producing output on the standard error, > or it might be something else entirely. > > So Simon is attempting to get SA to run flawlessly, because then it can't > tickle the procmail bug. This isn't a fix, it's a band-aid, but because > he apparently doesn't have the option of installing a newer procmail ...
But my point is that the triplets error message is not output to stderr unless debugging is on. I cannot see any way in which this can affect procmail -- unless maybe procmail has a problem with output on stderr as you suggest. But if that's the case, then running SpamAssassin without -d would fix it. Simon, have you tried using spamc? that is (a) faster and (b) will not produce any output on stderr, so if this is the bug, it'll work around it. --j. ------------------------------------------------------- Sponsored by: AMD - Your access to the experts on Hammer Technology! Open Source & Linux Developers, register now for the AMD Developer Symposium. Code: EX8664 http://www.developwithamd.com/developerlab _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
