spamassassin 3.1.1 is out. The changes in this release are as follows: Validation of configuration option errors was improved. Support for the new Mail::DomainKeys API was added. Large modifications were made to sa-update to better support rule updates. CRLF line endings are detected and used if the input message uses them. The RPM spec file for x86_64 platforms was fixed. Release focus: 7 - Major bugfixes
btw copying the 3.1.0-r2 ebuild works fine. here's some changes: 3.1.1 includes a large number of bug fixes and documentation updates. Here is an abbreviated changelog (since 3.1.0) for major updates (see the Changes file for a complete list): - better validate a number of different configuration options - support new Mail::DomainKeys API, which changed incompatibly between 0.18 and 0.80 without warning - more properly handle new Received header formats - bug 4788: backport sa-update from 3.2 along with the local_state_dir code, etc. - bug 4760: strictly validate trusted/internal network configurations - bug 4696: consolidated fixes for timeout bugs - bug 3710: add timeout to connect so spamc -t works - bug 4363: if a message uses CRLF for line endings, use it for header rewrites as well - bug 4748: add ExpressionEngine and Google redirector patterns - bug 3815: add _RELAYCOUNTRY_ tag so that the RelayCountry plugin can put in the list of countries relayed through - bug 4090: x86_64 platforms (linux specifically) have an issue compiling libspamc.so causing RPM build failures - bug 4791: fix issue where perl would throw a UTF-8 warning for certain messages - bugs 4606, 4609: Adjust MIME parsing limits - bug 4780: fix IP_ADDRESS & LOCALHOST regexes to correctly parse IPv6 addresses - bug 4728: DUL rules should only use the last external IP, not all but the first of the external IPs - bug 4700: certain privileged configuration settings can inject code, due to a bad fix for bug 3846. Back that out - bug 4655: have redhat-rc-script create .pid file for spamassassin service to avoid killing the wrong processes and leaving spamd running
I'll need to confirm all of the deps (don't want the mess I made last time again :)
Created attachment 81980 [details] New SA ebuild Testable ebuild for 3.1.1, including everything under a USE flag of one sort or another.
maybe create /var/lib/spamassassin also, I havent figured out how this sa-update thing works
played with sa-update more. seems like we need only create /var/lib/spamassassin directory in ebuild and then user adds sa-update into cron job spamassassin automaticaly loads updated preferences from /var directory
I upgraded my test server (which was already running SpamAssassin 3.1.0) with this new ebuild. It seems to work fine after testing it with spamd and also with Postfix + amavisd-new. Thank you and keep up the good work! My USE flags for SpamAssassin at this servee: --- [ebuild R ] mail-filter/spamassassin-3.1.1 +berkdb +dcc -doc +extramodules +ipv6 +ldap -minimal +mysql +postgres +pyzor -qmail +razor -spf -sqlite +ssl +tools 0 kB [1] ---
Looks like this version wants another perl module: Can't locate Crypt/OpenSSL/Bignum.pm in @INC (@INC contains: ../lib /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux /usr/lib64/perl5/vendor_perl/5.8.8 /etc/perl /usr/lib64/perl5/vendor_perl /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux /usr/lib64/perl5/site_perl/5.8.8 /usr/lib64/perl5/site_perl /usr/lib64/perl5/5.8.8/x86_64-linux /usr/lib64/perl5/5.8.8 /usr/local/lib/site_perl .) at /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/Crypt/OpenSSL/RSA.pm line 17. Installing dev-perl/Crypt-OpenSSL-Bignum-0.03 has taken care of that, however dev-perl/Crypt-OpenSSL-Bignum-0.03 is not stable for anything nor is it ~amd64.
(In reply to comment #7) > Looks like this version wants another perl module: > > Can't locate Crypt/OpenSSL/Bignum.pm in @INC (@INC contains: ../lib ... > /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux/Crypt/OpenSSL/RSA.pm line 17. > actually it looks like you were using a pre-r1 of openssl-rsa (in which we realized and added the dep for bignum support).
(In reply to comment #8) > actually it looks like you were using a pre-r1 of openssl-rsa (in which we > realized and added the dep for bignum support). bug 123488 was the bug that amd64 hasn't responded on yet fwiw
done. bug 125899 opened as a result (bulk keywording requests for all of the archs)
found out that sa-update need app-crypt/gnupg
