RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 940419 [details]
spamassassin-3.3.2-sa-update_systemd.patch

Description of problem:
Using amavisd-new (from Fedora EPEL 7) together with SpamAssassin (from RHEL 7)
leads to the result that /usr/share/spamassassin/sa-update.cron never performs
the condrestart of amavisd-new (or spampd) even if the services are up/running.
This is because the script still looks for initscript files rather checking the
systemd service files or the status. Having no condrestart (or reload; depends
on the kind of service itself) leads usually to no refresh of possible updates
of the SpamAssassin channel for the given service/consumer (such as amavisd).

Version-Release number of selected component (if applicable):
spamassassin-3.3.2-18.el7.x86_64
amavisd-new-2.9.1-5.el7.noarch

How reproducible:
Everytime, see above.

Actual results:
/usr/share/spamassassin/sa-update.cron is not ready for systemd (related to 
amavisd-new, spampd).

Expected results:
Systemd-ready /usr/share/spamassassin/sa-update.cron script.

Cross-filed case #01200307 on the Red Hat customer portal.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-0545.html