==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
======== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
======== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release):
- Linux/BSD distribution name and version:
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):
- Web server (Apache or Nginx):
- Manage mail accounts with iRedAdmin-Pro?
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
I use Iredmail 0,9,8 in CT Centos 7 in Proxmox 5,2, when I finish accomplished the Iredmail's installation new, the amavisd meets at a run perfectly, bat reinitiate CentOS7's CT when connecting me command telnet localhost 10024, it am  hit the top of that amavisd does not start and therefore I can not make use of this.

I have updated intervening Clamav command frehsclam and it updates perfectly.

They can give me any solution with regard to this matter, because I am interested in utilizing amavisd I eat new Antivirus of my mail.

The system's exits

report de  /var/log/maillog

Sep  6 11:23:40 correo postfix/amavis/smtp[2560]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Sep  6 11:23:40 correo postfix/amavis/smtp[2561]: connect to 127.0.0.1[127.0.0.1]:10024: Connection refused
Sep  6 11:23:40 correo postfix/amavis/smtp[2558]: 904D08A0E88: to=<admin@rubia.alinet.cu>, relay=none, delay=463, delays=463/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2559]: 204058A0E86: to=<admin@rubia.alinet.cu>, relay=none, delay=469, delays=469/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2560]: D8C2E8A0E84: to=<admin@rubia.alinet.cu>, relay=none, delay=475, delays=475/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2561]: B75B38A0E79: to=<admin@rubia.alinet.cu>, relay=none, delay=920, delays=920/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2558]: 904D08A0E88: to=<postmaster@rubia.alinet.cu>, relay=none, delay=463, delays=463/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2560]: D8C2E8A0E84: to=<postmaster@rubia.alinet.cu>, relay=none, delay=475, delays=475/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2559]: 204058A0E86: to=<postmaster@rubia.alinet.cu>, relay=none, delay=469, delays=469/0.01/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)
Sep  6 11:23:40 correo postfix/amavis/smtp[2561]: B75B38A0E79: to=<postmaster@rubia.alinet.cu>, relay=none, delay=920, delays=920/0.02/0/0, dsn=4.4.1, status=deferred (connect to 127.0.0.1[127.0.0.1]:10024: Connection refused)

report systemctl start amavisd

Warning: amavisd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Job for amavisd.service failed because a configured resource limit was exceeded. See "systemctl status amavisd.service" and "journalctl -xe" for details.

report systemctl status amavisd

#systemctl status amavisd
Warning: amavisd.service changed on disk. Run 'systemctl daemon-reload' to reload units.
Job for amavisd.service failed because a configured resource limit was exceeded. See "systemctl status amavisd.service" and "journalctl -xe" for details.
[root@correo ~]# systemctl status amavisd
* 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 Thu 2018-09-06 11:26:59 EDT; 30s ago
     Docs: http://www.ijs.si/software/amavisd/#doc
  Process: 2664 ExecStart=/usr/sbin/amavisd -c /etc/amavisd/amavisd.conf (code=exited, status=0/SUCCESS)
Main PID: 2211 (code=exited, status=1/FAILURE)

Sep 06 11:26:59 correo systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
Sep 06 11:26:59 correo systemd[1]: Unit amavisd.service entered failed state.
Sep 06 11:26:59 correo systemd[1]: amavisd.service failed.
Sep 06 11:26:59 correo systemd[1]: amavisd.service holdoff time over, scheduling restart.
Sep 06 11:26:59 correo systemd[1]: start request repeated too quickly for amavisd.service
Sep 06 11:26:59 correo systemd[1]: Failed to start Amavisd-new is an interface between MTA and content checkers..
Sep 06 11:26:59 correo systemd[1]: Unit amavisd.service entered failed state.
Sep 06 11:26:59 correo systemd[1]: amavisd.service failed.
Warning: amavisd.service changed on disk. Run 'systemctl daemon-reload' to reload units.