inet_protocols can't be preseeded

After a quick look into postfix.config and postfix.postinst, I'm not sure postfix/protocols is considered "changed" in case you preseed that value, in which case you'd skip the "setting inet_protocols" stage in postinst.

This is a pretty old bug, but it looks like it's still present in precise (postfix 2.9.1-4).

Looking at the postinst script, I think the fix is pretty trivial - setting the changed flag for postfix/protocols in fset_all_changed(). I'm attaching a patch that should take care of this.

The attachment "postfix_protocols_preseed.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu-reviewers team please also unsubscribe the team from this bug report.

[This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.]

I also went ahead and opened an upstream bug - http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671235

It looks like this bug is still present in trusty - postfix 2.11.0-1.

I'm going to bump the upstream bug as well, but is there any chance we can get this patch into the Ubuntu package since upstream seems unwilling to fix this? I can create a debdiff if that would be helpful.

@matthew-l-dailey,

Could you put together a debdiff for this patch against the latest utopic sources?
This looks to be a fairly good guide.
http://packaging.ubuntu.com/html/traditional-packaging.html

Also if you are feeling frisky you could also create a debdiff for the trusty and precise trees and submit it via the SRU Process described here.
https://wiki.ubuntu.com/StableReleaseUpdates

If you have any questions feel free to ping me via e-mail or IRC.

Looks good to me. I'll get it added into the debian source next time I upload.

This patch should also go into trusty so that it can be picked up for 14.04.2.

Uploaded for Vivid, Utopic, and Trusty.

This bug was fixed in the package postfix - 2.11.3-1ubuntu1

---------------
postfix (2.11.3-1ubuntu1) vivid; urgency=medium

  * support postfix/protocols (LP: #583216)
 -- Seyeong Kim <email address hidden> Mon, 02 Feb 2015 15:50:04 -0600

Packages are in the upload queues awaiting the SRU team, unsubscribing ubuntu-sponsors.

Hello Japje, or anyone else affected,

Accepted postfix into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postfix/2.11.1-1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Hello Japje, or anyone else affected,

Accepted postfix into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postfix/2.11.0-1ubuntu1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Tested OK on Utopic and Trusty, thanks!

This bug was fixed in the package postfix - 2.11.0-1ubuntu1

---------------
postfix (2.11.0-1ubuntu1) trusty; urgency=low

  * support postfix/protocols (LP: #583216)
 -- Seyeong Kim <email address hidden> Mon, 02 Feb 2015 16:20:29 -0600

The verification of the Stable Release Update for postfix has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package postfix - 2.11.1-1ubuntu1

---------------
postfix (2.11.1-1ubuntu1) utopic; urgency=medium

  * support postfix/protocols (LP: #583216)
 -- Seyeong Kim <email address hidden> Mon, 02 Feb 2015 16:15:31 -0600

patch for precise

Sponsored for precise.

Hello Japje, or anyone else affected,

Accepted postfix into precise-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postfix/2.9.6-1~12.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

precise-proposed/main postfix amd64 2.9.6-1~12.04.3

installation output

setting alias maps
setting alias database
mailname is not a fully qualified domain name. Not changing /etc/mailname.
setting destinations: precise-postfix, localhost.localdomain, , localhost
setting relayhost:
setting mynetworks: 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
setting mailbox_size_limit: 0
setting recipient_delimiter: +
setting inet_interfaces: all
setting inet_protocols: all

This bug was fixed in the package postfix - 2.9.6-1~12.04.3

---------------
postfix (2.9.6-1~12.04.3) precise; urgency=medium

  * support postfix/protocols (LP: #583216)
 -- Seyeong Kim <email address hidden> Tue, 17 Feb 2015 08:01:59 -0600