The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: pepe@naleco.com (Josh Good)
Subject: [TUHS] who invented the email attachment?
Date: Sun, 19 Mar 2017 12:42:18 +0100	[thread overview]
Message-ID: <20170319114216.GE21805@naleco.com> (raw)
In-Reply-To: <61ff3fb7-7b96-d129-6a02-a56059bfe991@mhorton.net>

On 2017 Mar 18, 16:46, Mary Ann Horton wrote:
> 
> Should I make a claim to be the inventor of the email attachment? [...] 
> 
> 2. In 1980, I wrote uuencode. [...]

I would say yes to your question. More or less.

However, the "attachment" as a concept has more to do with
"presentation" of the email message: the "attached" part is always, even
in MIME messages, part of the body of the RFC822 message.

In that sense, it does not matter whether it is inline source code,
inline 'shar'-ed files, inline UUencoded, or inline MIME. What makes
it an "attachment", is the MUA ability to present it and to manage it
as a distinct part of the email message, different from the headers and
different from the "textual" body. 

So, according to that, the inventor of the "attachment" was whoever wrote
the first MUA capable of presenting and managing certain body parts of
a RFC822 message as such separate entity. The "attachment", therefore,
would be a user interface design decision, undoubtedly facilitated by
some underlying technology such as uuencode which defined a boundary to
mark the 'begin' and 'end' of the inlined non-textual data.

But I have been wrong before - many times.

-- 
Josh Good



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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 23:46 Mary Ann Horton
2017-03-19  0:12 ` William Corcoran
2017-03-19  2:41 ` Dave Horsfall
2017-03-19  4:11   ` Nick Downing
2017-03-20  1:21   ` Mary Ann Horton
2017-03-20  2:23     ` Clem Cole
2017-03-20  7:32     ` arnold
     [not found]     ` <58cfaea1.7iwnMeBm9Gzvxy4O%schily@schily.net>
2017-03-20 17:34       ` Mary Ann Horton
2017-03-19 11:42 ` Josh Good [this message]
2017-03-19  2:14 Doug McIlroy

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=20170319114216.GE21805@naleco.com \
    --to=pepe@naleco.com \
    /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).