Message

A typical message can include several encrypted and non-encrypted parts.

The top level message contains one or more parts. A message is represented in the stream in the following example.

<MIME-Message>
<Header>
...
</Header>
<Preamble>
</Preamble>
<MIME-Message-Part>
...
</MIME-Message-Part>
...
...
<MIME-Message-Part>
...
</MIME-Message-Part>
<Epilogue>
</Epilogue>
</MIME-Message>

The message always contains a Header. See "Header" for more information. But some of the fields of the header are optional. Following this is the Preamble, which can be omitted in its entirety. Following this are one or more Message Parts, and finally an optional Epilogue.

If the message is a simple single-part MIME message, then no Preamble or Epilogue is permitted, and the single message part cannot have a Header.

If a Boundary Header field is specified in a multipart message, then this is used as the Boundary value in the final MIME message.

If the message is a simple single-part MIME message, then no Preamble or Epilogue is permitted, and the single message part cannot have a Header. The data presented to the adapter for a single-part MIME message should have the following form:

<MIME-Message>
<Header>
...
</Header>
<Message-Part-Data>
This is my data
</Message-Part-Data>
</MIME-Message>

Notice that there are no <MIME-Message-Part>...</MIME-Message-Part> tags. The type tree install_dir\examples\adapters\mime\mime.mtt provided with the product can be used to create single-part data.