I'd be more concerned about the BAYES_99 hit than the FRT_PRICE.  If this mail is not spam then bayes shouldn't be tripping on it.

You can run these messages through the bayes training process to get the bayes score lowered.

You could also make a whitelist_from_rcvd entry in local.cf


Brent Gardner
that is interesting. I saw that but interpeted what I was looking at as
the BAYES_99   added a score of 1 , where as the FRT_PRICE added 3.n.

so by the 'bayes training process' you are referring to the [email protected] & [email protected]
yes?
so an action step would be to have mr. price forward the `good' but marked ***SPAM*** email to
the account [email protected].

regarding your suggestion: "   whitelist_from_rcvd entry in local.cf    "
i would put in my /etc/mail/spamassassin/local.cf
a line like
whitelist_from_rcvd *@thatOutsideDom.com
yes?

Do you have any thoughts of why InsidePerson_1 can volley emails back and forth with OutsidePerson  without a ***SPAM***  but as soon as InsidePerson_1 emails to  OutsidePerson  with InsidePerson_2 it is tagged ***SPAM***
( and only this one account - InsidePerson_2 is Mr. Price )
that is so challenging to me.
could there be something about his account?
could the AWL be corrupt?

Thanks for all the input , it is always rewarding to share & hear from others.

jS

I see talk of "running a  message through SA with debugging turned on"
but I have not found how one does that.

ps
I found this - which does not get "me" any closer to a solution
0 down vote accepted

BAYES_99 is a statistical component of SpamAssasin. It is using some sort/variation of Naive Bayes which has (to keep it simple) some sort of probability saying that some word/token is likely to be spam or not to be spam.

In "math" these could be expressed like this:

P(Class_Spam | Email)
P(NotClass_Spam | Email)

Transformations lead to e.g. this equation:

enter image description here



Yikes ; I am just trying to admin a mail server not build a time machine :)

Reply via email to