From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: mml.el changes
Date: Tue, 02 Aug 2005 10:47:42 +0900 [thread overview]
Message-ID: <b4mwtn53y9t.fsf@jpl.org> (raw)
In-Reply-To: <b4m3bpt6td2.fsf@jpl.org>
>>>>>> In <m3u0i9mjsh.fsf@doze.jochen-kuepper.de> Jochen Küpper wrote:
>> With current cvs Gnus I have problems with pgp/mime signed messages.
>>>>> In <b4m3bpt6td2.fsf@jpl.org> Katsumi Yamaoka wrote:
> 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...
Fixed. Now the content type defaults to text/plain if it is not
for attaching a file. Thanks for pointing it out.
prev parent reply other threads:[~2005-08-02 1:47 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
2005-08-02 1:47 ` Katsumi Yamaoka [this message]
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=b4mwtn53y9t.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).