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

[neil garratt]

Internal error.
Software failed to install.
Some software failed to upload properly

These are some of the messages I get regularly. In fact every time I start the pc.

Any thoughts? Solutions?

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: amavisd-new 1:2.10.1-4ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-37.39-generic 4.8.16
Uname: Linux 4.8.0-37-generic i686
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: i386
Date: Thu Feb 16 19:46:39 2017
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-07-14 (217 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.4
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.10.1-4ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to yakkety on 2016-10-31 (108 days ago)

[Joshua Powers (powersj)]

From log:

Feb 16 19:46:39 neil-Lenovo amavis[3940]: The value of variable $myhostnam...n
Feb 16 19:46:39 neil-Lenovo amavis[3940]: a fully qualified domain name; p....
Feb 16 19:46:39 neil-Lenovo amavis[3940]: You must explicitly assign a FQD...e
Feb 16 19:46:39 neil-Lenovo amavis[3940]: in /etc/amavis/conf.d/05-node_id...s
Feb 16 19:46:39 neil-Lenovo amavis[3940]: network name!
Feb 16 19:46:39 neil-Lenovo amavis[3940]: (failed).

[Joshua Powers (powersj)]

Thank you for taking the time to file a bug report.

Per the log message above it appears that amavis needs the FQDN set. If you
set this it should be able to start properly.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, 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".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community