Re: IMPORTANT NOTICE FOR PEOPLE RUNNING TRUNK re: [Bug 7826] Improve language around whitelist/blacklist and master/slave
This is foolish, we are losing control. I have nothing else to think about ...
and the next one that needs to change its name is the TV series "The Blacklist"?
And the next would be to delete the word "black"?
This is my opinion.
On 10 luglio 2020 a 09:05:26, Kevin A. McGrail (kmcgr...@apache.org) scritto:
Gents, while this may appear to be a response to racial tensions in the US of
late, you might be surprised to learn that the project has been working on this
type of change for quite some time.
- We start using Blocklist at least as early as 2012 when I drafted this:
https://cwiki.apache.org/confluence/display/SPAMASSASSIN/DnsBlocklistsInclusionPolicy
- And the vote on and discussion on this change was based on a UK article
https://www.zdnet.com/article/uk-ncsc-to-stop-using-whitelist-and-blacklist-due-to-racial-stereotyping/
which I brought to the PMC on 4/5. We brought it for a vote on 5/3.
So this isn't about US politics, it isn't rash and no it's not a joke. This is
about doing the right thing and getting rid of racially charged language. I'd
appreciate support in this change or at least if you can't say something nice
or helpful, just keep it to yourselves.
Regards,
KAM
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171
On Fri, Jul 10, 2020 at 2:50 AM Axb wrote:
the US problems won't be fixed with renaming B&W lists.
Seriously.. you have more important issues...
On 7/10/20 8:42 AM, jdow wrote:
> Be sure to purge every instance of "fork" in the code because it sounds
> too close to the other F..K word. Get the fork out of there.
>
> {O,o}
> i.e are you guys being just a little stupid here?
>
> On 20200709 21:00:37, Kevin A. McGrail wrote:
>> IMPORTANT NOTICE
>>
>> If you are running trunk, we are working on changing terms like
>> whitelist to welcomelist and blacklist to blocklist.
>>
>> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7826
>>
>> The first test of this work is done with allowlist_to replacing
>> whitelist_to
>> Committed revision 1879456.
>>
>> If you are using trunk, there may be disruption since routines,
>> plugins and rule changes will all interweave.
>>
>> *IF YOU ARE RUNNING TRUNK: I recommend you subscribe to the
>> d...@spamassassin.apache.org
>> mailing list to stay abreast of the changes.*
>> *
>> *
>> Please let me know if you have any questions!
>>
>> Regards,
>> KAM
>> --
>> Kevin A. McGrail
>> Member, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: problem with spamassassin for WIndows
Ok Groach, I perfectly understand. I already asked to Hmailserver forum about this issue. Thanks again. Da: Groach (mailto:groachmail-stopspammin...@yahoo.com) Rispondi: Groach (mailto:groachmail-stopspammin...@yahoo.com) Data: 18 febbraio 2018 at 19:02:46 A: users@spamassassin.apache.org (mailto:users@spamassassin.apache.org) Oggetto: Re: problem with spamassassin for WIndows > Keysteal, you will get your help for that on the hmailserver forum (where you > are following the guide from). > > This mail list is strictly spamassassin and not for the bespoke configuration > you are trying with mysql. > > (And we have already seen that some Linux snobs will refuse you your right to > use an os different to theirs and ask for help). > > Do not pursue this particular question on here. > > On 18 February 2018 16:23:22 GMT+00:00, Gianluca Furnarotto > wrote: > >Thanks Groach, and all guys that answered to me. This was very helpful. > >Next step for me is using Mysql to store learning spam. I followed a > >guide, but when I start sa-learn I have a strange windows error : "The > >program can't start because libmysql__.dll is missing from your > >computer. Try reinstalling > >the program to fix this problem" > >I find the .dll inside a perl folder, and I tried to copy everywhere, > >but nothing has changed. > > > >-- > >Gianluca Furnarotto > > > >Da: Groach > >(mailto:groachmail-stopspammin...@yahoo.com) > >Rispondi: Groach > >(mailto:groachmail-stopspammin...@yahoo.com) > >Data: 18 febbraio 2018 at 11:57:44 > >A: users@spamassassin.apache.org > >(mailto:users@spamassassin.apache.org) > >Oggetto: Re: problem with spamassassin for WIndows > > > >> Gianluca > >> > >> 1, Your .PRE files are (by default) in: > >> > >> %ProgramFiles(x86)%\JAM Software\SpamAssassin for > >Windows\etc\spamassassin > >> > >> You will find the 'AutoLearnThreshold' plugin you need in v310.pre. > >> You will find the BAYES and SHORTCIRCUIT plugins you need in v320.pre > >(they may already be enabled - but if not just removed the #) > >> > >> Then remove the loading of them from your Local.cf. > >> > >> 2, > >> To make them useful, your LOCAL.CF should read something like: > >> > >> (Example) > >> > >> > ifplugin Mail::SpamAssassin::Plugin::Shortcircuit > >> > > >> > # default: strongly-whitelisted mails are *really* whitelisted now, > >if the > >> > # shortcircuiting plugin is active, causing early exit to save CPU > >load. > >> > # Uncomment to turn this on > >> > # > >> > shortcircuit USER_IN_WHITELIST on > >> > shortcircuit USER_IN_DEF_WHITELIST on > >> > > >> > endif # Mail::SpamAssassin::Plugin::Shortcircuit > >> > >> > >> > >> > >> On 18/02/2018 01:21, John Hardin wrote: > >> > On Sun, 18 Feb 2018, Gianluca Furnarotto wrote: > >> > > >> > > I’ve done this modifications in local.cf: > >> > > > >> > > # ifplugin > >> > > > >> > > loadplugin Mail::SpamAssassin::Plugin::Shortcircuit > >> > > loadplugin Mail::SpamAssassin::Plugin::AutoLearnThreshold > >> > > loadplugin Mail::SpamAssassin::Plugin::Bayes > >> > > > >> > > #ok_languages en it > >> > > > >> > > ok_locales en > >> > > > >> > > # endif > >> > > > >> > > And command spamassassin —lint doesn’t show any errors. Tomorrow > >I will continue > >> > > the debugging. It seems it doesn’t agree ifplugin-endif and also > >ok_languages > >> > > >> > Three points: > >> > > >> > (1) the syntax for "ifplugin" is: > >> > > >> > ifplugin Mail::SpamAssassin::Plugin::whatever > >> > > >> > It's a test to see whether that plugin is loaded, so that you can > >write plugin-dependent rules without generating lint errors when the > >plugin isn't loaded. > >> > > >> > (2) "ifplugin" only accepts one plugin name. > >> > > >> > (3) "loadplugin" commands should be in your v340.pre file, so that > >they get loaded before any rules. > >> > > >> > > >> > If you added that "ifplugin" block to your config file, what > >exactly were you trying to achieve with that block? > >> > > >> > > >> > > -- > Sent from my Android device with K-9 Mail. Please excuse my brevity.
Re: problem with spamassassin for WIndows
Thanks Groach, and all guys that answered to me. This was very helpful. Next step for me is using Mysql to store learning spam. I followed a guide, but when I start sa-learn I have a strange windows error : "The program can't start because libmysql__.dll is missing from your computer. Try reinstalling the program to fix this problem" I find the .dll inside a perl folder, and I tried to copy everywhere, but nothing has changed. -- Gianluca Furnarotto Da: Groach (mailto:groachmail-stopspammin...@yahoo.com) Rispondi: Groach (mailto:groachmail-stopspammin...@yahoo.com) Data: 18 febbraio 2018 at 11:57:44 A: users@spamassassin.apache.org (mailto:users@spamassassin.apache.org) Oggetto: Re: problem with spamassassin for WIndows > Gianluca > > 1, Your .PRE files are (by default) in: > > %ProgramFiles(x86)%\JAM Software\SpamAssassin for Windows\etc\spamassassin > > You will find the 'AutoLearnThreshold' plugin you need in v310.pre. > You will find the BAYES and SHORTCIRCUIT plugins you need in v320.pre (they > may already be enabled - but if not just removed the #) > > Then remove the loading of them from your Local.cf. > > 2, > To make them useful, your LOCAL.CF should read something like: > > (Example) > > > ifplugin Mail::SpamAssassin::Plugin::Shortcircuit > > > > # default: strongly-whitelisted mails are *really* whitelisted now, if the > > # shortcircuiting plugin is active, causing early exit to save CPU load. > > # Uncomment to turn this on > > # > > shortcircuit USER_IN_WHITELIST on > > shortcircuit USER_IN_DEF_WHITELIST on > > > > endif # Mail::SpamAssassin::Plugin::Shortcircuit > > > > > On 18/02/2018 01:21, John Hardin wrote: > > On Sun, 18 Feb 2018, Gianluca Furnarotto wrote: > > > > > I’ve done this modifications in local.cf: > > > > > > # ifplugin > > > > > > loadplugin Mail::SpamAssassin::Plugin::Shortcircuit > > > loadplugin Mail::SpamAssassin::Plugin::AutoLearnThreshold > > > loadplugin Mail::SpamAssassin::Plugin::Bayes > > > > > > #ok_languages en it > > > > > > ok_locales en > > > > > > # endif > > > > > > And command spamassassin —lint doesn’t show any errors. Tomorrow I will > > > continue > > > the debugging. It seems it doesn’t agree ifplugin-endif and also > > > ok_languages > > > > Three points: > > > > (1) the syntax for "ifplugin" is: > > > > ifplugin Mail::SpamAssassin::Plugin::whatever > > > > It's a test to see whether that plugin is loaded, so that you can write > > plugin-dependent rules without generating lint errors when the plugin isn't > > loaded. > > > > (2) "ifplugin" only accepts one plugin name. > > > > (3) "loadplugin" commands should be in your v340.pre file, so that they get > > loaded before any rules. > > > > > > If you added that "ifplugin" block to your config file, what exactly were > > you trying to achieve with that block? > > > > >
Re: problem with spamassassin for WIndows
I’ve done this modifications in local.cf: # ifplugin loadplugin Mail::SpamAssassin::Plugin::Shortcircuit loadplugin Mail::SpamAssassin::Plugin::AutoLearnThreshold loadplugin Mail::SpamAssassin::Plugin::Bayes #ok_languages en it ok_locales en # endif And command spamassassin —lint doesn’t show any errors. Tomorrow I will continue the debugging. It seems it doesn’t agree ifplugin-endif and also ok_languages On 17 febbraio 2018 a 22:28:03, Bill Cole (sausers-20150...@billmail.scconsult.com) scritto: On 17 Feb 2018, at 14:48 (-0500), Kevin A. McGrail wrote: > I gave you a suggestion the other day. Your configuration is wrong. > You aren't passing lint > > Look at that line 717 or if that's not the right line number, look at > your configuration around your DB for Bayes. I'm not sure that Bayes has anything to do with it specifically. To get to Parser.pm line 571, it seems to me that the Parser needs to read a line that starts with "ifplugin" (or "if plugin") and that it is expecting a plugin name argument on that line. I can reproduce the base error by adding these 2 lines to any of the .pre or .cf files in the site preferences directory or to the active user_prefs file: ifplugin endif The one oddity is that I don't get any ' line [number]' clause in the error message from creating that broken config. This may be a Windows-specific quirk (I don't have a Windows machine for testing) or it may indicate some more arcane issue in how the configuration is being parsed. So the thing to look for is 'ifplugin' in local.cf, any other *.pre or *.cf file in the same directory as local.cf, or your user_prefs file. It should be followed by the name of a plugin, a block of lines defining rules or setting configuration parameters, and an "endif" line. > > On 2/17/2018 2:31 PM, Gianluca Furnarotto wrote: >> So, anyone can't give me a suggestion? >> >> >> On 16 febbraio 2018 a 08:24:04, Gianluca Furnarotto >> (keyst...@libero.it <mailto:keyst...@libero.it>) scritto: >> >>> Hi Bill, >>> >>> this is the result of the command you suggested to type: >>> >>> feb 16 07:21:09.678 [21824] warn: Use of uninitialized value $_[1] >>> in hash eleme >>> nt at Mail/SpamAssassin/Conf/Parser.pm line 571, line 717. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Currently Seeking Steady Work: https://linkedin.com/in/billcole
Re: problem with spamassassin for WIndows
I confirm you that problem is in local.cf, into these lines: ifplugin Mail::SpamAssassin::Plugin::Shortcircuit Mail::SpamAssassin::Plugin::AutoLearnThreshold Mail::SpamAssassin::Plugin::Bayes ok_languages en it endif If I comment all these lines, I don’t have any warning error. I don’t understand why. On 17 febbraio 2018 a 22:28:03, Bill Cole (sausers-20150...@billmail.scconsult.com) scritto: On 17 Feb 2018, at 14:48 (-0500), Kevin A. McGrail wrote: > I gave you a suggestion the other day. Your configuration is wrong. > You aren't passing lint > > Look at that line 717 or if that's not the right line number, look at > your configuration around your DB for Bayes. I'm not sure that Bayes has anything to do with it specifically. To get to Parser.pm line 571, it seems to me that the Parser needs to read a line that starts with "ifplugin" (or "if plugin") and that it is expecting a plugin name argument on that line. I can reproduce the base error by adding these 2 lines to any of the .pre or .cf files in the site preferences directory or to the active user_prefs file: ifplugin endif The one oddity is that I don't get any ' line [number]' clause in the error message from creating that broken config. This may be a Windows-specific quirk (I don't have a Windows machine for testing) or it may indicate some more arcane issue in how the configuration is being parsed. So the thing to look for is 'ifplugin' in local.cf, any other *.pre or *.cf file in the same directory as local.cf, or your user_prefs file. It should be followed by the name of a plugin, a block of lines defining rules or setting configuration parameters, and an "endif" line. > > On 2/17/2018 2:31 PM, Gianluca Furnarotto wrote: >> So, anyone can't give me a suggestion? >> >> >> On 16 febbraio 2018 a 08:24:04, Gianluca Furnarotto >> (keyst...@libero.it <mailto:keyst...@libero.it>) scritto: >> >>> Hi Bill, >>> >>> this is the result of the command you suggested to type: >>> >>> feb 16 07:21:09.678 [21824] warn: Use of uninitialized value $_[1] >>> in hash eleme >>> nt at Mail/SpamAssassin/Conf/Parser.pm line 571, line 717. -- Bill Cole b...@scconsult.com or billc...@apache.org (AKA @grumpybozo and many *@billmail.scconsult.com addresses) Currently Seeking Steady Work: https://linkedin.com/in/billcole
Re: problem with spamassassin for WIndows
So, anyone can't give me a suggestion?
On 16 febbraio 2018 a 08:24:04, Gianluca Furnarotto (keyst...@libero.it)
scritto:
Hi Bill,
this is the result of the command you suggested to type:
feb 16 07:21:09.678 [21824] warn: Use of uninitialized value $_[1] in hash eleme
nt at Mail/SpamAssassin/Conf/Parser.pm line 571, line 717.
On 16 febbraio 2018 a 02:06:40, Bill Cole
(sausers-20150...@billmail.scconsult.com) scritto:
On 15 Feb 2018, at 15:33, Gianluca Furnarotto wrote:
> Hi,
>
> I am trying to use Bayes with spamassassin, now it seems stop to
> learn, and
> when I use a command as "sa-learn --dump magic", or "sa-learn --sync",
> or other sa-learn commands,
> it appears this error:
> "Use of uninitialized value $_[1] in hash element at
> Mail/SpamAssassin/Conf/Parser.pm line 571."
>
> Line 571 is this:
> " } "
> inside these lines.
> " elsif ($type == $Mail::SpamAssassin::Conf::CONF_TYPE_ADDRLIST) {
> $cmd->{code} = \&set_addrlist_value;
> }" <--- line 571
That absolutely IS NOT line 571 of Mail/SpamAssassin/Conf/Parser.pm in
SA version 3.4.1. That's line 685.
The relevant lines in Mail/SpamAssassin/Conf/Parser.pm:
568
569 # functions supported in the "if" eval:
570 sub cond_clause_plugin_loaded {
571 return $_[0]->{conf}->{plugins_loaded}->{$_[1]};
572 }
573
My first guess on this is that your configuration has a typo. Try
running 'spamassassin --lint' to check it.
The error message indicates that something is calling the subroutine
'cond_clause_plugin_loaded' in a way that gives it only one parameter
where it is expecting 2, the first of which is an object reference.
Re: problem with spamassassin for WIndows
Hi Bill,
this is the result of the command you suggested to type:
feb 16 07:21:09.678 [21824] warn: Use of uninitialized value $_[1] in hash eleme
nt at Mail/SpamAssassin/Conf/Parser.pm line 571, line 717.
On 16 febbraio 2018 a 02:06:40, Bill Cole
(sausers-20150...@billmail.scconsult.com) scritto:
On 15 Feb 2018, at 15:33, Gianluca Furnarotto wrote:
> Hi,
>
> I am trying to use Bayes with spamassassin, now it seems stop to
> learn, and
> when I use a command as "sa-learn --dump magic", or "sa-learn --sync",
> or other sa-learn commands,
> it appears this error:
> "Use of uninitialized value $_[1] in hash element at
> Mail/SpamAssassin/Conf/Parser.pm line 571."
>
> Line 571 is this:
> " } "
> inside these lines.
> " elsif ($type == $Mail::SpamAssassin::Conf::CONF_TYPE_ADDRLIST) {
> $cmd->{code} = \&set_addrlist_value;
> }" <--- line 571
That absolutely IS NOT line 571 of Mail/SpamAssassin/Conf/Parser.pm in
SA version 3.4.1. That's line 685.
The relevant lines in Mail/SpamAssassin/Conf/Parser.pm:
568
569 # functions supported in the "if" eval:
570 sub cond_clause_plugin_loaded {
571 return $_[0]->{conf}->{plugins_loaded}->{$_[1]};
572 }
573
My first guess on this is that your configuration has a typo. Try
running 'spamassassin --lint' to check it.
The error message indicates that something is calling the subroutine
'cond_clause_plugin_loaded' in a way that gives it only one parameter
where it is expecting 2, the first of which is an object reference.
problem with spamassassin for WIndows
Hi,
I am trying to use Bayes with spamassassin, now it seems stop to learn, and
when I use a command as "sa-learn --dump magic", or "sa-learn --sync", or other
sa-learn commands,
it appears this error:
"Use of uninitialized value $_[1] in hash element at
Mail/SpamAssassin/Conf/Parser.pm line 571."
Line 571 is this:
" } "
inside these lines.
" elsif ($type == $Mail::SpamAssassin::Conf::CONF_TYPE_ADDRLIST) {
$cmd->{code} = \&set_addrlist_value;
}" <--- line 571
I'm not a perl programmer, so I need help to understand what is wrong.
Thanks.
p.s.: this is the Jam Software Spamassassin version for Windows
