Gnus development mailing list
 help / color / mirror / Atom feed
From: Jesper Harder <harder@myrealbox.com>
Subject: Re: Verifying inline gpg signatures
Date: Thu, 24 Apr 2003 04:09:43 +0200	[thread overview]
Message-ID: <m3n0igabo8.fsf@defun.localdomain> (raw)
In-Reply-To: <m33clgxvkb.fsf@defun.localdomain>

Jesper Harder <harder@myrealbox.com> writes:

[We fail to detect inline PGP with format=flowed]

> Simon Josefsson <jas@extundo.com> writes:
>
>> 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.

But I suppose making it work for non-QP encoded articles is better than
nothing?

I first assumed that it wouldn't be useful because Gnus always QP
encodes inline PGP, so it didn't work when I tested it with a message
from Gnus.  But the Mozilla plugin which probably generates all of the
problematic messages doesn't do it for us-ascii, so it works in that
case.

Should we do it?



  reply	other threads:[~2003-04-24  2:09 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
2003-04-24  2:09               ` Jesper Harder [this message]
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=m3n0igabo8.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).