Hi Daniela, NoNewPrivileges=false
seems to be needed. There are many other similar systemd settings that can cause your problem, e.g. SecureBits, Capabilities, and others. Can you as a test try to run amavisd without systemd, directly from a shell? systemctl stop amavisd sudo -u amavis -s /usr/sbin/amavisd -c amavisd.conf debug Best Regards Matthias Am 15.05.2015 um 09:46 schrieb bortolotti: > Good morning, > here it is our output: > > amavisd.conf > $daemon_user = "amavis"; # (no default; customary: vscan or > amavis), -u > $daemon_group = "amavis"; # (no default; customary: vscan or > amavis), -g > # $daemon_chroot_dir = $MYHOME; # chroot directory or undef, -R > > [root@postman amavisd]# getenforce > Disabled > > grep -i runasuser /etc/mail/*cf > /etc/mail/sendmail.cf:#O RunAsUser=sendmail > /etc/mail/submit.cf:O RunAsUser=smmsp > > We tried to put the amavis user in group smmsp but we had same > permission problem > > In the amavis startup /usr/lib/systemd/system/amavisd.service we have: > > User=amavis > Group=amavis > NoNewPrivileges=true <------ > > > Is this a problem? > > Best regards > Daniela Bortolotti >
