package postfix 3.1.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
postfix (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
Setting up postfix (3.1.0-3) ...
setting explicit chroot on /etc/postfix:
postconf: fatal: file /etc/postfix/
dpkg: error processing package postfix (--configure):
subprocess installed post-installation script returned error exit status 1
[ line 126 of master.cf is commented out, why does it have a problem with it? ]
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: postfix 3.1.0-3
ProcVersionSign
Uname: Linux 3.13.0-48-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Fri Sep 16 23:14:42 2016
Ec2AMI: ami-5189a661
Ec2AMIManifest: (unknown)
Ec2Availability
Ec2InstanceType: m3.large
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ErrorMessage: subprocess installed post-installation script returned error exit status 1
RelatedPackageV
dpkg 1.18.4ubuntu1.1
apt 1.2.12~
SourcePackage: postfix
Title: package postfix 3.1.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-09-17 (0 days ago)
Thank you for your report.
This looks like a local configuration problem, rather than a bug in Ubuntu. We can provide more details of help if you provide your configuration file as an attachment.
You can find pointers to get help for this sort of problem here: http:// www.ubuntu. com/support/ community
Since we use this bug tracker to track bugs in Ubuntu, rather than configuration problems, I'm marking this bug as Invalid. This helps us to focus on fixing bugs in Ubuntu.
If you believe that this is really a bug, then you may find it helpful to read "How to report bugs effectively" http:// www.chiark. greenend. org.uk/ ~sgtatham/ bugs.html. We'd be grateful if you would then provide a more complete description of the problem, explain why you believe this is a bug in Ubuntu rather than a problem specific to your system, and then change the bug status back to New.