Hello Ms. Horton, In reading your initial part of your question, my visceral response was to think "the email attachment was created by whoever developed uuencode." Only, to discover you wrote uuencode. So, who created the email attachment? Mary Ann Horton created the email attachment. That's who. Truly, Bill Corcoran On Mar 18, 2017, at 7:46 PM, Mary Ann Horton <mah@mhorton.net<mailto:mah@mhorton.net>> wrote: I'd like the opinion of this August Group. Should I make a claim to be the inventor of the email attachment? (It would go on my web site, resume, the Wikipedia page, that sort of thing.) Here's my understanding of the time line on all of this. 1. Originally, our files were all plain text and we just included them in the email message body. The ~r command in Kurt Shoen's Mail program was typical. There was no name for this, we were just emailing files. 2. In 1980, I wrote uuencode. It's stated purpose was to "encode a binary file for transmission by email". I didn't use the term "attachment". It became part of 4.0BSD and later systems, and was widely used. 3. In 1985, Lotus created cc:Mail. It eventually included attachments, using a file store method. When they added an SMTP gateway later, it used uuencode as the format. I believe cc:Mail first used the term "attachment". 4. Microsoft did the same thing with MS Mail somewhat later, possibly in the 1990s. It also used uuencode in the SMTP gateway. 5. In 1992, Nathaniel Borenstein and Ned Freed invented MIME. It had a different (and IMHO much better) way to send attachments, and it became an Internet Standard sometime later, possibly in 1996. What do you all think? Mary Ann

On 2017 Mar 18, 16:46, Mary Ann Horton wrote: 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