mydestinations can't be preseeded

[Waldemar]

Binary package hint: postfix

Preseeding of several values that I tried works fine, except for the "Other destinations to accept mail for (blank for none):" setting. If I preseed it to

postfix postfix/destinations string

and then reconfigure the package, it still drops back to the default. I thought it might be connected to an empty value being set, but even a non-empty value is not being honored. All the other values that I have tried do work, so I suppose it is a bug related to this setting only. Please correct me if I am being stupid.

Thanks for the help.
Waldemar

[Marcus Asshauer (mcas)]

Thank you for reporting this bug. Please add your ubuntu version and the output of apt-cache policy postfix.

[Waldemar (waldemar-opencodes)]

Sorry about this. I am using hardy.

apt-cache policy postfix
postfix:
  Installed: 2.5.1-2ubuntu1
  Candidate: 2.5.1-2ubuntu1
  Version table:
 *** 2.5.1-2ubuntu1 0
        500 http://gb.archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

Many thanks for looking into this,
Waldemar

[Christian Quast (wildcart)]

Hi,

I have the exact same problem. I try to automatically install postfix on several computers and the preseeded destination setting is overwritten regardless of what I am doing.

apt-cache policy postfix
postfix:
  Installed: (none)
  Candidate: 2.5.1-2ubuntu1
  Version table:
     2.5.1-2ubuntu1 0
        500 http://mpi-deb.mpi-bremen.de hardy/main Packages

regards
Christian

[Marcus Asshauer (mcas)]

Thank you for your answers. I mark this bug as confirmed because of your infomations.

[LaMont Jones (lamont)]

Postfix currently assumes that if postfix/destinations is set to a non-default value (debconf flag 'set' is true), then postconf has the correct (quite likely to have been changed by the user by editing main.cf), and loads it from there, in order to handle the case where users get annoyed at postfix overwriting their editor changes when they run dpkg-reconfigure.

So the real question becomes: how does a config script distinguish between initial install and upgrade, which I expect is quite simple.

(Dropping the above here to remind me where to actually start looking when I get back to it later.)