1 (edited by cvcvelo 2022-02-19 06:18:02)

Topic: spamassassin.updates.org not resolving

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 1.5.1
- Deployed with iRedMail Easy or the downloadable installer? downloadable
- Linux/BSD distribution name and version: Debian 11.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MySQL (MariaDB)
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? yes
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

Spamassassin's daily cron job (in /etc/cron.daily/spamassassin) failed like this:

/etc/cron.daily/spamassassin:
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
sa-update failed for unknown reasons

And dig fails to resolve an A record for 'updates.spamassassin.org'.

I found this thread on the spamassassin user's mailing list suggesting this is related to a permissions issue. On this system, /var/lib/spamassassin is owned by debian-spamd:debian-spamd.

I can su to that user and try running sa-update but it fails like this:

gpg: WARNING: unsafe ownership on homedir '/etc/spamassassin/sa-update-keys'
gpg: failed to create temporary file '/etc/spamassassin/sa-update-keys/.#lk0x00005606b5a0db30.mail9.1506231': Permission denied
gpg: keyblock resource '/etc/spamassassin/sa-update-keys/pubring.kbx': Permission denied
gpg: no writable keyring found: Not found
gpg: error reading '/usr/share/spamassassin/sa-update-pubkey.txt': General error
gpg: import from '/usr/share/spamassassin/sa-update-pubkey.txt' failed: General error
gpg: process '/usr/bin/gpg --homedir='/etc/spamassassin/sa-update-keys' --batch --no-tty --status-fd=1 -q --logger-fd=1 --import' finished: exit 2
gpg: WARNING: unsafe ownership on homedir '/etc/spamassassin/sa-update-keys'
gpg: process '/usr/bin/gpg' finished: exit 2
error: GPG validation failed!
The update downloaded successfully, but it was not signed with a trusted GPG
key.  Instead, it was signed with the following keys:

    24F434CE

Perhaps you need to import the channel's GPG key?  For example:

    wget https://spamassassin.apache.org/updates/GPG.KEY
    sa-update --import GPG.KEY

channel 'updates.spamassassin.org': GPG validation failed, channel failed

And running sa-update or the /etc/cron.daily/spamassassin script as root fails with the first code block above.

This error began today. I haven't changed any configuration parameter on this system in some time.

Thanks in advance for clues on getting the spamassassin cron job working again.

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 (edited by cvcvelo 2022-02-19 06:18:21)

Re: spamassassin.updates.org not resolving

cvcvelo wrote:

Thanks in advance for clues on getting the spamassassin cron job working again.

There is also this bug report, now resolved, but I'm unclear on what, if anything, to change on an iRedMail system.

3

Re: spamassassin.updates.org not resolving

confim, having the same "issue" on my side sad

4

Re: spamassassin.updates.org not resolving

Same issue. Been happening over the last 2 days. Maybe coincided with an update I did to my server's OS mid week.

5

Re: spamassassin.updates.org not resolving

Just need to wait at this point for mirrors to replicate the latest version, as  1898171 RULES (not anything installed on your machine) have experimental features debian's perl don't like.

New rules are in revision 1898196 of SA RULES, but we're basically waiting on DNS txt record to update to point to that...

```
dig +short txt 4.4.3.updates.spamassassin.org
3.3.3.updates.spamassassin.org.
"1898171"
```

^^^ still resolving bad version

6

Re: spamassassin.updates.org not resolving

I simply also note bug confimation on GoogleFroups of "Debian" ("linux.debian.bugs.dist" group)  https://groups.google.com/g/linux.debia … qf31WJcIcg