The optional message body contains the content of the message. As with the message header, the program enqueuing the message has nearly complete control over the contents of the message body. The only exception to this is when the message is structured with multiple parts or requires encoding, for example if it contains binary data, or lines requiring wrapping. In such cases, the SDK will ensure that the message body conforms to MIME standards (RFCs 2045– 2049).
As with the message header, message body lines are written with the routines mtaEnqueueWrite() and mtaEnqueueWriteLine().
Enqueued messages may be seen in the MTA queue directories and are merely ASCII text files. In the following sample message, lines 1 and 2 are the message envelope, the next four lines are the header, and the rest of the lines are the body.
firstname.lastname@example.org email@example.com Date: Tues, 1 Apr 2003 15:01 PST From: John Doe To: Mike Smith Subject: Lunch today Mike, Just confirming our lunch appointment today I’ll meet you at the restaurant at noon. John
As stated earlier, do not directly read from or write messages to the MTA message queues. Always use the SDK routines or Callable Send. The file structure of messages in the MTA queues are subject to change. In addition, site specific constraints may be placed on things such as encodings, and character set usage. The SDK routines automatically handle these and other issues.