http://bugzilla.opensuse.org/show_bug.cgi?id=983476 http://bugzilla.opensuse.org/show_bug.cgi?id=983476#c2 --- Comment #2 from Freek de Kruijf --- No it is not related to the pam-config problem. The output of systemctl status amavis.service shows a stopped child process. # systemctl status amavis.service -l ● amavis.service - Amavisd-new Virus Scanner interface Loaded: loaded (/usr/lib/systemd/system/amavis.service; enabled; vendor preset: disabled) Active: inactive (dead) since Fri 2016-06-10 12:40:27 CEST; 1h 19min ago Process: 17159 ExecStopPost=/usr/sbin/amavisd-milter.sh stop (code=exited, status=0/SUCCESS) Process: 3408 ExecStop=/usr/sbin/amavisd -P stop (code=exited, status=0/SUCCESS) Process: 3431 ExecStart=/usr/sbin/amavisd -P foreground (code=exited, status=0/SUCCESS) Process: 3429 ExecStartPre=/usr/sbin/amavisd-milter.sh start (code=exited, status=0/SUCCESS) Process: 3424 ExecStartPre=/bin/echo Starting virus-scanner (amavisd-new): (code=exited, status=0/SUCCESS) Main PID: 3431 (code=exited, status=0/SUCCESS) Status: "Child processes have been stopped." The same when the amavis is running OK. # systemctl status amavis.service -l ● amavis.service - Amavisd-new Virus Scanner interface Loaded: loaded (/usr/lib/systemd/system/amavis.service; enabled; vendor preset: disabled) Active: active (running) since Fri 2016-06-10 14:00:45 CEST; 3min 7s ago Process: 17159 ExecStopPost=/usr/sbin/amavisd-milter.sh stop (code=exited, status=0/SUCCESS) Process: 3408 ExecStop=/usr/sbin/amavisd -P stop (code=exited, status=0/SUCCESS) Process: 22939 ExecStartPre=/usr/sbin/amavisd-milter.sh start (code=exited, status=0/SUCCESS) Process: 22935 ExecStartPre=/bin/echo Starting virus-scanner (amavisd-new): (code=exited, status=0/SUCCESS) Main PID: 22942 (/usr/sbin/amavi) Status: "Initialization done." CGroup: /system.slice/amavis.service └─22942 /usr/sbin/amavisd (ch2-avail) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=983476 http://bugzilla.opensuse.org/show_bug.cgi?id=983476#c4 --- Comment #4 from Freek de Kruijf --- The error message: /usr/sbin/amavisd-milter.sh: line 3: /etc/sysconfig/amavis: No such file or directory can easily be avoided by inserting a test for existence of /etc/sysconfig/amavis in that script. -- You are receiving this mail because: You are on the CC list for the bug.