From: Simon Josefsson <jas@extundo.com>
Subject: Re: gnus and enigmail
Date: Sat, 22 Nov 2003 19:16:15 +0100 [thread overview]
Message-ID: <ilu3ccgb768.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m365hci8ko.fsf@neo.loria>
Vincent Bernat <vincent.bernat@raysa.org> writes:
> Hello !
>
> Enigmail may sign in plain text but then Gnus is not able to check the
> signature. What should I change to make Gnus check signatures for this
> kind of mail ?
Could you post an example with Enigmail?
> Evolution inverts MIME decoding and GPG signing so signatures appear
> as bad. Is there a way to tell Gnus to invert MIME decoding and GPG
> checking to check this kind of signatures as well ?
Not right now, I think. The inline PGP needs an overhaul. During
sending, it should warn the user about all possible dangers of using
QP, and allow the user to chose how to send it (there are three
different ways of sending inline PGP with QP). During receiving, it
should try all three different ways before giving up.
next parent reply other threads:[~2003-11-22 18:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m365hci8ko.fsf@neo.loria>
2003-11-22 18:16 ` Simon Josefsson [this message]
[not found] ` <m38ym8f2ea.fsf@neo.loria>
[not found] ` <iluoev38rxb.fsf@latte.josefsson.org>
2003-11-25 2:42 ` Vincent Bernat
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=ilu3ccgb768.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).