Return-Path: Received: from [188.165.201.100] (HELO magelo.com) by mail.tffenterprises.com (CommuniGate Pro SMTP 6.0) with ESMTP id 16314297 for cgpsa-discuss@mail.tffenterprises.com; Wed, 23 Apr 2014 23:37:09 -0700 Received-SPF: pass receiver=mail.tffenterprises.com; client-ip=188.165.201.100; envelope-from=cme@magelo.com Received: from internal.domain; Thu, 24 Apr 2014 08:36:58 +0200 From: "Christian Meunier" To: "CGPSA Discussion List" Subject: Re[2]: [CGPSA] CGPSA not working properly anymore with SA Date: Thu, 24 Apr 2014 06:36:47 +0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; format=flowed; charset=utf-8 In-Reply-To: Message-Id: Mime-Version: 1.0 Reply-To: "Christian Meunier" User-Agent: eM_Client/6.0.20154.0 Hi Daniel, Thanks for jumping in. I somehow resolved the issue... Running spamassassin --lint revealed that I had no rules installed and=20 that I needed to do an sa-update (I swear, I did it before...) Once I did that, it worked again. So like I suspected, it was something stupid but I kinda blame=20 Spamassassin for not letting me know sooner in its debug info... After looking at the log, everything seems to work, the only exception=20 is Pyzor: Apr 24 06:25:07.031 [32399] dbg: pyzor: pyzor is not available: no pyzor= =20 executable found Apr 24 06:25:07.031 [32399] dbg: pyzor: no pyzor found, disabling Pyzor If I run spamassassin localy, SA finds pyzor but when it is instancied=20 with cgpsa, somehow SA does not find it anymore. It's not a big deal but if somehow you know why is this happening, would= =20 be nice to fix that little thing as well. Thanks again Shawn and Daniel for your help ! -- Chris ------ Original Message ------ From: "Daniel M. Zimmerman" To: "CGPSA Discussion List" Sent: 23/04/2014 05:21:18 Subject: Re: [CGPSA] CGPSA not working properly anymore with SA > >On 22 Apr 2014, at 0:36, Christian Meunier wrote: > >> Hi Shawn, >> >> Thanks again for your help. >> Here is a gist with local.cf, cgpsa.conf and cgpsa.err >> > https://gist.github.com/Tlvenn/11168670 >> >> Regarding local.cf, I know that right now I have a vanilla, out of=20 >>the box, local.cf. >> I dont remember doing anything there to tell SA to include spam=20 >>status headers. From their documentation, it looks like it's done=20 >>already by default. > >In an older version, SpamAssassin changed its defaults such that it=20 >doesn't include the X-Spam-Level header by default anymore; adding=20 >something like: > >add_header all Level _STARS(%)_ > >to local.cf will add that header. > >That having been said, your log there shows a message that is _not_=20 >being detected as spam (score 0.0/4.0). If you run a test from the=20 >command line on a message that is not spam, what do you get? Also keep=20 >in mind that when you run "spamassassin" from the command line you get=20 >your own personal settings (perhaps cached from old versions in your=20 >.spamassassin directory) in addition to local.cf... > >-Dan > >--- >Daniel M. Zimmerman >http://www.tffenterprises.com/~dmz/ > > >----- >This message is from the CGPSA Mailing List. >To unsubscribe, E-mail to: .=