Closed Bug 292165 Opened 20 years ago Closed 19 years ago

Wrong time/date reported by Thunderbird

Categories

(Thunderbird :: General, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: jeremy, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Sometimes I get response emails that have a date before the original was sent.
(i.e. I sent email on 4-27-05, I get a response on 4-26-05)

Reproducible: Couldn't Reproduce

Steps to Reproduce:
1.Sort email by date
2.notice that some email is dated wrong
3.



Expected Results:  
Given the right date for the incoming email.

XP Pro, ZoneAlarm, Thunderbird 1.0.2, Firefox 1.0.3, Internet time synced with
time.windows.com, DLink DI 514 router synced with time.nist.gov
What's the date header in the incoming mail ?
use Message source [ctrl+U] to see the header.
(In reply to comment #1)
> What's the date header in the incoming mail ?
> use Message source [ctrl+U] to see the header.
> 

From - Wed Apr 27 10:50:12 2005
X-Account-Key: account3
X-UIDL: 1aec2d75ac9584ae37a6fef58f33f239
X-Mozilla-Status: 0213
X-Mozilla-Status2: 00000000
Return-path: <daniel@thecpuguys.net>
Envelope-to: jeremy@thecpuguys.net
Delivery-date: Wed, 27 Apr 2005 10:05:51 -0400
Received: from cpu by mainstream.navigatoris.us with local-bsmtp (Exim 4.50)
	id 1DQnAf-0007Jt-En
	for jeremy@thecpuguys.net; Wed, 27 Apr 2005 10:05:50 -0400
Received: from [66.182.221.91] (helo=nawlbu0iq9inv8)
	by mainstream.navigatoris.us with smtp (Exim 4.50)
	id 1DQnAf-0007Hz-3O
	for jeremy@thecpuguys.net; Wed, 27 Apr 2005 10:05:45 -0400
Message-ID: <001a01c54a69$0843f4e0$6400a8c0@nawlbu0iq9inv8>
From: "daniel white" <daniel@thecpuguys.net>
To: "The CPU Guys" <jeremy@thecpuguys.net>
References: <001501c54a24$bf67dbe0$6400a8c0@nawlbu0iq9inv8>
<426F2D49.30400@thecpuguys.net>
Subject: Re: Fw: Web Completion
Date: Tue, 26 Apr 2005 09:05:39 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on 
	mainstream.navigatoris.us
X-Spam-Level: 
X-Spam-Status: No, score=0.3 required=5.0 tests=AWL,DATE_IN_PAST_24_48 
	autolearn=no version=3.0.2

I thought what I'd do was, I'd pretend I was one of those deaf-mutes.



----- Original Message -----
From: "The CPU Guys" <jeremy@thecpuguys.net>
To: "daniel white" <daniel@thecpuguys.net>
Sent: Wednesday, April 27, 2005 1:12 AM
Subject: Re: Fw: Web Completion


> 
>
> 
> I thought what I'd do was, I'd pretend I was one of those deaf-mutes.
> 
> 
> 
>
> --Jeremy
>
> daniel white wrote:
>
> >
> > ----- Original Message -----
> > *From:* fortie_a@bellsouth.net <mailto:fortie_a@bellsouth.net>
> > *To:* daniel@thecpuguys.net <mailto:daniel@thecpuguys.net> ; The CPU
> > Guys <mailto:jeremy@thecpuguys.net>
> > *Sent:* Tuesday, April 26, 2005 9:07 PM
> > *Subject:* Web Completion
> >
> > 
> > 
> > 
> > 
> > I thought what I'd do was, I'd pretend I was one of those deaf-mutes.
> >
> > 
> >
> >
> > __________ NOD32 1.1079 (20050426) Information __________
> >
> > This message was checked by NOD32 antivirus system.
> > http://www.nod32.com
>
>I thought what I'd do was, I'd pretend I was one of those deaf-mutes.
> --
> Best regards,
> Jeremy Baham
> The CPU Guys
> 
>
>
>




__________ NOD32 1.1079 (20050426) Information __________

This message was checked by NOD32 antivirus system.
http://www.nod32.com
(In reply to comment #1)
> What's the date header in the incoming mail ?
> use Message source [ctrl+U] to see the header.
> 

(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7)
Gecko/20050414 Firefox/1.0.3
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7)
Gecko/20050414 Firefox/1.0.3
> 
> Sometimes I get response emails that have a date before the original was sent.
> (i.e. I sent email on 4-27-05, I get a response on 4-26-05)
> 
> Reproducible: Couldn't Reproduce
> 
> Steps to Reproduce:
> 1.Sort email by date
> 2.notice that some email is dated wrong
> 3.
> 
> 
> 
> Expected Results:  
> Given the right date for the incoming email.
> 
> XP Pro, ZoneAlarm, Thunderbird 1.0.2, Firefox 1.0.3, Internet time synced with
> time.windows.com, DLink DI 514 router synced with time.nist.gov

(In reply to comment #1)
> What's the date header in the incoming mail ?
> use Message source [ctrl+U] to see the header.
> 

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.