The return ("From:") address to be set in the message header and envelope
Note that this is the composite from address from the message template, including both Full Name, and email address in one of a number of valid formats according to Internet and news address formats.
If this is not present or empty then it will be created from the name and email properties. Note that it is preferable to reference name and email properties rather than the raw from property for almost all purposes.
email
string
7-240 characters
Optional.
The email part of the from address in the article header
name
string
7-240 characters
Optional.
The return ("From:") address to be set in the message header and envelope
Must be a valid RFC822 sender addresses
groups
array of strings
1 - 20 newsgroup identifiers, each of up to 240 characters
Optional. An array of valid newsgroup identifiers
references
array of strings
0 - 20 strings, each of up to 240 characters
Optional. An array of valid message Ids, of articles which a preceed this on in the thread All addresses must be valid RFC822 message IDs
subject
string
1-80 characters
Optional. A valid subject line for this message Without the "Subject: " header text
date
string
1-80 characters
Optional. An RFC 822 Date string
messageID
string
1-80 characters
Optional. Read only string, the message ID of this message.
Optional. This is the message to which this article is a direct reply (if it is a reply)
htmlBody
string
0-16384 characters
Optional.
Read only string, an HTML representation of the raw body text.
Special characters within HTML (e.g. <, >, & etc), are concerted into their escaped equivalent for output.
Additionaly heuristics are applied to the plain text in order to detect strings which look like embedded HTTP URLs, or e-mail addresses. These are converted into hyperlinks suitable for direct output to a browser.
