postfix fails to install/upgrade with error exit status 75: invalid hostname configuration

Asked by Dave D

After install error is reported

ProblemType: Package
DistroRelease: Ubuntu 11.04
Package: postfix 2.8.2-1ubuntu2.1
ProcVersionSignature: Ubuntu 2.6.38-11.50-generic 2.6.38.8
Uname: Linux 2.6.38-11-generic i686
Architecture: i386
Date: Mon Oct 10 17:23:54 2011
ErrorMessage: subprocess installed post-installation script returned error exit status 75
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
SourcePackage: postfix
Title: package postfix 2.8.2-1ubuntu2.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 75
UpgradeStatus: Upgraded to natty on 2011-05-04 (159 days ago)

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu postfix Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
Scott Kitterman (kitterman) said :
#1

This is not a package bug, but the package correctly responding to a bad configuration in your system:

Running newaliases
newaliases: warning: valid_hostname: invalid character 32(decimal): PARENTS PC
newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: PARENTS PC
dpkg: error processing postfix (--configure):
 subprocess installed post-installation script returned error exit status 75

I'm converting this bug report to a support question so you can get help setting a valid hostname.

Revision history for this message
Eliah Kagan (degeneracypressure) said :
#2

Change your hostname (i.e., the name of your computer) to something without a space (also no punctuation and no leading numeral, but you already don't have those things). ParentsPC or PARENTSPC would work.

One way to change your hostname is to edit /etc/hostname. See http://www.ducea.com/2006/08/07/how-to-change-the-hostname-of-a-linux-system/ (go down to "Permanent hostname change on Debian based systems") for details.

Revision history for this message
John McCormick (jmccormi7224157) said :
#3

I had noticed some suggestive "fix" comments on various sites and even did an rm on /usr/sbin/postfix but that didn't work either ---
(Of course, before that, I had tried the conventional apt remove and purge commands on it as well --- The log I've enclosed below is probably the same as others (who have had a similar problem) but thought I'd include (FYI) ---
Also, I noticed that in /etc/postfix/main.cf that the system was "barking" at myhostname (bad parameter value) -- Is that something I could edit that file to correct it ? -- Just a thought or suggestion --

===============================================
Running newaliases
newaliases: warning: valid_hostname: misplaced delimiter: jmccormi-Studio-1558..
newaliases: fatal: file /etc/postfix/main.cf: parameter myhostname: bad parameter value: jmccormi-Studio-1558..
dpkg: error processing package postfix (--configure):
 installed postfix package post-installation script subprocess returned error exit status 75
Processing triggers for libc-bin (2.32-0ubuntu6) ...
Errors were encountered while processing:
 postfix
E: Sub-process /usr/bin/dpkg returned an error code (1)
===============================================

Thanks, John McCormick --- Email: <email address hidden>

Revision history for this message
John McCormick (jmccormi7224157) said :
#4

I also have a hunch that if you could prompt (at "update-manager" time) my OS to a Partial Upgrade and I would like to have that happen because it prompted me already and I failed to make that upgrade --- it's possible, if you gave me another chance to do this "Partial Upgrade" that this problem might fix itself -- (In other words, please give me a way to trigger a "partial upgrade" as I would be curious to know if that might automatically fix this postfix problem
=====
John McCormick
======
Email: <email address hidden>

Can you help with this problem?

Provide an answer of your own, or ask Dave D for more information if necessary.

To post a message you must log in.