Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Is Thunderbird using "sent date" instead of actual received time in "Received"?

  • 1 Antwort
  • 2 haben dieses Problem
  • 1 Aufruf
  • Letzte Antwort von Zenos

more options

It seems as if Thunderbird (45.2.0 Danish) uses the sent date as received date and not the actual date and time of received.

In attached image the two last columns are Received and Date. The mails are from an ip camera that sends mails with an error in the date field (as shown in the mailheader in the image) but this error ought not to have any influence of the actual time of recieving the mail (which, more or less, is show in the message body)

It seems as if Thunderbird (45.2.0 Danish) uses the sent date as received date and not the actual date and time of received. In attached image the two last columns are Received and Date. The mails are from an ip camera that sends mails with an error in the date field (as shown in the mailheader in the image) but this error ought not to have any influence of the actual time of recieving the mail (which, more or less, is show in the message body)
Angefügte Screenshots

Alle Antworten (1)

more options

The "Received" value is indeed a bit mysterious. I can understand that historically one might not want to use the computer's own time since computer clocks used not to be reliable. Now we are all accustomed to ntp synchronization by default (I remember having to download and install an ntp client to make it work at all) it's easy to take an accurate clock for granted.

If it doesn't record the local time when the incoming message is processed, you'd expect the client to parse the Received: headers and find the latest time listed, this being the one when it arrived at your incoming server.

Finally, whatever value is used, Thunderbird doesn't seem able to sort on the Received column.

Your data does strongly suggest that it's using the defective time placed into the message's Date: header, and the Jan 1970 date indicates that it wasn't able to parse the defective date/time, so is effectively using 0 as the date.