Closed
Bug 328328
Opened 18 years ago
Closed 16 years ago
Bad interpretation of an "apple-mail" due to a supposed overflow in references
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: guillaume.tardy, Assigned: mscott)
Details
(Whiteboard: closeme 2008-08-21)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; fr; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1 I use to write often to a friend of mine. He uses a macintosh and the software "Mail" installed on its computer. He usually answer to those mails and I do so with his reply. After a while (for 1/2 days), his reply go directly in the junk. While openning it, the sender, the user are not shown, and most of all, the content of the mail is completely erratic : no charset and no page set-up Reproducible: Always Steps to Reproduce: 1. Writing a mail with an "apple-mail" user 2. Ask him to reply to your mail 3. Reply to his reply 4. Continue the reply method for a long time (increases the number of references) 5. After a while, the mail recieved won't be correctly interpreted by Thunderbird Actual Results: The mail is not correctly interpreted : the sender, the subject, and the references of the mail are set to "" (nothing). Therefore the content of the mail is correctly interpreted, especially the page setup and the charset. And as the "header" doesn't work the mail is automatically sent to "Junk". Expected Results: The references of the mail, sender, subject should work, and the content of the mail should be correctly interpreted. I made some researches on those problems. It appeared that the problem can be due to an overflow in the references (the number of references seems to reach the maximum allowed by Thunderbird), especially because it is a long-replied-mail. Here is the header of a broken mail (took from the source code) (mails are hidden. If you want a sample mail, please ask me and I will send it to you by mail or any other way !) : From - Thu Feb 23 17:38:28 2006 X-Account-Key: account3 X-UIDL: 1140712105.27298.mrelay5-1 X-Mozilla-Status: 0001 X-Mozilla-Status2: 00000000 Return-Path: <xxxxxxxxx@laposte.net> Delivered-To: online.fr-xxxxxxxx@free.fr Received: (qmail 23976 invoked from network); 23 Feb 2006 16:27:56 -0000 Received: from mx.laposte.net (81.255.54.11) by mrelay5-1.free.fr with SMTP; 23 Feb 2006 16:27:56 -0000 Received: from [192.168.1.4] (86.193.175.182) by mx.laposte.net (7.2.060.1) (authenticated as xxxxxxxxxxxxxxx) id 43839F4103735D5F for xxxxxx@free.fr; Thu, 23 Feb 2006 17:27:54 +0100 Mime-Version: 1.0 (Apple Message framework v746.2) In-Reply-To: <43FDBB20.90608@free.fr> References: <E779BF5E-C9BB-46B0-A591-3B15D4F09E2C@laposte.net> <43FB490B.6090207@free.fr> <EF168685-C4A9-4C91-AC20-E1E0E73D7EB0@laposte.net> <43FC156F.5090603@free.fr> <1BEE48FD-399E-4D25-9F38-D07FA17B5F80@laposte.net> <43FC2ECA.4010105@free.fr> <2E819718-0E69-4D44-A524-AEE37F18D5B6@laposte.net> <43FC3BA0.9010808@free.fr> <3C3F3541-9095-4F76-B975-AA434C60D201@laposte.net> <43FC4AA5.5020501@free.fr> <9059D9B7-FAAE-4417-A72C-1BE449D74C57@laposte.net> <43FC65BE.3030105@free.fr> <47680B09-012F-4750-B5C6-9E04BE944F00@laposte.net> <43FC6B9E.8040601@free.fr> <400F60A9-C03F-457C-92C5-B67E0E56A1F8@laposte.net> <43FC719F.4030300@free.fr> <B5FB00D7-50BD-4D20-8CBE-C7D0702E6624@laposte.net> <43FC8B98.9020608@free.fr> <A23506D4-E879-4411-AE3D-4B4312A9F451@laposte.net> <43FD808B.9090201@free.fr> <5B867A69-C5E1-44EF-BC80-C40E72617AB2@laposte.net> <43FD8873.1040900@free.fr> <934F431C-5F15-4DC4-84FA-2680385E7ADB@laposte.net> <43FDA40F.50002@free.fr> <20027416-4031-44D8-A50F-06395638F0C7@lapost e.net> <43FDBB20.90608@free.fr> Content-Type: multipart/mixed; boundary=Apple-Mail-29--803958349 Message-Id: <4827C801-0BB2-4ACC-B8A3-4B830D4EAE2A@laposte.net> From: XXXXXXXXXXXXXXX <xxxxxxxxxx@laposte.net> Subject: Re: Effet :-<) Date: Thu, 23 Feb 2006 17:26:38 +0100 To: XXXXXXXXXXXXXX <xxxxxxxxxxxx@free.fr> X-Mailer: Apple Mail (2.746.2) --Apple-Mail-29--803958349 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=ISO-8859-1; format=flowed Tiens, une premi=E8re sortie =E0 l'air libre pour la vm :
Comment 1•18 years ago
|
||
If I'm reading that correctly, that's a bug in Apple Mail - if it's putting a blank line in between the reference headers and the Content-Type header, that makes the Content-Type header and everything that follows part of the message body, according to the message rfc/822 standard. Is it Apple Mail that's sending the message that way?
(In reply to comment #1) What I'll do is ask him a copy of his header (send by "Mail"), this way we can check if the header was badly sent by "Mail" or was badly interpreted by Thunderbird. If this is the Apple Mail fault, what should be done ? How can this bug be transferred to Mail, and how can we follow the correction ?
Comment 3•18 years ago
|
||
I don't know how to deal with Apple Mail bugs. It's not an open source project with an open bug reporting system, as far as I know...however, your friend should check that he's using the latest version of Apple Mail. It's hard to believe that a bug like that wouldn't be fixed...
Here is the header of the sent mail from my friend. I don't think the problem comes from a version of Apple Mail as he usually do all the updates. The thing is why the mail is bad interpreted only because of a blank line, and secondly why references made an "overflow"... I tried to do the same thing by sending me an e-mail with Thunderbird, and it didn't occured, as Thunderbird prevents this "overflow" by "removing" some redondant references (for example : the first reference is always here but the second reference will be removed, then the third etc.). I didn't try to open the mail with another software, but my friend can already open his mail. Even badly written ? Header of the mail : From gaussic@free.fr Thu Feb 23 14:36:01 2006 Return-Path: <xxxxxxxxxxxxxxxxxxxx@free.fr> Received: from smtp.laposte.net (10.150.9.33) by mx.laposte.net (7.2.060.1) id 43839F3B030B962F for xxxxxxxxxxxxxxxx@laposte.net; Thu, 23 Feb 2006 14:36:01 +0100 Received: from smtp4.wanadoo.fr (193.252.22.27) by smtp.laposte.net (7.2.056.5) id 43FDA401000160E8 for xxxxxxxxxxxxxxxxxx@laposte.net; Thu, 23 Feb 2006 14:36:00 +0100 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf0408.wanadoo.fr (SMTP Server) with ESMTP id 04B051C00110 for <xxxxxxxxxxxxxxxxx@laposte.net>; Thu, 23 Feb 2006 14:36:00 +0100 (CET) Received: from [192.168.1.13] (LSt-Amand-152-31-40-192.w82-127.abo.wanadoo.fr [82.127.95.192]) by mwinf0408.wanadoo.fr (SMTP Server) with ESMTP id 0914B1C0010D for <xxxxxxxxxxxxxx@laposte.net>; Thu, 23 Feb 2006 14:35:56 +0100 (CET) X-ME-UUID: 20060223133557373.0914B1C0010D@mwinf0408.wanadoo.fr Message-ID: <43FDBB20.90608@free.fr> Date: Thu, 23 Feb 2006 14:39:44 +0100 From: XXXXXXXXXXXXXX <xxxxxxxxxxxxx@free.fr> User-Agent: Thunderbird 1.5 (Windows/20051201) MIME-Version: 1.0 To: XXXXXXXXXXXXXX <xxxxxxxxxxxxxxx@laposte.net> Subject: Re: Effet :-<) References: <E779BF5E-C9BB-46B0-A591-3B15D4F09E2C@laposte.net> <43FB490B.6090207@free.fr> <EF168685-C4A9-4C91-AC20-E1E0E73D7EB0@laposte.net> <43FC156F.5090603@free.fr> <1BEE48FD-399E-4D25-9F38-D07FA17B5F80@laposte.net> <43FC2ECA.4010105@free.fr> <2E819718-0E69-4D44-A524-AEE37F18D5B6@laposte.net> <43FC3BA0.9010808@free.fr> <3C3F3541-9095-4F76-B975-AA434C60D201@laposte.net> <43FC4AA5.5020501@free.fr> <9059D9B7-FAAE-4417-A72C-1BE449D74C57@laposte.net> <43FC65BE.3030105@free.fr> <47680B09-012F-4750-B5C6-9E04BE944F00@laposte.net> <43FC6B9E.8040601@free.fr> <400F60A9-C03F-457C-92C5-B67E0E56A1F8@laposte.net> <43FC719F.4030300@free.fr> <B5FB00D7-50BD-4D20-8CBE-C7D0702E6624@laposte.net> <43FC8B98.9020608@free.fr> <A23506D4-E879-4411-AE3D-4B4312A9F451@laposte.net> <43FD808B.9090201@free.fr> <5B867A69-C5E1-44EF-BC80-C40E72617AB2@laposte.net> <43FD8873.1040900@free.fr> <934F431C-5F15-4DC4-84FA-2680385E7ADB@laposte.net> <43FDA40F.50002@free.fr> <20027416-4031-44D8-A50F-06395638F0C7@lapost e.net> In-Reply-To: <20027416-4031-44D8-A50F-06395638F0C7@laposte.net>
Comment 5•16 years ago
|
||
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies? (1.5.0.x is now end-of-life and the latest supported 2.0.0.x is now 2.0.0.16)
Whiteboard: closeme 2008-08-21
Comment 6•16 years ago
|
||
RESO INCO per lack of response to previous comment. If you feel this change was made in error, please respond to the bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → INCOMPLETE
Sorry, I was not able to check this out yet as I was out of the office, but, I'll try once more as soon as I can (Might be next week) Regards, Guillaume
You need to log in
before you can comment on or make changes to this bug.
Description
•