From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/21770 Path: main.gmane.org!not-for-mail From: "James H. Cloos Jr." Newsgroups: gmane.emacs.gnus.general Subject: Re: Mime PGP for pgnus Date: 04 Mar 1999 15:52:35 -0600 Sender: owner-ding@hpc.uh.edu 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 1035159812 24648 80.91.224.250 (21 Oct 2002 00:23:32 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:23:32 +0000 (UTC) Cc: ding@gnus.org Return-Path: Original-Received: from fisher.math.uh.edu (fisher.math.uh.edu [129.7.128.35]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id QAA28386 for ; Thu, 4 Mar 1999 16:54:45 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by fisher.math.uh.edu (8.9.1/8.9.1) with ESMTP id PAB09475; Thu, 4 Mar 1999 15:53:41 -0600 (CST) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Thu, 04 Mar 1999 15:53:39 -0600 (CST) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.7.3/8.7.3) with ESMTP id PAA05192 for ; Thu, 4 Mar 1999 15:53:29 -0600 (CST) Original-Received: from jhcloos.com (cloos@austin.jhcloos.com [206.224.83.202]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id QAA28348 for ; Thu, 4 Mar 1999 16:53:19 -0500 (EST) Original-Received: (from cloos@localhost) by jhcloos.com (8.8.7/8.8.7) id PAA15798; Thu, 4 Mar 1999 15:52:35 -0600 Original-To: soma@cs.unm.edu (Anil B. Somayaji) In-Reply-To: soma@cs.unm.edu's message of "03 Mar 1999 20:18:20 -0700" Original-Lines: 72 Precedence: list X-Majordomo: 1.94.jlt7 Xref: main.gmane.org gmane.emacs.gnus.general:21770 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:21770 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>>>> "Anil" == Anil B Somayaji writes: Cloos> Cloos> Cloos> This is the message Cloos> Cloos> Anil> While this syntax tells you more about what the real message will look Anil> like, it is really ugly - not something you'd want to see often, and Anil> hard to generate by hand if things got munged while editing. Cloos> Cloos> This is the message Cloos> Anil> This would be really nice - clean, easy to type in manually. However, Anil> how would this integrate with other mml stuff? If that could all be Anil> normal (i.e. the same as without signing), with the backend figuring Anil> out the right MIME structure, that would be excellent. That was my intent. Specifically, I'm thinking along the lines of having unknown mml tags looked up in an alist whenever they are processed -- this will most likely require one alist for each step of the process, assuming multiple steps even occur.... By using an alist, other modules can seemlessly implement non-internal tags, much like how minor modes interact with the major modes. A tag like <#mc-sign> would then require args akin to (mc-sign)'s. Getting the tage right for anon-relays would take some care. Anil> James, thanks for bringing this up. I like to PGP sign all of my Anil> messages, and until I upgraded to the recent pgnus (>0.70) versions, I Anil> did this using TM's MIME PGP stuff. The new mml stuff breaks TM, so Anil> I've switched to plain PGP signatures. I'd like to switch back, but I Anil> haven't spent enough time with the gnus code to figure out how to Anil> implement it with mml. But, if someone else starts, I'll be happy to Anil> help! Yes, I also like to sign everything, and would much prefer to MIME everything as well, since it works so well with pgnus and AFAIK vm. I'd also like to see rfc2440 messages presented just like rfc2015 messages are. Ie, a pseudo-mime-part button a la the pseudo-mime buttons generated for uuencoded sections, et al. Also, mailcrypt should be able to hook in to verify the message if said button is selected, for either 2440 or 2015 messages. Unfortunatly, 2440 & 2015 messages cannot be inter-converted; the buffer range that is digested includes the body part headers in 2015 and Hash: headers in 2040.... Perhaps -- to plagiarise another post today -- my wetware will be able to page in enough of my (presumably not _too_ archaic :) lisp knowl- edge that I may be able to code some of this w/o spending several millidays looking up docs for each sexp written..... - -JimC - -- James H. Cloos, Jr. 1024D/ED7DAEA6 E9E9 F828 61A4 6EA9 0F2B 63E7 997A 9F17 ED7D AEA6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v0.9.2 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE23wCemXqfF+19rqYRAgWSAKCxLdeDRy3dGQDF9/9U+N3WyFkrTACeIQeB CYS9BsaM/IcwWwMCG3Dbpy0= =xmfj -----END PGP SIGNATURE-----