package amavisd-new 1:2.4.2-6.2ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1

[crazy_j]

Binary package hint: amavisd-new

Upgrades seem to be an issue with all kubuntu major things. adept it's self seems to be very buggy, although it may be charter communications(my cable internet). Kind of doubtful as I did an Install of 7.10 on my mothers computer and she has a diffrent provider, and still had update issues, inside of 7.10, now upgrading to 8.04 seems even tugher.

ProblemType: Package
Architecture: i386
Date: Mon Mar 24 06:06:44 2008
DistroRelease: Ubuntu 7.10
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: amavisd-new 1:2.4.2-6.2ubuntu1
PackageArchitecture: all
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.4.2-6.2ubuntu1 failed to install/upgrade: subprocess post-installation script returned error exit status 1
Uname: Linux Bobbie-Jo 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

[Scott Kitterman (kitterman)]

Did you read the error message:

  The value of variable $myhostname is "Bobbie-Jo", but should have been
  a fully qualified domain name; perhaps uname(3) did not provide such.
  You must explicitly assign a FQDN of this host to variable $myhostname
  in /etc/amavis/conf.d/05-node_id, or fix what uname(3) provides as a host's
  network name!

Do what it says and the package installation will finish.

[crazy_j (slapping-monkeys)]

I'm new to linux so how do I do that?

[Scott Kitterman (kitterman)]

I'm going to convert this over to a support question then so you can get help with it.

[Scott Kitterman (kitterman)]

Bug reporter needs help editing his configuration file.

[Daniel Hahler (blueyed)]

In fact, it's a bug in amavis, which does not accept hyphens in the hostname, which is valid according to http://en.wikipedia.org/wiki/Hostname#Restrictions_on_valid_host_names (and otherwise "hostname --fqdn" would not output it, which gets done in the conf file mentioned above).

[Daniel Hahler (blueyed)]

Bleh.. mixed hostname with top level domain, which gets checked.
Although "foo.bar-bar" is a valid FQDN according to "hostname --fqdn", allowing a hyphen there would not fix the problem for crazy_j: there's no TLD at all.

Converting to a question again, sorry.