From: "Georg C. F. Greve" <greve@gnu.org>
Cc: ding@gnus.org
Subject: Re: Two and a half PGP-MIME issues
Date: 22 Nov 2000 15:38:14 +0100 [thread overview]
Message-ID: <m3u290rs15.fsf@reason.gnu-hamburg> (raw)
In-Reply-To: <2n8zqcnm94.fsf@tiger.jia.vnet>
[-- Attachment #1.1: Type: text/plain, Size: 1364 bytes --]
|| On 22 Nov 2000 15:00:18 +0100
|| zsh@cs.rochester.edu (ShengHuo ZHU) wrote:
>> > > 1. Decrypting mails with umlauts in the body produces \201's
>> > > in front of every umlaut. These mails were encrypted within
>> > > Gnus. Same effect for encryption / decryption without really
>> > > sending a mail (`K E' - see 1½), so it must be a Gnus issue.
Funnily enough I did NOT have this problem until I kicked out gpg.el
(in the contrib directory) from my configuration to check out whether
the recipient problem would disappear with mailcrypt 3.5.5.
However: after kicking it out, I see the same problem now. Strange
enough it does not appear in my archived mails (they look fine) only
in those coming in from somewhere else.
>> > Probably fixed. Please try and tell me the result.
>> No, I see the same result as before. I'm using Emacs 20.7.2 with
>> Mule-UCS on Debian Potato. Please tell me if I should provide you
>> with more information on my environment or sample mails / buffers
>> etc.
sz> Are \201's produced if you manually decrypt the message?
Not here. They look fine when being decoded with Seahorse.
Regards,
Georg
--
Georg C. F. Greve <greve@gnu.org>
the monthly GNU forum in English, German,
French, Spanish and Japanese. Check it out
at http://brave-gnu-world.org/
[-- Attachment #2: Type: application/pgp-signature, Size: 268 bytes --]
next prev parent reply other threads:[~2000-11-22 14:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-21 21:22 Raymond Scholz
2000-11-22 1:04 ` ShengHuo ZHU
2000-11-22 12:04 ` Raymond Scholz
2000-11-22 13:56 ` ShengHuo ZHU
2000-11-22 14:38 ` Georg C. F. Greve [this message]
2000-11-22 14:49 ` Raymond Scholz
2000-11-22 15:03 ` ShengHuo ZHU
2000-11-25 14:40 ` Raymond Scholz
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=m3u290rs15.fsf@reason.gnu-hamburg \
--to=greve@gnu.org \
--cc=ding@gnus.org \
/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).