From: Richard Salz <rich.salz@gmail.com>
To: Clem Cole <clemc@ccc.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c)
Date: Sun, 31 May 2020 12:25:47 -0400 [thread overview]
Message-ID: <CAFH29toQesHQtrwQPw=eO4uiy3mw-PrvT3WcYaukBW9BP3hBWA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2P6_knffBX66XMb-SZf+om1AOooN36xaea+M0=Tb5weqg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
"I'll try" Wow, that was quite some "try" Kudo's!
> This is important because the original ARPAnet NCP used FTP to do mail
transfer.
If you look at RFC 765 (dated June 1980) , there are nearly a dozen
mail-related FTP commands. By RFC 959, it's successor five years later, all
of them were gone.
Another eary MTA was the MMDF, the Multichannel Memorandum Distribution
Facility, from U Delware. BBN ran it. One key point is that somehow when
used with MH you could get real-time address verification before sending,
"user rs@bbn.com doesn't exist." BBN ran MMDF for a long time because a key
exec liked/needed that feature, long after 4.2 and sendmail. (My group was
one of the first to run sendmail, which I liked because of the "R$" lines
in its CF files. (Not really :) My Usenet/email gateway code had to
support MMDF but it was only ever used on bbn.com)
> could recognize ArpaNET address postfix and had a hack in it, that
allowed the 'user' part of the address to include UUCP addresses
Originally ihnp4!mirror!rs@seismo.arpa, then ihnp4!mirror!rs@seismo.css.gov
and then rs%mirror.uucp@seismo.css.gov and then rs@mirror.tmc.com Thanks
to Mary Ann and the "UUCP Mapping Project" for making much of that possible
and Peter Honeyman for Pathlias, and MX records for the last part. The
pre-MX styles received much scorn from Research, and if you search for
"that hideous name" you can find a paper on it. There's also a pathlias
paper, which Honey later said "was too good for Usenix" but he had nowhere
else to submit it.
[-- Attachment #2: Type: text/html, Size: 2834 bytes --]
next prev parent reply other threads:[~2020-05-31 16:26 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 12:34 [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-05-28 13:08 ` Rob Pike
2020-05-28 13:30 ` Clem Cole
2020-05-28 13:47 ` Clem Cole
2020-05-28 16:08 ` Mary Ann Horton
2020-05-28 18:00 ` Clem Cole
2020-05-28 18:35 ` Richard Salz
2020-05-28 18:51 ` Clem Cole
2020-05-29 0:18 ` Greg 'groggy' Lehey
2020-05-29 5:10 ` Michael Stiller via TUHS
2020-05-29 5:19 ` Greg 'groggy' Lehey
2020-05-29 13:39 ` Clem Cole
2020-05-29 15:43 ` Warner Losh
2020-05-29 16:12 ` Clem Cole
2020-05-29 17:14 ` Mary Ann Horton
2020-05-28 13:46 ` Clem Cole
2020-05-31 13:01 ` [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) markus schnalke
2020-05-31 14:53 ` Clem Cole
2020-05-31 16:25 ` Richard Salz [this message]
2020-05-31 16:50 ` Larry McVoy
2020-05-31 17:09 ` Ralph Corderoy
2020-05-31 17:25 ` Jon Steinhart
2020-05-31 17:28 ` [TUHS] mh/hm, mmh Mary Ann Horton
2020-05-31 18:56 ` Eric Allman
2020-05-31 19:49 ` Clem Cole
2020-05-31 21:31 ` Mary Ann Horton
2020-06-01 6:32 ` Caipenghui
2020-06-01 7:14 ` markus schnalke
2020-05-31 12:35 ` [TUHS] fmt(1): history, POSIX, -t, -c markus schnalke
2020-06-03 0:43 [TUHS] mh/hm, mmh (was: fmt(1): history, POSIX, -t, -c) Bakul Shah
2020-06-03 0:49 ` Clem Cole
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='CAFH29toQesHQtrwQPw=eO4uiy3mw-PrvT3WcYaukBW9BP3hBWA@mail.gmail.com' \
--to=rich.salz@gmail.com \
--cc=clemc@ccc.com \
--cc=tuhs@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).