problems with TheBat inline pgp messages

Thomas Spuhler ThomasSpuhler at
Wed Feb 11 08:32:57 CET 2004

Thanks Adrian.
PGP/Mime would make it possible for Evolution users to read the
signatures. Ximian just tells that inline signatures are not RFC
compliant and will not change their program. Around 50% on this list use
inline signatures

On Wed, 2004-02-11 at 06:52, Adrian 'Dagurashibanipal' von Bidder wrote:
> On Wednesday 11 February 2004 12.46, Kai Raven wrote:
> > Version: PGPsdk version 1.7.1 (C) 1997-1999 Network Associates, Inc. and
> > its affiliated companies.
> I like this bug. It should convince people that using PGP/MIME will be the 
> future...
> Kai, the problem is correctly identified: the long version line.
> The question is: who breaks it into two lines? The sender or the recipient?
> MUAs should not send lines longer than 76 chars, so at a first guess it could 
> be on the sending side.
> OTOH, the sending side could be breaking the line correctly, with a '=' at the 
> end in the quoted-printable output. Then it would be sylpheeds fault for not 
> correctly reassembling that line (inline is a signature on the *decoded* mail 
> body, as opposed to PGP/MIME, where the signature is done on the encoded body 
> as it is sent over the network).
> -- vbi
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : /pipermail/attachments/20040211/627a6ea6/attachment.bin

More information about the Gnupg-users mailing list