Len,
> good point, was su'd to root
>
> > If not - and
> >I suspect you're not - different per-user SA settings may be the source
> >of these differences. What score do you get when you run spamc on that
> >same file as the amavis user?
>
> I changed the file to vscan:vscan, su'd to vscan and c
Len Conrad wrote:
>> [snip]
> I changed the file to vscan:vscan, su'd to vscan and command line
> spamassassin returned:
>
> Content analysis details: (6.8 points, 5.0 required)
what tests where hit?
also, what results do you see if you reinject the message into
amavisd-new? it is possible t
On Tue, Jul 29, 2008 at 05:00:53PM -0500, Len Conrad wrote:
> >On Tue, Jul 29, 2008 at 02:36:36PM -0500, Len Conrad wrote:
> > > >We're trying to replace a Windows anti-spam on the mailbox servers
> > > >with amavisd/sa/clam on the front-end mx.
> > > >
> > > >We are running in tandem both now in t
>On Tue, Jul 29, 2008 at 02:36:36PM -0500, Len Conrad wrote:
> > >We're trying to replace a Windows anti-spam on the mailbox servers
> > >with amavisd/sa/clam on the front-end mx.
> > >
> > >We are running in tandem both now in the amavis/sa/clam testing phase.
> > >
> > >The backend mail content-
On Tue, Jul 29, 2008 at 02:36:36PM -0500, Len Conrad wrote:
> >We're trying to replace a Windows anti-spam on the mailbox servers
> >with amavisd/sa/clam on the front-end mx.
> >
> >We are running in tandem both now in the amavis/sa/clam testing phase.
> >
> >The backend mail content-scanner is sti
>We're trying to replace a Windows anti-spam on the mailbox servers
>with amavisd/sa/clam on the front-end mx.
>
>We are running in tandem both now in the amavis/sa/clam testing phase.
>
>The backend mail content-scanner is still catching too many true
>spams that get past amavis.
>
>We uploaded t
We're trying to replace a Windows anti-spam on the mailbox servers
with amavisd/sa/clam on the front-end mx.
We are running in tandem both now in the amavis/sa/clam testing phase.
The backend mail content-scanner is still catching too many true
spams that get past amavis.
We uploaded the spams
We're trying to replace a Windows anti-spam on the mailbox servers
with amavisd/sa/clam on the front-end mx.
We are running both now. the backend mail scanner is still catching
too many true spams.
We uploaded the backend spams to the mx and run them through spamc,
with these results:
705240
