From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: mml.el changes
Date: Tue, 02 Aug 2005 10:05:29 +0900 [thread overview]
Message-ID: <b4m3bpt6td2.fsf@jpl.org> (raw)
In-Reply-To: <m3u0i9mjsh.fsf@doze.jochen-kuepper.de>
>>>>> In <m3u0i9mjsh.fsf@doze.jochen-kuepper.de> Jochen Küpper wrote:
> With current cvs Gnus I have problems with pgp/mime signed messages.
> See attached message for details.
> ,----
>| GNU Emacs 22.0.50.27 (i686-pc-linux-gnu, GTK+ Version 2.4.14) of 2005-07-31
>| No Gnus v0.4
> `----
> The text of the body is marked as application/octet-stream instead of
> text/plain, as it used to be. Therefore, the message text is not
> visible or only visible as MIME button (application/octet-stream),
> depending on MUA.
> Is there any new configuration necessary or is this simply a bug?
Confirmed. It's a real problem. I think it might be necessary
that the mml encoder recognizes the signed (or encrypted) part
as text, though I'm not sure whether it can be done automatically.
Anyway, I'll look into it...
next parent reply other threads:[~2005-08-02 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3u0i9mjsh.fsf@doze.jochen-kuepper.de>
2005-08-02 1:05 ` Katsumi Yamaoka [this message]
2005-08-02 1:47 ` Katsumi Yamaoka
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=b4m3bpt6td2.fsf@jpl.org \
--to=yamaoka@jpl.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).