Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@chow.mat.jhu.edu>
Cc: ding@gnus.org
Subject: Re: old style forwarding
Date: Fri, 28 May 1999 14:33:25 -0400	[thread overview]
Message-ID: <x7u2sxrqmi.fsf@chow.mat.jhu.edu> (raw)
In-Reply-To: Steinar Bang's message of "28 May 1999 16:31:21 +0200"

Steinar Bang <sb@metis.no> writes:
> That's what I've been doing.  That is, the ordinary forward adds to
> many headers, so I've been using "Digest and Mail".  Less stuff to
> edit away... 

Speaking about the stuff to edit away, included below are the headers
I get when I try to forward your messages.  It seems to me that many
of these really should not be here, e.g. "X-Gnus-Mail-Source",
"X-Gnus-Article-Number" and maybe "Xref", since they were added
by Gnus.  Similarly, maybe "X-From-Line:" should be removed or
converted back to "From" I think.

Also, it would be nice if I could configure my set-up to omit
additional headers, e.g. Received headers.  Is there I variable for
this?  I looked in the manual (0.80) and couldn't find it.

Dan

X-From-Line: owner-ding@hpc.uh.edu  Fri May 28 10:33:12 1999
Return-Path: <owner-ding@hpc.uh.edu>
Received: from lisa.math.uh.edu (lisa.math.uh.edu [129.7.128.49])
	by chow.mat.jhu.edu (8.9.1/8.9.1) with ESMTP id KAA23427
	for <jdc@chow.mat.jhu.edu>; Fri, 28 May 1999 10:33:11 -0400 (EDT)
Received: from sina.hpc.uh.edu (lists@Sina.HPC.UH.EDU [129.7.3.5])
	by lisa.math.uh.edu (8.9.1/8.9.1) with ESMTP id JAC26217;
	Fri, 28 May 1999 09:33:10 -0500 (CDT)
Received: by sina.hpc.uh.edu (TLB v0.09a (1.20 tibbs 1996/10/09 22:03:07)); Fri, 28 May 1999 09:32:27 -0500 (CDT)
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 JAA06770
	for <ding@hpc.uh.edu>; Fri, 28 May 1999 09:32:19 -0500 (CDT)
Received: from viffer.oslo.metis.no (sb@viffer.oslo.metis.no [195.0.254.249])
	by sclp3.sclp.com (8.8.5/8.8.5) with ESMTP id KAA00864
	for <ding@gnus.org>; Fri, 28 May 1999 10:31:24 -0400 (EDT)
Received: (from sb@localhost)
	by viffer.oslo.metis.no (8.8.8/8.8.8) id QAA08171;
	Fri, 28 May 1999 16:31:21 +0200
To: ding@gnus.org
Subject: Re: old style forwarding
References: <whhfoxmne0.fsf@viffer.oslo.metis.no> <7t1btf546l6.fsf@fly.srk.fer.hr>
From: Steinar Bang <sb@metis.no>
Date: 28 May 1999 16:31:21 +0200
In-Reply-To: Toni Drabik's message of "28 May 1999 16:22:29 +0200"
X-Gnus-Mail-Source: file:~/Mail/ding
Message-ID: <wh7lptl0zq.fsf@viffer.oslo.metis.no>
User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/20.4 (Emerald)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ding@hpc.uh.edu
Precedence: list
X-Majordomo: 1.94.jlt7
Lines: 15
Xref: chow.mat.jhu.edu ding:12523
X-Gnus-Article-Number: 12523   Fri May 28 12:46:46 1999


  reply	other threads:[~1999-05-28 18:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-05-28 11:42 Steinar Bang
1999-05-28 14:22 ` Toni Drabik
1999-05-28 14:31   ` Steinar Bang
1999-05-28 18:33     ` Dan Christensen [this message]
1999-06-13  0:46       ` Lars Magne Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x7u2sxrqmi.fsf@chow.mat.jhu.edu \
    --to=jdc@chow.mat.jhu.edu \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).