Closed
Bug 276940
Opened 20 years ago
Closed 20 years ago
Date of message from 1/1/1970
Categories
(Thunderbird :: Mail Window Front End, defect)
Tracking
(Not tracked)
People
(Reporter: roger, Assigned: mscott)
Details
Hi there. I'd *some* new message comes in with correct header info but it show itself as from 1/1/1970 08:00. I found it quite similar to the one with 12/31/1969. Is there any resolution/explaination to this? I am using IMAP from a linux email server running qmail. Even the syslog sent from the same server has the same date problem. Below is the header of one of the messages. I'd replaced the IP with aaa.bbb.ccc.ddd to avoid violating the company policy. Sorry for that. *** Subject: 「普通話拼音標注工具」工作坊 From: CPS-Course <course@cps.com.hk> To: CPS-Course <course@cps.com.hk> X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <HAA7MMZZAYcDkt@mail.seeder.net.tw> Delivered-To: xxxx@yyyy.com Received: (qmail 14161 invoked by uid 404); 2 Dec 2004 15:14:02 -0000 Received: from HAA7MMZZAYcDkt@mail.seeder.net.tw by by uid 404 with Dolphinia Email Engine (. Clear:. Processed in 0.717602 secs); 02 Dec 2004 15:14:02 -0000 Received: from unknown (HELO ?aaa.bbb.ccc.ddd?) (aaa.bbb.ccc.ddd) by 0 with SMTP; 2 Dec 2004 15:14:01 -0000 Received: from [218.189.131.21] by [aaa.bbb.ccc.ddd] via smtpd (for [aaa.bbb.ccc.ddd]) with ESMTP; Thu, 2 Dec 2004 22:59:41 +0800 Received: from pavo by sky.seed.net.tw with SMTP id mJqw4gPbgmsqVLPakU; Thu, 02 Dec 2004 23:13:58 +0800 Message-ID: <QN7@yahoo.com> X-Mailer: Ou1sx7FdvXQ1ryicy526P Content-Type: text/plain; Content-Transfer-Encoding: Quoted-Printable X-Priority: 3 X-MSMail-Priority: Normal X-Dolphinia-Email-Engine-: added fake MIME-Version header MIME-Version: 1.0 ***
Comment 1•20 years ago
|
||
Altho the mail has plenty of correct dates in the Received headers, it does not have a Date: header. *** This bug has been marked as a duplicate of 73565 ***
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•