From: "David Presotto" <presotto@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] In-reply-to
Date: Sat, 28 Dec 2002 16:03:45 -0500 [thread overview]
Message-ID: <c8ecbaa953721d0d6a3084e7ff58450a@plan9.bell-labs.com> (raw)
When replying to a message with a message-id, upas now
adds a In-Reply-To: header containing the original
message number. This is for people that maintain converation
threads this way.
Also, /mail/box/<username>/pipefrom replaces /bin/upassend.
If it exists, marshal pipes the prepared message to it rather
than upas/send. In the case of replies, upas passes to it the
upas/fs directory of the message being replied to in the
env variable `replymsg'.
You can use pipefrom for a number of things; saving copies
of messages you send, making the reply address match the address
the mail was sent to, adding recipients to your filter lists...
reply other threads:[~2002-12-28 21:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=c8ecbaa953721d0d6a3084e7ff58450a@plan9.bell-labs.com \
--to=presotto@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).