From: "boyd, rounin" <boyd@insultant.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] mail
Date: Mon, 1 Sep 2003 16:22:31 +0200 [thread overview]
Message-ID: <032a01c37094$7b6b34c0$b9844051@insultant.net> (raw)
In-Reply-To: <ffe76a32a00e8a6c09d4be67ae5ff2d1@plan9.bell-labs.com>
> And, by the way, filter looks through the message to get the
> sender address.
i see. i wanted to avoid messages in /tmp and 822 parsing.
i shall have to think about it. perhaps i should write a tool
(i already have the code) to pick the headers apart, although
i'm loathed to do it.
upas/fs looks interesting. thanks.
next prev parent reply other threads:[~2003-09-01 14:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-01 14:08 [9fans] (no subject) David Presotto
2003-09-01 14:22 ` boyd, rounin [this message]
2003-09-01 14:26 ` [9fans] mail David Presotto
2003-09-01 14:37 ` boyd, rounin
-- strict thread matches above, loose matches on Subject: below --
2003-09-01 3:09 boyd
2003-09-01 13:54 ` David Presotto
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='032a01c37094$7b6b34c0$b9844051@insultant.net' \
--to=boyd@insultant.net \
--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).