On Fri, 16 Jan 2004, Matt Kettler wrote:
> Hmm, does formail wind up generating a new set of message headers?
It must modify them, because your suggestion (spamassassin -t < tmp)
generates the same results as previously. Using the bounce function
of Pine also generates new headers--I had notice
At 07:56 AM 1/16/04 -0500, Theodore Heise wrote:
cat tmp | formail -s sendmail theo
Apparently this must process the mail differently than the normal
receiving routine. If I use "bounce" in Pine, the Bayes results are
approximately the same as before adding the new rules. I don't
quite underst
On Thu, 15 Jan 2004, Theodore Heise wrote:
> > first, run spamassassin --lint
> >
> > sounds like there's a typo in the rules you downloaded and SA is puking on
> > your configfiles.
>
> Matt, thanks very much. There were several errors, I fixed them and
> now it runs without complaints. Howev
On Thu, 15 Jan 2004, Matt Kettler wrote:
> At 08:01 PM 1/15/2004, Theodore Heise wrote:
> >My problem is that now Bayes doesn't seem to be working right, as if
> >SA is ignoring my learned tokens? It also seems to be now missing
> >some rules that I presume are default (e.g., MSGID_FROM_MTA_SHO
At 08:01 PM 1/15/2004, Theodore Heise wrote:
My problem is that now Bayes doesn't seem to be working right, as if
SA is ignoring my learned tokens? It also seems to be now missing
some rules that I presume are default (e.g., MSGID_FROM_MTA_SHORT,
PRIORITY_NO_NAME, and CLICK_BELOW) The results for
Okay, I know I'm missing something that should be obvious, but I've
scoured the documentation on the SA website, in the source tree, and
perldoc Mail::SpamAssassin, and been unable to understand my problem.
I'm running spamassassin (not spamd) v 2.61 system-wide on a single
user Slackware 9.1 box
