a) Does spamc work from the command line? b) What user is procmail running as? c) What does the procmail log say? d) What does the syslog say?
C Chuck Wolber wrote: CW> CW> I'm seeing the same problem as well. We discussed this a while back and CW> nothing really came of it. Periodically I will try some different CW> arguments in the startup script or the procmail recipe, but the fact CW> remains that everything seems to be ignored unless you use spamassassin -P CW> in the procmail recipe. I only have 50 users right now so it's not much of CW> a problem for me at this time. CW> CW> -Chuck CW> CW> > The 2nd of 2 problems; this works: CW> > CW> > :0fw CW> > | spamassassin -P CW> > CW> > :0: CW> > * ^X-Spam-Status: Yes CW> > /dev/null CW> > CW> > This doesn't: CW> > CW> > :0fw CW> > | /usr/bin/spamc CW> > CW> > :0: CW> > * ^X-Spam-Status: Yes CW> > /dev/null CW> > CW> > This (obviously?) doesn't either: CW> > CW> > :0fw CW> > | spamc CW> CW> _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
