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

[JKMore]

1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to get 333 kB of archives.
After this operation, 5,120 B disk space will be freed.
Get:1 http://ppa.launchpad.net/plushuang-tw/uget-stable/ubuntu yakkety/main amd64 uget amd64 2.0.8-0ubuntu0~yakkety [333 kB]
Fetched 333 kB in 1s (287 kB/s)
(Reading database ... 659635 files and directories currently installed.)
Preparing to unpack .../uget_2.0.8-0ubuntu0~yakkety_amd64.deb ...
Unpacking uget (2.0.8-0ubuntu0~yakkety) over (2.0.7-1ubuntu1) ...
Setting up uget (2.0.8-0ubuntu0~yakkety) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for desktop-file-utils (0.23-1ubuntu1) ...
Setting up amavisd-new (1:2.10.1-4ubuntu1) ...
Creating/updating amavis user account...
Job for amavis.service failed because the control process exited with error code.
See "systemctl status amavis.service" and "journalctl -xe" for details.
invoke-rc.d: initscript amavis, action "start" failed.
● amavis.service - LSB: Starts amavisd-new mailfilter
   Loaded: loaded (/etc/init.d/amavis; generated; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mon 2016-12-26 00:55:31 CST; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 8327 ExecStart=/etc/init.d/amavis start (code=exited, status=1/FAILURE)

Dec 26 00:55:31 vkmore-Satellite-C55-C amavis[8327]: Starting amavisd: The ...
Dec 26 00:55:31 vkmore-Satellite-C55-C amavis[8327]: a fully qualified doma...
Dec 26 00:55:31 vkmore-Satellite-C55-C amavis[8327]: You must explicitly as...
Dec 26 00:55:31 vkmore-Satellite-C55-C amavis[8327]: in /etc/amavis/conf.d/...
Dec 26 00:55:31 vkmore-Satellite-C55-C amavis[8327]: network name!
Dec 26 00:55:31 vkmore-Satellite-C55-C amavis[8327]: (failed).
Dec 26 00:55:31 vkmore-Satellite-C55-C systemd[1]: amavis.service: Control pr...
Dec 26 00:55:31 vkmore-Satellite-C55-C systemd[1]: Failed to start LSB: Start...
Dec 26 00:55:31 vkmore-Satellite-C55-C systemd[1]: amavis.service: Unit enter...
Dec 26 00:55:31 vkmore-Satellite-C55-C systemd[1]: amavis.service: Failed wit...
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package amavisd-new (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of amavisd-milter:
 amavisd-milter depends on amavisd-new; however:
  Package amavisd-new is not configured yet.

dpkg: error processing package amavisd-milter (--configure):
 dependency problems - leaving unconfigured
Processing triggers for bamfdaemon (0.5.3+16.10.20160929-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
No apport report written because the error message indicates its a followup error from a previous failure.
                          Processing triggers for man-db (2.7.5-1) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Errors were encountered while processing:
 amavisd-new
 amavisd-milter
E: Sub-process /usr/bin/dpkg returned an error code (1)
vkmore@vkmore-Satellite-C55-C:~$

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: amavisd-new 1:2.10.1-4ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering:
 uget:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Mon Dec 26 00:55:31 2016
ErrorMessage: subprocess installed post-installation script returned error exit status 1
InstallationDate: Installed on 2016-10-29 (57 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt 1.3.3
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-11-08 (48 days ago)

[Seth Arnold (seth-arnold)]

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

[Joshua Powers (powersj)]

I believe the full systmctl message is something to the effect of:

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

[Joshua Powers (powersj)]

In this case, what you need to do is exactly what the message says, set the FQDN or edit /etc/amavis/conf.d/05-node_id and modify the $myhostname variable to be a FQDN.

Since there isn't enough information in your report to differentiate between a local configuration problem and a bug in Ubuntu, I'm marking this bug as Incomplete. 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.

If indeed this is a local configuration problem, you can find pointers to get help for this sort of problem here: http://www.ubuntu.com/support/community

[Launchpad Janitor (janitor)]

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