On 19 Jul 2020, at 19:41, Kevin A. McGrail wrote:
> OK, can you ask for specifics on their use case because if the post-sa
> work is not involving these rules or trivial to update, it might be best
> to follow KISS.
I sent email after replying. Will update on list if/when I hear back.
Best regar
OK, can you ask for specifics on their use case because if the post-sa
work is not involving these rules or trivial to update, it might be best
to follow KISS.
On 7/19/2020 10:39 PM, Luis E. Muñoz wrote:
> On 19 Jul 2020, at 19:17, Kevin A. McGrail wrote:
>
>> Ahh yes, good point. Do we know of
On 19 Jul 2020, at 19:17, Kevin A. McGrail wrote:
Ahh yes, good point. Do we know of anyone with this parsing report
template type of use case?
I know of at least two use cases where the report template is parsed
post-sa. I don't know if the specific rules in contention are involved
in sai
On 7/19/2020 10:03 PM, John Hardin wrote:
> Problem is, that's a rule definition and it wouldn't peacefully
> coexist with the "alias" directive as I have it envisioned. Perhaps we
> allow "meta RULENAME" to remove "alias RULENAME" while retaining the
> lint warning for other rule types.
Ahh yes, g
On Sun, 19 Jul 2020, Kevin A. McGrail wrote:
On 7/19/2020 9:29 PM, John Hardin wrote:
I was mulling the utility of a new config directive in 4.0 to address
backwards compatibility of rule names:
alias RULENAME RULENAME_2
...which would recognize any config-file directives for RULENAME an
On 7/19/2020 9:29 PM, John Hardin wrote:
>
>>
>> What do you think of this change along with removing the score from
>> 50_scores.cf? I think it will work back to 3.3.x:
>>
>> if can(Mail::SpamAssassin::Conf::feature_blocklist_welcomelist)
>> #bz7826 renames whitelist to welcomelist
>> heade
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7838
--- Comment #22 from Kevin A. McGrail ---
svn commit -m 'More Tweaking to USER_IN_WELCOMELIST_TO' 60_whitelist.cf
50_scores.cf
Sending50_scores.cf
Sending60_whitelist.cf
Transmitting file data ..
Committed revision 1880056.
On Sun, 19 Jul 2020, Kevin A. McGrail wrote:
On 7/19/2020 7:39 PM, John Hardin wrote:
The non-can_welcome_block branch should not be renaming the rule.
Doing that breaks existing production installs.
I agree is causing unexpected local rules and local rule scoring issues
trying to get pre-3.
On 7/19/2020 7:39 PM, John Hardin wrote:
>
> The non-can_welcome_block branch should not be renaming the rule.
> Doing that breaks existing production installs.
I agree is causing unexpected local rules and local rule scoring issues
trying to get pre-3.4.3 releases to work.
What do you think of
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
We only publish one set of rules so you will see that become welcome
instead of white. If you are using a modern day 3.4.3 or greater, you can
likely prepare for the changes now by adding both to meta rules. Can you
show an example of your dependency?
On Sun, Jul 19, 2020, 13:06 Thom van der Boo
> 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 and the version of SA
you are using.
> frankly where i start t
> are you guys crazy doing that to *existing* stable installs and what
> does that mean for setups with "warn: rules: error: unknown eval
> 'check_to_in_whitelist' for USER_IN_WELCOMELIST_TO"
I've heard back from testers using 3.3.1 to 3.4.2 that the issue is
resolved re: the eval or unknown rul
All:
As of today, the configuration option WHITELIST_TO has been renamed
WELCOMELIST_TO with an alias for backwards compatibility.
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
20200718: Spam or ham is below threshold of 150,000:
http://ruleqa.spamassassin.org/?daterev=20200718
20200718: Spam: 1607585, Ham: 133096
The spam and ham counts on which this script alerts are from
http://ruleqa.spamassassin.org/?daterev=20200718
Click "(source details)" (it's tiny and low
15 matches
Mail list logo
