| <message> | |
| <header> | |
| <field> | |
| Content-Type: multipart/mixed; boundary="boundary"</field> | |
| </header> | |
| <multipart> | |
| <preamble> | |
| preamble | |
| </preamble> | |
| <body-part> | |
| <header> | |
| <field> | |
| Content-Type: text/plain</field> | |
| </header> | |
| <body> | |
| first part | |
| </body> | |
| </body-part> | |
| <body-part> | |
| <header> | |
| <field> | |
| Content-Type: text/plain</field> | |
| </header> | |
| <body> | |
| from the rfc: | |
| ================================ | |
| encapsulation := delimiter transport-padding | |
| CRLF body-part | |
| ================================ | |
| and also | |
| ================================ | |
| "Composers MUST NOT generate non-zero length transport | |
| padding, but receivers MUST be able to handle padding | |
| added by message transports." | |
| ================================ | |
| second part have a start boundary ending with spaces | |
| and also have a boundary not at the beginning | |
| --boundary | |
| ... that should be ignored | |
| also a boundary with more data (a tab) shoud be ignored | |
| --boundary | |
| end of part | |
| </body> | |
| </body-part> | |
| <epilogue> | |
| epilouge</epilogue> | |
| </multipart> | |
| </message> |