Red Hat Bugzilla – Bug 1022927
Please enhance /usr/share/spamassassin/sa-update.cron with RHEL 6 script
Last modified: 2014-07-15 09:06:30 EDT
Description of problem:
Package spamassassin-3.3.1-2.el5 from 2011 contains long and extended script
/usr/share/spamassassin/sa-update.cron, which takes care about SpamAssassin
channels, imports GPG keys as needed and finally also restarts services such
as SpamAssassin (spamd), Amavisd-New and MIMEDefang if needed.
Compared to that, package spamassassin-3.3.1-4.el5 is a simple stupid script
that only does sa-update(1) (after sleeping for random time) and restarts a
possible SpamAssassin server process (spamd) - no handling of Amavisd-New or
Version-Release number of selected component (if applicable):
Everytime, just update from older SpamAssassin to latest in RHEL 5.
SpamAssassin 3.3.1-4.el5 cripples /usr/share/spamassassin/sa-update.cron.
Non-crippled /usr/share/spamassassin/sa-update.cron like 3.3.1-2.el5 again.
As even Fedora Rawhide ships the more extended script (see Fedora GIT), I do
not see any reason to deal with that (unintended?) new change.
Cross-filed ticket 00970061 in the Red Hat customer portal.
Sorry, I have to correct myself here: I mixed up RHEL 5 and 6. Actually even
spamassassin-3.3.1-2.el5 ships that small and crippled version of the cronjob.
Instead I would like to raise the request to ship the more enhanced version of
/usr/share/spamassassin/sa-update.cron of RHEL 6 also in RHEL 5 hereby.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in the last planned RHEL5 minor release. This Bugzilla will soon be CLOSED as WONTFIX. To request that Red Hat re-consider this request, please re-open the bugzilla via appropriate support channels and provide additional business and/or technical details about its importance to you.
Thank you for submitting this request for inclusion in Red Hat Enterprise Linux 5. We've carefully evaluated the request, but are unable to include it in RHEL5 stream. If the issue is critical for your business, please provide additional business justification through the appropriate support channels (https://access.redhat.com/site/support).