[EMAIL PROTECTED] wrote:
User-Agent: Mutt/1.4.2.1i

Yeah, I saw that after the fact...


But the date looks fine in Pine...

The NNTP interface in TBird shows the bad date and this weirdness

From: [EMAIL PROTECTED] (Unknown Sender)

too.  Now that I reread the headers, I think this hop is the problem:

Received: from h-170.pert.com.ar (HELO alerce1-mr.pert.com.ar) (200.68.65.170)
    by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Fri, 28 Jul 2006 
04:42:47 -0700
Received: from morticia.pert.com.ar ([192.168.1.7]:51104 "EHLO morticia")
        by alerce1-mr.pert.com.ar with ESMTP id S1084509AbWG1Lms (ORCPT
        <rfc822;[email protected]>); Fri, 28 Jul 2006 08:42:48 -0300


Note that the *morticia.pert.com.ar* machine time is _after_ the _h-170.pert.com.a_ time (when adjusted for timezone). Apparently TBird is actually reading all of the Received: headers and freaking out because the clock on morticia is fast (rather than just using the Date: field).

I guess I'll go checkout Tbird's bugtracker and see if anyone has reported this already...

John

--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4501 Forbes Boulevard
Suite H
Lanham, MD  20706
301-459-3366 x.5010
fax 301-429-5748

Reply via email to