Bug 142015 - display errornous base64 encoding?
Summary: display errornous base64 encoding?
Status: RESOLVED NOT A BUG
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-02-21 12:32 UTC by Christof Schulze
Modified: 2009-08-05 12:37 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 Christof Schulze 2007-02-21 12:32:36 UTC
Version:            (using KDE KDE 3.5.6)
Installed from:    Gentoo Packages

I am not sure if this really is a bug but here it goes:
I got an email from a trac system which reads like the attached message.
It does not get displayed correctly - I believe because of the errors in the bas64 encoding. The mail is readable however when using sylpheed-claws.
Is it possible to display a mail like this with kmail so that the content will be readable? Is this a kmail problem or is it the mail?

If it is the mail: Is it possible to make kmail a little more error-prone to this? I understand that I cannot expect a broken mail to be displayed correctly - yet life would be easier if it was readable like in sc.



Return-Path: <*****@faracvs>
Received: from murder ([unix socket])
	 (authenticated user=**** bits=0)
	 by faracvs (Cyrus v2.3.7-Gentoo) with LMTPA;
	 Wed, 21 Feb 2007 11:30:04 +0100
Received: from localhost (localhost [127.0.0.1])
	by faracvs.****** (Postfix) with ESMTP id C065517801D
	for <****@localhost>; Wed, 21 Feb 2007 11:30:02 +0100 (CET)
X-Flags: 0000
Delivered-To: GMX delivery to ***********
Received: from pop.gmx.net [213.165.64.22]
	by localhost with POP3 (fetchmail-6.3.4)
	for <erika@localhost> (single-drop); Wed, 21 Feb 2007 11:30:02 +0100 (CET)
Received: (qmail invoked by alias); 21 Feb 2007 10:23:25 -0000
Received: from ******** (EHLO ************) [***.***.***.***]
  by mx0.gmx.net (mx100) with SMTP; 21 Feb 2007 11:23:25 +0100
Received: from ********* (localhost [127.0.0.1])
	by ******** (Postfix) with ESMTP id 8614217801D
	for <*******>; Wed, 21 Feb 2007 11:23:25 +0100 (CET)
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: base64
From: "christsc-darbackup" <trac@faracvs>
Sender: trac@faracvs
X-Trac-Version: 0.10.1
Cc: christof.schulze@gmx.net
X-Mailer: Trac 0.10.1, by Edgewall Software
X-Trac-Project: christsc-darbackup
Date: Wed, 21 Feb 2007 10:23:25 -0000
Reply-To: trac-noreply@faracvs
X-URL: https://faracvs
X-Trac-Ticket-URL: https://faracvs.cs.uni-magdeburg.de/projects/christsc-darbackup/ticket/79
Message-ID: <084.7a9852cdc7fbcc844ba59858efe7a02e@faracvs.cs.uni-magdeburg.de>
X-Trac-Ticket-ID: 79
X-GMX-Antivirus: -1 (not scanned, may not use virus scanner)
X-GMX-Antispam: -2 (not scanned, spam filter disabled)
X-GMX-UID: ry/6bXCsLi5nhRcOXGtpI49jZml1ZJiX
Subject: [christsc-darbackup] #79: VERSION string in resulting shell script
X-Virus-Status: No
X-Virus-Checker-Version: clamassassin 1.2.3 with clamdscan / ClamAV 0.88.5/2614/Tue Feb 20 19:53:11 2007
X-UID: 103
X-Length: 3233
Status: R
X-Status: NC
X-KMail-EncryptionState:  
X-KMail-SignatureState:  
X-KMail-MDN-Sent:  

has trailing "-"

Izc5OiBWRVJTSU9OIHN0cmluZyBpbiByZXN1bHRpbmcgc2hlbGwgc2NyaXB0IGhhcyB0cmFpbGlu
ZyAiLSINCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCiBSZXBvcnRlcjogIGFub255bW91cyAgICB8ICAg
ICAgIFR5cGU6ICBlbmhhbmNlbWVudA0KICAgU3RhdHVzOiAgbmV3ICAgICAgICAgIHwgICBQcmlv
cml0eTogIG1ham9yICAgICAgDQpNaWxlc3RvbmU6ICBWZXJzaW9uIDAuOCAgfCAgICBWZXJzaW9u
OiAgMC43ICAgICAgICANCiBLZXl3b3JkczogICAgICAgICAgICAgICB8ICANCi0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0rLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0NCg0KDQotLSANClRpY2tldCBVUkw6IDxodHRwczovL2ZhcmFjdnMuY3MudW5pLW1h
Z2RlYnVyZy5kZS9wcm9qZWN0cy9jaHJpc3RzYy1kYXJiYWNrdXAvdGlja2V0Lzc5Pg0KY2hyaXN0
c2MtZGFyYmFja3VwIDxodHRwczovL2ZhcmFjdnMuY3MudW5pLW1hZ2RlYnVyZy5kZS9wcm9qZWN0
cy9jaHJpc3RzYy1kYXJiYWNrdXA+DQpNeSBleGFtcGxlIHByb2plY3Q=
Comment 1 Martin Koller 2009-08-05 12:37:01 UTC
I'm not the encoding guru, but I ask myself, how can such a mail be displayed correctly ?
The Content-Transfer-Encoding says base64, but the content is partly plain text (the line 'has trailing "-"') and partly base64 encoded.
In my test I just removed the 'has trailing "-"' line and, voila, the text is shown correctly.
For me it's also not clear, what that single half-line 'has trailing "-"' shall mean at all, because the complete decoded rest says (see below).
So I'd say, this is not worth looking into any further.


#79: VERSION string in resulting shell script has trailing "-"
-------------------------+--------------------------------------------------
 Reporter:  anonymous    |       Type:  enhancement
   Status:  new          |   Priority:  major      
Milestone:  Version 0.8  |    Version:  0.7        
 Keywords:               |  
-------------------------+--------------------------------------------------


-- 
Ticket URL: <https://faracvs.cs.uni-magdeburg.de/projects/christsc-darbackup/ticket/79>
christsc-darbackup <https://faracvs.cs.uni-magdeburg.de/projects/christsc-darbackup>
My example project