Closed Bug 298419 Opened 20 years ago Closed 20 years ago

Message date stripped from POP3 download

Categories

(SeaMonkey :: MailNews: Backend, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: l.d.best, Assigned: Bienvenu)

Details

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

Currently running 7.7 because I hoped "going backwards" might solve problem.  It
first appeared in 1.7.8 when downloaded mail suddenly had only a time shown in
the 'inbox'; when full headers were displayed, there was also no date there
either.  I have uninstalled, reinstalled, uninstalled, installed earlier
version, and still the problem remains.  (I've looked at every "preference" and
"setting" I can find and nothing seems to apply.)

Viewing messages via webmail showed the dates; I thought it might be a change on
ISP server itself, so tried OE ... and OE had no problem keeping and displaying
the full date/time line.  It's Moz ...

Reproducible: Always

Steps to Reproduce:
1.  Get Messages
2.  Look at messages in 'inbox'
3.  See all new messages missing dates 

Actual Results:  
see #3 above

Expected Results:  
The DATE of message should have been part of the message, rather than just a time.
Mozilla mail has 'always' (for as long as I remember at least) hidden the date
part for messages that were sent "today". If you'll check tomorrow, the date
will be there again.

(It's theoretically possible Mozilla 1.7.8 introduced a bug that somehow really
modified the message source to remove the date. If this is the case and view
source on the message (ctrl-u) does not show a Date: header with both date and
time, please reopen and accept my apologies for marking invalid.)
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
Summary: Message date stripped from POP3 download → Message date stripped from POP3 download
You need to log in before you can comment on or make changes to this bug.