SpamAssassin and cox.net email

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Sanjay Darisi
Date:  
Subject: SpamAssassin and cox.net email
This is a multi-part message in MIME format.
--------------000503080807040501030803
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

wrote:

>>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
>
>
>
>---------------------------------------------------
>PLUG-discuss mailing list -
>To subscribe, unsubscribe, or to change you mail settings:
>http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>
>
>

Oops...my bad...you are correct. I didn't read your first email well. If
it's the COX web client that is not doing its job, hmm... thats bad. How
about my email? I use mozilla client though.

Thanks,
Sanjay.


--------------000503080807040501030803
Content-Type: text/html; charset=us-ascii
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta http-equiv="Content-Type" content="text/html;charset=ISO-8859-1">
  <title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
<a class="moz-txt-link-abbreviated" href="mailto:alandd@consultpros.com"></a> wrote:<br>
<blockquote type="cite"
 cite="mid34308.64.105.64.37.1071099063.squirrel@68.165.192.154">
  <blockquote type="cite">
    <pre wrap="">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.
    </pre>
  </blockquote>
  <pre wrap=""><!---->
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



---------------------------------------------------
PLUG-discuss mailing list - <a class="moz-txt-link-abbreviated" href="mailto:PLUG-discuss@lists.plug.phoenix.az.us"></a>
To subscribe, unsubscribe, or to change you mail settings:
<a class="moz-txt-link-freetext" href="http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss">http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss</a>

</pre>
</blockquote>
Oops...my bad...you are correct. I didn't read your first email well.
If it's the COX web client that is not doing its job, hmm... thats bad.
How about my email? I use mozilla client though. <br>
<br>
Thanks,<br>
Sanjay.<br>
<br>
</body>
</html>

--------------000503080807040501030803--