postfix upgrade does not add 'retry' service

Bug #172925 reported by Matt LaPlante
2
Affects Status Importance Assigned to Milestone
postfix (Ubuntu)
Fix Released
Medium
LaMont Jones

Bug Description

Binary package hint: postfix

Doing an upgrade from feisty to gusty, postfix gets upgraded from the 2.3.x series to the 2.4.x series.

As per the release notes here:
ftp://ftp.reverse.net/pub/postfix/official/postfix-2.4.6.RELEASE_NOTES

There is a "Major changes - critical" feature added to the 2.4.0 release as follows:
------------------------------------------------------------------------------------------------------------------
[Incompat 20061209] The upgrade procedure adds a new "retry" service
to the master.cf file. If you make the mistake of copying old
Postfix configuration files over the new files, the queue manager
may log warnings with:

    warning: connect to transport retry: Connection refused

To fix your master.cf file, use "postfix upgrade-configuration"
followed by "postfix reload".
------------------------------------------------------------------------------------------------------------------

I discovered after my gutsy upgrade that this feature was *not* added to my master.cf. I don't believe the install procedure gave any warning of this, so it was purely chance that I noticed it in the release notes. Running 'postfix upgrade-configuration' manually did in fact modify my master.cf without causing any problems for my existing config. The upgrade procedure should probably call this function at post-install, or at very minimum, warn the user to run it.

Revision history for this message
Scott Kitterman (kitterman) wrote :

Confirmed. I also get:

    Note: the following files or directories still exist but are no
    longer part of Postfix:

     /usr/share/doc/postfix/QMQP_README

Changed in postfix:
importance: Undecided → Medium
status: New → Confirmed
LaMont Jones (lamont)
Changed in postfix:
assignee: nobody → lamont
status: Confirmed → In Progress
Revision history for this message
Scott Kitterman (kitterman) wrote :

One other comment is that postfix upgrade-configuration leaves the new service unchrooted. Is that correct?

Revision history for this message
LaMont Jones (lamont) wrote :

This is fixed in 2.4.6-2

Changed in postfix:
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.