| Rev | Author | # | Line |
|---|---|---|---|
| 1 | PerryLorier | 1 | [Acronym] for __M__ultipurpose __I__nternet __M__ail __E__xtensions |
| 2 | |||
| 6 | JohnMcPherson | 3 | The format for modern email messages, this specifies how to encode attachments, and non-text bodies. It also includes a type system, allowing type information to be included with message parts, and a means of specifying non-[ASCII] text in message headers. |
| 1 | PerryLorier | 4 | |
| 4 | StephenLewis | 5 | The MIME standards build on the message format specified in RFC:822 (now updated to RFC:2822), so a MIME message is also an RFC:822 message, hence can be sent using standard internet protocols (such as [SMTP]) |
| 2 | PerryLorier | 6 | |
| 4 | StephenLewis | 7 | |
| 5 | StephenLewis | 8 | MIME is currently a set of 5 [RFC]s: [1] |
| 4 | StephenLewis | 9 | |
| 10 | * RFC:2045 - Basic specification for MIME messages | ||
| 11 | * RFC:2046 - MIME media typing system, and core type definitions | ||
| 6 | JohnMcPherson | 12 | * RFC:2047 - RFC:822 extensions to allow non-[ASCII] data in message headers |
| 4 | StephenLewis | 13 | * RFC:2048 - [IANA] registration procedures for MIME related facilities |
| 14 | * RFC:2049 - MIME conformance criteria | ||
| 15 | |||
| 16 | These documents revise older versions of the MIME standard, such as RFC:1341 and RFC:1342 | ||
| 5 | StephenLewis | 17 | |
| 18 | [1] There are a bunch of additions, but these include most of the important basics | ||
| 7 | StuartYeates | 19 | |
| 20 | ---- | ||
| 21 | CategoryStandards |
lib/plugin/WlugLicense.php (In template 'html'):99: Warning: Invalid argument supplied for foreach()
lib/plugin/WlugLicense.php (In template 'html'):111: Warning: in_array() [<a href='function.in-array'>function.in-array</a>]: Wrong datatype for second argument