ok, i solved the problem, it was effectively the path of AVP for
scanning amavis runtime dir (add "*/var/spool/amavis" in Names)
sorry for theses useless emails :)
Brunet Eric wrote:
> Rainer Link wrote:
> >> I assume that :
> >> amavis work fine ('make check' is ok)
> >> AvpDaemonClient works fine too (good return code (0) in dirs not
> >> infected) and code 4 for infected file
> >
> >
> > By default, the runtime directory of AMaViS is /var/amavis - please
> >make
> > sure, AvpDaemon "observs" this directory, too.
>
> yes good notice, but kavdaemon don't want to scan /var/amavis,
> howener i add this in defUnix.prf:
> Names=*/home;*/tmp;*/var/tmp;/usr/src;/mnt/cdrom;/var/amavis
> ~~~~~~~~~~~
> it's wrong??
>
> > Set log_level to 5 in /usr/sbin/amavis, so amavis does a very verbose
> > logging. Depining how amavis is configured, amavis logs either via
> > syslog or to /var/amavis/amavis.log
> this is a exim log (debug_level=5) of a mail which is attached the
> EICAR.COM file:
>
> |delivering ericb@??? as ericb using amavis:
> | uid=1039 gid=1031 home=NULL current=/var/spool/amavis
> | auxiliary group list: <none>
> |set_process_info: 16152 delivering 181VeS-0004CU-00 to ericb using |amavis
> |amavis transport entered
> |set_process_info: 16154 reading output from
> |/usr/local/amavis/sbin/amavis -f <${sender_address}> -d |{pipe_addresses}
> |Writing message to pipe
> |amavis transport yielded 0
> ~~~~~~~~~
> why amavis don't detect eicar virus, it work with virus-msg test script!!!
>
> moreover:
> i tried the new version of AVP (4.0.2 intead of 3.0 build 136) and
> AvpDaemonClient return strange error code:
> #/opt/AVP/AvpDaemonClient /tmp
> ....
> /tmp/EICAR.COM infected: EICAR-Test-File
> ...
>
> Return code: 20
> Humm, it is not 4 instead???
>
> i begin to think that exim+amavis+avp will not work a day :(
>
> thank for your patience
>
>
>
>
