Bug 863140 - inet_protocols is accidentally specified twice in the default /etc/postfix/main.cf
Summary: inet_protocols is accidentally specified twice in the default /etc/postfix/ma...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: postfix
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-04 14:20 UTC by Matt Kinni
Modified: 2013-08-01 20:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-01 20:06:54 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Matt Kinni 2012-10-04 14:20:36 UTC
Description of problem:
This doesn't really cause a problem, but I'm OCD about config files ;)

egrep -n ^inet_protocols /etc/postfix/main.cf 
119:inet_protocols = all
680:inet_protocols = ipv4


Version-Release number of selected component (if applicable):
postfix-2.9.4-3.fc17.x86_64

Expected results:
inet_protocols is only specified once to reduce ambiguity

Comment 1 Dave Habben 2013-03-20 18:27:52 UTC
Postfix will not listen on IPv6 with this duplicate entry that disables IPv6.

Please remove from the bottom of main.cf
 inet_protocols = ipv4

Comment 2 Jaroslav Škarvada 2013-03-21 11:08:57 UTC
Thanks for the report. It seems upstream changed their default config, we need to update our distro specific patch.

Comment 3 Fedora Update System 2013-03-21 14:05:22 UTC
postfix-2.9.6-4.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/postfix-2.9.6-4.fc18

Comment 4 Fedora Update System 2013-03-21 14:42:20 UTC
postfix-2.9.6-2.fc17 has been submitted as an update for Fedora 17.
https://admin.fedoraproject.org/updates/postfix-2.9.6-2.fc17

Comment 5 Fedora Update System 2013-03-22 00:41:52 UTC
Package postfix-2.9.6-2.fc17:
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing postfix-2.9.6-2.fc17'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-4204/postfix-2.9.6-2.fc17
then log in and leave karma (feedback).

Comment 6 Fedora End Of Life 2013-07-04 07:44:09 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 7 Fedora End Of Life 2013-08-01 20:06:58 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


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