[Bug 1727699] Re: SSL issue upgrading postfix

2018-02-14 Thread Launchpad Bug Tracker
This bug was fixed in the package postfix - 3.1.0-3ubuntu0.3 --- postfix (3.1.0-3ubuntu0.3) xenial; urgency=medium * Only run post 3.0 master.cf fixup if upgrading from version before the fix. (LP: #1727699) This is a pick of 37b37e93 from Debian packaging repo at

[Bug 1727699] Re: SSL issue upgrading postfix

2018-02-14 Thread ChristianEhrhardt
Verified from xenial: submission inet n - - - - smtpd becomes submission inet n - - y - smtpd With proposed submission inet n - - - - smtpd stays submission inet n - - - -

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-17 Thread Chris J Arges
Hello tom, or anyone else affected, Accepted postfix into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postfix/3.1.0-3ubuntu0.3 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-08 Thread ChristianEhrhardt
I updated the bug to include the SRU teamplate, but I wonder as I don't see my upload in the SRU queue. Uploading again postfix_3.1.0-3ubuntu0.3_source.changes ... - this time it appears in the queue. The upload is the same, so if there are anywhere two of them just kill one of them. **

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-02 Thread Bug Watch Updater
** Changed in: postfix (Debian) Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727699 Title: SSL issue upgrading postfix To manage notifications about this

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-02 Thread ChristianEhrhardt
Based on the insight that this was added to 3.x but post Xenial being released I provided a fix to be tried in ppa [1]. An associated merge proposal for the packaging is up for review at [2] [1]: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3095 [2]:

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-02 Thread Launchpad Bug Tracker
** Merge proposal linked: https://code.launchpad.net/~paelzer/ubuntu/+source/postfix/+git/postfix/+merge/335622 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727699 Title: SSL issue upgrading

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-02 Thread ChristianEhrhardt
I think I found it, the check to: if `dpkg --compare-versions "$2" lt 3.1.0-1~`; then has no else clause that we could hit. But by checking more in Detail I realized that this version check is not in all releases. It was added in 3.1.3-1 and thereby is in all releases. It is in Zesty and later

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-02 Thread ChristianEhrhardt
https://git.launchpad.net/postfix/commit/?id=37b37e93b5b58ae8b01cdd68b2059922e891d0aa -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727699 Title: SSL issue upgrading postfix To manage

[Bug 1727699] Re: SSL issue upgrading postfix

2018-01-02 Thread tom
> If you hit this on an upgrade from 3.x -> 3.x that would be wrong - did you?. yes, the log says it was an upgrade from 3.1.0-3ubuntu0.1 to 3.1.0-3ubuntu0.2 /var/log# grep post dpkg.log.1 2017-12-19 12:56:30 upgrade postfix:amd64 3.1.0-3ubuntu0.1 3.1.0-3ubuntu0.2 2017-12-19 12:56:30 status

[Bug 1727699] Re: SSL issue upgrading postfix

2017-12-19 Thread ChristianEhrhardt
[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816172 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1727699 Title: SSL issue upgrading postfix To manage notifications about this bug go to:

[Bug 1727699] Re: SSL issue upgrading postfix

2017-12-19 Thread ChristianEhrhardt
The line you wonder essentially does: set_postconf -F -c "/etc/postfix" submission/inet/chroot=y And yes this is setting the "y" in your case I'd think. As I outlined before this was (I guess) meant to carry the old default to stay the same on an upgrade. IMHO this is fine on a certain

[Bug 1727699] Re: SSL issue upgrading postfix

2017-12-19 Thread tom
Hello, it happened again. this time I have the log of the installation procedure: Setting up postfix (3.1.0-3ubuntu0.2) ... Installing new version of config file /etc/init.d/postfix ... initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection

[Bug 1727699] Re: SSL issue upgrading postfix

2017-11-02 Thread ChristianEhrhardt
Hi, wise to track all of /etc. I can't reproduce to have this update changing my postfix conf. The only change that would touch this in a meaningful way should be form a 2.x to a 3.x installation. Hmm, the only thing that would remotely make sense is that the fix to "- debian/postfix.postinst:

[Bug 1727699] Re: SSL issue upgrading postfix

2017-10-27 Thread tom
Hi, thanks for the investigation, I can give you some other details: I made a system update with a lot of packages, including this one: postfix:amd64 3.1.0-3 => 3.1.0-3ubuntu0.1 which I presumed is the cause the problem. Looking at the package diff I cannot see where the problem is

[Bug 1727699] Re: SSL issue upgrading postfix

2017-10-27 Thread ChristianEhrhardt
Hi Tom, on the version originally release in Xenial I see: 3.1.0-3: #submission inet n - y - - smtpd 3.1.0-3ubuntu0.1 #submission inet n - y - - smtpd After the upgrade it still is the same, and it is a comment in both. There is