Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

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

  • 1 답장
  • 2 이 문제를 만남
  • 1 보기
  • 최종 답변자: 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)
첨부된 스크린샷

모든 댓글 (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.