https://bugzilla.novell.com/show_bug.cgi?id=788780 https://bugzilla.novell.com/show_bug.cgi?id=788780#c3 Freek de Kruijf <f.de.kruijf@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- InfoProvider|f.de.kruijf@gmail.com | --- Comment #3 from Freek de Kruijf <f.de.kruijf@gmail.com> 2012-11-16 12:15:10 UTC --- I tested things again and found that there is a huge possibility for misunderstanding. This comes from the fact that the systemv name for amavis is amavis, however the systemd name is amavisd. So in the Description the right commands should have amavisd.service as parameter instead of amavis.service. systemctl commands for both names are accepted of which only the start command with amavis.service gives an error message, which does not give the information to get on the right track. The output of the enable command even suggest that it has been enabled succesfull. Neither the syslog (journalctl --lines=20) nor (systemctl status amavis.service) provides useful information to pinpoint the problem that amavisd.service should have been used. Back to the original problem. The above may be the cause that this YaST module does not start amavis. But it should also start and enable freshclam.service and clamd.service. freshclam may need a parameter set in the config file /etc/freshclam.conf (uncommenting the line for DatabaseMirror and adapting the right name and /etc/clamd.conf. At least /etc/amavisd.conf needs to have the parameter $mydomain set and probably $myhostname. BTW the comment at this last parameter should be "must be a fully-qualified host name", it is not a domain name. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.