--- Nigel Horne <[EMAIL PROTECTED]> wrote:
> On Friday 21 Jan 2005 14:46, N Fung wrote:
> >
> > --- Nigel Horne <[EMAIL PROTECTED]> wrote:
> >
> > > On Friday 21 Jan 2005 14:15, N Fung wrote:
> > > > --- Nigel Horne <[EMAIL PROTECTED]> wrote:
> > > >
> > > > > Presumably you ran clamd with 0.80. Please
> start
> > > > > clamd as you did
> > > > > with 0.80, disable --internal, restart
> > > clamav-milter
> > > > > and report the results.
> > > >
> > > > As per your instructions, I did:
> > > >
> > > > Started clamd first and ran clamav-milter
> withOUT
> > > > --internal. Result: infected mail sent to the
> > > > quarantine address. It worked as in 0.80.
> Just
> > > what I
> > > > wanted.
> > > >
> > > > >
> > > > > Also, try without the -o option but with
> > > --internal.
> > > >
> > > > That didn't work. Infected mail was rejected.
>
> > > > /var/log/maillog said:
> > >
> > > In that case it DID work, the infected mail was
> > > intercepted.
> >
> > OK. It worked. I guess the quarantine address has
> to
> > be somewhere "outside" if --internal is active?
>
> No, the -o option will always block locally created
> emails.
I'm sorry if I wasn't clear about this; when I tested
it with these flags:
-HNPCl --max-children=5
--quarantine=quart<localdomain>
Note that -o was NOT used.
The infected mail was NOT delivered to the local user
user "quart." The infected mail was discarded.
Thanks.
N.
__________________________________
Do you Yahoo!?
Yahoo! Mail - Find what you need with new enhanced search.
http://info.mail.yahoo.com/mail_250
_______________________________________________
http://lists.clamav.net/cgi-bin/mailman/listinfo/clamav-users
