SpamAssassin 3.4.2

Erulezz · Sep 21, 2018

tristan said:
Almost feels like these updates aren’t tested before release on CB at all by the DirectAdmin. Maybe they should hire an email specialist again? Jeff’s absense really begins to show.

While I also understand your frustration, isn't that a bit harsh? It was under investigation as described in post #9 & #20

You can almost expect these annoyances with a new update after 3.5 years with the infrastructure changes and stopping with SHA-1 signatures. I'm just glad that there is news from the SA project (also news on v4.0.0) as I thought the project was dead.

jca · Sep 26, 2018

DirectAdmin Support said:
Hmm.. I think it's the sought.rules.yerp.org channel.
I've not yet been able to find any info on if that channel SHOULD be working, in which case, they'd need to setup the mirror and A records.
Or if it no longer supported for 3.4.2.

John,

Seems SoughtRules is no longer supported:

https://wiki.apache.org/spamassassin/SoughtRules

DirectAdmin Support · Sep 26, 2018

jca said:
John,

Seems SoughtRules is no longer supported:

https://wiki.apache.org/spamassassin/SoughtRules

Great, thanks for the information

matkra · Sep 27, 2018

https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7629

matkra said:

CentOS 6.10

Code:

spamassassin -V

SpamAssassin version 3.4.2
  running on Perl version 5.10.1

working fine (?) after upgrade but in /var/log/maillog during message scanning:

Code:

