Re: Lint failing
Alan, I have the serious impression that you are still running CentOS 6 as spamassassin 3.3.1 is the default spamassassin version of CentOS 6. Centos 6 was released back in 2011 and full upgrades stopped on 2017-05-10 (maintanance releases until november 2020). Are you still running CentOS 6? I am not going to spend any second helping you if you run a pre-dinosour version of both the OS and spamassassin. Met vriendelijke groet, Mit freundlichen Grüßen, Best regards, Thom van der Boon Van: "asparks" Aan: "Kevin A. McGrail" Cc: "SA Mailing list" Verzonden: Dinsdag 3 augustus 2021 17:35:51 Onderwerp: Re: Lint failing SO, OK... it's Tuesday and there's no resolution to the issue. Thanks. rules: failed to run URI_HOST_IN_BLOCKLIST test, skipping: (Can't locate object method "check_uri_host_in_blacklist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2022) line 394. ) rules: failed to run URI_HOST_IN_WELCOMELIST test, skipping: (Can't locate object method "check_uri_host_in_whitelist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2022) line 1489. ) channel: lint check of update failed, channel failed On 2021-07-31 12:21 PM, Kevin A. McGrail wrote: Alan, After a change is made to a rule, there is an automated process. The rule qa and update process is not quick. Nor is it causing any issues except not getting updates for rules. There are no major rule updates pending so it's a non impacting issue. However, now you know why the KAM ruleset exists because the process for stock rule publishing is too slow. Recommend you ignore the issue until Monday and if it doesn't resolve then we'll look at it again and try and figure out why a good rule set is not being published. On Sat, Jul 31, 2021, 13:15 Alan Sparks < [ mailto:aspa...@doublesparks.net | aspa...@doublesparks.net ] > wrote: BQ_BEGIN So it's Saturday, not Monday yet, but nothing has changed... has a "fix" been published yet? Maybe the fix doesn't work? ]$ sudo /usr/bin/sa-update - Update available for channel [ http://updates.spamassassin.org/ | updates.spamassassin.org ] rules: failed to run URI_HOST_IN_BLOCKLIST test, skipping: (Can't locate object method "check_uri_host_in_blacklist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 394. ) rules: failed to run URI_HOST_IN_WELCOMELIST test, skipping: (Can't locate object method "check_uri_host_in_whitelist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 1489. ) channel: lint check of update failed, channel failed Update failed, exiting with code 4 -Alan On 7/29/2021 1:36 PM, Kevin A. McGrail wrote: BQ_BEGIN Fixes are likely done and just waiting on masscheck, etc. to publish rules. If it isn't fixed by Monday, please let us know. P.S. 3.3.1 is very old. Can you upgrade? -- Kevin A. McGrail Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project [ https://www.linkedin.com/in/kmcgrail | https://www.linkedin.com/in/kmcgrail ] - 703.798.0171 On Thu, Jul 29, 2021 at 11:21 AM Alan Sparks < [ mailto:aspa...@doublesparks.net | aspa...@doublesparks.net ] > wrote: BQ_BEGIN Starting yesterday, my SA 3.3.1 running on CentOS started throwing lint errors, as below. Is there a fix for this? Thanks in advance. -Alan $ sudo /usr/bin/sa-update -vvv Update available for channel [ http://updates.spamassassin.org/ | updates.spamassassin.org ] rules: failed to run URI_HOST_IN_BLOCKLIST test, skipping: (Can't locate object method "check_uri_host_in_blacklist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 394. ) rules: failed to run URI_HOST_IN_WELCOMELIST test, skipping: (Can't locate object method "check_uri_host_in_whitelist" via package "Mail::SpamAssassin::PerMsgStatus" at (eval 2016) line 1489. ) channel: lint check of update failed, channel failed Update failed, exiting with code 4 BQ_END BQ_END BQ_END
Re: Constructive solution to the blacklist thread
Dear everybody, Could we please "cut the crap" and stop with all the polictics. SpamAssassin is a fantastic piece of software in reducing the amount of spam which gets into our inboxes. I do thank Kevin and everybody contributing for their past, present and future work. I do not like the proposed change, because of greylisting. What is between a welcomelist and a blocklist? I would have liked it much more if the colors of a traffic light were chosen (greenlist, amberlist, redlist). That also would create posibilities like "very dark amber" (= almost red) For instance every mail from a .icu domain would be amber listed with me Met vriendelijke groet, Best regards, Thom van der Boon E-Mail: t...@vdb.nl Van: "Eric Broch" Aan: "SA Mailing list" Verzonden: Zaterdag 25 juli 2020 14:03:43 Onderwerp: Re: Constructive solution to the blacklist thread On 7/24/2020 6:00 PM, Noel Butler wrote: On 25/07/2020 04:03, Kevin A. McGrail wrote: BQ_BEGIN I'd say too many people without merit and knowledge of the project spouting off building on misinformation and rants more fitting for a racist channel on 4chan would be my analysis of what started the discussion. here we go again, attacking people calling them racists and radical extremists because we wont roll over and bow to your american political dictatorship, you act as has been shown here with no thought to others or consequences to others, you act without even understanding of what the colour based terms are and where they came from, if you actually did any research into this (which you admit you did not) youd realise that. There are 192 _other_ countries in the world, the USA is united states of america, not united states of world - get used to pushbacks from those who are sick of the USA pushing their views and values on to others because of their own failings, especially when you cant even protect your own kids from mass murder at hands of gun nuts, when you can, THEN you can come here and beat your chest about how great a nation you are. BQ_END Practically, the U.S., its politicians and citizens, have embraced every plank of the Communist Manifesto. I cannot belief how fast the delusion has set in here. This is no longer a Constitutional Republic but has been taken over by Marxists and their ideology, Marxism is not benign but malignant. This is why the whole world feels pressure from the U.S. if not by open warfare by sanctions, or revolutionaries released on your streets. Your politicians and media are bought off and controlled by the CIA. The delusion is so complete that as we see with the S.A. project no shots will be fired. In soviet fashion the agenda is perpetrated.
Re: IMPORTANT NOTICE: Rules referencing WHITELIST or BLACKLIST in process of being Renamed
Dear Kevin,
I maintain a rule set specificly targeted at the Dutch language: [
https://dutchspamassassinrules.nl/DSR/DSR.cf |
https://dutchspamassassinrules.nl/DSR/DSR.cf ]
One example is that our IRS ("Belastingdienst") is whitelisted by the following
rule:
whitelist_from_spf *@belastingdienst.nl
Our IRS ("Belastingdienst") uses DKIM, SPF and DMARC, so fake messages are
extremely easy to detect.
This list (DSR) is used by a number of mailservers in the Netherlands. So the
changes that were made. will impact all servers that use the DSR
Met vriendelijke groet, Best regards,
Thom van der Boon
E-Mail: t...@vdb.nl
Van: "Kevin A. McGrail"
Aan: "Thom van der Boon"
Cc: "SA Mailing list" , "SpamAssassin Devel
List"
Verzonden: Zondag 19 juli 2020 19:56:34
Onderwerp: Re: IMPORTANT NOTICE: Rules referencing WHITELIST or BLACKLIST in
process of being Renamed
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 Boon < [ mailto:t...@vdb.nl |
t...@vdb.nl ] > wrote:
Dear Kevin,
Could you please clearify what versions are affected in these changes?
My own rules rely heavily on whitelist_from_spf
Met vriendelijke groet, Best regards,
Thom van der Boon
E-Mail: [ mailto:t...@vdb.nl | t...@vdb.nl ]
Van: "Kevin A. McGrail" < [ mailto:kmcgr...@apache.org | kmcgr...@apache.org ]
>
Aan: "SA Mailing list" < [ mailto:users@spamassassin.apache.org |
users@spamassassin.apache.org ] >, "SpamAssassin Devel List" < [
mailto:d...@spamassassin.apache.org | d...@spamassassin.apache.org ] >
Verzonden: Zondag 19 juli 2020 18:09:36
Onderwerp: IMPORTANT NOTICE: Rules referencing WHITELIST or BLACKLIST in
process of being Renamed
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 you have custom scoring or any custom rules building on
USER_IN_WHITELIST_TO, please accept our apologies and change the
references to USER_IN_WELCOMELIST_TO.
In order to remove racially charged configuration options, whitelist
will become welcomelist and blacklist will become blocklist. More
changes will be coming for this with these small changes in the stock
ruleset.
Apologies for the disruption and thanks to those who are reporting
issues as we work through the changes.
Regards,
KAM
--
Kevin A. McGrail
kmcgr...@apache.org
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
[ https://www.linkedin.com/in/kmcgrail | https://www.linkedin.com/in/kmcgrail ]
- 703.798.0171
Re: IMPORTANT NOTICE: Rules referencing WHITELIST or BLACKLIST in process of being Renamed
Dear Kevin, Could you please clearify what versions are affected in these changes? My own rules rely heavily on whitelist_from_spf Met vriendelijke groet, Best regards, Thom van der Boon E-Mail: t...@vdb.nl Van: "Kevin A. McGrail" Aan: "SA Mailing list" , "SpamAssassin Devel List" Verzonden: Zondag 19 juli 2020 18:09:36 Onderwerp: IMPORTANT NOTICE: Rules referencing WHITELIST or BLACKLIST in process of being Renamed 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 you have custom scoring or any custom rules building on USER_IN_WHITELIST_TO, please accept our apologies and change the references to USER_IN_WELCOMELIST_TO. In order to remove racially charged configuration options, whitelist will become welcomelist and blacklist will become blocklist. More changes will be coming for this with these small changes in the stock ruleset. Apologies for the disruption and thanks to those who are reporting issues as we work through the changes. Regards, KAM -- Kevin A. McGrail kmcgr...@apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
