From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/37529 Path: main.gmane.org!not-for-mail From: Andreas Jaeger Newsgroups: gmane.emacs.gnus.general Subject: Re: encrypted mails and quoted-printable Date: Sun, 05 Aug 2001 18:30:26 +0200 Sender: aj@suse.de Message-ID: References: <2ny9oz4q77.fsf@piglet.jia.vnet> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Trace: main.gmane.org 1035172928 14364 80.91.224.250 (21 Oct 2002 04:02:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 04:02:08 +0000 (UTC) Return-Path: Return-Path: Original-Received: (qmail 27356 invoked from network); 5 Aug 2001 16:36:38 -0000 Original-Received: from mail.kdt.de (195.8.224.4) by gnus.org with SMTP; 5 Aug 2001 16:36:38 -0000 Original-Received: from arthur.inka.de (arthur.kdt.de [195.8.250.5]) by mail.kdt.de (8.11.1/8.11.0) with ESMTP id f75GaZY04006 for ; Sun, 5 Aug 2001 18:36:35 +0200 Original-Received: from gromit.moeb ([192.168.27.3] ident=postfix) by arthur.inka.de with esmtp (Exim 3.30 #1) id 15TQnO-00073i-00 for ding@gnus.org; Sun, 05 Aug 2001 18:30:30 +0200 Original-Received: by gromit.moeb (Postfix, from userid 207) id 2084E1EA37; Sun, 5 Aug 2001 18:30:28 +0200 (CEST) Mail-Copies-To: never Original-To: ding@gnus.org In-Reply-To: (Simon Josefsson's message of "Sun, 05 Aug 2001 16:02:28 +0200") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) XEmacs/21.4 (Academic Rigor) Original-Lines: 41 Xref: main.gmane.org gmane.emacs.gnus.general:37529 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:37529 --=-=-= Content-Transfer-Encoding: quoted-printable Simon Josefsson writes: > Andreas Jaeger writes: >=20 >>> QP encoding is to avoid the article to be mangled. Though a message >>> contains only ASCII, lines starting with "From " or so be mangled. >>=20 >> I see - but that's rather unfortunate. Is there no way to avoid this? >> I'd rather don't use QP. >=20 > Then you'd be breaking the PGP/MIME specification, and the receiver > probably couldn't validate your message. >=20 > 3. Content-Transfer-Encoding restrictions >=20 > Multipart/signed and multipart/encrypted are to be treated by agents > as opaque, meaning that the data is not to be altered in any way [1]. > However, many existing mail gateways will detect if the next hop does > not support MIME or 8-bit data and perform conversion to either > Quoted-Printable or Base64. This presents serious problems for > multipart/signed, in particular, where the signature is invalidated > when such an operation occurs. For this reason all data signed > according to this protocol MUST be constrained to 7 bits (8- bit data > should be encoded using either Quoted-Printable or Base64). But this means that I still can use ASCII for 7bits and do not need to use QP for 7-bit only data. Have a look at this email - it's signed, contains AFAIK no 8-bit data and is still QP. That's the problem I see. Thanks for the explanation I now accept that I have to live with QP as soon as my emails contain 8-bit data. Andreas =2D-=20 Andreas Jaeger SuSE Labs aj@suse.de private aj@arthur.inka.de http://www.suse.de/~aj --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7bXSkOJpWPMJyoSYRAqp/AJkBP36OgqzSa2pw9mNXSYHrLbrbtACffwk4 9R20TPinM6igvqmEALJO3G4= =3dhj -----END PGP SIGNATURE----- --=-=-=--