Closed Bug 597996 Opened 14 years ago Closed 14 years ago

Received time displayed is actually Sent time

Categories

(Thunderbird :: Mail Window Front End, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 402594

People

(Reporter: bjl, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.9.2.10) Gecko/20100914 Firefox/3.6.10 ( .NET CLR 3.5.30729) Build Identifier: 3.1.4 I think the Received date/time displayed in the list of messages might actually be the Sent date/time. The value shown for Received is the same as Date. Working at home I had to use Outlook Web Access and was surprised to find email arriving in the wrong order although the date/time stamps were sequential. (I now realise OWA was using the Received time - presumable the time the server received messages and not the time the client sent the email.) Coming in to work I find TB showing messages in the correct order and with different date/times shown as Date from those I saw in OWA. Checking TB against Outlook (now Web Access) I find the TB Date matches the Outlook Sent date/time. The TB Received also matches the Outlook Sent date/time. Therefore I suspect TB is showning the Sent date/time in it's Received column. Reproducible: Always
Version: unspecified → 3.1
Whiteboard: dupme?
Same problem as Bug 402594? If so, why you couldn't reach Bug 402594 before your new bug open at B.M.O? If you searched B.M.O very well, did you use "Advanced Search" of B.M.O? If you used "Advanced Search" of B.M.O, have you searched DUP'ed bugs too, instead of open bugs only?
I did search and didn't spot it in the results. If that offends you then I apolgise. If this is a duplicate why did you not just close it?
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Whiteboard: dupme?
(In reply to comment #2) > If that offends you then I apolgise. Oh, no, no. No need of your apology. I wanted to know you did search or not, and if you searched, what search method did you use, because "Simple Search" had problem of inaccurate search, and because "Advanced Search" is very hard to use for non-developer due to difficulty in search condition setting and due to difficulty in deciding search term (a user say freeze, another says hang, others say hung, ...). I wanted to know what was hardle in your case to reach already reported bugs for similar or same problem, in order to improve current search of B.M.O and/or to improve documentation/guide for searching at B.M.O. > If this is a duplicate why did you not just close it? It's simply because I couldn't know dup or not. I saw bug reports of same bug summary for at least next two cases. a) Same as your case: IMAP and Received header is not downloaded upon fetch. b) Same date/time in Date: and Received:, then same date/time at thread pane. Bug opner thought "Received" column value is timestamp when mail is downloaded from POP3 server. How can a people surely know that your comment #0 is never for b)?
WADA, Thanks for the explanation. I thought you were just telling me off for not searching. I did only use the Simple Search. I'm still fairly new to Bugzilla and with poor eyesight it can be difficult reading through a large number of search results. By the way, I am using IMAP to an Exchange 2007 server. I did set the status to "Duplicate". I hope that was right.
(In reply to comment #5) > I did only use the Simple Search. It's usually impossible to find already opened bugs via "Simle Search"。 "1716 bugs found" was returned for next "Simple Search", > Status: Open > Product: MailNews Core > Words: received date does not work on IMAP (always the same as date) > Note: the Words: is absolutely same as bug summary of Bug 402594. altough Bug 402594 was listed at top because Words: was intentionally set to absolutely same one as bug summary of Bug 402594. Who can reach already opened bug when "1716 bugs found" is returned, even though Words: is set absolutely same as existent bug's one? > By the way, I am using IMAP to an Exchange 2007 server. If IMAP, your duping is correct. Do workaround stated in that bug, please.
You need to log in before you can comment on or make changes to this bug.