From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] /n/smtp
Date: Wed, 1 Nov 2000 21:00:33 +0100 [thread overview]
Message-ID: <007501c0443e$6537f100$0ab9c6d4@cybercable.fr> (raw)
In-Reply-To: <20001101182523.BEDAD199E6@mail>
From: <forsyth@caldo.demon.co.uk>
> boyd fell into the RFC trap by naming the service /n/smtp.
thanks. yes i should have called it something else: /n/rfc822
or /chan/postoffice.
it's sendmail -t funtionality that i want; reading the
destinations out of the headers. this does work. it has
nothing to do with smtp until the message gets sent via
smtp and i never envisioned an MTA dumping messages into
it, just the user agent.
russ told me that it would serve no purpose, but i
'counter attacked' :-) importing it off the firewall.
a free proxy; code running on the the firewall with
9P/styx gluing it to wherever it's needed.
how many plan 9 programmers does it take to change a
lightbulb? none, you just import one from somewhere
else :-)
if i could concentrate at work, i'd probably code
it. that, is the impossible part: 32 in a open plan
office, 32 phones, 32+ mobiles. by the time i've
'survived' the day i'm just too knackered to do
anything but veg out on the sofa, with 'coma' [my
sony vaio 505].
yesterday's brilliant achievement was:
chmod 775 dir
even better than the day of:
mkdir d1
mkdir d2
seriously, i get paid to do that. 18 years of unix,
15 years of IP -- wasted.
next prev parent reply other threads:[~2000-11-01 20:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-01 18:21 forsyth
2000-11-01 20:00 ` Boyd Roberts [this message]
2000-11-01 20:47 Russ Cox
2000-11-01 21:48 ` Boyd Roberts
2000-11-01 22:02 ` Boyd Roberts
2000-11-01 22:10 ` Scott Schwartz
2000-11-01 22:23 ` Boyd Roberts
[not found] <rob@plan9.bell-labs.com>
2000-11-01 22:23 ` rob pike
2000-11-01 22:38 ` Scott Schwartz
2000-11-03 19:21 Ozan Yigit
2000-11-03 20:29 ` Boyd Roberts
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='007501c0443e$6537f100$0ab9c6d4@cybercable.fr' \
--to=boyd@planete.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).