Bug 184154 - Date in message list is not updated
Summary: Date in message list is not updated
Status: RESOLVED DUPLICATE of bug 178035
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-12 16:37 UTC by Sten Heinze
Modified: 2009-03-19 00:41 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sten Heinze 2009-02-12 16:37:49 UTC 
Version:           KMail version 1.11.0/KDE 4.2.0 (using KDE 4.2.0)
Compiler:          gcc from Debian testing 4.3.2-2 
OS:                Linux
Installed from:    Debian testing/unstable Packages

1.
If KMail receives new email, it only shows the normal date in the message list for the new emails instead of fancy date. It does show the fancy date (Today, Yesterday...) for all messages in the mailbox when KMail started. 

2.
The date of older messages is not updated, e.g. Today into Yesterday on the next day (I usually don't restart my laptop, just suspend it).

How to reproduce and expected behaviour:
1.
Open KMail, check mails. New mails don't use fancy dates as it is expected.

2.
Keep KMail running until the next day. Mails with fancy date "Today" don't get the date updated to "Yesterday" as it should be.

Regards,
Sten
Comment 1 Jaime Torres 2009-02-12 17:23:57 UTC 
Thank you for taking the time to report this bug and helping to make KDE better. This particular bug has already been reported and is a duplicate of bug 178035, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.



*** This bug has been marked as a duplicate of bug 178035 ***