Class Poco::Net::MailMessage

If pStoreFactory is not null, message attachments will be handled by the object created by the factory. Most common reason is to temporarily save attachments to the file system in order to avoid potential memory exhaustion when attachment files are very large.

Destructor

~MailMessage

virtual ~MailMessage();

Destroys the MailMessage.

Member Functions

addAttachment

void addAttachment(
    const std::string & name,
    PartSource * pSource,
    ContentTransferEncoding encoding = ENCODING_BASE64
);

Adds an attachment to the mail message by calling addPart(name, pSource, CONTENT_ATTACHMENT, encoding);

The part name, and the filename specified in the part source must not contain any non-ASCII characters. To include non-ASCII characters in the part name or filename, use RFC 2047 word encoding (see encodeWord()).

addContent

void addContent(
PartSource * pSource,
ContentTransferEncoding encoding = ENCODING_QUOTED_PRINTABLE
);

Adds a part to the mail message by calling addPart("", pSource, CONTENT_INLINE, encoding);

addPart

void addPart(
    const std::string & name,
    PartSource * pSource,
    ContentDisposition disposition,
    ContentTransferEncoding encoding
);

Adds a part/attachment to the mail message.

The MailMessage takes ownership of the PartSource and deletes it when it is no longer needed.

The MailMessage will be converted to a multipart message if it is not already one.

addRecipient

void addRecipient(
const MailRecipient & recipient
);

Adds a recipient for the message.

createPartStore

PartSource * createPartStore(
    const std::string & content,
    const std::string & mediaType,
    const std::string & filename = ""
);

Returns either default StringPartSource part store or, if the part store factory was provided during construction, the one created by PartStoreFactory. Returned part store is allocated on the heap; it is caller's responsibility to delete it after use. Typical use is handler passing it back to MailMessage, which takes care of the cleanup.

encodeWord

static std::string encodeWord(
const std::string & text,
const std::string & charset = "UTF-8"
);

If the given string contains non-ASCII characters, encodes the given string using RFC 2047 "Q" word encoding.

The given text must already be encoded in the character set given in charset (default is UTF-8).

Returns the encoded string, or the original string if it consists only of ASCII characters.

getContent

const std::string & getContent() const;

Returns the content of the mail message.

A content will only be returned for single-part messages. The content of multi-part mail messages will be reported through the registered PartHandler.

getContentType

const std::string & getContentType() const;

Returns the content type for the message.

getDate

Poco::Timestamp getDate() const;

Returns the value of the Date header.

getSender

const std::string & getSender() const;

Returns the sender of the message (taken from the From header field).

getSubject

const std::string & getSubject() const;

Returns the subject of the message.

isMultipart

bool isMultipart() const;

Returns true iff the message is a multipart message.

parts

const PartVec & parts() const;

Returns const reference to the vector containing part stores.

read

void read(
std::istream & istr,
PartHandler & handler
);

Reads the MailMessage from the given input stream.

If the message has multiple parts, the parts are reported to the PartHandler. If the message is not a multi-part message, the content is stored in a string available by calling getContent().

read

void read(
std::istream & istr
);

Reads the MailMessage from the given input stream.

The raw message (including all MIME parts) is stored in a string and available by calling getContent().

See also: Poco::Net::MessageHeader::read()

recipients

const Recipients & recipients() const;

Returns the recipients of the message.

setContent

void setContent(
const std::string & content,
ContentTransferEncoding encoding = ENCODING_QUOTED_PRINTABLE
);

Sets the content of the mail message.

If the content transfer encoding is ENCODING_7BIT or ENCODING_8BIT, the content string must be formatted according to the rules of an internet email message.

The message will be sent as a single-part message.

Note that single CR or LF characters as line delimiters must not be used. Content lines always should be terminated with a proper CRLF sequence.