package postfix 3.1.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75

Bug #1711432 reported by ydheur
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
postfix (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

unexpected bug.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: postfix 3.1.0-3
ProcVersionSignature: Ubuntu 4.4.0-92.115-generic 4.4.76
Uname: Linux 4.4.0-92-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
Date: Tue Aug 15 22:14:51 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 75
EtcMailname: YYY14.04
Hostname: YYY14.04
InstallationDate: Installed on 2014-06-15 (1158 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
PostconfMydomain: 04
PostconfMyhostname: YYY14.04
PostconfMyorigin: /etc/mailname
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt 1.2.24
ResolvConf:
 # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
 # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
 nameserver 127.0.1.1
SourcePackage: postfix
Title: package postfix 3.1.0-3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
UpgradeStatus: Upgraded to xenial on 2016-06-09 (434 days ago)

Revision history for this message
ydheur (ydheur) wrote :
tags: removed: need-duplicate-check
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Hi ydheur,

there seems to be a conflict with your system setup and the constraints postfix has on install.
It tries to set up a basic configuration base on your hostname.

That is according to the logs:
  Hostname: YYY14.04

The scripts ahve to derive from there (no better source of that info) so they do.
But a dot in a hostname is splitting a fqdn so the actual main host is considered to be "04".

That in turn is invalid and lets the configuration fail, here from your log:
  newaliases: warning: valid_hostname: numeric hostname: 04
  newaliases: fatal: file /etc/postfix/main.cf: parameter mydomain: bad parameter value: 04

You have to adapt your hostname to be compatible or setup and configure postfix on your own not relying on the scripts that run on install. I'd recommend the former

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Thank you for your report.

This looks like a local configuration problem, rather than a bug in Ubuntu.

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.

Changed in postfix (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for postfix (Ubuntu) because there has been no activity for 60 days.]

Changed in postfix (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.