[SOLVED] Spamassassin failing to update

[Peter Nielsen]

Hi

At 5:17 this morning I started to get the following error when spamassassin tries to update. No changes have been made to cron job or any other configs.

Update available for channel updates.spamassassin.org: 1898122 -> 1898145
http: (curl) GET http://sa-update.dnswl.org/1898145.tar.gz, success
http: (curl) GET http://sa-update.dnswl.org/1898145.tar.gz.sha512, success
http: (curl) GET http://sa-update.dnswl.org/1898145.tar.gz.asc, success
config: invalid regexp for __URI_TRY_3LD 'm,^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b,i': Variable length lookbehind is experimental in regex; marked by <-- HERE in m/(?i)^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b <-- HERE /

channel 'updates.spamassassin.org': lint check of update failed, channel failed
Update failed, exiting with code 4
Importing gpg key from /etc/mail/spamassassin/channel.d/KAM_channel.conf
Updating kam.sa-channels.mcgrail.com
Update finished, no fresh updates were available
TASK OK



Br
/Peter

 

[Stoiko Ivanov]

seems like an issue with the last rule-update:
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7956

should be resolved soon - in the mean-time I'd expect the current rules to perform fine

I hope this helps!

 

[zolthar]

I am getting similar errors - would they be the related?

/etc/cron.hourly/sa-update:
config: invalid regexp for __URI_TRY_3LD 'm,^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b,i': Variable length lookbehind is experimental in regex; marked by <-- HERE in m/(?i)^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b <-- HERE /

channel 'updates.spamassassin.org': lint check of update failed, channel failed
config: invalid regexp for __URI_TRY_3LD 'm,^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b,i': Variable length lookbehind is experimental in regex; marked by <-- HERE in m/(?i)^https?://(?:try(?!r\.codeschool)|start|get(?!\.adobe)|save|check(?!out)|act|compare|join|learn(?!ing)|request|visit(?!or|\.vermont)|my(?!sub|turbotax|news\.apple|a\.godaddy|account|support|build|blob)\w)[^.]*\.[^/]+\.(?<!list-manage\.)(?:com|net)\b <-- HERE /

channel 'updates.spamassassin.org': lint check of update failed, channel failed

This started for me yesterday at 3pm AEST - I ignored them as they usually fix itself after 1-2 hours, however this appears persistent.

Coincidently, mine started occurring after I did some updates:

root@spam:~# tail -3 /var/log/apt/history.log
Commandline: apt-get dist-upgrade
Upgrade: libexpat1:amd64 (2.2.10-2, 2.2.10-2+deb11u1), libwbclient0:amd64 (2:4.13.13+dfsg-1~deb11u2, 2:4.13.13+dfsg-1~deb11u3), libsmbclient:amd64 (2:4.13.13+dfsg-1~deb11u2, 2:4.13.13+dfsg-1~deb11u3), libcryptsetup12:amd64 (2:2.3.5-1, 2:2.3.7-1+deb11u1), smbclient:amd64 (2:4.13.13+dfsg-1~deb11u2, 2:4.13.13+dfsg-1~deb11u3), samba-libs:amd64 (2:4.13.13+dfsg-1~deb11u2, 2:4.13.13+dfsg-1~deb11u3), samba-common:amd64 (2:4.13.13+dfsg-1~deb11u2, 2:4.13.13+dfsg-1~deb11u3)
End-Date: 2022-02-18 17:52:01

 

[olluz]

yes, same here

 

[GarrettB]

It's the remote content of the update that is failing. The failing portion is not currently in the working files. There is a fix in the works so when the error goes away it will mean the update is successful with the fix.

 

[Peter Nielsen]

Problem got solved this morning.
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7956

Thanks for your help Stoiko