Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

date of message is not correct in imap (thunderbird)

  • 1 réponse
  • 1 a ce problème
  • 5 vues
  • Dernière réponse par 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?

Toutes les réponses (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.