From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/35720 Path: main.gmane.org!not-for-mail From: "Georg C. F. Greve" Newsgroups: gmane.emacs.gnus.general Subject: Re: Crypto-MIME in GNUS Date: 10 Apr 2001 15:27:54 +0200 Sender: "Georg C. F. Greve" Message-ID: References: NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" X-Trace: main.gmane.org 1035171417 4587 80.91.224.250 (21 Oct 2002 03:36:57 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:36:57 +0000 (UTC) Return-Path: Original-Received: (qmail 25532 invoked by alias); 10 Apr 2001 13:28:59 -0000 Original-Received: (qmail 25527 invoked from network); 10 Apr 2001 13:28:58 -0000 Original-Received: from mail-ffm-p.arcor-ip.de (HELO mail.arcor-ip.de) (145.253.2.10) by gnus.org with SMTP; 10 Apr 2001 13:28:58 -0000 Original-Received: from fusebox.gnu-hamburg (212.144.208.69) by mail.arcor-ip.de; 10 Apr 2001 15:28:34 +0200 Original-Received: from reason.gnu-hamburg (root@reason.gnu-hamburg [10.129.4.1]) by fusebox.gnu-hamburg (8.11.1/8.11.1) with ESMTP id f3ADSXu14167 for ; Tue, 10 Apr 2001 15:28:33 +0200 Original-Received: (from greve@localhost) by reason.gnu-hamburg (8.11.2/8.11.2/Debian 8.11.2-1) id f3ADRsK03099; Tue, 10 Apr 2001 15:27:54 +0200 Original-To: ding@gnus.org Organisation: GNU Project X-Home-Page: http://www.gnu.org/people/greve.html X-PGP-Affinity: will accept encrypted messages for GNU Privacy Guard X-PGP-Fingerprint: 2D68 D553 70E5 CCF9 75F4 9CC9 6EF8 AFC2 8657 4ACA In-Reply-To: (Simon Josefsson's message of "10 Apr 2001 12:50:40 +0200") User-Agent: Gnus/5.090001 (Oort Gnus v0.01) Emacs/20.7 Original-Lines: 75 Xref: main.gmane.org gmane.emacs.gnus.general:35720 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:35720 --==-=-= Content-Type: multipart/mixed; boundary="=-=-=" --=-=-= Content-Transfer-Encoding: quoted-printable Hi Simon, || On 10 Apr 2001 12:50:40 +0200 || Simon Josefsson wrote:=20 >> 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. 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. >> 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? >> 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. >> What is also nice is an easy way to include public keys into the >> mail with correct MIME type. The solution I have is ugly but I >> didn't have time to think about something better and for now it >> works. sj> Ah, this is really useful.=20=20 So glad you agree. :-) sj> Is there a MIME type for pgp public sj> keys?=20=20 Yes: application/pgp-keys sj> Cool. I'm still using the mailcrypt default bindings which gets sj> me a nice menu where I can choice to insert my public key as a sj> block. ...which requires much more action on the receiving part to import the key. With a proper MIME part, a good mailreader can import that key with a single keystroke.=20 Regards, Georg =2D-=20 Georg C. F. Greve Free Software Foundation Europe (http://fsfeurope.org) Brave GNU World (http://brave-gnu-world.org) --=-=-=-- --==-=-= Content-Type: application/pgp-signature -----BEGIN PGP MESSAGE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard iD8DBQE60wpabvivwoZXSsoRAnE7AJsGR9bn22vEs4bWk41BISOetfI+pACfS5o2 3wmbezG8m99GV03kky+tTGc= =bnme -----END PGP MESSAGE----- --==-=-=--