From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/35727 Path: main.gmane.org!not-for-mail From: Simon Josefsson Newsgroups: gmane.emacs.gnus.general Subject: Re: Crypto-MIME in GNUS Date: 10 Apr 2001 15:23:24 +0200 Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035171423 4628 80.91.224.250 (21 Oct 2002 03:37:03 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:37:03 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: (qmail 26573 invoked by alias); 10 Apr 2001 15:22:47 -0000 Original-Received: (qmail 26568 invoked from network); 10 Apr 2001 15:22:47 -0000 Original-Received: from dolk.extundo.com (195.42.214.242) by gnus.org with SMTP; 10 Apr 2001 15:22:47 -0000 Original-Received: from sjosefsson-lap (slipsten.extundo.com [195.42.214.241]) (authenticated) by dolk.extundo.com (8.11.3/8.11.3) with ESMTP id f3AFNkj18942; Tue, 10 Apr 2001 17:23:48 +0200 Original-To: "Georg C. F. Greve" In-Reply-To: ("Georg C. F. Greve"'s message of "10 Apr 2001 15:27:54 +0200") Mail-Copies-To: nobody User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.2 (Urania) Original-Lines: 57 Xref: main.gmane.org gmane.emacs.gnus.general:35727 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:35727 "Georg C. F. Greve" writes: > >> The biggest problem was that the gnus crypto function didn't work > >> since it gave mailcrypt the buffer to encrypt that didn't contain > >> headers so mailcrypt had no way to determine who to encrypt it > >> for. > > sj> Weird, this is definitely not the case for me. Could you tell > sj> why `message-options-set-recipient' function fail to figure out > sj> recipients? Or if there's some problem in mml2015 when mailcrypt > sj> is given the information snarfed from the *mail* buffer? > > I'm suspecting you are not using Crypto-*MIME* but rather encrypt the > whole buffer as it is (which is the old way gnus used to do it). I > have been doing it myself but a lot of non-gnus users have problems > with it... also if there is a standard one should stick to it. Well, there are at least two standards here. :-) FWIW, people I communicate with that uses Outlook and some PGP plugin does not handle PGP/MIME (RFC2015). The plugin perform PGP-operations on each MIME part individually and only insert the PGP output instead of the MIME content of that part. I don't think it even modifies MIME headers. Yuk. > And when using Crypto-MIME, mailcrypt never ever sees the headers > (which is as it should be) - it is gnus' job to figure out the > recipients and the last time I tried (CVS version about three months > ago), it didn't do it. So I wrote these other functions. Ok -- that's what I meant, this works for me with current Gnus. > >> Also when I got it to work half-way I realized that CC and BCC > >> were ignored. > > sj> Right, `message-options-set-recipient' only look at the To: > sj> header. > > Exactly. Which is stupid. Unless the others are also you (which is not > the standard case, imho), they won't be able to read the mail then. So > why bother sending it to them at all? I've no idea. :-) I changed it, it should look at Cc and Bcc now. > >> Also I wanted a nice way to determine whether to encrypt or sign > >> that I could toggle while composing the mail. > > sj> Hm, `C-c RET s p' or `C-c RET c p'? > > ...does pretty much the same. But only almost. It only encrypts the > following part, not the whole message. When I encrypt I normally want > the whole thing encrypted... otherwise you run a high chance to > insert another part and accidentally lose encryption that way. Ah, yes, I agree. Those commands are made to only sign or encrypt the current MML part, but maybe that's not very intuitive. Perhaps they could be changed?