https://bugs.exim.org/show_bug.cgi?id=2112
Bug ID: 2112 Summary: Avast scanner does not work when options specified Product: Exim Version: 4.89 Hardware: x86 OS: All Status: NEW Severity: bug Priority: medium Component: Content Scanning Assignee: t...@duncanthrax.net Reporter: and...@topdog.za.net CC: exim-dev@exim.org When options are specified to the avast scanner it fails to scan and issues a defer instead for all mail. For example. av_scanner = avast:/var/run/avast/scan.sock:SENSITIVITY +pup It seems to me the logic is built for the following protocol response. == start == 220 DAEMON SENSITIVITY +pup 210 SENSITIVITY DATA 200 SENSITIVITY OK == end == How ever the actual protocol echos back the settings like so: == start == socat /var/run/avast/scan.sock - 220 DAEMON SENSITIVITY +pup 210 SENSITIVITY DATA SENSITIVITY +worm +trojan +adware +spyware +dropper +kit +joke +dangerous +dialer +rootkit +exploit +pup +suspicious +pube 200 SENSITIVITY OK == end == The current code does not handle the line starting with SENSITIVITY it expects a line starting with 200 instead. -- You are receiving this mail because: You are on the CC list for the bug. -- ## List details at https://lists.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##