On Fri, Jan 10, 2003 at 11:57:43AM -0500, Mark T. Valites wrote:
> I dropped 'use_terse_report = 0' into my personal user_prefs file, but it
> didn't seem to make any difference.
that's not the one that'll solve your problem. it's a combination of
the trifecta. See http://spamassassin.taint.org/
On Fri, 10 Jan 2003, Ross Vandegrift wrote:
> On Fri, Jan 10, 2003 at 10:34:11AM -0500, Mark T. Valites wrote:
> > > This looks like an HTML mail with the body report enabled. This is
> > > what happens when you do that (the body report isn't HTML, it's text,
> > > so your browser/MUA munges the
On Fri, Jan 10, 2003 at 10:34:11AM -0500, Mark T. Valites wrote:
> > This looks like an HTML mail with the body report enabled. This is
> > what happens when you do that (the body report isn't HTML, it's text,
> > so your browser/MUA munges the report). ;)
It could be. It also looks like what ha
On Fri, 10 Jan 2003, Theo Van Dinter wrote:
> On Fri, Jan 10, 2003 at 09:50:59AM -0500, Mark T. Valites wrote:
> > SPAM: Start SpamAssassin results
> > --
> > SPAM: This mail is probably spam. The original message has been altered
> > SPAM: so you can reco
On Fri, Jan 10, 2003 at 09:50:59AM -0500, Mark T. Valites wrote:
> SPAM: Start SpamAssassin results
> --
> SPAM: This mail is probably spam. The original message has been altered
> SPAM: so you can recognise or block similar unwanted mail in future. SPAM:
>
I've been doing some testing lately before I implement spamassassin here
site-wide. I've been extremely happy with the results so far. In my
testing, I was lucky enough to have a good chunk of our department
volunteer/ get suckered into testing it out for me. I set all of them up
with .procmailr
