=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am training spamassassin and for right now, just let it tag spam but sill=
=20
pass it on to my client.  Several times now I have had email from cox.net=20
tagged as spam.  One was identified from the sender as sent via the web mai=
l=20
interface.  I can train, of course, but when I tell postfix to shovel the=20
spam away, I may start missing cox.net email that I don't want to miss.

Does Cox know or care that their email gets these tags (from a list email j=
ust=20
minutes ago):

SPAM: ----------------------------------------------------------------------
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: See http://spamassassin.org/tag/ for more details.
SPAM:=20
SPAM: Score: 5.00
SPAM: Threshold: 5
SPAM:=20
SPAM: INVALID_DATE       (1.5 points)  Invalid Date: header (not RFC 2822)
SPAM: NO_REAL_NAME       (1.3 points)  From: does not include a real name
SPAM: SPAM_PHRASE_00_01  (0.8 points)  BODY: Spam phrases score is 00 to 01=
=20
(low)
SPAM:                    [score: 0]
SPAM: SUPERLONG_LINE     (0.0 points)  BODY: Contains a line >=3D199 charac=
ters=20
long
SPAM: KNOWN_MAILING_LIST (-0.1 points) Email came from some known mailing l=
ist=20
software
SPAM: FORGED_RCVD_TRAIL  (2.0 points)  trail of Received: headers seems to =
be=20
forged
SPAM: AWL                (-0.5 points) AWL: Auto-whitelist adjustment
SPAM:=20

Kind of funny, I guess.  I'd complain if I were a Cox customer.

Alan
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/1q/tUIl18h7/dy4RAhDcAJ9zyYL1JDytThA6fXBLE/4qoWlAPgCgtYyE
X5ypJ7Rr8BmhjOBD24OYup8=3D
=3DtWbR
=2D----END PGP SIGNATURE-----