It's a site-wide implementation, that I've had for atleast the last 18 or so months, without any noticeable problems. I have a feeling it occured when I upgraded to 3.0.1, but I can't pinpoint it. I'm just at a loss as to whats going on..
I did search for any other bayes_* files, just to make sure I wasn't somehow using a different set of tokens than the ones I expected.. and there are no other ones present on my system.


-adam
-----
        "laughter is like music"



on 11/23/2004 9:43 PM Nate Carlson said the following:
On Tue, 23 Nov 2004, Adam Beatham wrote:

Unfortunately, there is nothing that is just jumping out at me. permissions are fine, nothing noticeable in the logs. and the strangest
piece is that it stamps some, but not others..


I tested with a couple pieces of mail that had no BAYES_* test/score in
the headers, and ran it through spamassassin -D, and then they both WERE
stamped with BAYES_* scores..


Are you doing some form of per-user bayes, or global?

Is the receipient for all the messages the same? Do certain senders get bayes tagging, and not others?

--
Nate Carlson <[EMAIL PROTECTED]>   | Phone : (952)943-8700
http://www.real-time.com                | Fax   : (952)943-8500

_______________________________________________
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


_______________________________________________ Visit http://www.mimedefang.org and http://www.canit.ca MIMEDefang mailing list [EMAIL PROTECTED] http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

Reply via email to