SpamAssassin and cox.net email

>
> If spamassassin maintains a personal database (training info), you need
> to try re-training it. I don't think there is something that COX can do
> about it. Have you tried re-training it? I don't know how spamassassin
> works though.

Yep, that is what I am doing, training it.

However, my point was that email from Cox has the errors I reported.
Errors coming from them and their web client or host or where ever. These
errors:

INVALID_DATE       (1.5 points)  Invalid Date: header (not RFC 2822)
NO_REAL_NAME       (1.3 points)  From: does not include a real name
FORGED_RCVD_TRAIL  (2.0 points)  trail of Received: headers seems to be
forged

No real name is not a big deal but the other two shold be non-issues for a
correctly programmed email client, I would think.

If I were a Cox customer, would I want the email I send to have these
problems? Would I want the email I send to possibly be lost to /dev/null
because other ISPs think it is spam?

Anyway, it is really not much of an issue for me. I don't know why I
worry about it since I am not a Cox customer. I'll just see if I can
train around it.

Alan