Bug 175965 - Incoming emails are corrupted by two inserted newlines in X-KMail-MDN-Sent header field
Summary: Incoming emails are corrupted by two inserted newlines in X-KMail-MDN-Sent he...
Status: RESOLVED DUPLICATE of bug 86302
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: 1.10.3
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-24 10:07 UTC by kablooie
Modified: 2009-03-19 00:35 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kablooie 2008-11-24 10:07:49 UTC
Version:           1.10.3 (using KDE 4.1.3)
Compiler:          gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11)  
OS:                Linux
Installed from:    Ubuntu Packages

When I receive an email in kmail, it sometimes gets corrupted (about 30% chance). The list of emails says then that the mail has "no subject", sender "unknown", date "unknown". When I open the mbox file with a text editor, I notice that an empty line is inserted in the X-KMail-MDN-Sent header field. Once I remove the empty line (and the trailing garbage in the next line), Kmail recognizes the other header fiels.

My workaround is to manualy edit each file that contains a concerned email, but this is not an option in the long run.


Unfortunately, I got no idea how to reproduce this really annoying bug. I know that others have been trying to make it reproducible (see e.g. bug 86302) and failed.

I attach an example email where I replace personal information with the same number of X (since someone suggested it might be an issue of how many characters are used in the header).

------------------
X-Apparently-To: xxxxxxxxxxxxxxx@ymail.com via xx.xxx.xxx.xxx; Mon, 24 Nov 2008 00:44:36 -0800
X-YMailISG: skXVPEctYB1lF0gUpR9tq93QrI6fwkL95J.ffKT8Ss6za5LTGwDijSJbtjL2B5B4QpI0h.EEoyOsymCip0BE2H.b_dbU328sWeLpT8m_T6EgxP9wpbrm3cNplzVYGeSMBEXLK2Lb7GIWilXPahKV8dYL7EwhavOQcEf4xAYlwXAeoozJi6mEnUW0_YL3CCjkZfEyOsvb95a_Zm49nYWHPlK22P3tPYzQUeKuEMur0MJMR.KC7SbKqdtcfPa_FoacRLqk0kMVVIdScaPMwIexHUiqe5kLnoM3Mr4pLgrXWKu0hoUghhD.78WRrV5SEAcfsE4kWfnr7x6oh10YFdeAtmzLj1wAD6sHylQhH86ZliVdBjcAPz90P8a71lojofX2t7roPg--                                                                                

X-Originating-IP: [xxx.xxx.xx.xxx]                                                                                       
Authentication-Results: mta477.mail.mud.yahoo.com  from=xxxxxxxx.xx; domainkeys=neutral (no sig)                         
Status: R                                                                                                                
X-Status: N                                                                                                              
X-KMail-EncryptionState:                                                                                                 
X-KMail-SignatureState:                                                                                                  
X-KMail-MDN-Sent:                                                                                                        

; from=xxxxxxxx.xx; dkim=neutral  (no  sig)
Received: from xxx.xxx.xx.xxx  (EHLO xxxxxxxx.xx) (xxx.xxx.xx.xxx)
  by mta477.mail.mud.yahoo.com with SMTP; Mon, 24 Nov 2008 00:44:36 -0800
Received: from [xx.xx.xxx.xx] (account xxxxxxxx@xxxxxxxx.xx HELO [xxx.xxx.x.xxx])
  by xxx.xxxxxxxx.xx (CommuniGate Pro SMTP 5.0.14)
  with ESMTPA id 7450695 for xxxxxxxxxxxxxxx@ymail.com; Mon, 24 Nov 2008 09:44:35 +0100
Message-ID: <492A696C.70903@xxxxxxxx.xx>
Date: Mon, 24 Nov 2008 09:44:28 +0100
From: xxxxxxxx xxxxxx <xxxxxxxxxxxxxxxxx@xxxxxxxx.xx>
User-Agent: Thunderbird 2.0.0.17 (X11/20080925)
MIME-Version: 1.0
To: xxxxxxxx xxxxxxxx <xxxxxxxxxxxxxxx@ymail.com>
Subject: Testtesttest
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

this is a test email
Comment 1 Christophe Marin 2008-11-24 10:13:47 UTC
I will reopen the bug 86302. Thank you for your report.

*** This bug has been marked as a duplicate of bug 86302 ***