Gnus development mailing list
 help / color / mirror / Atom feed
From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: Problem with Mozilla Thunderbird PGP mails
Date: Wed, 17 Mar 2004 12:06:12 +1000	[thread overview]
Message-ID: <microsoft-free.8765d4p6qz.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <m38yi1341t.fsf@defun.localdomain> (Jesper Harder's message of "Tue, 16 Mar 2004 03:43:10 +0100")

[-- Attachment #1: Type: text/plain, Size: 901 bytes --]

* Jesper Harder <harder@ifa.au.dk> writes:

  > Hit the Thunderbird developers with a cluestick?

I like this solution. :-)

  > Seriously, to accomodate inapproriate use of inline pgp we have to
  > look for magic strings inside MIME multiparts (and format=flowed
  > parts).

Couldn't Gnus just simply scan the message for 
"----Begin PGP Signed Message----", or whatever it is?  But that won't
solve the problem of PGG not being able to verify the sig (mailcrypt
can, BTW).

So this problem is two-fold (and not our fault)...

  1) Gnus doesn't recognise that the message is signed.

  2) PGG can't verify the signature. (possibly related to #1)

 

-- 
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
|              Ashes to ashes, dust to dust.               |
|      The proof of the pudding, is under the crust.       |
|------------------------------<sryoungs@bigpond.net.au>---|

[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]

  reply	other threads:[~2004-03-17  2:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-15 23:46 Steve Youngs
2004-03-16  0:37 ` Jesper Harder
2004-03-16  1:57   ` Steve Youngs
2004-03-16  2:43     ` Jesper Harder
2004-03-17  2:06       ` Steve Youngs [this message]
2004-03-17 14:40         ` Jesper Harder
2004-05-16 14:34       ` Lars Magne Ingebrigtsen
2004-05-16 15:39         ` Jesper Harder
2004-05-16 15:59           ` Lars Magne Ingebrigtsen

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=microsoft-free.8765d4p6qz.fsf@eicq.dnsalias.org \
    --to=sryoungs@bigpond.net.au \
    /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).