Bug 437024 - main.cf inet_protocols hackery introduces invalid syntax
Summary: main.cf inet_protocols hackery introduces invalid syntax
Alias: None
Product: Fedora
Classification: Fedora
Component: postfix   
(Show other bugs)
Version: rawhide
Hardware: All Linux
Target Milestone: ---
Assignee: Thomas Woerner
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2008-03-11 18:12 UTC by Aaron Richton
Modified: 2008-03-12 12:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-03-12 12:48:22 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Aaron Richton 2008-03-11 18:12:26 UTC
Description of problem:
postfix.spec (2.5.1-1) puts in:

321 inet_protocols = all        (enable IPv4, and IPv6 if supported)

to main.cf during %install. See postconf(5):

Empty lines and whitespace-only lines are ignored, as are lines whose first
non-whitespace character is a #

So, per syntax, comments must be standalone and must have #. This fails on both
counts; it's invalid syntax. Suggest replacing with:

# (enable IPv4, and IPv6 if supported)
inet_protocols = all

across two lines.

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

How reproducible:
rpm -i

Steps to Reproduce:
1. install rpm-based distro
2. run rpm -i
3. profit? no, you can't profit, mail isn't working.
Actual results:
in %post, 
postfix: fatal: unknown inet_protocols value "(enable" in "all        (enable
IPv4, and IPv6 if supported)"

Expected results:
some other issue that's causing 2.5.1-1 to not start clean on a virgin install
that I need to look into next

Additional info:
also affects 2.4.6 builds, not present postfix-2.3.3-2

Comment 1 Thomas Woerner 2008-03-12 12:48:22 UTC
Fixed in rawhide in package postfix-2.5.1-2.fc9.

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