Please backport Postfix 3.3.1 bugfix release to bionic (for Docker/container deployments)
Bug #1772858 reported by
Gert van Dijk
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| postfix (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
Postfix 3.3.0 [1] is available in bionic at the time of writing and added support for running in containers by having the master process running in the foreground. 3.3.1 bugfix release [2] became available May 20 with a fix for using this feature:
> Postfix did not support running as a PID=1 process, which complicated Postfix deployment in
> containers. The "postfix start-fg" command will now run the Postfix master daemon as a PID=1
> process if possible.
Along with other bugfixes done in this release, I'd like to request an update for Postfix bionic to 3.3.1.
Thanks!
[1]: http://
[2]: http://
Revision history for this message
| Andreas Hasenack (ahasenack) wrote | #1 |
| Changed in postfix (Ubuntu): | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
Revision history for this message
| Christian Ehrhardt (paelzer) wrote | #2 |
To post a comment you must log in.
Thanks for filing this bug in Ubuntu, and sorry for getting to it so late.
This seems like a reasonable bugfix request.
Upstream patch that brought postfix from 3.3.0 to 3.3.1 and includes the fix: https:/
The actual fix shouldn't be hard to extract from that.
Would you be able to provide a simple testcase for this bug? Something simple that breaks with 3.3.0, and should work with 3.3.1?