|
|
It’s unclear to me why the older SpamAssassin would have changed the ruleset it was using. What I’d probably try would be:
1) see what happens if you tell CGPSA to use the newer Perl (and newer SpamAssassin) instead; if it works, you’re set, and if not, you can try…
2) turn on verbose logging in CGPSA (see the config file) while it’s still running the old SpamAssassin, so that you can see where it’s loading the ruleset from.
-Dan
Sent from mobile, please forgive spelling errors or brevity
> On Oct 28, 2024, at 03:28, Jona Tallieu (T & T nv) Junk@tnt.be <cgpsa-discuss@mail.tffenterprises.com> wrote:
>
> Thank you so much for your answer!
>
> 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/spamassassin/.
> But since the OS update (and the included SA update) it seems it’s using a default ruleset somewhere.
>
> Any way to force the SA 3.4.6 to use the original rules at /etc/spamassassin/ ?
>
> Thank you!
>
>
> J.
>
>
>
>> On 27 Oct 2024, at 08:15, Daniel M. Zimmerman dmz@tffenterprises.com <cgpsa-discuss@mail.tffenterprises.com> wrote:
>>
>> Looking at what you’ve written here, my guess is that CGPSA and your “spamassassin” command line tool are using different Perl distributions (and therefore different SpamAssassin installations). Make sure the “#!/path/to/perl” line at the top of the CGPSA script has the full path to the Perl that your “spamassassin” script is using (you can check the top of that script, or just use “which perl” to find your system Perl, which I assume is where you’ve installed SpamAssassin 4).
>>
>> Note that I’ve only done very, very limited testing with CGPSA and SpamAssassin 4; it may work fine, but there may be unforeseen issues.
>>
>> -Dan
>>
>> Sent from mobile, please forgive spelling errors or brevity
>>
>>>> On Oct 18, 2024, at 17:55, Jona Tallieu (T & T nv) Junk@tnt.be <cgpsa-discuss@mail.tffenterprises.com> wrote:
>>>
>>> Dear,
>>>
>>> It’s 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.
>>>
>>> spamassassin --version
>>> SpamAssassin version 4.0.0
>>> running on Perl version 5.36.0
>>>
>>> But in the cgpsa headers in an e-mail:
>>> X-Spam-Checker-Version: SA 3.4.6
>>>
>>> I also see that whitelisted addresses:
>>> whitelist_from *@samsonite.com
>>> still get spam boxed…
>>>
>>> Any ideas?
>>>
>>> Thank you!
>>>
>>>
>>> Best,
>>>
>>>
>>> Jona
>>>
>>>
>>>
>>>> On 15 May 2024, at 23:07, Daniel M. Zimmerman dmz@tffenterprises.com <cgpsa-discuss@mail.tffenterprises.com> wrote:
>>>>
>>>> I’m unfamiliar with “CGP SPEC”, but I’m assuming they haven’t changed anything in the CLI to break its compatibility with previous versions of the CLI protocol, so from that perspective it should probably work fine. Just be sure you have reasonable versions of Perl and the other dependencies installed, and note that CGPSA has not been tested with SpamAssassin 4 (at least, not by me - if anybody else has, please let me know).
>>>>
>>>> -Dan
>>>>
>>>>>> On May 14, 2024, at 01:18, Jona Tallieu (T & T nv) Junk@tnt.be <cgpsa-discuss@mail.tffenterprises.com> wrote:
>>>>>
>>>>> Dear,
>>>>>
>>>>> Anyone running CGPSA on Debian 12 in combination with CGP SPEC 8.0.5?
>>>>>
>>>>> Should I expect problems when upgrading to this combo? Things I need to know before?
>>>>>
>>>>> Thank you!
>>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>> Jona
>>>>>
>>>>
>>>>
>>>> -----
>>>> This message is from the CGPSA Mailing List.
>>>> To unsubscribe, E-mail to: <cgpsa-discuss-off@mail.tffenterprises.com>.
>>>
>>
>>
>> -----
>> This message is from the CGPSA Mailing List.
>> To unsubscribe, E-mail to: <cgpsa-discuss-off@mail.tffenterprises.com>.
>
|
|