package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

[Ady Ayala]

ubuntu 15.10 in: System -> About Ubuntu

when I do: lsb_release -rd in the bash: Ubuntu 16.04 LTS

xenial xerus package

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: amavisd-new 1:2.10.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-36.41-generic 4.2.8-ckt8
Uname: Linux 4.2.0-36-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.19.1-0ubuntu5
AptOrdering:
 amavisd-new: Configure
 NULL: ConfigurePending
Architecture: i386
Date: Sun May 29 19:47:24 2016
DpkgTerminalLog:
 amavisd-new (1:2.10.1-2ubuntu1) wird eingerichtet ...
 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.
DuplicateSignature: package:amavisd-new:1:2.10.1-2ubuntu1:Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
InstallationDate: Installed on 2014-06-10 (718 days ago)
InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release i386 (20130820.1)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt 1.0.10.2ubuntu2
SourcePackage: amavisd-new
Title: package amavisd-new 1:2.10.1-2ubuntu1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Robie Basak (racb)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

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.

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

Or 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.