X-Virus-Flag: No (epsilon3) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/simple; d=tffenterprises.com; s=jul20; bh=fFk4MkXHJJDG55UG1e/HB7OYx+gcEN94cKWfgo35ONQ=; h=To:In-Reply-To:References:Message-Id:Date:Subject:Mime-Version:From: Content-Transfer-Encoding:Content-Type; b=kgZqQ1r3ZhBjlJXNi3PBYHo/3fsCjOpMv+7 rQiQd5bayur4ekJulk+VXIX1vFp1vMFyz4XBfp6iOm6U5cLggll6Tyg63DVrotb0UBr7XLUbW+Qv4 hblPG76Dbc7eOHV+rkhAYSzhbFCPbf6+Z/67/0I8s0OyKt6k1C5uJEVt9tA= From: "Daniel M. Zimmerman dmz@tffenterprises.com" Received: from [50.39.100.104] (account dmz@mail.tffenterprises.com HELO smtpclient.apple) by mail.tffenterprises.com (CommuniGate Pro SMTP 6.2.15) with ESMTPSA id 23210340 for cgpsa-discuss@mail.tffenterprises.com; Mon, 28 Oct 2024 03:12:36 -0700 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) Subject: Re: [CGPSA] CGPSA on Debian 12 with CGP SPEC 8.0.5 Date: Mon, 28 Oct 2024 18:12:23 +0800 Message-Id: <3D214C20-969E-4464-A5A7-BA67F088D408@tffenterprises.com> References: <3CED846A-E432-437F-BE19-9302CE95010B@tnt.be> In-Reply-To: <3CED846A-E432-437F-BE19-9302CE95010B@tnt.be> To: CGPSA Discussion List X-Mailer: iPhone Mail (22C5109p) It=E2=80=99s unclear to me why the older SpamAssassin would have changed the= ruleset it was using. What I=E2=80=99d probably try would be: 1) see what happens if you tell CGPSA to use the newer Perl (and newer SpamA= ssassin) instead; if it works, you=E2=80=99re set, and if not, you can try=E2= =80=A6 2) turn on verbose logging in CGPSA (see the config file) while it=E2=80=99s= still running the old SpamAssassin, so that you can see where it=E2=80=99s l= oading the ruleset from. =20 -Dan=20 Sent from mobile, please forgive spelling errors or brevity > On Oct 28, 2024, at 03:28, Jona Tallieu (T & T nv) Junk@tnt.be wrote: >=20 > =EF=BB=BFThank you so much for your answer! >=20 > I would not mind keep using SA 3.4.6 as long as it would use the ruleset I= collected and the whitelists I configured, which are located at cd /etc/spa= massassin/. > But since the OS update (and the included SA update) it seems it=E2=80=99s= using a default ruleset somewhere. >=20 > Any way to force the SA 3.4.6 to use the original rules at /etc/spamassass= in/ ? >=20 > Thank you! >=20 >=20 > J. >=20 >=20 >=20 >> On 27 Oct 2024, at 08:15, Daniel M. Zimmerman dmz@tffenterprises.com wrote: >>=20 >> Looking at what you=E2=80=99ve written here, my guess is that CGPSA and y= our =E2=80=9Cspamassassin=E2=80=9D command line tool are using different Per= l distributions (and therefore different SpamAssassin installations). Make s= ure the =E2=80=9C#!/path/to/perl=E2=80=9D line at the top of the CGPSA scrip= t has the full path to the Perl that your =E2=80=9Cspamassassin=E2=80=9D scr= ipt is using (you can check the top of that script, or just use =E2=80=9Cwhi= ch perl=E2=80=9D to find your system Perl, which I assume is where you=E2=80= =99ve installed SpamAssassin 4). >>=20 >> Note that I=E2=80=99ve only done very, very limited testing with CGPSA an= d SpamAssassin 4; it may work fine, but there may be unforeseen issues. >>=20 >> -Dan >>=20 >> Sent from mobile, please forgive spelling errors or brevity >>=20 >>>> On Oct 18, 2024, at 17:55, Jona Tallieu (T & T nv) Junk@tnt.be wrote: >>>=20 >>> =EF=BB=BFDear, >>>=20 >>> It=E2=80=99s been running for a while, but CGPSA is not using the latest= installed spamassassin. >>> And is not using the /etc/mail/spamassassin directory for the rules. >>>=20 >>> spamassassin --version >>> SpamAssassin version 4.0.0 >>> running on Perl version 5.36.0 >>>=20 >>> But in the cgpsa headers in an e-mail: >>> X-Spam-Checker-Version: SA 3.4.6 >>>=20 >>> I also see that whitelisted addresses: >>> whitelist_from *@samsonite.com >>> still get spam boxed=E2=80=A6 >>>=20 >>> Any ideas? >>>=20 >>> Thank you! >>>=20 >>>=20 >>> Best, >>>=20 >>>=20 >>> Jona >>>=20 >>>=20 >>>=20 >>>> On 15 May 2024, at 23:07, Daniel M. Zimmerman dmz@tffenterprises.com wrote: >>>>=20 >>>> I=E2=80=99m unfamiliar with =E2=80=9CCGP SPEC=E2=80=9D, but I=E2=80=99m= assuming they haven=E2=80=99t changed anything in the CLI to break its comp= atibility with previous versions of the CLI protocol, so from that perspecti= ve it should probably work fine. Just be sure you have reasonable versions o= f Perl and the other dependencies installed, and note that CGPSA has not bee= n tested with SpamAssassin 4 (at least, not by me - if anybody else has, ple= ase let me know). >>>>=20 >>>> -Dan >>>>=20 >>>>>> On May 14, 2024, at 01:18, Jona Tallieu (T & T nv) Junk@tnt.be wrote: >>>>>=20 >>>>> Dear, >>>>>=20 >>>>> Anyone running CGPSA on Debian 12 in combination with CGP SPEC 8.0.5? >>>>>=20 >>>>> Should I expect problems when upgrading to this combo? Things I need t= o know before? >>>>>=20 >>>>> Thank you! >>>>>=20 >>>>>=20 >>>>> Best, >>>>>=20 >>>>> Jona >>>>>=20 >>>>=20 >>>>=20 >>>> ----- >>>> This message is from the CGPSA Mailing List. >>>> To unsubscribe, E-mail to: .= >>>=20 >>=20 >>=20 >> ----- >> This message is from the CGPSA Mailing List. >> To unsubscribe, E-mail to: . >=20