hello David Saez Padros wrote:
>>I suppose that section is triggered by a "local" option >>stated as in: >> >> av_scanner = clamd:127.0.0.1 3310:local >> >>It would cause Exiscan to use clamd SCAN interface, >>as opposed to the STREAM one. >> >>Is a such understading correct? exactly > looks fine >>Is it known to work? :-) > > as i could remember that exact piece of code was contributed > by someone else (i never used clamd using host/port). If you > try, please let us know if this works or not. it works fine > Anyway documentation > should be updated with this option. > >>Yes, I'm aware one would normally use the SCAN >>interface with Unix-domain sockets. > > that would be the best and it's known to work. at the beginning exiscan used only TCP socket and SCAN interface, so it couldn't use clamd runing on another host. so exiscan must use STREAM interface with TCP socket. as far as i know clamd can't listen both TCP and unix sockets. so, if you need to check files from remote hosts, you need to use TCP socket. and now, for example, clamd and exim are running on the same host, but clamd need to check remote files, so clamd must use TCP socket. in this case exiscan can use SCAN interface or STREAM interface. now STREAM interface used by default. the "local" option allow to use SCAN interface. it's simple and well-tested. -- Best wishes Victor Ustugov mailto:[EMAIL PROTECTED] public GnuPG/PGP key: http://victor.corvax.kiev.ua/corvax.asc ICQ: 77186900, 32418694 CRV2-RIPE, CRV-UANIC -- ## List details at http://www.exim.org/mailman/listinfo/exim-users ## Exim details at http://www.exim.org/ ## Please use the Wiki with this list - http://www.exim.org/eximwiki/
