=2D----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 31 July 2002 02:11, Ingo Kl=F6cker wrote:
<snip>
> You are most likely correct. But as Marc already wrote the signed
> data MUST not be 8bit encoded according to the RFCs.
>
> So there are two bugs in the Aegypten code:
> 1. Signed data must not be 8bit encoded.
> 2. If a message part is 8bit encoded then this must be announced in
> the main header.
<snip>

ad 2: You all are making a problem where none exists ;-) multipart=20
subtypes _cannot_ have a non-identity CTE. Every MUA that adds a CTE=20
header to a mp/* part is severely broken ;-)

OTOH, the RFCs say that message/rfc822 (the other possible problem) MUST=20
have a CTE of 7bit. I'm not sure how to proceed in case an 8bit nested=20
body part is present, but I tend to simply use 8bit in this case.

Marc

Mutig warf sich die kleine =DCberwachungskamera zwischen T=E4ter und Opfer!
                                          --Rena Tangens / FoeBuD e.V.
=2D --=20
Marc Mutz <mutz@kde.org>
=2D----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9R6Kw3oWD+L2/6DgRAsTDAKCA9sDfiWZaiUi3VoJqNQ8TM5vKzwCgyRtW
7r1RUlU+HvJHeesURDBXv44=3D
=3DrSG5
=2D----END PGP SIGNATURE-----


_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail