msg:build

msg:build — Create a message

msg:build(headers, parts, attachments);

When calling this function, msg must be an empty message (created using msys.core.ec_message_new()). It requires the following inputs:

• headers a table of header name /header value pairs. If the header's value contains non-ASCII or non-printable ASCII text, the caller must encode the text appropriately (see RFC 2047).

• parts a table of alternative contents. Each pair consists of content-type/content pairs. For example, "text/plain; charset=utf8" / "Momentum 3.1 rocks."; "text/html" / "Momentum 3.1 rocks.". "

  If the value of Content-Type is text/* and there is no charset specified, the content will be quoted-printable encoded; if a charset is specified or content type is not text/*, the content will be base64 encoded.

• attachments an array of attachment objects. Each element is a table representing an attachment. The attachment table must contain the following pairs:

  • type the "content-type" of the attachment. If your content charset encoding is not UTF-8, you will need to specify it in here as a parameter. For example: charset=charset_encoding.

  • name a file name.

    Note#

    If the file is in the current directory, you cannot use the file name alone. As a workaround, precede the file name with ./, for example, ./attachment.txt.

  • headers a string of concatenated headers. Such as "Openby: iphone4\r\nCertificate: AKJSdwuiqdQIWDUHQIWDUH". Note that there should not be a CRLF at end.

  • content the content of the attachment. The value can be a string, an io_object or an ec_message. For a string, the content will be quoted-printable encoded for transferring; for an io_object, the content will be base64 encoded. It is the caller's responsibility to encode the io_object. When the content is an ec_message, values of type, name or headers are ignored. The ec_message will be treated as an attached mail with content-type equal to message/rfc822; name="Attached Message".