200802 - "delete junk after N days" uses message's Date (deletes msgs dated in past, keeps around msgs from future)

Status: RESOLVED DUPLICATE of bug 318897

(MailNews Core :: Filters, defect)

Description

[Ere Maijala (slow)]

There's a problem with the junk mail filters. If a newly received message is
classified as spam and its date is old enough (in error or in case I haven't
checked mail for so long time), the automatic deletion might delete it right
away. So, the message could be deleted without the user having any chance to
notice it. No problem with real spam, but false positives happen. If the user is
using immediate deletion, this could cause real dataloss. 

I think we should use the date received (by Mozilla) when checking if a message
should be delete from junk mail folder. This is the only valid date here. I
wouldn't want spam with a future date to keep hanging around either.

Comment 1

[(not reading, please use [e-mail] instead)]

mass re-assign.

Comment 2

[Mike Cowperthwaite]

Bugs about using 'received' date:
bug 123786: requests sorting by received
bug 166254: requests sorting by received (probably a dupe)
bug 190337: requests that Mozilla add a Received: header to d/l's messages

Comment 3

[Mike Cowperthwaite]

(In reply to comment #0)
> So, the message could be deleted without the user having any chance to
> notice it. No problem with real spam, but false positives happen. If the
> user is using immediate deletion, this could cause real dataloss. 

This is a possibility in several cases: the sender might have the calendar set wrong, or, the user could be away for a while, and downloads the new message after the period has expired.

Even better than the Received date (which means different things under IMAP and POP) you might considere adding an   X-Mozilla-Junked-Date  header for the moment when the message is actually detected as junk; but of course, no matter what scheme is put in place, an automated expiration always has the possibility for dataloss.


> I wouldn't want spam with a future date to keep hanging around either.

I'm about to dupe over a message about exactly that, so updating summary.

Comment 4

[Mike Cowperthwaite]

*** Bug 359021 has been marked as a duplicate of this bug. ***

Comment 5

[WADA:World Anti-bad-Duping Agency]

mailnews.use_received_date=false(default)/true is added to latest-trunk
nightly, and user can choose mail-date(date in "Date column") from Received: header
instead of from Date: header now. This enhancement can be a relief of this bug's
case for some(I think many) users. See Bug 341548 for detail.

Comment 6

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 7

[Wayne Mery (:wsmwk)]

(In reply to comment #5)
> mailnews.use_received_date=false(default)/true is added to latest-trunk
> nightly, and user can choose mail-date(date in "Date column") from Received:
> header
> instead of from Date: header now. This enhancement can be a relief of this
> bug's
> case for some(I think many) users. See Bug 341548 for detail.

rkent, hopefully you agree this is datalossy?

Comment 8

[Wayne Mery (:wsmwk)]

IMO bug 318897 is a better direction