From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: mh-e-devel@lists.sourceforge.net
Subject: Re: Gnus 5.10.6 problems with PGP/MIME (test cases)
Date: Tue, 17 Jan 2006 16:35:01 +0900 [thread overview]
Message-ID: <b4m3bjnwbmi.fsf@jpl.org> (raw)
In-Reply-To: <73630.1137440939@juniper.net>
[-- Attachment #1: Type: text/plain, Size: 1079 bytes --]
>>>>> In <73630.1137440939@juniper.net> Mark D. Baushke wrote:
> Note that the message 3:
> Content-Type: application/pgp; x-action=sign; format=text
> is still not really being recognized as a signed message. I do not know
> if there is any way to get GNUS to help us with that problem or not.
Well, where is such a content-type defined? I couldn't find it
out in the internet ("format=fixed" and "format=flowed" are
described in RFC2646 but "format=text" isn't).
Does "format=text" mean a message necessarily contains text that
can be displayed regardless of a type (which is "application/pgp"
in that case)? ...[1]
Or, does it hold good only in the case where a type is
"application/pgp"? ...[2]
If the answer for [1] is yes, we can do the following:
Add "application/pgp" to the variables `mm-automatic-display'
and `mm-inlined-types'. For an experiment, you can do it as
follows:
(push "application/pgp" mm-automatic-display)
(push "application/pgp" mm-inlined-types)
And modify mm-uu.el. Here's a patch, which can be applied to
both Gnus 5.10.6 and No Gnus:
[-- Attachment #2: mm-uu.el.diff.gz --]
[-- Type: application/x-gzip, Size: 281 bytes --]
[-- Attachment #3: Type: text/plain, Size: 25 bytes --]
The message 3 is here:
[-- Attachment #4: 3.gz --]
[-- Type: application/x-gzip, Size: 399 bytes --]
next prev parent reply other threads:[~2006-01-17 7:35 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 1:12 Mark D. Baushke
2006-01-13 23:24 ` Reiner Steib
2006-01-14 2:58 ` Mark D. Baushke
2006-01-14 14:58 ` Katsumi Yamaoka
2006-01-16 0:39 ` Katsumi Yamaoka
2006-01-16 6:36 ` Mark D. Baushke
2006-01-16 7:58 ` Katsumi Yamaoka
2006-01-16 8:41 ` Katsumi Yamaoka
2006-01-16 9:00 ` Katsumi Yamaoka
2006-01-16 19:17 ` Bill Wohler
2006-01-16 19:48 ` Mark D. Baushke
2006-01-17 7:35 ` Katsumi Yamaoka [this message]
2006-01-17 9:00 ` Mark D. Baushke
2006-01-17 10:53 ` Katsumi Yamaoka
2006-01-17 18:17 ` Mark D. Baushke
2006-01-18 5:33 ` Katsumi Yamaoka
2006-01-18 10:04 ` Mark D. Baushke
2006-01-18 12:40 ` Katsumi Yamaoka
2006-01-18 17:25 ` Mark D. Baushke
2006-01-18 17:29 ` Mark D. Baushke
2006-01-19 6:01 ` Katsumi Yamaoka
2006-01-19 9:13 ` Mark D. Baushke
2006-01-19 6:01 ` Synch of PGG (was Re: Gnus 5.10.6 problems with PGP/MIME (test cases)) Katsumi Yamaoka
2006-01-19 11:53 ` Synch of PGG Katsumi Yamaoka
2006-01-19 13:01 ` Simon Josefsson
2006-01-19 13:38 ` Reiner Steib
2006-01-19 13:47 ` Miles Bader
2006-01-19 14:48 ` Katsumi Yamaoka
2006-02-07 4:53 ` Gnus 5.10.6 problems with PGP/MIME (test cases) Daiki Ueno
2006-02-07 7:12 ` Mark D. Baushke
2006-02-07 7:46 ` Katsumi Yamaoka
2006-02-07 8:57 ` Daiki Ueno
2006-02-07 9:40 ` Mark D. Baushke
[not found] ` <9bda6607-510b-468c-bd1e-ec9b8865cdd2@well-done.deisui.org>
[not found] ` <15566.1139355525@juniper.net>
2006-02-08 8:09 ` Daiki Ueno
2006-02-08 8:30 ` Katsumi Yamaoka
2006-02-08 9:06 ` Daiki Ueno
2006-02-08 9:55 ` Katsumi Yamaoka
2006-02-09 5:24 ` Daiki Ueno
2006-02-09 5:29 ` Daiki Ueno
2006-02-09 5:48 ` Katsumi Yamaoka
2006-02-09 6:40 ` Mark D. Baushke
2006-02-09 6:44 ` Mark D. Baushke
2006-02-09 7:31 ` Katsumi Yamaoka
2006-02-09 7:42 ` Mark D. Baushke
[not found] ` <82857.1139467447-3r7Miqu9kMnR7s880joybQ@public.gmane.org>
2006-02-09 8:27 ` refered article lookup (was: Gnus 5.10.6 problems with PGP/MIME (test cases)) Jochen Küpper
2006-02-09 9:19 ` refered article lookup Katsumi Yamaoka
2006-02-08 15:27 ` Gnus 5.10.6 problems with PGP/MIME (test cases) Mark D. Baushke
2006-02-07 10:02 ` Katsumi Yamaoka
2006-02-07 23:40 ` Daiki Ueno
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=b4m3bjnwbmi.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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).