From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/19683 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.gnus.general Subject: Re: MIME and mailcrypt Date: 04 Dec 1998 19:22:53 +0100 Sender: owner-ding@hpc.uh.edu Message-ID: References: <871zmgoc4d.fsf@wsfs05.mckesson.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 X-Trace: main.gmane.org 1035157988 12835 80.91.224.250 (20 Oct 2002 23:53:08 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Sun, 20 Oct 2002 23:53:08 +0000 (UTC) Return-Path: Original-Received: from gizmo.hpc.uh.edu (gizmo.hpc.uh.edu [129.7.102.31]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id NAA28974 for ; Fri, 4 Dec 1998 13:23:48 -0500 (EST) Original-Received: from sina.hpc.uh.edu (lists@sina.hpc.uh.edu [129.7.3.5]) by gizmo.hpc.uh.edu (8.9.1/8.9.1) with ESMTP id MAA26017; Fri, 4 Dec 1998 12:23:24 -0600 Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 04 Dec 1998 12:23:25 -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 MAA03650 for ; Fri, 4 Dec 1998 12:23:14 -0600 (CST) Original-Received: from jagor.srce.hr (hniksic@jagor.srce.hr [161.53.2.130]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id NAA28950 for ; Fri, 4 Dec 1998 13:23:04 -0500 (EST) Original-Received: (from hniksic@localhost) by jagor.srce.hr (8.9.0/8.9.0) id TAA16840; Fri, 4 Dec 1998 19:22:54 +0100 (MET) Original-To: ding@gnus.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h writes: > "Hrvoje" == Hrvoje Niksic writes: > > Hrvoje> Or, am I missing something? > > I think what you are missing is that mailcrypt (through PGP) > encloses the entire message buffer, from the '--text follows this > line--' line to (point-max). In other words, mailcrypt has no idea > what a multipart message is. This sounds like a design deficiency in mailcrypt. But it sounds fixable; a PGP-enhanced message.el could create the MIME wonder, and then call mailcrypt on the result, and then trivially insert the multipart/signed junk around it. This could be done around the time when `message-send-hook' is run, or even after that. The only thing that should be "fixed" in mailcrypt is the dependency on "--text follows this line--"-style message; ideally, a mailcrypt function should be called to handle the encryption/signing of a textual region, and it should return the result in Lisp. If this process bombs out, the user should be presented with the original message buffer, MML and all. -- Hrvoje Niksic | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Don't get even, get odd!