Mailing List Archive

Marcus Schopen skrev den 2020-07-11 23:43:
> config: warning: description exists for non-existent rule
> USER_IN_ALLOWLIST_TO

meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)

i have still some bricks of Ritter Sport chocolate :=)

Thanks. Please see https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7838
and this should be resolved. I'm surprised a warning caused a failure
though.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Sat, Jul 11, 2020 at 5:55 PM Benny Pedersen <me@junc.eu> wrote:

> Marcus Schopen skrev den 2020-07-11 23:43:
> > config: warning: description exists for non-existent rule
> > USER_IN_ALLOWLIST_TO
>
> meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)
>
> i have still some bricks of Ritter Sport chocolate :=)
>

Am 11.07.20 um 23:55 schrieb Benny Pedersen:
> Marcus Schopen skrev den 2020-07-11 23:43:
>> config: warning: description exists for non-existent rule
>> USER_IN_ALLOWLIST_TO
>
> meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)

Hello,

My SA hit the same update issue. It was unable to update to 1879805.

I tried to place "meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)" in $LOCAL_RULES_DIR/local.cf
But that failed, too.

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

Andreas

It will get fixed when masscheck pushes out a new ruleset.

On Tue, Jul 14, 2020, 07:20 A. Schulze <sca@andreasschulze.de> wrote:

>
>
> Am 11.07.20 um 23:55 schrieb Benny Pedersen:
> > Marcus Schopen skrev den 2020-07-11 23:43:
> >> config: warning: description exists for non-existent rule
> >> USER_IN_ALLOWLIST_TO
> >
> > meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)
>
> Hello,
>
> My SA hit the same update issue. It was unable to update to 1879805.
>
> I tried to place "meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)" in
> $LOCAL_RULES_DIR/local.cf
> But that failed, too.
>
> 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
>
> Andreas
>

The lint failure was only changed to debug since 3.4.3.

On Sun, Jul 12, 2020 at 04:59:51PM -0400, Kevin A. McGrail wrote:
> Thanks.? Please see?[1]https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7838
> and this should be resolved.? I'm surprised a warning caused a failure though.
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> [2]https://www.linkedin.com/in/kmcgrail?- 703.798.0171
>
>
> On Sat, Jul 11, 2020 at 5:55 PM Benny Pedersen <[4]me@junc.eu> wrote:
>
> Marcus Schopen skrev den 2020-07-11 23:43:
> > config: warning: description exists for non-existent rule
> > USER_IN_ALLOWLIST_TO
>
> meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)
>
> i have still some bricks of Ritter Sport chocolate :=)
>
>
> References:
>
> [1] https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7838
> [2] https://www.linkedin.com/in/kmcgrail
> [4] mailto:me@junc.eu

Ahh yes. So it's an older SpamAssassin install. Good call.

On Tue, Jul 14, 2020, 08:04 Henrik K <hege@hege.li> wrote:

>
> The lint failure was only changed to debug since 3.4.3.
>
> On Sun, Jul 12, 2020 at 04:59:51PM -0400, Kevin A. McGrail wrote:
> > Thanks. Please see [1]
> https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7838
> > and this should be resolved. I'm surprised a warning caused a failure
> though.
> > --
> > Kevin A. McGrail
> > Member, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > [2]https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Sat, Jul 11, 2020 at 5:55 PM Benny Pedersen <[4]me@junc.eu> wrote:
> >
> > Marcus Schopen skrev den 2020-07-11 23:43:
> > > config: warning: description exists for non-existent rule
> > > USER_IN_ALLOWLIST_TO
> >
> > meta USER_IN_ALLOWLIST_TO (USER_IN_WHITELIST_TO)
> >
> > i have still some bricks of Ritter Sport chocolate :=)
> >
> >
> > References:
> >
> > [1] https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7838
> > [2] https://www.linkedin.com/in/kmcgrail
> > [4] mailto:me@junc.eu
>

Kevin A. McGrail skrev den 2020-07-14 13:55:
> It will get fixed when masscheck pushes out a new ruleset.

until this happen all can restore old ruleset from tarballs

please do not make this problem ever again

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

We believe this problem is related to both a problem in the rules as well
as the outdated version of SA by the user. Sa-update on 3.4.3+ will
install on a lint warning.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Jul 14, 2020 at 10:34 AM Benny Pedersen <me@junc.eu> wrote:

> Kevin A. McGrail skrev den 2020-07-14 13:55:
> > It will get fixed when masscheck pushes out a new ruleset.
>
> until this happen all can restore old ruleset from tarballs
>
> please do not make this problem ever again
>

Kevin A. McGrail skrev den 2020-07-14 16:46:
> We believe this problem is related to both a problem in the rules as
> well as the outdated version of SA by the user. Sa-update on 3.4.3+
> will install on a lint warning.

its a clear bug on its own

Yep, agreed. A fix has been committed on the 10th but it's got to go
through masscheck to get published which might take another few days.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Jul 14, 2020 at 11:00 AM Benny Pedersen <me@junc.eu> wrote:

> Kevin A. McGrail skrev den 2020-07-14 16:46:
> > We believe this problem is related to both a problem in the rules as
> > well as the outdated version of SA by the user. Sa-update on 3.4.3+
> > will install on a lint warning.
>
> its a clear bug on its own
>

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!

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
KMcGrail@Apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

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.

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

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

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.

On 15.07.20 12:29, Fr?d?ric Nass wrote:
>From: Fr?d?ric Nass <frederic.nass@univ-lorraine.fr>
>To: kmcgrail@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, uhlar@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.

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
KMcGrail@Apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

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
KMcGrail@Apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

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!

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
KMcGrail@Apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

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 <kmcgrail@apache.org> 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

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