(Short version: they get displayed as an equals sign plus two 7-bit characters.)

Defines how to escape non-US-ASCII characters so that they can be represented in only 7-bit characters.

The quoted-printable encoding (Defined in Section 5.1 of RFC 1341) is designed to handle this. HTML files (which might have more than 1000-character lines) and files with international characters are good examples of this. Quoted Printableīefore the 8BITMIME extension, there needed to be a way to send content that couldn't be 7bit over SMTP.

Similar to 8bit, RFC 1341 states that it's not really a legitimate encoding transfer encoding. You can still include any characters you want, and there's no extra encoding. Binary Encodingīinary is the same as 8bit, except that there's no line length restriction. Note that this extension does NOT eliminate the possibility of an SMTP server limiting line length servers are free to implement this extension but nevertheless set a line length limit no lower than 1000 octets. But even then, line limits still may apply: Since then we've gotten 8bit MIME Extensions in RFC 6152. Thus there are no circumstances in which the '8bit' or 'binary' Content-Transfer-Encoding is actually legal on the Internet. However, RFC 1341 contains this tidbit:Īs of the publication of this document, there are no standardized Internet transports for which it is legitimate to include unencoded 8-bit or binary data in mail bodies. This seems like a step up from 7bit, since it gives you more freedom in your content. It just means that you're not guaranteeing that none of the bytes will have the highest bit set to '1'.

8Bit EncodingĨbit means 'My data may include extended ASCII characters they may use the 8th (highest) bit to indicate special characters outside of the standard US-ASCII 7-bit characters.' As with 7bit, there's still a 1000-character line limit.Ĩbit, just like 7bit, does not actually do any transformation of the bytes as they're written to or read from the wire. But that wasn't true in 2005 and it isn't true today. The idea here is that if you're just writing in 'plain English text' you'll be fine.

It's also easy to eyeball 7bit content and make sense of it. Note that when you choose 7bit, you're agreeing that all of the lines in your content are less than 1000 characters in length.Īs long as your content adheres to these rule, 7bit is the best transfer encoding, since there's no extra work necessary you just read/write the bytes as they come off the pipe. 7Bit Encodingħbit simply means 'My data consists only of US-ASCII characters, which only use the lower 7 bits for each character.' You're basically guaranteeing that all of the bytes in your content already adhere to the restrictions of SMTP, and so it needs no special treatment. The values for the Content-Transfer-Encoding header describe the rule that you've chosen to solve this problem. SMTP doesn't allow this, so you need to use 'transfer encoding' to describe how you've worked around the mismatch. Think of an image file, or a text file that contains Unicode characters: the bytes of these files will often have their 8th bit set to '1'. The content that we want to send will often not obey this restriction inherently. That means that none of the bytes you send down the pipe can have the most significant ('highest-order') bit set to '1'.

SMTP, by definition (RFC 821), limits mail to lines of 1000 characters of 7 bits each. The situation kinda goes from bad to worse. It can be a bit dense to read, but the 'Content-Transfer-Encoding' section of RFC 1341 has all of the details:

Base64 encoding java 8 mail