Bug 1890230 Comment 143 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

(In reply to José María Fernández from comment #141)
> I updated to 128.4.1esr , I have repaired the 729MB INBOX of one of my IMAP accounts (hosted at imap.gmx.com) , and now INBOX has 17 entries out of  "9769+ conversations" with completely wrong dates (i.e. the timestamp of the re-fetch instead of the right one)

Sounds a lot like Bug 1911916... (I think that was the one Arthur was referring to, and the patches were uplifted to 128esr a couple of days ago, but I don't know which version they'll show up in).

> But about the other 17 e-mails with wrong timestamps, I have been having a look at these e-mails through the GMX web site, and they are properly represented (even the correct date).

I would check the raw headers for one of your affected messages ("view source" in TB, or "download raw" maybe in a webmail interface). Bug 1911916 was a workaround for malformed messages without a "Date:" header - it stores an additional timestamp in the mbox separator (the line just before the first message header, eg "From - Tue Dec 09 15:30:45 2014") and uses this if "Date:" is missing. The "From " timestamp is just the time the message was written into the mbox - usually time of reception, or time of folder repair.

It's likely that the GMX IMAP server does a similar trick - it keeps track of the reception time of messages and uses that to fill in if  "Date:" is missing.
I would guess that most of those 17 emails are emails from an automated system, rather than sent directly by a real person.
(In reply to José María Fernández from comment #141)
> I updated to 128.4.1esr , I have repaired the 729MB INBOX of one of my IMAP accounts (hosted at imap.gmx.com) , and now INBOX has 17 entries out of  "9769+ conversations" with completely wrong dates (i.e. the timestamp of the re-fetch instead of the right one)

Sounds a lot like Bug 1911916... (I think that was the one Arthur was referring to, and the patches were uplifted to 128esr a couple of days ago, but I don't know which version they'll show up in [EDIT: they're in 128.4.2esr]).

> But about the other 17 e-mails with wrong timestamps, I have been having a look at these e-mails through the GMX web site, and they are properly represented (even the correct date).

I would check the raw headers for one of your affected messages ("view source" in TB, or "download raw" maybe in a webmail interface). Bug 1911916 was a workaround for malformed messages without a "Date:" header - it stores an additional timestamp in the mbox separator (the line just before the first message header, eg "From - Tue Dec 09 15:30:45 2014") and uses this if "Date:" is missing. The "From " timestamp is just the time the message was written into the mbox - usually time of reception, or time of folder repair.

It's likely that the GMX IMAP server does a similar trick - it keeps track of the reception time of messages and uses that to fill in if  "Date:" is missing.
I would guess that most of those 17 emails are emails from an automated system, rather than sent directly by a real person.
(In reply to José María Fernández from comment #141)
> I updated to 128.4.1esr , I have repaired the 729MB INBOX of one of my IMAP accounts (hosted at imap.gmx.com) , and now INBOX has 17 entries out of  "9769+ conversations" with completely wrong dates (i.e. the timestamp of the re-fetch instead of the right one)

Sounds a lot like Bug 1911916... (I think that was the one Arthur was referring to, and the patches were uplifted to 128esr a couple of days ago, but I don't know which version they'll show up in [EDIT: they're in 128.4.2esr](https://bugzilla.mozilla.org/show_bug.cgi?id=1911916#c49) ).

> But about the other 17 e-mails with wrong timestamps, I have been having a look at these e-mails through the GMX web site, and they are properly represented (even the correct date).

I would check the raw headers for one of your affected messages ("view source" in TB, or "download raw" maybe in a webmail interface). Bug 1911916 was a workaround for malformed messages without a "Date:" header - it stores an additional timestamp in the mbox separator (the line just before the first message header, eg "From - Tue Dec 09 15:30:45 2014") and uses this if "Date:" is missing. The "From " timestamp is just the time the message was written into the mbox - usually time of reception, or time of folder repair.

It's likely that the GMX IMAP server does a similar trick - it keeps track of the reception time of messages and uses that to fill in if  "Date:" is missing.
I would guess that most of those 17 emails are emails from an automated system, rather than sent directly by a real person.

Back to Bug 1890230 Comment 143