# Do modern internet email systems still uuencode (8 bit to 7 bit) binary attachments?

**URL:** <https://boards.straightdope.com/t/do-modern-internet-email-systems-still-uuencode-8-bit-to-7-bit-binary-attachments/679468>\
**Category:** Factual Questions\
**Created:** [January 22, 2014, 7:40pm UTC](https://boards.straightdope.com/t/do-modern-internet-email-systems-still-uuencode-8-bit-to-7-bit-binary-attachments/679468 "2014-01-22T19:40:43Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Revtim](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/revtim/32/1042_2.png) [@Revtim](https://boards.straightdope.com/u/Revtim)\
**Post date:** [January 22, 2014, 7:40pm UTC](https://boards.straightdope.com/t/do-modern-internet-email-systems-still-uuencode-8-bit-to-7-bit-binary-attachments/679468/1 "2014-01-22T19:40:43Z")

</div>

Old internet geezers like me remember when in order to send a binary attachment you had to uuencode into 7-bit text to get it across the internet. It wasn’t long before email clients, web based and otherwise, did this for you transparently. But it was my understanding that the conversion to 7-bit still had to be done at some layer.

Is this still the case? When I send an email from Gmail with binary attachment to say, Yahoo mail, is there still a 7-bit step involved requiring uuencoding? Or is it 8-bit end to end now? Email is notorious for being still of archaic design, so it would not surprise me if there still some 7-bit linkages still.

---

<div class="post-metadata">

**Author:** ![friedo](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@friedo](https://boards.straightdope.com/u/friedo)\
**Post date:** [January 22, 2014, 7:59pm UTC](https://boards.straightdope.com/t/do-modern-internet-email-systems-still-uuencode-8-bit-to-7-bit-binary-attachments/679468/2 "2014-01-22T19:59:31Z")

</div>

Virtually all email is now sent in [MIME](http://en.wikipedia.org/wiki/MIME) format, which contains extensive rules for encoding binary data as well as doing multi-part attachments. (You are probably familiar with MIME media types if you’ve done any web development.)

The default encoding for MIME messages is a 7bit encoding, which can still be used and works fine. The Content-Transfer-Encoding header mechanism allows you to specify other encodings, including base64 (the most common encoding for emails, IME) and 8bit (which really means binary but with some line-endings in it) and actual binary.

Email headers must still be 7-bit clean.

---

<div class="post-metadata">

**Author:** ![AHunter3](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/ahunter3/32/368_2.png) [@AHunter3](https://boards.straightdope.com/u/AHunter3)\
**Post date:** [January 22, 2014, 11:11pm UTC](https://boards.straightdope.com/t/do-modern-internet-email-systems-still-uuencode-8-bit-to-7-bit-binary-attachments/679468/3 "2014-01-22T23:11:08Z")

</div>

I remember BinHexing, instead of UUEncoding (being a Mac person) but yeah.

> [@](#):
>
> (This file must be converted with BinHex 4.0)  
> :%e4TE@_eDh4eU#jTE@&RC5jcC@%!39"36’&eFh3K!!!&k_-!!&Rd±P6593K!!%  
> (etc)

In some shape way fashion or form it has to be represented as text characters. Email (to the astonishment of many people) is still [technically a plain text format](http://en.wikipedia.org/wiki/HTML_email).

---

<div class="post-metadata">

**Author:** ![friedo](https://avatars.discourse-cdn.com/v4/letter/f/8edcca/32.png) [@friedo](https://boards.straightdope.com/u/friedo)\
**Post date:** [January 22, 2014, 11:35pm UTC](https://boards.straightdope.com/t/do-modern-internet-email-systems-still-uuencode-8-bit-to-7-bit-binary-attachments/679468/4 "2014-01-22T23:35:13Z")

</div>

BinHex was basically the same as UU but had extra doohickeys in it to handle the MacOS resource fork.