Hello and thank you for reporting this bug.
I am unable to reproduce this in a LXD yakkety container. To rule out a configuration issue, can you please provide the output of:
systemctl status amavis.service journalctl -xe
upon the failure; as well as, possibly, the output from runing
sudo systemctl start amavis.service
and then move this bug back to New?
Hello and thank you for reporting this bug.
I am unable to reproduce this in a LXD yakkety container. To rule out a configuration issue, can you please provide the output of:
systemctl status amavis.service
journalctl -xe
upon the failure; as well as, possibly, the output from runing
sudo systemctl start amavis.service
and then move this bug back to New?