RE: Invalid Date header - Date not RFC 2822

I think you to post the actual email somewhere where it won't be mangled by typos or whatever and then post the link for our review. We can run the message through our SpamAssassin systems to see the result.

Hold on! If you are USING the affected system, then since you replied to me directly instead of through the list, I have your message headers, and they went through my SpamAssassin, and did not trigger the INVALID_DATE rule.

Your headers were:

X-Spam-Checker-Version: SpamAssassin 3.1.7 (2006-10-05) on mail.visioncomm.net
X-Spam-Level:
X-Spam-Status: No, score=0.0 required=5.0 tests=AWL=-0.001,BAYES_50=0.001

        autolearn=no version=3.1.7
X-Envelope-From:<tlepiane@logisticssoftware.com> Received: from smtp104.rog.mail.re2.yahoo.com [206.190.36.82] by mail.visioncomm.net
  (SMTPD32-8.15) id A057105E0080; Fri, 31 Aug 2007 11:14:31 -0400 Received: (qmail 346 invoked from network); 31 Aug 2007 15:14:30 -0000 Received: from unknown (HELO tlepiane)
(tlepiane1215@rogers.com@99.245.199.125 with login)   by smtp104.rog.mail.re2.yahoo.com with SMTP; 31 Aug 2007 15:14:30 -0000 X-YMail-OSG:
XbW59_gVM1nvMY0rJi2tqABT_L2Jbu8isr.CVezWeeHCZ7R2zFUn68g5txp0maaAFg-- From: "Tony Le Piane" <tlepiane@logisticssoftware.com> To: "'Dan Barker'" <dbarker@visioncomm.net> References: <003101c7ebde$d12aab10$7dc7f563@tlepiane> <200708311106655.SM02240@dan>
Subject: RE: Invalid Date header - Date not RFC 2822 Date: Fri, 31 Aug 2007 11:14:28 -0400
Message-ID: <003f01c7ebe1$a1027410$7dc7f563@tlepiane> MIME-Version: 1.0
Content-Type: text/plain;

        charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138 Thread-Index: Acfr26RJaVTTLagcRu6TVtg75WdrTgAAMOFgAAECJXAAADKc8A== In-Reply-To: <200708311106655.SM02240@dan> X-IMail-Queuename:<3057105e00803aca>
X-RCPT-TO: <dbarker@visioncomm.net>
Status: U
X-UIDL: 488427562 and the Date: header is correct and the rule did not fire. The trick now is to get the reporting server's copy of the headers and make them fix their issue - assuming they actually do have an invalid date.

Good luck with that!

Dan

Do you need help?
In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related spamassassin.apache.org Links users Request more information about Pantek

-----Original Message-----
From: Tony Le Piane [mailto:tlepiane@logisticssoftware.com] Sent: Friday, August 31, 2007 11:14 AM
To: 'Dan Barker'
Subject: RE: Invalid Date header - Date not RFC 2822

Hi Dan,

That was a typo when I copied .. its actually -0400

I have compared it to other SMTP headers and don't see any differences. Also looked at RFC 2822 and we comply.

As mentioned we been running this services for over 5 years and no all of a sudden we get classified as spam. I don't get it.

Really appreciate your reply.

Best Regards,

Tony

Do you need more help?
In addition to our free technical library, Pantek provides professional IT services to companies who utilize Open Source software: Learn more about Pantek's Technical Support offerings Place an order for 24/7/365 Technical Support here Learn more about Pantek, who we are, and what we do Chat with a Live Operator Related spamassassin.apache.org Links users Request more information about Pantek

-----Original Message-----
From: Dan Barker [mailto:dbarker@visioncomm.net] Sent: August 31, 2007 11:06 AM
To: 'Tony Le Piane'
Subject: RE: Invalid Date header - Date not RFC 2822

