From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/64840 Path: news.gmane.org!not-for-mail From: Katsumi Yamaoka Newsgroups: gmane.emacs.gnus.general Subject: Re: Simplify inline forward headers Date: Mon, 25 Jun 2007 19:36:56 +0900 Organization: Emacsen advocacy group Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1182767836 11407 80.91.229.12 (25 Jun 2007 10:37:16 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 25 Jun 2007 10:37:16 +0000 (UTC) To: ding@gnus.org Original-X-From: ding-owner+M13351=ding+2Daccount=gmane.org@lists.math.uh.edu Mon Jun 25 12:37:15 2007 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from util0.math.uh.edu ([129.7.128.18]) by lo.gmane.org with esmtp (Exim 4.50) id 1I2lwX-0001Bu-Sx for ding-account@gmane.org; Mon, 25 Jun 2007 12:37:14 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by util0.math.uh.edu with smtp (Exim 4.63) (envelope-from ) id 1I2lwW-0005bt-Nl for ding-account@gmane.org; Mon, 25 Jun 2007 05:37:12 -0500 Original-Received: from mx1.math.uh.edu ([129.7.128.32]) by util0.math.uh.edu with esmtps (TLSv1:AES256-SHA:256) (Exim 4.63) (envelope-from ) id 1I2lwV-0005bn-CL for ding@lists.math.uh.edu; Mon, 25 Jun 2007 05:37:11 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx1.math.uh.edu with esmtp (Exim 4.67) (envelope-from ) id 1I2lwU-0000xu-0S for ding@lists.math.uh.edu; Mon, 25 Jun 2007 05:37:11 -0500 Original-Received: from orlando.hostforweb.net ([216.246.45.90]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1I2lwQ-00067n-00 for ; Mon, 25 Jun 2007 12:37:06 +0200 Original-Received: from [66.225.201.151] (port=43576 helo=mail.jpl.org) by orlando.hostforweb.net with esmtpa (Exim 4.63) (envelope-from ) id 1I2lwJ-00010Z-SM for ding@gnus.org; Mon, 25 Jun 2007 05:37:00 -0500 X-Hashcash: 1:20:070625:ding@gnus.org::ACtNxC/OSE1lt5iS:00003m+Z X-Face: #kKnN,xUnmKia.'[pp`;Omh}odZK)?7wQSl"4o04=EixTF+V[""w~iNbM9ZL+.b*_CxUmFk B#Fu[*?MZZH@IkN:!"\w%I_zt>[$nm7nQosZ<3eu;B:$Q_:p!',P.c0-_Cy[dz4oIpw0ESA^D*1Lw= L&i*6&( User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (gnu/linux) Cancel-Lock: sha1:hFg1P3OqXfxRm7BupXNbkqg/D7w= X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - orlando.hostforweb.net X-AntiAbuse: Original Domain - gnus.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - jpl.org X-Source: X-Source-Args: X-Source-Dir: X-Spam-Score: -2.4 (--) List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:64840 Archived-At: >>>>> In Leo wrote: > ----- Katsumi Yamaoka (2007-06-25) wrote:----- >>> I often have to inline forward messages to people who are not using >>> Gnus. However, almost all headers in the original messages are >>> included which make the emails look messy. >> >>> I wonder how to make inline forward only include headers in >>> gnus-visible-headers. >> >> `gnus-visible-headers' is unlikely to contain some headers which are >> indispensable for forwarding MIME messages. > By `forwarding MIME messages' do you mean the non-inline alternatives of > `gnus-summary-mail-forward'? I meant just inline, i.e., using MML. But I might have misunderstood; though I'm not quite sure of it, even if removing all headers in the case where MML is used, it might cause no problem if `message-remove-ignored-headers' is performed in the present way. Please note, Gnus doesn't use MML by default when forwarding signed or encrypted messages. > We could use another variable (e.g. message-forward-kept-headers) to > contain headers that should be kept. I don't want a new variable which is simply an inverse of an existing variable. >> You can modify the `message-forward-ignored-headers' variable instead. >> I don't have an idea of making it remove more headers by default. > I want to make something like this to work by modifying > `message-remove-ignored-headers': > if message-forward-kept-headers is nil, > `message-forward-ignored-headers' is used; otherwise, > message-forward-kept-headers is used. > Ideas? I don't know what may become *the default values* that satisfy many users. Although I humbly think adding "^Received:" to the default value of `message-forward-ignored-headers' might be a good idea, I'm satisfied with deleting some headers manually. ;-)