[GH-ISSUE #1775] "UNCHECKED" Added to email headline #1400

New issue

Closed

opened 2026-02-27 11:16:54 +03:00 by kerem · 3 comments

kerem commented

2026-02-27 11:16:54 +03:00

Owner

Originally created by @ghost on GitHub (Sep 12, 2019).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/1775

Impacted versions

Modoboa: 1.14.0
installer used: Yes
Webserver: Nginx

Current behavior

After a while, all emails being received by the server will have "UNCHECKED" added to the emails headline. Restarting the server will temporarily fix it, but after a while, it will be back.

As far as I can tell, it has something to do with ClamAV not checking the emails for vira?

/var/log/mail.log

Sep 10 08:26:34 mail amavis[518]: (00518-10) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused
Sep 10 08:26:35 mail amavis[518]: (00518-10) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused
Sep 10 08:26:35 mail amavis[518]: (00518-10) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamav/clamd.ctl, retrying (2)
ep 10 08:26:41 mail amavis[518]: (00518-10) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused
Sep 10 08:26:41 mail amavis[518]: (00518-10) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd.ctl (All attempts (1) failed connecting $
Sep 10 08:26:41 mail amavis[518]: (00518-10) (!)WARN: all primary virus scanners failed, considering backups
Sep 10 08:26:41 mail amavis[518]: (00518-10) (!!)AV: ALL VIRUS SCANNERS FAILED

/var/log/clamav/freshclam.log

Thu Sep 12 13:53:33 2019 -> Received signal: wake up
Thu Sep 12 13:53:33 2019 -> ClamAV update process started at Thu Sep 12 13:53:33 2019
Thu Sep 12 13:53:33 2019 -> WARNING: Your ClamAV installation is OUTDATED!
Thu Sep 12 13:53:33 2019 -> WARNING: Local version: 0.100.3 Recommended version: 0.101.4
Thu Sep 12 13:53:33 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav
Thu Sep 12 13:53:33 2019 -> main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr)
Thu Sep 12 13:53:33 2019 -> daily.cld is up to date (version: 25570, sigs: 1757748, f-level: 63, builder: raynman)
Thu Sep 12 13:53:33 2019 -> bytecode.cvd is up to date (version: 330, sigs: 94, f-level: 63, builder: neo)

Originally created by @ghost on GitHub (Sep 12, 2019). Original GitHub issue: https://github.com/modoboa/modoboa/issues/1775 # Impacted versions * Modoboa: 1.14.0 * installer used: Yes * Webserver: Nginx # Current behavior After a while, all emails being received by the server will have "***UNCHECKED***" added to the emails headline. Restarting the server will temporarily fix it, but after a while, it will be back. As far as I can tell, it has something to do with ClamAV not checking the emails for vira? /var/log/mail.log ``` Sep 10 08:26:34 mail amavis[518]: (00518-10) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused Sep 10 08:26:35 mail amavis[518]: (00518-10) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused Sep 10 08:26:35 mail amavis[518]: (00518-10) (!)ClamAV-clamd: All attempts (1) failed connecting to /var/run/clamav/clamd.ctl, retrying (2) ep 10 08:26:41 mail amavis[518]: (00518-10) (!)connect to /var/run/clamav/clamd.ctl failed, attempt #1: Can't connect to a UNIX socket /var/run/clamav/clamd.ctl: Connection refused Sep 10 08:26:41 mail amavis[518]: (00518-10) (!)ClamAV-clamd av-scanner FAILED: run_av error: Too many retries to talk to /var/run/clamav/clamd.ctl (All attempts (1) failed connecting $ Sep 10 08:26:41 mail amavis[518]: (00518-10) (!)WARN: all primary virus scanners failed, considering backups Sep 10 08:26:41 mail amavis[518]: (00518-10) (!!)AV: ALL VIRUS SCANNERS FAILED ``` /var/log/clamav/freshclam.log ``` Thu Sep 12 13:53:33 2019 -> Received signal: wake up Thu Sep 12 13:53:33 2019 -> ClamAV update process started at Thu Sep 12 13:53:33 2019 Thu Sep 12 13:53:33 2019 -> WARNING: Your ClamAV installation is OUTDATED! Thu Sep 12 13:53:33 2019 -> WARNING: Local version: 0.100.3 Recommended version: 0.101.4 Thu Sep 12 13:53:33 2019 -> DON'T PANIC! Read https://www.clamav.net/documents/upgrading-clamav Thu Sep 12 13:53:33 2019 -> main.cvd is up to date (version: 58, sigs: 4566249, f-level: 60, builder: sigmgr) Thu Sep 12 13:53:33 2019 -> daily.cld is up to date (version: 25570, sigs: 1757748, f-level: 63, builder: raynman) Thu Sep 12 13:53:33 2019 -> bytecode.cvd is up to date (version: 330, sigs: 94, f-level: 63, builder: neo) ```

kerem closed this issue

2026-02-27 11:16:55 +03:00

kerem commented

2026-02-27 11:16:55 +03:00

Author

Owner

@tonioo commented on GitHub (Oct 11, 2019):

@WonderingDane Have you tried to restart clamav?

@tonioo commented on GitHub (Oct 11, 2019): @WonderingDane Have you tried to restart clamav?

kerem commented

2026-02-27 11:16:55 +03:00

Author

Owner

@ghost commented on GitHub (Oct 11, 2019):

Yes, same as restarting the server. Eventually it will start putting "unchecked" in the mail title.

@ghost commented on GitHub (Oct 11, 2019): Yes, same as restarting the server. Eventually it will start putting "unchecked" in the mail title.

kerem commented

2026-02-27 11:16:55 +03:00

Author

Owner

@zwitterion commented on GitHub (Oct 11, 2019):

I had a similar problem. In my case the issue was that the VM had not enough RAM, this will cause clamav to crash after running for few seconds. Switching to a VM with 3GB solved my problem.
Have you checked clamav logs/status? (service clamd status)

@zwitterion commented on GitHub (Oct 11, 2019): I had a similar problem. In my case the issue was that the VM had not enough RAM, this will cause clamav to crash after running for few seconds. Switching to a VM with 3GB solved my problem. Have you checked clamav logs/status? (service clamd status)