Well, the DATE header is incomplete. You could look up RFC 2822 (unless that's too much work) or just look at the date (and compare it to incoming date records from other SMTP servers). You'll see the trailing two zeros are missing (assuming you are in the Eastern Time Zone).

hth

Dan

-----Original Message-----
From: Tony Le Piane [mailto:tlepiane@logisticssoftware.com] Sent: Friday, August 31, 2007 10:54 AM
To: users@spamassassin.apache.org
Subject: Invalid Date header - Date not RFC 2822

> We have been running our service for almost 5 years and this problem
started
> with this ISP client of yours (TELEBEC) last week after they upgraded
their
> servers to the latest version of SPAMASSASSIN I'm told. We are now being
> considered spammers.
>
>
>
> Firstly I have been told that it is a date problem (Invalid Date - not
> RFC
> 2822) which no one on their end can seem to give me a straight answer.
Now
> they are telling me to go to the SpamAssassin web-site to determine
> what

the
> problem is.
>
>
>
> When I run my email through
> http://emailcheck.activecampaign.com/index.php I get the following
> error which seems to be the problem but yet I can't see this anywhere
> in

the
> header or body of my email: "1.8 INVALID_DATE Invalid Date:
> header (not RFC 2822)"
>
>
>
>
>
> My Headers are:
>
>
>
> Received: from mail.hekru.net [66.185.198.204] by mail.hekru.net
>
> (SMTPD-8.22) id AE31015C; Fri, 24 Aug 2007 16:23:13 -0400
>
> To: <support@logisticssoftware.com>
>
> From: RNS Express <rnsexpress@logisticssoftware.com>
>
> Date: Fri, 24 Aug 2007 16:19:26 -0400
>
> Subject: CCN - 8661019249 Goods Released
>
> Content-Type: text/html; charset=UTF-8
>
> Message-Id: <200708241623453.SM01356@mail.hekru.net>
>
> X-RCPT-TO: support@logisticssoftware.com
>
> Status: U
>
> X-UIDL: 486276248
>
> X-IMail-ThreadID: 3e3101aa0000e806
>
>
>
>
>
> My Body is:
>
>
>
> <html lang="fr"><font size=7 face="Free 3 of
9">*8661019249*</font><br><font
> size=2 face="Microsoft Sans Serif">8661019249</font><br><br><font
> size=7 face="Free 3 of 9">*90548070083893*</font><br><html><font
> size=2 face="Microsoft Sans
> Serif">90548070083893</font><br><br><body><font
size=2
> face="Courier New,Courier,Mono">Canada Customs Response/Release
Notification
> Report<br><br>Release Date:&nbsp;&nbsp;&nbsp;2007/08/24<br>Release
> Time:&nbsp;&nbsp;&nbsp;16:07<br>Service Option:&nbsp;257&nbsp;RMD EDI
>
(Post-Arrival)<br>Transaction:&nbsp;&nbsp;&nbsp;&nbsp;90548070083893<br>Carg
> o Number:&nbsp;&nbsp;&nbsp;8661019249<br>Release
> Office:&nbsp;497&nbsp;Toronto International Airport (Pearson)<br>Sub
> Location:&nbsp;&nbsp;&nbsp;4298&nbsp;TOTAL EXPRESS INTERNATIONAL
> FREIGHT FORWARDING <br><br>Release
> Code:&nbsp;&nbsp;&nbsp;4&nbsp;-&nbsp;Goods
> Released<br><br></font></body></html>
>
>
>
>
>
> I have attached an example of our email that is now being considered spam.
>
>
>
>
>
> Thank-you for any possible guidance and resolution.
>
>
>
> Best Regards,
>
> Tony Le Piane
> Logistics Software Corp.
> (905) 881-0320
> www.logisticssoftware.com <BLOCKED::http://www.logisticssoftware.com/>
>
>
>
> The information contained in this communication and its attachment(s)
> is intended only for the use of the individual to whom it is addressed
> and may contain information that is privileged, confidential, or
> exempt from disclosure. If the reader of this message is not the
> intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this communication is strictly prohibited.
> If you have received this communication in error, please notify
> info@logisticssoftware.com and delete the communication without
> retaining

any copies.
>
> Thank you.
Received on Fri Aug 31 11:31:10 2007