we would like to test something before to increase the timout and retransmits
each ten minutes you ping the clamav database and if one signature is new, then you reload the database. During 45s to 60s your server will soft reject email with attachment of your user and remote user.
In short during 10% of time your server is unable to scan email due to the database reload
To compare, I reload the database between two or four hours.
so first
systemctl status amavisd
We would like you remove amavisd-new
yum remove amavisd-new spamassassin
then check in your maillog if clamd reload each ten minutes the database, obviously it should be better to remove the trick you did in the antivirus.conf
Every ten minute I check if the database must be reloaded, so the fix we want to test is to stay the timout to 5 second but try to retransmits 10 times
we will change the behaviour, we think your users wonât be impacted.
We want to keep the soft reject for external/remote smtp, so after 2 attempts of 5 seconds we soft reject the email if clamav is not reachable
For authenticated users via the server smtp, we try to contact clamav, if clamav does not answer during the default time, then we add the symbol of clamav failure scan, but we do not soft reject the email.
In short the human sender is complaining to wait at worse 53 seconds to send an email, but the machine doesnât really care to wait