Seems it is indeed a bug, users on the mailing list could verify it. See
this thread: http://lists.amavis.org/pipermail/amavis-
users/2011-March/69.html
It seems to be directly related to the number of maximum instances.
netstat doesn't seem to give helpful information:
==
floeff@myserver:~$
Hi Florian
The 'restart' and 'force-reload' commands both stop and start the amavis
daemon which would explain why you have seen similar behaviour from both
commands.
I suspect that this is caused by the port not being fully released
before the new instance of the daemon tries to bind to the port
Seems to occur as well when "restart" is used.
==
Mar 11 08:35:19 myserver amavis[31199]: starting. /usr/sbin/amavisd-new at
myserver.alkernetz amavisd-new-2.6.4 (20090625), Unicode aware
Mar 11 08:35:19 myserver amavis[31199]: Perl version 5.010001
Mar 11 08:35:19 myserver amavis[
