User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:220.127.116.11) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729) Build Identifier: Mail Display Date use Date from client which is some times wrong I get mails from one in Japan. The mail in die mail list are sorted by the send date of the client. If I take a view into the mail header. The date is '29.08.2009 23:38' (client date in Japan without time zone) and the Delivery-Date is 'Sat, 29 Aug 2009 14:38:40 +0200' which is the server date in Europe). I think you can't trust the client date (special if it is in the future of the server time). In this case use the server date in the display list. Reproducible: Always Steps to Reproduce: 1. get Mail from other client with other time zone. 2. 3.
It is quite possible that the email was delivered a while after it was originally sent, or the user has a misconfigured time. The date the client shows is the date/time at which the user sent it. The delivery date is the time at which the server received it. If there is a delay in transmission, or the users chooses to delay the send across the internet for a while (e.g. he is offline) then the delivery date can be different to the date the client displays. Therefore I think this is invalid. If you think not, please attach the date related headers obtained by going to view -> message source.
This is not about a delay - the sender has used a timestamp without a timezone, so that it appears to be in the future. But timestamps are always unreliable , so I don't know what the solution would be. Sorting to the Delivery-Date would also put messages in the incorrect order, if one of them experienced delay.
(In reply to comment #3) > This is not about a delay - the sender has used a timestamp without a timezone, > so that it appears to be in the future. Jo, not quite - the sender has probably used a timezone, but Thunderbird never displays that to the user in the message header. Hence my request for more information from the headers shown in view -> message source.
Not blocking on this as it feels more like a sender timestamp issue rather than an issue within Thunderbird.
Flags: blocking-thunderbird3? → blocking-thunderbird3-
ska... (In reply to comment #2) > ... > Therefore I think this is invalid. If you think not, please attach the date > related headers obtained by going to view -> message source.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Keywords: qawanted → testcase-wanted
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.