[Bug 1595096] [NEW] cannot create multi postfix instance by postmulti command

Launchpad Bug Tracker 1595096 at bugs.launchpad.net
Sat Mar 25 00:51:41 UTC 2017


You have been subscribed to a public bug by Jon Grimm (jgrimm):

On ubuntu 16.04 xenial,postfix 3.1.0-3

postfix/postmulti-script: fatal: Missing main.cf prototype:
/etc/postfix/main.cf.proto


SRU Template:


[Impact] 

 * postmulti is broken for all intents and purposes without working
around the missing cf prototypes.

 * This fix simply copies master/main.cf prototypes from
/usr/share/postfix/ to where postmulti expects them.

 * Note: The issue can be worked around manually copying proto files
appropriately to make the postmulti script happy.


[Test Case]

 * detailed instructions how to reproduce the bug

Broken looks like:

root at x1:/home/ubuntu# postmulti -e init
root at x1:/home/ubuntu# postmulti -I postfix-example -G mta -e create
postfix/postmulti-script: fatal: Missing main.cf prototype: /etc/postfix/main.cf.proto   
 

When fixed:

root at x1:/home/ubuntu# postmulti -e init
root at x1:/home/ubuntu# postmulti -I postfix-example -G mta -e create
root at x1:/home/ubuntu# postmulti -l
- - y /etc/postfix
postfix-example mta n /etc/postfix-example


[Regression Potential]

 * I've tested the break and fix on xenial and yakkety.

 * This path is entirely broken right now, so regression risk no worse
than current situation as fix is simply copying the missing proto cf
file into the expected location.

[Other Info]
 
 * Fix backported from debian.  Already fixed in the postfix version in zesty.

** Affects: postfix (Ubuntu)
     Importance: Medium
     Assignee: Jon Grimm (jgrimm)
         Status: Fix Released

** Affects: postfix (Ubuntu Xenial)
     Importance: Medium
     Assignee: Jon Grimm (jgrimm)
         Status: In Progress

** Affects: postfix (Debian)
     Importance: Unknown
         Status: Fix Released

-- 
cannot create multi postfix instance by postmulti command
https://bugs.launchpad.net/bugs/1595096
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.



More information about the Ubuntu-sponsors mailing list