From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: gnus-summary-mail-forward-full-headers
Date: 25 Oct 1996 09:03:18 +0100 [thread overview]
Message-ID: <x6wwwfii7t.fsf@eyesore.no> (raw)
In-Reply-To: Sean Lynch's message of 24 Oct 1996 10:22:34 -0700
Sean Lynch <seanl@Internex.NET> writes:
> Since I couldn't find a function in Gnus to forward with full headers,
> so I could complain about spam, I wrote a function to do it:
It sounds like a useful idea, but perhaps just using a prefix with
`S o m' and `S o p' should force full headers instead? I've now done
so in 0.53.
--
"Yes. The journey through the human heart
would have to wait until some other time."
prev parent reply other threads:[~1996-10-25 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-24 17:22 gnus-summary-mail-forward-full-headers Sean Lynch
1996-10-24 21:39 ` gnus-summary-mail-forward-full-headers Eric Hendrickson
1996-10-25 8:03 ` Lars Magne Ingebrigtsen [this message]
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=x6wwwfii7t.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).