Bug 766090 - Postfix is ancient
Summary: Postfix is ancient
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: postfix
Version: 6.4
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-10 03:02 UTC by Philip Prindeville
Modified: 2012-02-08 17:24 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-08 17:24:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Philip Prindeville 2011-12-10 03:02:15 UTC 
Description of problem:

The current release of Postfix is 2.8.8.  Fedora is shipping 2.8.7. RHEL needs to ship something with more recent security fixes in place.


Version-Release number of selected component (if applicable):

2.6.6-2

How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Philip Prindeville 2011-12-10 03:03:35 UTC 
I've built rawhide (master) for EL6 and it builds fine.
Comment 3 Jaroslav Škarvada 2011-12-11 12:30:07 UTC 
(In reply to comment #0)
Thanks for the report.

> The current release of Postfix is 2.8.8.
>
Today (2011-12-11) I cannot see official announcement of 2.8.8, nor find the official release on upstream FTP server.

> to ship something with more recent security fixes in place.
> 
Which security fixes? AFAIK all CVEs got backported to RHEL, namely 
CVE-2011-0411, CVE-2011-1720.
Comment 4 Philip Prindeville 2011-12-11 19:21:03 UTC 
Sorry, I think the announcement of 2.8.8 was premature.

2.8.7 has XCLIENT, XFORWARD, and DNSBL support for defeating spammers that aren't in the 2.6 and 2.7 legacy and stable releases.
Comment 7 RHEL Program Management 2012-02-08 17:24:59 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.