SpamAssassin 3.4.5

Erulezz

Verified User
Joined
Sep 14, 2015
Messages
956
Location
🇳🇱
2021-03-24: Apache SpamAssassin 3.4.5 has been released! Apache SpamAssassin 3.4.5 is primarily a security release. In this release, there are bug fixes for one CVE:

  • CVE-2020-1946 for Malicious rule configuration (.cf) files can be configured to run system commands.
*** On March 1, 2020, we stopped 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. ***
*** There will be no more development or bug fixes in the 3.4 branch unless a new security issue requires a 3.4.6 release. All future releases and bug fixes will be in the 4.0 series. ***
 
Also 4.0 will be released soon. It's already in the SVN and some linux distros already have packages for it.
 
During update on FreeBSD I got the following:

Code:
server socket setup failed, retry 1: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 2: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 3: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 4: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 5: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 6: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 7: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 8: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 9: spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783: Address already in use

Despite that it updated successfully and works fine.
 
I got a couple of dozen warnings on Debian 10 using the CustomBuild plugin, but it still updated successfully. This doesn't happen with updates for other packages.

Code:
Warning: fread() expects parameter 1 to be resource, boolean given in /usr/local/directadmin/plugins/custombuild/admin/build_software_command.raw on line 27

Warning: fclose() expects parameter 1 to be resource, boolean given in /usr/local/directadmin/plugins/custombuild/admin/build_software_command.raw on line 48
 
Back
Top