MIME (Multipurpose Internet Mail Extensions) is a standard which was proposed by Bell Communications in 1991 in order to expand upon the limited capabilities of email, and in particular to allow documents (such as images, sound, and text) to be inserted in a message. It was originally defined by RFCs 1341 and 1342 in June 1992.
Using headers, MIME describes the type of message content and the encoding used.
MIME adds the following features to email service:
- Be able to send multiple attachments with a single message;
- Unlimited message length;
- Use of character sets other than ASCII code;
- Use of rich text (layouts, fonts, colours, etc)
- Binary attachments (executables, images, audio or video files, etc.), which may be divided if needed.
MIME uses special header directives to describe the format used in a message body, so that the email client can interpret it correctly:
- MIME-Version: This is the version of the MIME standard used in the message. Currently only version 1.0 exists.
- Content-type: Describes the data's type and subtype. It can include a "charset" parameter, separated by a semi-colon, defining which character set to use.
- Content-Transfer-Encoding: Defines the encoding used in the message body
- Content-ID: Represents a unique identification for each message segment
- Content-Description: Gives additional information about the message content.
- Content-Disposition: Defines the attachment's settings, in particular the name associated with the file, using the attribute filename.
Mime types:
application/base64
An mme file extension is related to the Multipurpose Internet Mail Extensions file format.
How to open:
Use compatible tools to work with *.mme files.
How to convert:
As far as we know, this .mme file type can't be converted to any other file format. This is usually the case of system, configuration, temporary, or data files containing data exclusive to only one software and used for its own purposes. Also some proprietary or closed file formats cannot be converted to more common file types in order to protect the intellectual property of the developer, which is for example the case of some DRM-protected multimedia files.