From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/23245 Path: main.gmane.org!not-for-mail From: Lars Magne Ingebrigtsen Newsgroups: gmane.emacs.gnus.general Subject: Re: I'm alive! Date: 13 Jun 1999 10:16:23 +0200 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 1035161014 976 80.91.224.250 (21 Oct 2002 00:43:34 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 00:43:34 +0000 (UTC) Return-Path: Original-Received: from farabi.math.uh.edu (farabi.math.uh.edu [129.7.128.57]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id EAA17581 for ; Sun, 13 Jun 1999 04:15:58 -0400 (EDT) Original-Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5]) by farabi.math.uh.edu (8.9.1/8.9.1) with ESMTP id DAB16814; Sun, 13 Jun 1999 03:15:46 -0500 (CDT) Original-Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Sun, 13 Jun 1999 03:16:32 -0500 (CDT) Original-Received: from sclp3.sclp.com (root@sclp3.sclp.com [204.252.123.139]) by sina.hpc.uh.edu (8.9.3/8.9.3) with ESMTP id DAA21627 for ; Sun, 13 Jun 1999 03:16:20 -0500 (CDT) Original-Received: from quimbies.gnus.org (bang.netfonds.no [195.1.89.231]) by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id EAA17566 for ; Sun, 13 Jun 1999 04:15:23 -0400 (EDT) Original-Received: (from larsi@localhost) by quimbies.gnus.org (8.8.7/8.8.7) id KAA14941; Sun, 13 Jun 1999 10:16:36 +0200 X-Now-Reading: Sheri S. Tepper's _The True Game_ X-Now-Playing: singles's _cotw_ Original-To: ding@gnus.org In-Reply-To: Florian Weimer's message of "12 Jun 1999 17:51:14 +0200" User-Agent: Gnus/5.070087 (Pterodactyl Gnus v0.87) XEmacs/21.2 (Sumida) X-Face: &w!^oO~dS|}-P0~ge{$c!h\ writes: > While you were away, I've stated publicly that I consider implementing > RFC 2015 support (MIME-PGP) for Gnus. It seems that quite a few people > are interested in that feature. They are. > As far as I understand the current MIME implementation, there is neither > a hook which makes it possible to generate MIME content based on the > encoded representation of another part (required for encoding), nor a > hook with which you can feed the raw message text contained in a part > through an external program (or an elisp function, for that matter) > and recursively process the output of this filter. I think a facility > analogous to `mailcap-mime-data' could be used. There is a `gnus-mime-multipart-functions' variable, and it can do whatever it wants with the multiparts it receives. (I added this to make it possible to do RFC 2015.) I haven't really looked all that closely at what a function that were to do RFC 2015 decoding would have to do, though. > In addition, a small change to `quoted-printable-encode-region' is > necessary: Optionally, "\nFrom " has to be encoded as "\nFrom=20" (as > required by MIME-PGP, because MTAs tend to replace a "\nFrom " with a > "\n>From ", thus invalidating the signature). In addition, when encoding > a part inside a `multipart/signed', `quoted-printable-encode-region' > has to be called not only for parts containing 8-bit characters, but > also when a "\nFrom " is encountered. I don't think this belongs in `quoted-printable-encode-region'. I certainly wouldn't want to see (say) a news article get bumped up from 7bit to qouted-printable just because there's a "\nFrom " in the message somewhere. I think the RFC 2015 function itself should do this encoding -- by calling `quoted-printable-encode-region', and then encoding the "\nFrom "'s itself. -- (domestic pets only, the antidote for overdose, milk.) larsi@gnus.org * Lars Magne Ingebrigtsen