Any multipart subtypes that an implementation does not recognize should be treated as being of subtype mixed. Sie besteht aus drei Blöcken. Zudem gibt es im Header den Content-Type multipart. Each MIME part has its own set of MIME Headers and is enclosed in the MIME boundary specified in the “Content-Type” header. A MIME boundary is a string that must be unique and guaranteed not to occur in any of its MIME parts.
Creates a multipart - mixed MIME message with the 1st part containing plain-text, and the 2nd part containing a GIF image. MIME multipart is a member of the MediaTypesFamily. In the preceding example , the courtesy message This is a multipart message in MIME format.
MIME UA because it does not follow a boundary= string. A UA that does not support MIME will display it, and at least this part of the message will be readable no matter what features the UA supports. Eines der Ziele von MIME ist eine saubere Deklaration des Inhalts um Interpretierungen zu verhindern.
Eine reine Text-Mail ist zwar weiterhin möglich, aber neu ist hier der Content-Type und die Angabe des Encoding. The MIME -Version: header tells the receiving UA to treat this as a MIME message. This tells the receiving UA that this message has parts separated by the string argument defined in boundary=.