Sep 20 11:50:38 spamd[13369]: Use of uninitialized value $( in numeric ne (!=) at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1510, <GEN8> line 23.
Sep 20 11:50:38 spamd[13369]: Use of uninitialized value $( in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1513, <GEN8> line 23.
Sep 20 11:50:38 spamd[13369]: util: setuid: ruid=507 euid=507 rgid=510 egid=510 
Sep 20 11:50:38 spamd[13370]: Use of uninitialized value $( in numeric ne (!=) at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1510.
Sep 20 11:50:38 spamd[13370]: Use of uninitialized value $( in concatenation (.) or string at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 1513.

LawsHosting · Sep 27, 2018

Is this currently safe to update?

Tristan · Sep 27, 2018

Peter Laws said:
Is this currently safe to update?

Yes, and in every case it's safer than not updating.

Remco00 · Sep 28, 2018

After updating spamd won't start:

Code:

# systemctl status spamassassin.service -l
● spamassassin.service - Spamassassin daemon
   Loaded: loaded (/etc/systemd/system/spamassassin.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Fri 2018-09-28 15:33:08 CEST; 18s ago
  Process: 30784 ExecStart=/usr/bin/spamd --pidfile /var/run/spamd.pid -d -c -m 15 --ipv4 (code=exited, status=255)
 Main PID: 2737 (code=exited, status=0/SUCCESS)

Sep 28 15:33:08 s08.server.nl systemd[1]: Failed to start Spamassassin daemon.
Sep 28 15:33:08 s08.server.nl systemd[1]: Unit spamassassin.service entered failed state.
Sep 28 15:33:08 s08.server.nl systemd[1]: spamassassin.service failed.
Sep 28 15:33:08 s08.server.nl systemd[1]: spamassassin.service holdoff time over, scheduling restart.
Sep 28 15:33:08 s08.server.nl systemd[1]: start request repeated too quickly for spamassassin.service
Sep 28 15:33:08 s08.server.nl systemd[1]: Failed to start Spamassassin daemon.
Sep 28 15:33:08 s08.server.nl systemd[1]: Unit spamassassin.service entered failed state.
Sep 28 15:33:08 s08.server.nl systemd[1]: spamassassin.service failed.

And mainlog shows:

Code:

2018-09-28 15:34:33 1g5suf-0008CA-AD spam acl condition: spamd: failed to connect to any address for 127.0.0.1: Connection refused
2018-09-28 15:34:33 1g5suf-0008CA-AD spam acl condition: all spamd servers failed

Suggestions how to solve this?

LawsHosting · Sep 28, 2018

When I attempt to restart spamd via DA, it looks for the non-existent init.d script?!

DirectAdmin Support · Sep 28, 2018

For older init.d systems, spamd is booted from the /etc/init.d/exim script.

As for spamd not starting, always check:
/var/log/maillog
/var/log/messages

might be in need of modules update from cpan, I'm not sure, would depend on the error message.

John

Remco00 · Sep 29, 2018

Maillog shows:

Code:

Sep 29 14:55:01 s08 spamd[12613]: config: no rules were found! Do you need to run 'sa-update'?

Looks like SpamAssassin won't start because it cannot upload the rules with sa-update because it ends with:

Code:

Sep 29 15:01:53.367 [15016] dbg: channel: channel pre file /var/lib/spamassassin/3.004002/updates_spamassassin_org.pre
can't resolve "85.17.150.123,85.17.96.69,62.212.64.122" to address at /usr/lib64/perl5/vendor_perl/Net/DNS/Resolver/Base.pm line 785.

Server is CentOS 7. Any clues?

Erulezz · Sep 29, 2018

Try to remove the /var/lib/spamassassin/3.004002 folder (backup folder first) and run sa-update -D again so the updater starts fresh.

By the way; I noticed after the upgrade the old /var/lib/spamassassin/3.004001 didn't get deleted. Isn't that something for CB to do after the update?

ayeweb · Sep 29, 2018

just update and now everything is ok.

Remco00 · Sep 29, 2018

Erulezz said:
Try to remove the /var/lib/spamassassin/3.004002 folder (backup folder first) and run sa-update -D again so the updater starts fresh.

By the way; I noticed after the upgrade the old /var/lib/spamassassin/3.004001 didn't get deleted. Isn't that something for CB to do after the update?

Thx Erulezz, I removed the folder and rerun sa-update -D but still same resolve error. Any other ideas?

Richard G · Sep 30, 2018

can't resolve "85.17.150.123,85.17.96.69,62.212.64.122"

Did you already try this completely?
http://forum.directadmin.com/showthread.php?t=56895&p=291118#post291118

Remco00 · Sep 30, 2018

Richard G said:
Did you already try this completely?
http://forum.directadmin.com/showthread.php?t=56895&p=291118#post291118

The file /etc/cron.daily/sa-update was allready updated with the correct line for the channel. Still keep getting the same error after running sa-update -D:

Code:

Sep 30 18:30:58.674 [60338] dbg: channel: channel pre file /var/lib/spamassassin/3.004002/updates_spamassassin_org.pre
can't resolve "85.17.150.123,85.17.96.69,62.212.64.122" to address at /usr/lib64/perl5/vendor_perl/Net/DNS/Resolver/Base.pm line 785.
[root@s08 ~]# spamassassin -V
SpamAssassin version 3.4.2
  running on Perl version 5.16.3

Richard G · Sep 30, 2018

Which version of Net:

NS are you using? And is this perl-Net-DNS or is it Net:

NS from Cpan?
Also, you don't use 8.8.8.8 or another google nameserver in your /etc/resolv.conf?

Tristan · Oct 1, 2018

tristan said:
Maybe we should remove the --nogpg part in the cron file as well? This seems to be working ok:

Code:

/usr/bin/sa-update -D --channel updates.spamassassin.org

Any news on whether we need that --nogpg? Seems more secure to leave that out.

Remco00 · Oct 1, 2018

Richard G said:
Which version of Net:NS are you using? And is this perl-Net-DNS or is it Net:NS from Cpan?
Also, you don't use 8.8.8.8 or another google nameserver in your /etc/resolv.conf?

Thx Richard, you pointed me in the right direction. Google nameservers were not present in resolv.conf but somehow networkmanager automaticly changed the syntax of the lines in resolv.conf like this:

Code:

nameserver 85.17.150.123,85.17.96.69,62.212.64.122

Changing it into:

Code:

nameserver 85.17.150.123
nameserver 85.17.96.69
nameserver 62.212.64.122

resolved the issue and now SA is working fine again.

Richard G · Oct 1, 2018

Glad I could be of some kind of help to you.

I've got a problem too. Since installing the new spamassassin I'm encountering these kind of errors in /var/log/maillog:

Code:

[b]Sep 30 07:12:45 server18 spamd[16416]: rules: failed to run DKIM_ADSP_CUSTOM_HIGH test, skipping:
Sep 30 07:12:45 server18 spamd[16416]:  (Not a HASH reference at /usr/share/perl5/Mail/SpamAssassin/Plugin/FromNameSpoof.pm line 319.

Sometimes extended with a GEN code like this:

Code:

Sep 30 07:23:01 server18 spamd[16416]: rules: failed to run DKIM_ADSP_CUSTOM_HIGH test, skipping:
Sep 30 07:23:01 server18 spamd[16416]:  (Not a HASH reference at /usr/share/perl5/Mail/SpamAssassin/Plugin/FromNameSpoof.pm line 319
, <GEN46> line 1295.

Line 319 contains this:

Code:

    return 0 if ($self->{main}{conf}{fns_ignore_dkim}{$addr});

It's not on every mail, but quite regularly.
Any clues on what might be causing this or even better, how to fix this?

ssgill · Oct 2, 2018

Hello all, i tried to upgrade spamassassin and instead of upgrading it downgraded my version.
Before updating

SpamAssassin version 3.4.1
running on Perl version 5.16.3

Using custombuild 2 tried from commandline and Custombuild from admin webpage.

After update

SpamAssassin version 3.4.0
running on Perl version 5.16.3

In versions text it have 3.4.2 and binary downloaded is 3.4.2

Initial log when build starts

Installing spamassassin 3.4.2...
Found /usr/local/directadmin/custombuild/Mail-SpamAssassin-3.4.2.tar.gz
Extracting ...
Done.
Configuring SpamAssassin 3.4.2...
NOTE: settings for "make test" are now controlled using "t/config.dist".
See that file if you wish to customize what tests are run, and how.

checking module dependencies and their versions...
checking binary dependencies and their versions...

***************************************************************************
NOTE: the optional fetch binary is not installed.

Sa-update will use curl, wget or fetch to download updates.
Because perl module LWP does not support IPv6, sa-update as of
3.4.0 will use these standard programs to download rule updates
leaving LWP as a fallback if none of the programs are found.

*IMPORTANT NOTE*: You only need one of these programs
It's only a concern if you are warned about all 3
i.e. (curl, wget & fetch) missing

dependency check complete...

optional binary missing or nonfunctional: fetch

warning: some functionality may not be available,
please read the above report before continuing!

And build finnish with

chmod 755 /usr/share/spamassassin
Enabling spamassassin in systemd...
Installing sa-update cronjob...
Downloading sa-update.sh...
--2018-10-02 15:31:46-- http://files9.directadmin.com/services/custombuild/sa-update.sh
Resolving files9.directadmin.com (files9.directadmin.com)... 69.162.69.58
Connecting to files9.directadmin.com (files9.directadmin.com)|69.162.69.58|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1334 (1.3K) [text/plain]
Saving to: '/usr/local/directadmin/custombuild/sa-update.sh'

100%[===================================================================================================================================================================================================>] 1,334 --.-K/s in 0s

2018-10-02 15:31:46 (177 MB/s) - '/usr/local/directadmin/custombuild/sa-update.sh' saved [1334/1334]

Enabling new SA plugins
Running sa-update.
Starting SpamAssassin.
--2018-10-02 15:31:49-- http://files9.directadmin.com/services/exim.spamassassin.conf
Resolving files9.directadmin.com (files9.directadmin.com)... 69.162.69.58
Connecting to files9.directadmin.com (files9.directadmin.com)|69.162.69.58|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 534 [text/plain]
Saving to: '/etc/exim.spamassassin.conf'

100%[===================================================================================================================================================================================================>] 534 --.-K/s in 0s

2018-10-02 15:31:49 (136 MB/s) - '/etc/exim.spamassassin.conf' saved [534/534]

Restarting exim.

Any one whats going on .

Thanks

SpamAssassin 3.4.2

Verified User

Verified User

Administrator

Verified User

Verified User

Verified User

Verified User

Verified User

Administrator

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User

Verified User