Hej,
First off, is exiscan discussed on exim ML now, or should exiscan
realted topics still be discussed on its old ML?
How does exim (exiscan) recognise problems during virus scanning? I'm
running my scanner via a Perl script, that is calling clamdscan after
recursive unpacking of archives. I thought I could tell exim that
something went wrong by exiting != 0, but exim doesn't seem to care
about the exit code of the cmdline-mode scanner process. Is this a bug?
This happens with exim 4.50 on debian sarge.
Configuration snippet:
| av_scanner = cmdline:/etc/shared/clamav/avscan.pl %s:\
| Found virus:'(.+)'e.
| acl_smtp_data = check_message
| begin acl
| check_message:
| discard demime = *
| malware = *
lg,
daniel
# exim4 -bV
Exim version 4.50 #1 built 27-May-2005 08:10:05
Copyright (c) University of Cambridge 2004
Berkeley DB: Sleepycat Software: Berkeley DB 4.2.52: (December 3, 2003)
Support for: iconv() IPv6 PAM Perl GnuTLS Content_Scanning Old_Demime
Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb
dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql
Authenticators: cram_md5 cyrus_sasl plaintext spa
Routers: accept dnslookup ipliteral iplookup manualroute queryprogram
redirect
Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp
Fixed never_users: 0
Configuration file is /etc/exim4/exim4.conf
