RFC 1521:MIME (Multipurpose Internet Mail Extensio...
RFC-Ref

internet mail


Click on the red underlined text to get to the source

... message handling system (i.e., the X.400 message is "tunneled" through Internet mail), where the non-textual information would definitely become useful again. ...


... [RFC-1426]. As of the publication of this document, there are no standardized Internet mail transports for which it is legitimate to include unencoded binary data ...
... Internet. However, in the event that binary mail transport becomes a reality in Internet mail, or when this document is used in conjunction with any other binary-capable ...
... transport, in the same manner that plain text mail has always been altered in Internet mail when passing between systems with differing newline conventions. If such alterations are likely to constitute a corruption of the data, it is probably more sensible to use the ...


... text/plain", which indicates plain (unformatted) text. The default Content-Type for Internet mail is "text/plain; charset=us- ...
... ISO-646] are NOT ASCII and their use in Internet mail is explicitly discouraged. The omission of the ISO 646 character set ...
... character sets have deliberately been omitted in favor of their 8859 replacements, which are the designated character sets for Internet mail. As of the publication of this document, the legitimate values for "X" are the digits 1 through 9. ...
... No other character set name may be used in Internet mail without the publication of a formal specification and its registration with IANA ...
... The primary subtype of text is "plain". This indicates plain (unformatted) text. The default Content-Type for Internet mail, "text/plain; charset ...
... be in force. (That is, the transport domains may resemble standard Internet mail transport as specified in RFC821std10(-> 2821prop) and ...


... violated, and care has been taken to avoid problems caused by additional restrictions imposed by the characteristics of some Internet mail transport mechanisms (see Appendix B). The "multipart" and "message" Content-Types ...


... For more information, the authors of this document may be contacted via Internet mail: Nathaniel S. Borenstein ...


... be in force. (That is, the transport domains may resemble standard Internet mail transport as specified in RFC821std10(-> 2821prop) and ...


... Borenstein, N., and N. Freed, "MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies", RFC 1341(-> 1521(-> 2049draft | 2048(-> 4289 | 4288) | 2047draft | 2046draft | 2045draft)), Bellcore, Innosoft, June 1992. ...
... Borenstein, N., "Implications of MIME for Internet Mail Gateways", RFC 1344, Bellcore, June 1992. ...



Google
Web
RFC-Ref