Hello, all, with so much volume on the list, I thought it would be
helpful to touch on a number of topics in one email.
Regards,
KAM
*> if you are running 3.X not trunk*
The rule renaming and scoring and description issues shoule be resolved
as soon as the automated system publishes the rules.
"Kevin A. McGrail" writes:
> All:
>
> As of today, the configuration option WHITELIST_TO has been renamed
> WELCOMELIST_TO with an alias for backwards compatibility.
Kevin,
Please consider adding an easy way to turn the backward compatibility on
and off.
So we, person in charge of mail system
Am 19.07.20 um 18:58 schrieb Reindl Harald:
> Am 19.07.20 um 18:47 schrieb Kevin A. McGrail:
>>
>>> i got the warning at the daily 12:30 AM lint today as well and as said
>>> that started long *after that* thread
>>
>> If you are running ruleset 1880040 and you are running spamassassin
>> --lint
Hello,
On Sun, 19 Jul 2020, Kevin A. McGrail wrote:
>
> > i got the warning at the daily 12:30 AM lint today as well and as said
> > that started long *after that* thread
>
> If you are running ruleset 1880040 and you are running spamassassin
> --lint and getting an error, please post the error
On Mon, 2020-07-20 at 09:30 -0700, John Hardin wrote:
> It would be helpful if we could be informed whether anyone has post-
> SA processing that looks for these rulenames in the SA hit results,
> e.g. for making message delivery decisions.
>
Repeating previously posted info for completeness: one
On Sun, 19 Jul 2020, Kevin A. McGrail wrote:
Additionally, the rule USER_IN_WHITELIST_TO has been renamed to
USER_IN_WELCOMELIST_TO to assist those running older versions of
SpamAssassin get stock rulesets.
If you have custom scoring or any custom rules building on
USER_IN_WHITELIST_TO, please
SpamAssassin version 3.3.0 has not had a rule update since 2020-07-19.
SpamAssassin version 3.3.1 has not had a rule update since 2020-07-19.
SpamAssassin version 3.3.2 has not had a rule update since 2020-07-19.
20200719: Spam and ham are above threshold of 150,000:
http://ruleqa.spamassassin.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7840
--- Comment #11 from Sebastian J. Bronner ---
Yes. I can confirm the absence of a warning as well as a successuful sa-update
run.
Thank you.
--
You are receiving this mail because:
You are the assignee for the bug.
