Re: IMPORTANT NOTICE FOR PEOPLE RUNNING TRUNK re: [Bug 7826] Improve language around whitelist/blacklist and master/slave
Maybe my tinfoil hat is tight, but that is no sin. Slander is a sin, and you are guilty of it. To call someone a racist, or white privileged, because they use the term 'blacklist' or 'whitelist' is slander. When you demonize someone or some people murder is not far behind. This is nothing but a political move and you know it. You want to put it in flowery language and tell us all how benevolent you are but in your "inclusivity" you slander those who oppose you. Slanderers are so VEEEY inclusive. You slander people who've done NOTHING wrong telling them they're "not decent," "racists," "privileged white people," and wackos. You're hypocrites. This is a very loving society you've put together. You slander and your conscience doesn't even prick you. You're building your utopia without God as He's obviously not in your conscience. What is the promised utopia without God? The Marxist society. Remember! In the Marxist society the "Useful Idiots" are first heads on the chopping block. Then, you may wake up from your delusion, but it will be to late. On 7/16/2020 12:16 AM, Thomas Cameron wrote: On 7/10/20 12:07 PM, Eric Broch wrote: Amen! This is not about racism this is about a Marxist (Socialist) takeover. They don't care if you use the terms whitelist or blacklist, this is a revolution. Soon, it will be as in Dr. Zhivago. You'll come home being dispossessed of your house and belongings under the supervision of the state, already going on as BLM freely loots and pillages. The "Useful Idiots" (not trying to be offensive, Kevin, but get a grip) don't know that after the reorganization is done, their heads will be on the chopping block as well...all planned in advance. These are sad days, woe is me if I don't speak out. Man, your tinfoil hat is on WAY too tight. Inclusivity is not Marxism, Eric. It's being a decent human being. You should try it some time. Thomas
Re: IMPORTANT NOTICE FOR PEOPLE RUNNING TRUNK re: [Bug 7826] Improve language around whitelist/blacklist and master/slave
On 7/10/20 12:07 PM, Eric Broch wrote: Amen! This is not about racism this is about a Marxist (Socialist) takeover. They don't care if you use the terms whitelist or blacklist, this is a revolution. Soon, it will be as in Dr. Zhivago. You'll come home being dispossessed of your house and belongings under the supervision of the state, already going on as BLM freely loots and pillages. The "Useful Idiots" (not trying to be offensive, Kevin, but get a grip) don't know that after the reorganization is done, their heads will be on the chopping block as well...all planned in advance. These are sad days, woe is me if I don't speak out. Man, your tinfoil hat is on WAY too tight. Inclusivity is not Marxism, Eric. It's being a decent human being. You should try it some time. Thomas
Re: IMPORTANT NOTICE FOR PEOPLE RUNNING TRUNK re: [Bug 7826] Improve language around whitelist/blacklist and master/slave
On 7/10/20 4:33 AM, jdow wrote:
Are we now going to be afraid of the unwelcome rather than the dark?
Are we going to shine a welcome on problems rather than light?
You guys are MAKING problems where they do not exist. Shame on you,
children.
{^_^}
Nah, you're clinging to old, exclusionary language and behavior when
being inclusive is so damned easy.
Shame on you, old-timer. Be better than this.
Thomas
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
Q: What did Marxists use to light their homes before candles? A: Electrcity. Get BlueMail for Android On Jul 15, 2020, 9:53 PM, at 9:53 PM, Noel Butler wrote: >I guess they're going to go back to the yellowish tinged incandescent >bulbs too, since LEDs available today produce " white " light. They'll >have to change their story books as well, cant call it after "dark" or >"dark" night|skies|... > >It's amazing how SOME Americans are quick to jump on bandwagons about >innocent terms are called, yet FAIL to do ANYTHING about their >population - even KIDS, getting slaughtered and gunned down nearly >every >second day in mass shootings. but you only have to look at how they are >acting with COVID19 to know they have NFI about civil priorities. > >No wonder the USA is the joke of the world - and its not all Trumps >fault <--- (jesus christ, I never thought I'd hear myself say that) > >On 16/07/2020 13:37, Eric Broch wrote: > >> You're the ones who've moved, I've gone nowhere. You'll never run out >of words to censor. Soon you'll be offended by everything. Where will >you hide then. I don't know how you'll escape the planet when everyone >and everything offends you. >> >> More importantly calling those racists who are not racists is >slander--bearing false witness against you neighbor--a violation of the >9th commandment. Instead of fearing God alone you adore the praise of >wicked men. >> >> On 7/15/2020 8:21 PM, Thomas Cameron wrote: >> On 7/15/20 9:12 PM, Eric Broch wrote: >> Using the word "blacklist" is racism. Does everyone get this! By >definition you ARE a "RACIST" and ARE "White Privilege[d]." >> >> This is a political movement to blacklist (oohhh, I said it) >anyone who does not comply. We're no longer angry, we're "not excited," >how generous. >> >> The spamassassin leadership team are political hacks. >> Don't let the door hit you on the way out, then. >> >> Thomas > >-- >Kind Regards, > >Noel Butler > > This Email, including attachments, may contain legally > privileged >information, therefore remains confidential and subject to copyright >protected under international law. You may not disseminate any part of >this message without the authors express written authority to do so. If >you are not the intended recipient, please notify the sender then >delete >all copies of this message including attachments immediately. >Confidentiality, copyright, and legal privilege are not waived or lost >by reason of the mistaken delivery of this message.
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
Tokenism is a big thing in politics, probably everywhere on this planet. Gotta
be seen as doing something, ya know. We need a third house in our legislature,
the House of Repeals that strikes out dumb laws hastily drafted to appease loud
mouths.
{o.o}
On 20200715 20:52:51, Noel Butler wrote:
I guess they're going to go back to the yellowish tinged incandescent bulbs too,
since LEDs available today produce " white " light. They'll have to change their
story books as well, cant call it after "dark" or "dark" night|skies|...
It's amazing how SOME Americans are quick to jump on bandwagons about innocent
terms are called, yet FAIL to do ANYTHING about their population - even KIDS,
getting slaughtered and gunned down nearly every second day in mass shootings.
but you only have to look at how they are acting with COVID19 to know they have
NFI about civil priorities.
No wonder the USA is the joke of the world - and its not all Trumps fault <---
(jesus christ, I never thought I'd hear myself say that)
On 16/07/2020 13:37, Eric Broch wrote:
You're the ones who've moved, I've gone nowhere. You'll never run out of words
to censor. Soon you'll be offended by everything. Where will you hide then. I
don't know how you'll escape the planet when everyone and everything offends you.
More importantly calling those racists who are not racists is slander--bearing
false witness against you neighbor--a violation of the 9th commandment.
Instead of fearing God alone you adore the praise of wicked men.
On 7/15/2020 8:21 PM, Thomas Cameron wrote:
On 7/15/20 9:12 PM, Eric Broch wrote:
Using the word "blacklist" is racism. Does everyone get this! By definition
you ARE a "RACIST" and ARE "White Privilege[d]."
This is a political movement to blacklist (oohhh, I said it) anyone
who does not comply. We're no longer angry, we're "not excited," how generous.
The spamassassin leadership team are political hacks.
Don't let the door hit you on the way out, then.
Thomas
--
Kind Regards,
Noel Butler
This Email, including attachments, may contain legally privileged information,
therefore remains confidential and subject to copyright protected under
international law. You may not disseminate any part of this message without the
authors express written authority to do so. If you are not the intended
recipient, please notify the sender then delete all copies of this message
including attachments immediately. Confidentiality, copyright, and legal
privilege are not waived or lost by reason of the mistaken delivery of this
message.
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
On 20200715 19:34:00, Noel Butler wrote:
On 16/07/2020 09:24, Kevin A. McGrail wrote:
All:
We're getting some positive attention from the verbiage change. See
https://www.linkedin.com/posts/kmcgrail_apache-spamassassin-leads-a-growing-list-activity-6689260331719520256-gMy7
for a link to a Guardian Digital post about it.
Anyway, I hope those not excited by the change will come around. We are
working hard to make it as painless as possible and we have gotten word
that several tools and projects that integrate with SpamAssassin will
follow suit.
Regards,
KAM
December 27 (our quietest time of year generally) this year has been slated for
our changeover to remove spamassassin from our network.
Our policies have long excluded using politically motivated companies,
organisations, equipment and software. you made this political, you do not care
for the opinions of others unless they agree with yours, so adios amigos.
You can probably fork the project and go on running what exists now going
forward. That is something I am mulling doing for myself. I just have to ask
myself, which is more painful?
{o.o}
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
I guess they're going to go back to the yellowish tinged incandescent bulbs too, since LEDs available today produce " white " light. They'll have to change their story books as well, cant call it after "dark" or "dark" night|skies|... It's amazing how SOME Americans are quick to jump on bandwagons about innocent terms are called, yet FAIL to do ANYTHING about their population - even KIDS, getting slaughtered and gunned down nearly every second day in mass shootings. but you only have to look at how they are acting with COVID19 to know they have NFI about civil priorities. No wonder the USA is the joke of the world - and its not all Trumps fault <--- (jesus christ, I never thought I'd hear myself say that) On 16/07/2020 13:37, Eric Broch wrote: > You're the ones who've moved, I've gone nowhere. You'll never run out of > words to censor. Soon you'll be offended by everything. Where will you hide > then. I don't know how you'll escape the planet when everyone and everything > offends you. > > More importantly calling those racists who are not racists is > slander--bearing false witness against you neighbor--a violation of the 9th > commandment. Instead of fearing God alone you adore the praise of wicked men. > > On 7/15/2020 8:21 PM, Thomas Cameron wrote: > On 7/15/20 9:12 PM, Eric Broch wrote: > Using the word "blacklist" is racism. Does everyone get this! By definition > you ARE a "RACIST" and ARE "White Privilege[d]." > > This is a political movement to blacklist (oohhh, I said it) anyone > who does not comply. We're no longer angry, we're "not excited," how > generous. > > The spamassassin leadership team are political hacks. > Don't let the door hit you on the way out, then. > > Thomas -- Kind Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore remains confidential and subject to copyright protected under international law. You may not disseminate any part of this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
On 16/07/2020 13:15, Benny Pedersen wrote: > Noel Butler skrev den 2020-07-16 04:34: > >> December 27 (our quietest time of year generally) this year has been >> slated for our changeover to remove spamassassin from our network. > > +1 > >> Our policies have long excluded using politically motivated companies, >> organisations, equipment and software. you made this political, you do >> not care for the opinions of others unless they agree with yours, so >> adios amigos. > > whats problem drinking coconut milk now ?, or even take another brik of white > chokolate from Ritter Sport ?, does it need to be orange to be good ?, or > black ?, maybe brown ?, is it political ? > > where will you go if not using spamassassin ? are you really so naive to think that SA is the only product around, or even the only free product around if your skimp? PS when i was a kid, a long, VERY long time ago I tried coconut milk - it was disgusting I dont eat chocolate. I dont eat sugar filled lollies, or any of that crap junk trash. -- Kind Regards, Noel Butler This Email, including attachments, may contain legally privileged information, therefore remains confidential and subject to copyright protected under international law. You may not disseminate any part of this message without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message.
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
You're the ones who've moved, I've gone nowhere. You'll never run out of words to censor. Soon you'll be offended by everything. Where will you hide then. I don't know how you'll escape the planet when everyone and everything offends you. More importantly calling those racists who are not racists is slander--bearing false witness against you neighbor--a violation of the 9th commandment. Instead of fearing God alone you adore the praise of wicked men. On 7/15/2020 8:21 PM, Thomas Cameron wrote: On 7/15/20 9:12 PM, Eric Broch wrote: So, This is the heading of the article: Apache SpamAssassin Leads A Growing List of Open-Source Projects Taking Steps to Correct Instances of Racism and White Privilege Using the word "blacklist" is racism. Does everyone get this! By definition you ARE a "RACIST" and ARE "White Privilege[d]." This is a political movement to blacklist (oohhh, I said it) anyone who does not comply. We're no longer angry, we're "not excited," how generous. The spamassassin leadership team are political hacks. Don't let the door hit you on the way out, then. Thomas
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
Noel Butler skrev den 2020-07-16 04:34: December 27 (our quietest time of year generally) this year has been slated for our changeover to remove spamassassin from our network. +1 Our policies have long excluded using politically motivated companies, organisations, equipment and software. you made this political, you do not care for the opinions of others unless they agree with yours, so adios amigos. whats problem drinking coconut milk now ?, or even take another brik of white chokolate from Ritter Sport ?, does it need to be orange to be good ?, or black ?, maybe brown ?, is it political ? where will you go if not using spamassassin ?
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
On 16/07/2020 09:24, Kevin A. McGrail wrote: > All: > > We're getting some positive attention from the verbiage change. See > https://www.linkedin.com/posts/kmcgrail_apache-spamassassin-leads-a-growing-list-activity-6689260331719520256-gMy7 > for a link to a Guardian Digital post about it. > > Anyway, I hope those not excited by the change will come around. We are > working hard to make it as painless as possible and we have gotten word > that several tools and projects that integrate with SpamAssassin will > follow suit. > > Regards, > > KAM December 27 (our quietest time of year generally) this year has been slated for our changeover to remove spamassassin from our network. Our policies have long excluded using politically motivated companies, organisations, equipment and software. you made this political, you do not care for the opinions of others unless they agree with yours, so adios amigos.
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
On 7/15/20 9:12 PM, Eric Broch wrote: So, This is the heading of the article: Apache SpamAssassin Leads A Growing List of Open-Source Projects Taking Steps to Correct Instances of Racism and White Privilege Using the word "blacklist" is racism. Does everyone get this! By definition you ARE a "RACIST" and ARE "White Privilege[d]." This is a political movement to blacklist (oohhh, I said it) anyone who does not comply. We're no longer angry, we're "not excited," how generous. The spamassassin leadership team are political hacks. Don't let the door hit you on the way out, then. Thomas
Re: Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
So, This is the heading of the article: Apache SpamAssassin Leads A Growing List of Open-Source Projects Taking Steps to Correct Instances of Racism and White Privilege Using the word "blacklist" is racism. Does everyone get this! By definition you ARE a "RACIST" and ARE "White Privilege[d]." This is a political movement to blacklist (oohhh, I said it) anyone who does not comply. We're no longer angry, we're "not excited," how generous. The spamassassin leadership team are political hacks. Eric On 7/15/2020 5:24 PM, Kevin A. McGrail wrote: All: We're getting some positive attention from the verbiage change. See https://www.linkedin.com/posts/kmcgrail_apache-spamassassin-leads-a-growing-list-activity-6689260331719520256-gMy7 for a link to a Guardian Digital post about it. Anyway, I hope those not excited by the change will come around. We are working hard to make it as painless as possible and we have gotten word that several tools and projects that integrate with SpamAssassin will follow suit. Regards, KAM
Thanks to Guardian Digital & LinuxSecurity for the nice post about SpamAssassin's upcoming change
All: We're getting some positive attention from the verbiage change. See https://www.linkedin.com/posts/kmcgrail_apache-spamassassin-leads-a-growing-list-activity-6689260331719520256-gMy7 for a link to a Guardian Digital post about it. Anyway, I hope those not excited by the change will come around. We are working hard to make it as painless as possible and we have gotten word that several tools and projects that integrate with SpamAssassin will follow suit. 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
Re: update fail
--On Wednesday, July 15, 2020 9:59 AM -0400 "Kevin A. McGrail" wrote: I'm sure someone has produced an RPM for CentOS 6 for 3.4.4 by now. I'm using John Hardin's recommendation from his 2020-02-07 post and it's working fine on CentOS 7: You can download the original (as well as later versions if/when they are produced) from FC rawhide here: http://mirror.siena.edu/fedora/linux/development/rawhide/Everything/source/tree/Packages/s/ (or whatever your closest FC Rawhide mirror is) Per Amir, if you install the perl-generators package from EPEL you can build that with no changes needed.
Re: update fail
On 7/15/2020 8:33 AM, Frédéric Nass wrote: > Thank you for your quick and enlightening response! I've seen your > other post today about rule update #1879885 that is to be realesed. Thanks, Frederic. I hope that fix will resolve your issue as well. I believe they are one and the same, i.e. a lint warning being treated as an error on older sa-updates but it gave me the opportunity to streamline the rule. > Thank you for fixing it for older SA versions (SA 3.3.1 is still the > one in CentOS/RHEL 6.10 supported until Nov. 30th). While we don't try and break older releases on purpose, distro policies that backport rather than upgrade is not the responsibility of the Apache SpamAssassin project. Here's our release support information: /A major release is supported for no less than 6 months after the release of the next major release. / /This means that as of November 30, 2014, all versions prior to 3.4.0 are considered unsupported./ So the version you are using is 6 years out of support. When 4.0.0 comes out as a major release, we will start looking at dropping support for 3.4. I'm sure someone has produced an RPM for CentOS 6 for 3.4.4 by now. You might consider asking about that and upgrading. There's a lot of great features (and bug and security fixes) in 3.4.4. And 3.4.5 will be coming soon too. A pre1 release is already out and I'm tweaking a pre2 for the past week. Regards, KAM
Re: update fail
Kevin, Thank you for your quick and enlightening response! I've seen your other post today about rule update #1879885 that is to be realesed. Thank you for fixing it for older SA versions (SA 3.3.1 is still the one in CentOS/RHEL 6.10 supported until Nov. 30th). Best regards, Frédéric. - Le 15 Juil 20, à 13:01, kmcgrail a écrit : > On 7/15/2020 6:29 AM, Frédéric Nass wrote: >> As of today July 15th, sa-update (3.3.1) is trying to install 1879817.tar.gz >> and >> it's still failing to do so. > Hi Frederic, > What's the error you are getting specifically? >> Can you tell us in which revision of the signatures this is expected to be >> fixed? And confirm that this fix will also work for older versions of SA? > I cannot because I don't know what problem you are having and it works for me > with no lint errors on 3.4.5. with ruleset 1879817. I'd like to get it working > and will look at the error from your sa-update. > A couple more points: > 3.3.1 is ancient released over a decade ago. 3.4.4 is significantly better not > to mention more secure with numerous bugs and security issues fixed including > a > few CVEs along the way. > Also are you aware that the project's rule updates are ending for that > version? > We've been working to convey that info and it's on the website:*** On March 1, > 2020, we will stop publishing rulesets with SHA-1 checksums. If you do not > update to 3.4.2 or later, you will be stuck at the last ruleset with SHA-1 > signatures. ***. This change is based on a policy requirement of the > foundation > and security issues with these weak hashes. > Regards, > KAM smime.p7s Description: S/MIME Cryptographic Signature
sa-update for versions 3.4.2 and older fail lint because of description on non-existent rule was Re: update fail
Just an update that this is fixed: https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7840 Should be a rule update published in the next 48 hours with the fix. Feedback welcome because we are making fixes for older versions so it's harder to gauge if it's fixed without user feedback. Regards, KAM On 7/15/2020 7:58 AM, Kevin A. McGrail wrote: > On 7/15/2020 7:13 AM, Marcus Schopen wrote: >> - >> config: warning: description exists for non-existent rule >> USER_IN_WELCOMELIST_TO >> >> Jul 15 13:10:33.621 [2458] dbg: diag: updates complete, exiting with >> code 4 >> Update failed, exiting with code 4 >> sa-update failed for unknown reasons >> - >> >> I will send you the complete output. >> > Ahh, that is a new problem and only affects old versions 3.4.2 and > before. Working on it. > > > > -- > Kevin A. McGrail > kmcgr...@apache.org > > Member, Apache Software Foundation > Chair Emeritus Apache SpamAssassin Project > https://www.linkedin.com/in/kmcgrail - 703.798.0171 -- Kevin A. McGrail kmcgr...@apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: update fail
On 7/15/2020 7:13 AM, Marcus Schopen wrote: > - > config: warning: description exists for non-existent rule > USER_IN_WELCOMELIST_TO > > Jul 15 13:10:33.621 [2458] dbg: diag: updates complete, exiting with > code 4 > Update failed, exiting with code 4 > sa-update failed for unknown reasons > - > > I will send you the complete output. > Ahh, that is a new problem and only affects old versions 3.4.2 and before. Working on it. -- Kevin A. McGrail kmcgr...@apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: update fail
Am Mittwoch, den 15.07.2020, 07:08 -0400 schrieb Kevin A. McGrail: > If it is still not working, what error are you getting, please? On 7/15/2020 6:59 AM, Marcus Schopen wrote: > > > Can you try now and lmk, please? I think the current ruleset is > > > 1879881 > > > has it fixed and is published. - config: warning: description exists for non-existent rule USER_IN_WELCOMELIST_TO Jul 15 13:10:33.621 [2458] dbg: diag: updates complete, exiting with code 4 Update failed, exiting with code 4 sa-update failed for unknown reasons - I will send you the complete output. Ciao!
Re: update fail
If it is still not working, what error are you getting, please? On 7/15/2020 6:59 AM, Marcus Schopen wrote: >> Can you try now and lmk, please? I think the current ruleset is >> 1879881 >> has it fixed and is published. -- Kevin A. McGrail kmcgr...@apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: update fail
This isn't the issue. We haven't turned off the sha1 sigs (yet). On 7/15/2020 7:06 AM, Matus UHLAR - fantomas wrote: > > it's described here and not expected to get fixed: -- Kevin A. McGrail kmcgr...@apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: update fail
On 15.07.20 12:29, Frédéric Nass wrote: From: Frédéric Nass To: kmcgr...@apache.org, users@spamassassin.apache.org Subject: update fail Hello Kevin, I am not kevin, is that fine? As of today July 15th, sa-update (3.3.1) is trying to install 1879817.tar.gz and it's still failing to do so. Can you tell us in which revision of the signatures this is expected to be fixed? And confirm that this fix will also work for older versions of SA? it's described here and not expected to get fixed: https://spamassassin.apache.org/news.html *** On March 1, 2020, we will stop publishing rulesets with SHA-1 checksums. If you do not update to 3.4.2 or later, you will be stuck at the last ruleset with SHA-1 checksums. *** -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I'm not interested in your website anymore. If you need cookies, bake them yourself.
Re: update fail
Am Mittwoch, den 15.07.2020, 12:59 +0200 schrieb Marcus Schopen: > The version for Ubuntu 16.04 LTS is Spamassassin 2.4.2. Sorry, Spamassassin 3.4.2-0ubuntu0.16.04.4 of course.
Re: update fail
On 7/15/2020 6:29 AM, Frédéric Nass wrote: > As of today July 15th, sa-update (3.3.1) is trying to install > 1879817.tar.gz and it's still failing to do so. Hi Frederic, What's the error you are getting specifically? > Can you tell us in which revision of the signatures this is expected > to be fixed? And confirm that this fix will also work for older > versions of SA? I cannot because I don't know what problem you are having and it works for me with no lint errors on 3.4.5. with ruleset 1879817. I'd like to get it working and will look at the error from your sa-update. A couple more points: 3.3.1 is ancient released over a decade ago. 3.4.4 is significantly better not to mention more secure with numerous bugs and security issues fixed including a few CVEs along the way. Also are you aware that the project's rule updates are ending for that version? We've been working to convey that info and it's on the website:*** On March 1, 2020, we will stop publishing rulesets with SHA-1 checksums. If you do not update to 3.4.2 or later, you will be stuck at the last ruleset with SHA-1 signatures. ***. This change is based on a policy requirement of the foundation and security issues with these weak hashes. Regards, KAM
Re: update fail
Am Mittwoch, den 15.07.2020, 06:26 -0400 schrieb Kevin A. McGrail: > Yeah, that's just a lint warning. A fix was committed but I had to > work > out a merge complaint on the rule system publishing this morning. I > believe a Yes, but it prevents the signatures from being updated! > Can you try now and lmk, please? I think the current ruleset is > 1879881 > has it fixed and is published. > > However SA 3.4.3+ will still install updates with just a warning. > Can > you upgrade your SA or are you stuck at 3.4.2? The version for Ubuntu 16.04 LTS is Spamassassin 2.4.2. I don't want to update the whole server or build a backport on the fly. In this respect it would be good if the updates are also suitable for a still supported Ubuntu LTS. 1879817 is the current version and still fails. Ciao Marcus
update fail
Hello Kevin, As of today July 15th, sa-update (3.3.1) is trying to install 1879817.tar.gz and it's still failing to do so. Can you tell us in which revision of the signatures this is expected to be fixed? And confirm that this fix will also work for older versions of SA? Best regards, Frédéric. smime.p7s Description: S/MIME Cryptographic Signature
Re: update fail
Yeah, that's just a lint warning. A fix was committed but I had to work out a merge complaint on the rule system publishing this morning. I believe a Can you try now and lmk, please? I think the current ruleset is 1879881 has it fixed and is published. However SA 3.4.3+ will still install updates with just a warning. Can you upgrade your SA or are you stuck at 3.4.2? Regards, KAM > Problem now "USER_IN_WELCOMELIST_TO" with spamassassin 3.4.2- > 0ubuntu0.16.04.4 on Ubuntu 16.04 LTS: > > --- > /etc/cron.hourly/spamassassin: > config: warning: description exists for non-existent rule > USER_IN_WELCOMELIST_TO > > channel: lint check of update failed, channel failed > sa-update failed for unknown reasons > --- > > So all Ubuntu 16.04 LTS and my be older Debian installations are > affected. > > Ciao! > > -- Kevin A. McGrail kmcgr...@apache.org Member, Apache Software Foundation Chair Emeritus Apache SpamAssassin Project https://www.linkedin.com/in/kmcgrail - 703.798.0171
Re: spamhaus enabled by default
On Tue, 2020-07-14 at 22:57 -0400, Kevin A. McGrail wrote: > > A pointer to the wiki might be useful in the config files as well as > > > the > > > docs. Suggestions of which files? > > > > local.cf is the obvious one. > > > > Might not be a bad choice. I've never even looked at a stock local.cf > from the project in 20 years though. Need to do a vanilla install and > see what is in there and where it is generated. > What about the docs? Where would you look for this nugget of > information as a user? > As a long-time UNIX/Linux developer I'd naturally look in the Spamassassin manpage, but I suspect a non-developer may not unless they're a power user. I'd also guess that others, including Mac and Windows users, would be looking for Help|About from a GUI app (nonapplicable here of course) or, failing that, to point a web browser at http://spamassassin.apache.org/ I think the best place to put warnings and advice about exceeding free usage RBL limits are: In the manpage: - the manpage, which only needs a single line saying something like: "Free RBL use limits: URL" added to its WEBSITES section On the Spamassassin website: - The top-level README - The Start Using page in the Wiki - the FAQ page. All these can link to a common page that describes low volume free use policies of Spamhaus and others RBL providers and how NOT using a local non-forwarding DNS can cause the user to get unexpected subscription requests from them. BTW, the page "https://www.spamtips.org/p/about-spamtipsorg.html - Configuration tips and tricks to maximize the effectiveness of SpamAssassin", which is linked to from the 'Docs' page seems to have vanished though the www.spamtips.org website is up and running. > Also: init.pre v330.pre and maybe v340.pre > > Well those pre files are pretty specific for new features in those > versions. > Fair point - I only included them because they load what look to be relevant plugins for this discussion. However, a note there may well propagate to future SA versions because typical developer version forking. Anyway, I hope these comments are useful. Martin
Re: Stop this before it goes any further (was Re: IMPORTANT NOTICE FOR PEOPLE RUNNING TRUNK re: [Bug 7826] Improve language around whitelist/blacklist and master/slave)
On 14 Jul 2020, at 12:59, Kurt Fitzner wrote: > This is truly unfortunate. Thanks for changing the topic to evade filters killing this idiotic thread. How supremely selfish and self-centered of you.
Re: spamhaus enabled by default
On 14/07/20 19:33, Charles Sprickman wrote: Since the consensus is that this is kind of a “turn it loose out of the box” situation, I think a nice compromise would be huge commented chunks around settings that would disable any commercial services that will start sending nastygrams if you are outside of their (sometimes complex and kind of opaque “free” use case). I do so wish some of those folks would take spamtraps in trade. We see spam from sources even the most expensive lists don’t see for at least 15-20 minutes - valuable data, IMHO. :) Well, we do have a "data sharing" program and are open to discussion of trading services for spamtraps/live traffic. We are especially interested in non US email traffic. If you or anyone else think that they have valuable data to share, please contact me offlist with details and I'll escalate to the relevant people -- Best regards, Riccardo Alfieri Spamhaus Technology https://www.spamhaustech.com/
Re: Negative lookbehind in URIs?
Bill, Shane... we do that with a plugin becasue exceptions must be considered... for example to avoid false positives with rewrited URLs (used by some companies) -Pedro.
Re: Negative lookbehind in URIs?
Nice Loren nowadays with uri_detail this is easily solved with something like uri_detail HTTPS_HTTP_MISMATCH text =~ /^https:\/\//i cleaned =~ /^http:\/\//iscore HTTPS_HTTP_MISMATCH 0.5describe HTTPS_HTTP_MISMATCH URL claims to use SSL but it does not -Pedro >On Wednesday, July 15, 2020, 02:20:34 AM GMT+2, Loren Wilton wrote: > I'm looking to detect a mismatch between the domain in the href > property of a URI and a domain in the anchor text itself. >Not using > lookbehind, but I long ago wrote these two rules to look for similar > situations. Either could be modified fairly easily to do what you want. >Note: these are probably around 10 years old, written before there were URI >rules (if I remember correctly) so there may be more efficient ways to do >these these days. Loren >#check for attempting to phish >rawbody __LW_PHISH_2 >m']+>https://[^\d]'is >full __LW_PHISH_2a >m']+>https://[^\d]'is >meta LW_PHISH_2 __LW_PHISH_2 || __LW_PHISH_2a >score LW_PHISH_2 50 >describe LW_PHISH_2 numeric href with https description >#score __LW_PHISH_2 1 >#score __LW_PHISH_2a 1 >rawbody __LW_PHISH_3 /]+>https:/is >full __LW_PHISH_3a /]+>https:/is >meta LW_PHISH_3 __LW_PHISH_3 || __LW_PHISH_3a >score LW_PHISH_3 50 >describe LW_PHISH_3 secure description with insecure link >#score __LW_PHISH_3 10 >#score __LW_PHISH_3a 1
Re: update fail
Am Dienstag, den 14.07.2020, 16:43 +0200 schrieb Benny Pedersen: > A. Schulze skrev den 2020-07-14 13:19: > > > I tried to place "meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)" > > in > > $LOCAL_RULES_DIR/local.cf > > But that failed, too. > > sorry then, my rule ensure that USER_IN_ALLOWLIST_TO exists if > USER_IN_WHITELIST_TO exists aswell > > if none of them exists you still have problems where rules depend on > one > of them > > i use sa 3.4.4 where the problem is none existsing with sa-update > > > I had to place the line in $LOCAL_RULES_DIR/local.pre. To me it > > looks > > like sa-update read only files named $LOCAL_RULES_DIR/*.pre > > want to provide sa-update -D on this ? > > if you miss plugins, it could fail on lint Problem now "USER_IN_WELCOMELIST_TO" with spamassassin 3.4.2- 0ubuntu0.16.04.4 on Ubuntu 16.04 LTS: --- /etc/cron.hourly/spamassassin: config: warning: description exists for non-existent rule USER_IN_WELCOMELIST_TO channel: lint check of update failed, channel failed sa-update failed for unknown reasons --- So all Ubuntu 16.04 LTS and my be older Debian installations are affected. Ciao!
Re: Negative lookbehind in URIs?
Dear Shane, Have you had a look at the uri_detail plugin? You should find interesting info there: perldoc Mail::SpamAssassin::Plugin::URIDetail I guess you should be able to do what you want with this plugin. But I rarely use it, so I can't help you further. In order to catch those mismatch that you mention, I rather use the phish sigs from ClamAV, which is very convenient to use. https://www.clamav.net/documents/phishsigs Lastly, as Bill Cole mentioned, you will have a lot of false positives. You should curate a list of commonly abused URI and only try to catch those. There are too many ESP rewriting links (for tracking purposes)... There are even banks using those ESP... Best, Laurent On 15.07.20 00:02, Shane Williams wrote: > > I'm looking to detect a mismatch between the domain in the href > property of a URI and a domain in the anchor text itself. It seems > like this is the right place for a negative lookbehind, and I don't > mind writing my own rule, but I can't help thinking that this has been > solved already. Searching the list for lookbehind comes up with a > couple of instances of people getting errors (about a variable length > lookbehind), but I'm not finding anything like what I'm looking for. > > Does anyone have a sample rule for this, or other suggestions on how > to detect this is in SA (maybe a plugin)? > > -- > Public key #7BBC68D9 at| Shane Williams > http://pgp.mit.edu/| System Admin - UT CompSci > =--+--- > All syllogisms contain three lines | sha...@shanew.net > Therefore this is not a syllogism | www.ischool.utexas.edu/~shanew >
Re: spamhaus enabled by default
On Tue, 2020-07-14 at 12:53 -0400, Kevin A. McGrail wrote: I agree with you about the idea of turning off everything and just delivering 100% commented configuration files.. I believe SA is a framework that must have walls & paint added to make it a house. Others want it ready to go as a pre-fab house aka a drop-in spam filter. As a project, the majority supports the drop-in model so I support the will of the PMC. The DNSBlocklist inclusion policy from 2011 has served us well with a lot of users and very few complaints. But if you think of edits it might need, we can always improve it. DNS Blocklists and the free for some model really help the drop in spam filter be effective. On 14.07.20 20:46, Martin Gregorie wrote: Maybe all that's needed is to better emphasize the point that that free use of RBLs, whose use by SA is configured on by default, require the user to have their own non-forwarding DNS installed and explain why. maybe a dns_query_restriction directive should be mentioned, maybe it should be pre-configured by default, but commented with explanation. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Atheism is a non-prophet organization.
