From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/3207 Path: news.gmane.org!not-for-mail From: Vincent Bernat Newsgroups: gmane.emacs.gnus.user Subject: Re: gnus and enigmail Date: Mon, 24 Nov 2003 18:42:09 -0800 Organization: Khabale.org Message-ID: References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Trace: sea.gmane.org 1138669387 18017 80.91.229.2 (31 Jan 2006 01:03:07 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:03:07 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:31:52 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!nsc.no!nextra.com!news.tele.dk!news.tele.dk!small.news.tele.dk!news-fra1.dfn.de!news-mue1.dfn.de!newsfeed.stueberl.de!teaser.fr!lucas.teaser.fr!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: guybrush.loria Original-X-Trace: lucas.loria 1069728134 30794 10.0.1.3 (25 Nov 2003 02:42:14 GMT) Original-X-Complaints-To: usenet@lucas.teaser.fr Original-NNTP-Posting-Date: Tue, 25 Nov 2003 02:42:14 +0000 (UTC) X-PGP-KeyID: 0xF22A794E X-PGP-Fingerprint: 5854 AF2B 65B2 0E96 2161 E32B 285B D7A1 F22A 794E User-Agent: Gnus/5.1003 (Gnus v5.10.3) XEmacs/21.4 (Rational FORTRAN, linux) Cancel-Lock: sha1:RhcD/n71FrP26IlelzJ2yAeLp5Q= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:3348 Original-Lines: 24 X-Gnus-Article-Number: 3348 Tue Jan 17 17:31:52 2006 Xref: news.gmane.org gmane.emacs.gnus.user:3207 Archived-At: OoO La nuit ayant déjà recouvert d'encre ce jour du samedi 22 novembre 2003, vers 23:28, Simon Josefsson disait: >>>> 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. >> >> Is it easy to do the receiving part ? > Boring work, but can be done. I have just check a message posted with Ximian Evolution 1.4.5 and they now sign correctly outgoing messages. Since I do not know any other clients messing with that, it should be useless to start coding alternate decodings. -- panic("huh?\n"); 2.2.16 /usr/src/linux/arch/i386/kernel/smp.c