Dirk Koopman wrote:
> Data file written for message 17zKGZ-0000C8-00
> calling exiscan(); timeout=60
> exiscan: starting
> exiscan_cleanup(): unlinking
> /var/spool/exim/scan/17zKGZ-0000C8-00/17zKGZ-0000C8-00-complete
> exiscan_cleanup(): unlinking
> /var/spool/exim/scan/17zKGZ-0000C8-00/textfile0 exiscan_cleanup():
> unlinking /var/spool/exim/scan/17zKGZ-0000C8-00/textfile1
> exiscan_cleanup(): unlinking
> /var/spool/exim/scan/17zKGZ-0000C8-00/New_Microsoft_Works_4.0_Sheet_or_
> Chart.wks.exe exiscan_cleanup(): unlinking
> /var/spool/exim/scan/17zKGZ-0000C8-00/textfile2 exiscan() returned 0
> [message processed ok] calling local_scan(); timeout=300
> local_scan() returned 0 NULL
That looks OK. No error message, so it connect and gets an answer. The
question is why kavdaemon does not find anything ? :)
How do you run kavdaemon ? From the exiscan manual:
----------------------------------------------------
Attention: you need to run kavdaemon with the disinfection option
disabled, and with proper path settings, like this:
./kavdaemon -E -f=/opt/AVP /
Note the slash at the end, it is important. /opt/AVP is the
default AVP base directory.
------------------------------------------------------
> exiscan_condition = 1
> exiscan_crypt_salt = kb
> exiscan_timeout = 60s
> exiscan_unpack_mime = true
> exiscan_av_condition = 1
> exiscan_av_action = reject
> exiscan_av_scanner = kavdaemon
> exiscan_av_kavdaemon_socket = /opt/AVP/AvpCtl
That is ok, too, so I guess kavdaemon has a configuration problem.
regards,
/tom
