555135 - Message date has incorrect timezone offset when UTC given as date base for Date header

Status: RESOLVED INCOMPLETE

(Thunderbird :: Folder and Message Lists, defect)

Description

[mozilla]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.2) Gecko/20100316 Firefox/3.6.2
Build Identifier: 3.0.3 /3.1b1

when message header is, for example, "Date: Fri, 26 Mar 2010 00:10:51 UTC"
the date displays in Folder Lists and Message Reader as 12:10 am, and not with the correct timezoneOffset, as it properly does when there's a +- offset in the Date field, or GMT is used in place of UTC


Reproducible: Always

Comment 1

[Ludovic Hirlimann [:Usul]]

Can you attach an example email here please ?

Comment 2

[WADA:World Anti-bad-Duping Agency]

> "Date: Fri, 26 Mar 2010 00:10:51 UTC"

Does it mean header of "string in place of UTC == 'UTC'?
If yes, where can we see description of "UTC is valid string as time zone"?
I couldn't find "UTC" in definition of obs-zone at 4.3. Obsolete Date and Time of RFC 2822.
> http://tools.ietf.org/html/rfc2822#section-4.3
> 4.3. Obsolete Date and Time
If no, which valid string defined by RFC 2822 is really used in the place of UTC of mail header?

Comment 3

[mozilla]

(In reply to comment #1)
> Can you attach an example email here please ?

Delivered-To: **@****.com
Received: by 10.229.73.194 with SMTP id r2cs237287qcj;
        Tue, 6 Apr 2010 18:06:29 -0700 (PDT)
Received: by 10.141.4.9 with SMTP id g9mr6316338rvi.232.1270602386626;
        Tue, 06 Apr 2010 18:06:26 -0700 (PDT)
Return-Path: <****@vm.vonage.com>
Received: from mail-ob-04.kiad0.s.vonagenetworks.net (mail-ob-04.kiad0.s.vonagenetworks.net [69.59.229.101])
        by mx.google.com with ESMTP id q10si9458394rvp.73.2010.04.06.18.06.24;
        Tue, 06 Apr 2010 18:06:25 -0700 (PDT)
Received-SPF: pass (google.com: domain of ****@vm.vonage.com designates 69.59.229.101 as permitted sender) client-ip=69.59.229.101;
Authentication-Results: mx.google.com; spf=pass (google.com: domain of ****@vm.vonage.com designates 69.59.229.101 as permitted sender) smtp.mail=****@vm.vonage.com; dkim=pass (test mode) header.i=@vonage.com
Message-Id: <[e-mail]>
Received: from nsash03.kiad0.s.vonagenetworks.net (nsash03.kiad0.s.vonagenetworks.net [69.59.237.16])
	by mail-ob-04.kiad0.s.vonagenetworks.net (Postfix) with ESMTP id 0A14C27A2FC
	for <**@****.com>; Wed,  7 Apr 2010 01:06:23 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=vonage.com;
	s=vonagedkim; t=1270602383; i=@vonage.com;
	bh=nXJgetADV/kG4PQsLn8i08uD055Bp0nK4cEhzljBogM=;
	h=From:X-Vonage-UUID;
	b=M4+XK1aRaU6/tMqZHqFvbYvBVKXfCvCEjHYTjZr95Xdmd1M8KVS7eGNFX7ktw468f
	 82NBfvjp11QW/DM4L/DOjDdIn3BtfnrXWdS6/C2IrP2oWF1+jowGcw7VagSzfQIhgk
	 7jup5VT/rx4jQvmQsFrZz+e2JRB6KzlVBKBSW+Kw=
From: *********@vm.vonage.com
To: **@****.com
Subject: You have received a new voicemail message
Date: Wed, 07 Apr 2010 01:06:23 UTC
X-Mailer: UTStarcom
X-UTStarFlags: 00000000001010010000000000000000000000000000
X-UTStarAlias: 
X-UTStarNameAnn: 
X-UTStarNameSrv: 
X-UTStarDrpt: 
X-UTStarFileName: 32#4d3503a
MIME-Version: 1.0

Comment 4

[mozilla]

Attachment: Shows at UTC/GMT, and not with timezone offset (-6) or (360)

Comment 5

[WADA:World Anti-bad-Duping Agency]

> Date: Wed, 07 Apr 2010 01:06:23 UTC

Have you READ a section of a RFC I pointed?
Where can we see statements about "UTC is valid string as time zone in Date: header of e-mail"?
Does your problem occur even with next Date: header?
> Date: Wed, 07 Apr 2010 01:06:23 UT
> Date: Wed, 07 Apr 2010 01:06:23 GMT
> Date: Wed, 07 Apr 2010 01:06:23 PST
> Date: Wed, 07 Apr 2010 01:06:23 PDT

By the way, "Received" column for timestamp in Received: header is alreay implemented in case of malformed Date: header or no Date: header. If IMAP, see bug 402594.

Comment 6

[mozilla]

Those all work correctly (however, I'm not sure I've seen a UT occurrence)

Comment 7

[WADA:World Anti-bad-Duping Agency]

> (however, I'm not sure I've seen a UT occurrence)

I didn't see UT since my first use of email. It was first time I was aware of "UT" in RFC 2822, even though I read some sections of RFC 2822, one of most basic mail related RFC, many times.

Do you agree on closing as INVALID?

Comment 8

[mozilla]

Invalid? while UT may be rare, UTC is quite common and clearly being parsed wrong

Comment 9

[WADA:World Anti-bad-Duping Agency]

Have you READ and UNDERSTAND a section of a RFC which I pointed?
Term of UTC is very commonly used, but it's not defined as a valid string for time-zone in Date: heder of e-mail. Valid string defined by RFC2822 as quivallence to +0000 is GMT and UT.

Could you ask developes of RFC to add "UTC" to obs-zone(==obsolete zone) first, or propose new RFC for "UTC" as time zone in Date: header first, please.

If you believe quirks for invalid string of UTC is mandatry feature of mailer, and if you believe such quirks is very very important for many many users, please open enhancement request bug(Severity=enhancement), after requesting bug fix of mailer which mail sender uses(if you know vendor of the mailer or company who uses the mailer/mail system), please.

Comment 10

[WADA:World Anti-bad-Duping Agency]

Bug 333547 was request of quirks for UTC of RSS feeds.
Setting dependency to it for ease of tracking.

Comment 11

[Wayne Mery (:wsmwk)]

can you reproduce this using a current version of thunderbird?

if you are unable to reproduce, please close by setting stats to resolved, and resolution to WORKSFORME or another appropriate setting.

If you are able to reproduce, add new details, and a testcase if one does not already exist in the bug report.

Comment 12

[Joshua Cranmer [:jcranmer]]

RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error please respond to this bug with your reasons why.