Closed Bug 200785 Opened 22 years ago Closed 21 years ago

when message date lies in future it should be changed to "invalid" or current date

Categories

(MailNews Core :: Database, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 194585

People

(Reporter: kriskelvin, Assigned: Bienvenu)

Details

User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3; MultiZilla v1.4.0.3f) Gecko/20030312 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3; MultiZilla v1.4.0.3f) Gecko/20030312 When the message date lies in the future, mozilla stores this unchanged though it cannot be true. Some spam-senders make use of this to have their mails always appear at the top of the date-sorted mail-window. Mozilla should change the date that _must_ be wrong or report it as invalid and sort invalid dates as oldest (the latter is the kmail behaviour) Reproducible: Always Steps to Reproduce: 1. receive a mail with date e.g. in far future 2. watch it sorted first with impossible date unchanged if sorting mail by date 3. Actual Results: impossible message dates are stored unchanged Expected Results: impossible message dates should be marked as invalid or changed to current date Maybe there are some relations to the spam-filter as well.
Summary: when message date lies in future it should be changed to "unvalid" or current date → when message date lies in future it should be changed to "invalid" or current date
This duplicates Bug 194585. As with that bug, I would argue that changing the data or reporting a massaged version of the data is not a good idea.
Whiteboard: DUPEME
*** This bug has been marked as a duplicate of 194585 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: MailNews → Core
Product: Core → MailNews Core
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: DUPEME
You need to log in before you can comment on or make changes to this bug.