* Mark via Postfix-users <markbsdmail2...@gmail.com>: > Disable clamav completely, restart your server and try it like that, > for a few days.
Nope! I don't see any reason to disable ClamAV completely. What I would definitely would to is *not* use the command line scanner utility clamscan to scan messages for malware. This will consume many resources any I suspect this to be the culprit without even looking any further. We know from the amavis mailing list and our own experience you do not want to use commandline utilities to scan messages. What you want is a running daemonized process that scans messages. In other words use clamd instead of clamscan (or even clamdscan) and hook clamd into the message delivery process using either clamav-milter, rspamd or amavis. > ClamAV is a RAM killer! That's an incorrect generalization. ClamAV runs on many machines - be it bare metal or VM - without any problems. The problem here very likely is using the commandline scanner instead of the daemonized process. p@rick -- [*] sys4 AG https://sys4.de, +49 (89) 30 90 46 64 Schleißheimer Straße 26/MG,80333 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
