From: Simon Josefsson <jas@extundo.com>
Subject: Re: Verifying inline gpg signatures
Date: Fri, 21 Mar 2003 20:58:23 +0100 [thread overview]
Message-ID: <iluznno331c.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m3vfyo6ul1.fsf@defun.localdomain> (Jesper Harder's message of "Thu, 13 Mar 2003 00:20:10 +0100")
Jesper Harder <harder@ifa.au.dk> writes:
> Graham Murray <graham@gmurray.org.uk> writes:
>
>> Yes. Looking again at the messages which do not automatically
>> verify, they are sent from Mozilla and have Content-Type: flowed. So
>> that could be what is causing the problem.
>
> Yes, format=flowed is the problem -- I can reproduce that with f=f
> messages produced by Gnus, too. Like this one.
The reason is that `gnus-display-mime' says
...
(let* ((handles (or ihandles
(mm-dissect-buffer nil gnus-article-loose-mime)
(and gnus-article-emulate-mime
(mm-uu-dissect))))
...
which means that pre-MIME parsing (mm-uu-dissect) is only done when
MIME isn't found. Apparently, a MIME message with only a text/plain
part makes mm-dissect-buffer return nil, so it is treated as a
pre-MIME message. So messages with CT parameters, such as
format=flowed, or generally any non-trivial MIME message, is treated
as a text part and mm-uu-dissect is never run.
Perhaps mm-uu-dissect should be run on all text/plain parts? Or all
text/.* parts? Opinions?
next prev parent reply other threads:[~2003-03-21 19:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-11 20:15 Graham Murray
2003-03-12 20:31 ` Jesper Harder
2003-03-12 20:51 ` Graham Murray
2003-03-12 21:28 ` Jesper Harder
2003-03-12 22:39 ` Graham Murray
2003-03-12 23:20 ` Jesper Harder
2003-03-21 19:58 ` Simon Josefsson [this message]
2003-03-21 21:24 ` Jesper Harder
2003-04-24 2:09 ` Jesper Harder
2003-04-24 15:47 ` Simon Josefsson
2003-03-21 21:42 ` ShengHuo ZHU
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=iluznno331c.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).