Bug 56413

Summary: Signed message arrives with invalid signature
Product: [Unmaintained] kmail Reporter: Christian Spitzlay <cmueller>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Christian Spitzlay 2003-03-26 00:38:07 UTC
Version:            (using KDE KDE 3.1.1)
Installed from:    Gentoo Packages
Compiler:          gcc 3.2.2 
OS:          Linux

Hello, 

I read bug report 48713 which seems to resemble 
my problem, but it is closed. 
My problem seems to be reproducible: 

It happens when I send a GPG signed message
with an attachment where the attachment is signed, too.  
No encryption is used.  

The encoding is nested in that case.
The version in my sentmail folder is ok, but the one 
that is received isn't.  I diffed the two versions 
and found out that there are *two* empty lines 
between the outer and the inner encoding headers 
that get compressed into *one* empty line, 
probably while in transit.  

I'm not sure what the RFCs say on this but 
I guess the problem will disappear if we have 
only one empty line to start with.  

Below is the relevant part of the original email:
 
--Boundary-03=_vMOg+vXnT9ZFMp6
Content-Type: multipart/mixed;
  boundary="Boundary-01=_oMOg+Y4H40nZbb8"
Content-Transfer-Encoding: 7bit
Content-Description: signed data
Content-Disposition: inline


--Boundary-01=_oMOg+Y4H40nZbb8
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: base64
Content-Description: body text
Content-Disposition: inline
Comment 1 Christian Spitzlay 2003-03-26 00:51:55 UTC
More precisely:  
This missing blank line has been the only difference  
inside the signed part of the email... 
 
Comment 2 Ingo Klöcker 2003-03-26 01:38:50 UTC

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