Closed
Bug 207045
Opened 22 years ago
Closed 22 years ago
Incorrect date is displayed for messages
Categories
(SeaMonkey :: MailNews: Message Display, defect)
Tracking
(Not tracked)
People
(Reporter: jeremy, Assigned: sspitzer)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3.1) Gecko/20030425
If I send mail using my webmail (squirrelmail), and attempt to pick up the mail
(IMAP) using Mozilla Mail, then the date is ALWAYS 1/01/1970 11:00AM.
However, this is not the date shown in the header of that email. The header is
correct.
Using Outlook Express, this problem cannot be replicated whether the mail is
picked up over IMAP or POP3 -- So I am sure that the problem is with Mozilla
not the webmail end.
Similarly, reading the mail back through the webmail is without fault.
Reproducible: Always
Steps to Reproduce:
1.Send email from webmail (squirrelmail)
2.Retrieve using Mozilla over IMAP
3.
Actual Results:
The date in the main inbox window (top right) is incorrect. It is always
1/01/1970 11:00AM
Expected Results:
Displayed the correct date (as per the header - View/Headers/All)
The only clue I can give is this:
In the message view window (bottom right), using 'normal headers'
(View/Headers/Normal), the header is
For normal (correctly displayed emails): Subject, From, Date, To
However, for the messages displayed incorrectly, the Date field is not
displayed (Subject, From, To only)
I don't know if this helps
Comment 1•22 years ago
|
||
Reporter, there is /no/ date-header in this message ! Unless you mean the 'X-te'
header, but that's not a standard header.
INVALID ?
I've noticed that Mozilla uses the date/time from the sender's Date message
header, whereas OE and other mail clients get the date elsewhere (maybe the
Received header?). For that reason, if the sender's computer's clock is wrong,
that is what is displayed in Mozilla. If there's no date header, I guess this
is what happens.
Comment 3•22 years ago
|
||
*** This bug has been marked as a duplicate of 73565 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•