From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Verifying inline gpg signatures
Date: Fri, 21 Mar 2003 22:24:04 +0100 [thread overview]
Message-ID: <m33clgxvkb.fsf@defun.localdomain> (raw)
In-Reply-To: <iluznno331c.fsf@latte.josefsson.org>
Simon Josefsson <jas@extundo.com> writes:
> Jesper Harder <harder@ifa.au.dk> writes:
>
>> 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?
It's a step in the right direction ... but not enough. The problem is
that text/plain parts with a format parameter haven't been QP decoded
at this stage, so uu-dissect will fail.
It happens because of this code in `article-decode-charset':
(when (and (or (not ctl)
(equal (car ctl) "text/plain"))
(not format)) ;; article with format will decode later.
(mm-decode-body
charset (and cte (intern (downcase
(gnus-strip-whitespace cte))))
(car ctl) prompt))
I didn't investigate what happens if the exception for text/plain parts
with a format parameter is removed -- but it was obviously put there
deliberately.
next prev parent reply other threads:[~2003-03-21 21:24 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
2003-03-21 21:24 ` Jesper Harder [this message]
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=m33clgxvkb.fsf@defun.localdomain \
--to=harder@myrealbox.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).