Created attachment 1010505 [details] proposed patch +++ This bug was initially created as a clone of Bug #1208362 +++ Description of problem: since last spamassassin update sa-learn claim about Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm Version-Release number of selected component (if applicable): spamassassin-3.4.0-1.el7.x86_64 How reproducible: on each sa-learn run in case of Razor2 is activated Actual results: Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 668. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 671. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 674. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 677. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 680. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 683. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 686. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 689. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 692. Use of uninitialized value $type in numeric eq (==) at /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Conf/Parser.pm line 695. Expected results: No such messages Additional info: Issue is already known somehow: http://www.fws.net/blog/template_permalink.asp?id=203 Workaround would be fixing the typo in /usr/local/share/perl/5.10.1/Mail/SpamAssassin/Plugin/Razor2.pm : On line 118, change: type => $Mail::SpamAssassin::Conf::CONF_TYPE_DURATIION, to: type => $Mail::SpamAssassin::Conf::CONF_TYPE_DURATION, --- Additional comment from Jakub Jelen on 2015-04-03 09:04:35 CEST --- Thank you for reporting. You are right. But unfortunately, spamassassin is not on ACL for RHEL-7.2 so I can't guarantee that it will be fixed in next release. If it is significant issue for you, I recommend to raise a ticket through your regular Red Hat support channel to receive proper attention. Attached patch for current spamassassin version.
spamassassin-3.4.0-13.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-13.fc22
spamassassin-3.4.0-13.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/spamassassin-3.4.0-13.fc21
Package spamassassin-3.4.0-13.fc22: * should fix your issue, * was pushed to the Fedora 22 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing spamassassin-3.4.0-13.fc22' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2015-5518/spamassassin-3.4.0-13.fc22 then log in and leave karma (feedback).
spamassassin-3.4.0-13.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.