Closed
Bug 529507
Opened 15 years ago
Closed 10 years ago
Sort by Received does not work (Threaded view)
Categories
(Thunderbird :: Folder and Message Lists, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: vkondakoff, Unassigned)
Details
(Keywords: testcase)
Attachments
(3 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2b2) Gecko/20091108 Firefox/3.6b2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091117 Shredder/3.0.1pre Changing sort order from 'Date' to 'Received' does not change the messages sort order. Here is a screenshot which illustrate a problem: http://rugby-forum.ru/temp/received.jpg . I received a spam message with fake 'Date' field: 01.03.2024. But this message has valid 'Received' field: 05.11.2009. Just to get this message from the bottom of my message list I changed the sort from 'Date (Ascending)' to 'Received (Ascending)'. And this does not change anything. I even tried to rebuild the Spam folder indexes and restart TB - no results. What is wrong here. I'm attaching two messages from this thread to this report. Reproducible: Always
Reporter | ||
Comment 1•15 years ago
|
||
Reporter | ||
Comment 2•15 years ago
|
||
Updated•14 years ago
|
Component: General → Folder and Message Lists
Keywords: testcase
QA Contact: general → folders-message-lists
Doesn't have to be spam emails - the emails shown in the attached image do all have a valid 'Date:' header and were generated either by swaks, or a Domino server.
Comment 5•12 years ago
|
||
Does repairing the folder helps ?
Comment 6•11 years ago
|
||
(In reply to Ludovic Hirlimann [:Usul] from comment #5) > Does repairing the folder helps ?
Flags: needinfo?(strauss)
Comment 7•10 years ago
|
||
"received" is not necessarily by date, and the column header is now different. Regardless, Valery reports "stopped to use Thunderbird long ago (after switching OS)."
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Flags: needinfo?(vkondakoff)
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•