Grasshopper hangs head in shame for not testing spamc standalone first. Changed qmail-scanner-queue.pl to remove -c on options line for spamc launch and ALL works as expected.
Many Many Thanks to all Michael Balamuth [EMAIL PROTECTED] -----Original Message----- From: Jason Staudenmayer [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 10:55 AM To: 'Michael Balamuth' Subject: RE: [SAtalk] New User question In qmail-scanner.pl remove th -c from the spamassassin binary line -----Original Message----- From: Michael Balamuth [mailto:[EMAIL PROTECTED] Sent: Friday, October 17, 2003 9:38 AM To: 'Patrick Morris' Cc: [EMAIL PROTECTED] Subject: RE: [SAtalk] New User question I apologize for not giving more detail. Being new to this list, I wasn't sure how much "stuff" people want to see on an initial question. We are running qmail with qmail-scanner 1.20rc3 (latest?) with qmail-scanner now running under its own uid of qscand. qmail-scanner is launched via qmail-queue patched using Bruce Guenther's QMAILQUEUE patch and first runs uvscan (a McAfee virus scan product) and then if there is no virus found flag, runs spamassassin using the client server pair spamd/spamc where spamd is running as user qscand as well. I also tried a user spamc (created with no login specifically by suggestion from one of the help files and as root as well. No difference. We see the header line indicating that qmail-scanner has run both uvscan first and then spamassassin. We also see the score line and the X-Spam-Status: Yes/No line as well, but that's it no matter what we try. I would have thought that is an intermediate were stripping headers, it would strip them all?? After qmail-scanner, the regular djb cycle completes and the logs reflect same. We are using mbox delivery with maildrop not procmail. I can provide clips from any logs anyone would like to see, but again, don't want to clutter up too much at once. Michael Balamuth [EMAIL PROTECTED] -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Patrick Morris Sent: Thursday, October 16, 2003 4:32 PM To: Michael Balamuth Cc: [EMAIL PROTECTED] Subject: Re: [SAtalk] New User question How are you calling SpamAssassin? If you're running it via some sort of helper app like Amavis or MIMEdefang, it may be stripping the headers normally added by SpamAssassin. Michael Balamuth wrote: >Further info. Upon reviewing the Mail::SpamAssassin::Conf documentation, I >noticed that one header X-Spam-Checker-Version is supposed to be >unremovable. I don't see that header in ANY emails processed. Yet I see >X-Spam-Status: (Yes/No) in ALL emails processed and NO OTHER headers >(X-Spam... headers that is) at all. I'm really in the dark here. > The --lint check is clean and the logs show processing statistics for each >of the emails I receive so I know they are getting looked at. > >Michael Balamuth >[EMAIL PROTECTED] > > ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk ------------------------------------------------------- This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo The Event For Linux Datacenter Solutions & Strategies in The Enterprise Linux in the Boardroom; in the Front Office; & in the Server Room http://www.enterpriselinuxforum.com _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
