Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

date of message is not correct in imap (thunderbird)

  • 1 reply
  • 1 has this problem
  • 5 views
  • Last reply by Matt

more options

In webmail (gmail) it is ok, but in thunderbird it is wrong

example of message with wrong date displayed (displayed "fetch date" + time 00:48)


Return-Path: <xxxx> Delivered-To: xxxx Received: (qmail 21222 invoked from network); 26 Feb 2006 19:30:09 -0000 Received: from unknown (HELO x.x.x.) (xxxx@[x.x.x.x])

         (envelope-sender <xxxx>)
         by mta11 (qmail-ldap-1.03) with SMTP
         for <xxxx>; 26 Feb 2006 19:30:09 -0000

From: <xxxx> Subject: xxxx To: <xxxx>, <xxxx>, <xxxx> Importance: high X-Priority: 1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----?...+'MMS_MSG_COMPOSER'+1140982778"


example of message with correct date


MIME-Version: 1.0 Received: by x.x.x.x with HTTP; Fri, 30 May 2014 01:17:40 -0700 (PDT) In-Reply-To: <> References: <> Date: Fri, 30 May 2014 09:17:40 +0100 Delivered-To: xxxx Subject: xxxx From: <xxxx> To: <xxxx> Content-Type: multipart/mixed; boundary=001a11c1b71cd8880604fa99adc4

It seams it does not parse the date correctly because there is no date field. Is this a bug or a feature?

In webmail (gmail) it is ok, but in thunderbird it is wrong example of message with wrong date displayed (displayed "fetch date" + time 00:48) ------------------------------------------------------------------------------------------------------------------- Return-Path: <xxxx> Delivered-To: xxxx Received: (qmail 21222 invoked from network); 26 Feb 2006 19:30:09 -0000 Received: from unknown (HELO x.x.x.) (xxxx@[x.x.x.x]) (envelope-sender <xxxx>) by mta11 (qmail-ldap-1.03) with SMTP for <xxxx>; 26 Feb 2006 19:30:09 -0000 From: <xxxx> Subject: xxxx To: <xxxx>, <xxxx>, <xxxx> Importance: high X-Priority: 1 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----?...+'MMS_MSG_COMPOSER'+1140982778" example of message with correct date --------------------------------------------------- MIME-Version: 1.0 Received: by x.x.x.x with HTTP; Fri, 30 May 2014 01:17:40 -0700 (PDT) In-Reply-To: <> References: <> Date: Fri, 30 May 2014 09:17:40 +0100 Delivered-To: xxxx Subject: xxxx From: <xxxx> To: <xxxx> Content-Type: multipart/mixed; boundary=001a11c1b71cd8880604fa99adc4 It seams it does not parse the date correctly because there is no date field. Is this a bug or a feature?

All Replies (1)

more options

Date is a required fi=eld for email, it is not optional. therefore whatever defective program or web service that is generating these mails needs to be fixed.