Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: encrypted mails and quoted-printable
Date: Sun, 05 Aug 2001 16:02:28 +0200	[thread overview]
Message-ID: <iluu1zmd2q3.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <u8elqqoeeo.fsf@gromit.moeb> (Andreas Jaeger's message of "Sun, 05 Aug 2001 14:54:39 +0200")

Andreas Jaeger <aj@suse.de> writes:

>> QP encoding is to avoid the article to be mangled.  Though a message
>> contains only ASCII, lines starting with "From " or so be mangled.
> 
> I see - but that's rather unfortunate.  Is there no way to avoid this?
> I'd rather don't use QP.

Then you'd be breaking the PGP/MIME specification, and the receiver
probably couldn't validate your message.

3.  Content-Transfer-Encoding restrictions

   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).



  reply	other threads:[~2001-08-05 14:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-08-02 10:00 Andreas Jaeger
2001-08-04 18:47 ` ShengHuo ZHU
2001-08-05 12:54   ` Andreas Jaeger
2001-08-05 14:02     ` Simon Josefsson [this message]
2001-08-05 16:30       ` Andreas Jaeger
2001-08-05 17:54         ` Florian Weimer
2001-08-05 21:33           ` Andreas Jaeger
2001-08-05 22:14         ` Simon Josefsson
2001-08-06  6:38           ` Florian Weimer
2001-08-05 14:20     ` Nuutti Kotivuori
2001-08-05 14:55       ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=iluu1zmd2q3.fsf@barbar.josefsson.org \
    --to=jas@extundo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).