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.
Bug 1479087 - [RFE] Please upgrade SpamAssassin package to latest upstream version (3.4.1)
Summary: [RFE] Please upgrade SpamAssassin package to latest upstream version (3.4.1)
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: spamassassin
Version: 7.4
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: rc
: ---
Assignee: Ondřej Lysoněk
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks: 1477664 1534569 1630905
TreeView+ depends on / blocked
 
Reported: 2017-08-07 22:41 UTC by Candace Sheremeta
Modified: 2022-03-13 14:22 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Clone Of:
: 1664283 (view as bug list)
Environment:
Last Closed: 2019-01-08 10:26:39 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Candace Sheremeta 2017-08-07 22:41:32 UTC
Proposed title of this feature request

Please upgrade version of SpamAssassin shipped with RHEL 7 to latest version from upstream (SpamAssassin 3.4.1)

What is the nature and description of the request?

Customer would like us to update the SpamAssassin package shipped with RHEL 7 to version 3.4.1

Why does the customer need this? (List the business requirements here)

Will include justification in private comment

Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL5, RHEL6)?

No - they have simply requested this be implemented ASAP

Is the sales team involved in this request and do they have any additional input?

No

List any affected packages or components.

SpamAssassin

Comment 4 Simon Matter 2018-09-18 13:05:37 UTC
Makes sense to change the requested version to 3.4.2 now.

Comment 5 Kenneth Porter 2018-10-13 03:59:14 UTC
Fedora 29 includes a SRPM:

https://dl.fedoraproject.org/pub/fedora/linux/development/29/Everything/source/tree/Packages/s/spamassassin-3.4.2-2.fc29.src.rpm

I've rebuilt and installed this successfully on CentOS 7.5. The one hitch is that the systemd unit file for 3.4.0 assumes Type=forking and -d is passed to the spamd executable. The Fedora 29 RPM for 3.4.2 assumes Type=simple so the daemonize option in /etc/sysconfig/spamassassin must be removed. I suggest changing the spec file to remove the (replace) from /etc/sysconfig/spamassassin.

Comment 12 Red Hat Bugzilla Rules Engine 2019-01-08 10:26:39 UTC
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.


Note You need to log in before you can comment on or make changes to this bug.