======== Required information ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1 (trying to get to 0.9.6)
- Linux/BSD distribution name and CentOS 7.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): MYSQL
- Web server (Apache or Nginx): Nginx
- Manage mail accounts with iRedAdmin-Pro? - no
- Related log if you're reporting an issue:
====
Hmmmm,
The service amavisd does not start anymore since I tried to update the amavisd.conf
"Add more banned file types/extensions in Amavisd."
Also when I go back to the backed up conf file, I receive the following error message...
_____________________________
systemctl status amavisd.service
● amavisd.service - Amavisd-new is an interface between MTA and content checkers.
Loaded: loaded (/usr/lib/systemd/system/amavisd.service; enabled; vendor preset: disabled)
Active: failed (Result: start-limit) since Mon 2017-01-23 22:47:46 CET; 2min 10s ago
Docs: http://www.ijs.si/software/amavisd/#doc
Process: 13545 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=13)
Main PID: 9226 (code=exited, status=0/SUCCESS)
Jan 23 22:47:45 office.example.com systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
Jan 23 22:47:45 office.example.com systemd[1]: Unit amavisd.service entered failed state.
Jan 23 22:47:45 office.example.com systemd[1]: amavisd.service failed.
Jan 23 22:47:46 office.example.com systemd[1]: amavisd.service holdoff time over, scheduling restart.
Jan 23 22:47:46 office.example.com systemd[1]: start request repeated too quickly for amavisd.service
Jan 23 22:47:46 office.example.com systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
Jan 23 22:47:46 office.example.com systemd[1]: Unit amavisd.service entered failed state.
Jan 23 22:47:46 office.example.com systemd[1]: amavisd.service failed.
____________________________
When I try:
amavisd reload
-->
Config file "/etc/amavisd.conf" does not exist, at /usr/sbin/amavisd line 2150.