The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: mah@mhorton.net (Mary Ann Horton)
Subject: [TUHS] attachments: MIME and uuencode
Date: Sat, 11 Mar 2017 11:07:26 -0800	[thread overview]
Message-ID: <71748884-ac1a-d565-aa08-80f9220594ac@mhorton.net> (raw)

I just heard from a historian named Piotr Klaban with an interesting 
historical sidelight.

Apparently today 3/11/17 is being publicized as the 25th anniversary of 
the email attachment, citing Nat Borenstein's MIME.  Piotr points out 
that uuencode predates MIME, and he's right.

I checked and, while I don't have any email archives from that time 
frame at Berkeley, I was able to find the 4BSD archive on minnie that 
dates the uuencode.1c man page at 6/1/80.  We didn't call them 
attachments back then, just sending binary files by email.  (Prior to 
then it was common to just include the text of the file raw in the 
email, which only worked for ASCII files.)  It was a few years later 
when cc:Mail and Microsoft Mail started calling uuencoded files embedded 
in email "attachments".

When MIME came out in 1992 I became a champion of SMTP/MIME as a 
standard - it was a big improvement.  But uuencod predated MIME by 12 years.

     Mary Ann




             reply	other threads:[~2017-03-11 19:07 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-11 19:07 Mary Ann Horton [this message]
2017-03-11 23:01 ` Paul Winalski
2017-03-11 23:05   ` Mary Ann Horton
2017-03-12  1:14     ` Dan Cross
2017-03-12  6:28       ` jsteve
2017-03-12 23:41         ` Gregg Levine
2017-03-13  0:00           ` Larry McVoy
2017-03-13  1:59             ` Dave Horsfall
2017-03-12 23:43       ` Mary Ann Horton
2017-03-12 21:10   ` Dave Horsfall
     [not found]     ` <12de3888-3a82-4a8c-9177-50e6cb4cb931.maildroid@localhost>
2017-03-19  2:34       ` Dave Horsfall
2017-03-12 13:53 ` Tim Bradshaw
2017-03-12 17:42 ` Clem Cole
2017-03-12 23:35   ` Mary Ann Horton
2017-03-13  0:07     ` Clem Cole
2017-03-13  0:09     ` Warren Toomey
2017-03-13  0:11       ` Clem Cole
2017-03-12 15:10 Noel Chiappa
2017-03-12 18:13 Doug McIlroy
2017-03-12 18:22 ` Larry McVoy
2017-03-12 18:26 ` Clem Cole
2017-03-13  0:34   ` Dan Cross
2017-03-13  1:28     ` Larry McVoy
2017-03-13  5:39       ` Dave Horsfall
2017-03-13 11:37   ` Steffen Nurpmeso
2017-03-13 20:21     ` Steffen Nurpmeso
2017-03-13 22:14       ` Doug McIlroy
2017-03-14 10:49         ` Steffen Nurpmeso
2017-03-12 18:33 ` Paul Winalski
2017-03-13  5:58   ` Dave Horsfall
2017-03-12 18:57 Andy Valencia
2017-03-12 20:04 Noel Chiappa
2017-03-12 21:34 ` Random832
2017-03-12 22:12   ` Noel Chiappa
2017-03-13 14:58     ` Michael Kjörling
2017-03-13 21:56       ` Dave Horsfall
2017-03-14 10:33         ` Steffen Nurpmeso
2017-03-16 18:52         ` Michael Kjörling

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=71748884-ac1a-d565-aa08-80f9220594ac@mhorton.net \
    --to=mah@mhorton.net \
    /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).