From: ajk@iu.edu (Andrew J. Korty)
Subject: mml-secure-message-encrypt-pgp leaves =20 all over the place
Date: Mon, 18 Aug 2003 18:40:35 -0500 [thread overview]
Message-ID: <7692.64195482737$1061257124@news.gmane.org> (raw)
When I encrypt mail with mml-secure-message-encrypt-pgp, it seems to
encode trailing spaces and other characters. So if a line had three
trailing spaces, the recipient, after decrypting the message, would
see =20=20=20 at the end of the line. How do I fix it so the
decrypted message looks the same as the original?
This doesn't happen with mml-secure-message-encrypt-pgpmime, but it
seems very few other MUAs implement that standard.
--
Andrew J. Korty, Principal Security Engineer, GCIA, GCFA
Office of the Vice President for Information Technology
Indiana University
reply other threads:[~2003-08-18 23:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='7692.64195482737$1061257124@news.gmane.org' \
--to=ajk@iu.edu \
/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).