I'm not getting any sniffer headers inserted, but then I'm running SA via amavisd-new, so I never get SA headers, only amavisd-new headers. Could this implementation have anything to do with the problem? Amavisd-new calls spamassassin directly via perl for each message and doesn't use spamd.
Dan Horne From: Pete McNeil [mailto:madscient...@armresearch.com] Sent: Wednesday, May 13, 2009 5:37 PM To: Alban Deniz Cc: Dan Horne Subject: Re: [sniffer] Re: SNF4SA - Message Sniffer Antispam Plugin for SpamAssassin Alban, I don't think this note made it to Dan or the list... I'm copying him on this. Alban Deniz wrote: Hi, When I ran the snf4sa plugin without SNFServer running, I got the following headers injected into the email: X-Spam-GBUdb-Analysis: _SNFGBUDBANALYSIS_ X-Spam-SNF-Result: _SNFRESULTTAG_ X-Spam-MessageSniffer-Rules: _SNFMESSAGESNIFFERRULES_ X-Spam-MessageSniffer-Scan-Result: _SNFMESSAGESNIFFERSCANRESULT_ If SNFServer were running, the _SNFXXX_ would have been replaced with the scan results. Also, the score was something like 8.3, which was from the other tests. the snf4sa plugin doesn't add to the score when SNFServer isn't running. I ran this using the spamassassin command, and got the following error (when SNFServer isn't running): [25199] warn: rules: failed to run SNF4SA test, skipping: [25199] warn: (Snf4sa: Error from SNFServer: cannot connect to socket (Connection refused) at /etc/spamassassin/snf4sa.pm line 466. [25199] warn: ) Received: from localhost by skidmark with SpamAssassin (version 3.2.5); Wed, 13 May 2009 17:13:41 -0400 Pete mentioned to me that your SNFServer is running. So, I think there might be some other problem (perhaps SNFServer isn't sending the messages the snf4sa plugin is expecting). What do you get when you pass the message through the spamassassin command? Thanks, Alban On Wednesday 13 May 2009 04:44:56 pm Pete McNeil wrote: > Dan Horne wrote: > > Oh, yeah, I should also include this from the mail logs. It doesn't > > look like SNF4SA is being run successfully, but it still results in a SA > > weight of 1 rather than the sa_score configured: > > Interesting -- I wonder why snf4sa did not connect with SNFServer --- Am > I correct that the later reference SNIFFER=6 indicates that a different > SNF implementation was successful? > > When you run SNFClient -status.second do you get XML status data? > > In any case-- if the plugin was unable to connect it should return a > zero score > > I'm passing this on to Alban. > > Thanks! > > _M > >
