From: perry at piermont.com (Perry E. Metzger)
Subject: [COFF] Today I learned something new about File Transfer Protocol.
Date: Mon, 9 Jul 2018 07:27:32 -0400 [thread overview]
Message-ID: <20180709072732.069437b9@jabberwock.cb.piermont.com> (raw)
In-Reply-To: <911994f5-9433-6967-8701-9b27c34d2471@spamtrap.tnetconsulting.net>
On Sun, 8 Jul 2018 21:30:20 -0600 Grant Taylor via COFF
<coff at minnie.tuhs.org> wrote:
> On 07/08/2018 02:28 PM, Perry E. Metzger wrote:
> > In the old old days, FTP had all sorts of other functions,
> > including mail transfer. (SMTP obsoleted that by 1980 or so.)
>
> Do you have any pointers handy (read: in cache) to where I can read
> more about FTP's involvement in early email?
>
> If not, I'll do some searches and see what I can come up with. If
> nothing else, I suspect that early RFCs 821 (?) will make
> references to what it's supplanting.
RFC 114 or 765 might cover it.
Perry
--
Perry E. Metzger perry at piermont.com
prev parent reply other threads:[~2018-07-09 11:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-08 5:17 gtaylor
2018-07-08 20:28 ` perry
2018-07-09 3:30 ` gtaylor
2018-07-09 3:36 ` imp
2018-07-09 4:02 ` gtaylor
2018-07-09 11:27 ` perry [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=20180709072732.069437b9@jabberwock.cb.piermont.com \
--to=coff@minnie.tuhs.org \
/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).