From: Lyndon Nerenberg <lyndon@messagingdirect.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] smtpfs
Date: Tue, 31 Oct 2000 09:27:53 +0000 [thread overview]
Message-ID: <86vguace31.fsf@gollum.esys.ca> (raw)
In-Reply-To: <024501c04064$a14477a0$0ab9c6d4@cybercable.fr>
>>>>> "Boyd" == Boyd Roberts <boyd@planete.net> writes:
Boyd> looking at inferno's smtp module i thought why not an
Boyd> smtpfs? all you do is write the 822 message into /n/smtp
Boyd> and it parses the message and delivers it.
How do you handle the case where the RCPT TO address doesn't
match the To: header address? They don't have to be the same.
What about DSN? AUTH?
Boyd> it's trivial.
I don't think so.
--lyndon
next prev parent reply other threads:[~2000-10-31 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 22:23 Boyd Roberts
2000-10-31 9:27 ` Lyndon Nerenberg [this message]
2000-11-01 2:04 ` Boyd Roberts
2000-11-01 17:09 ` Lyndon Nerenberg
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=86vguace31.fsf@gollum.esys.ca \
--to=lyndon@messagingdirect.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).