See METHODS in Mail::Reporter
Prints the message part, but all lines which start with 'From ' will get
a leading gt
. See Mail::Message::Body::printEscapedFrom().
Create a message part.
Option | Defined in | Default |
---|---|---|
body | Mail::Message | undef |
body_type | Mail::Message | |
container | <required> | |
deleted | Mail::Message | <false> |
field_type | Mail::Message | undef |
head | Mail::Message | <empty header> |
head_type | Mail::Message | |
labels | Mail::Message | {} |
log | Mail::Reporter |
|
messageId | Mail::Message | undef |
modified | Mail::Message | <false> |
trace | Mail::Reporter |
|
trusted | Mail::Message | <false> |
Shape a message part around a BODY. Bodies have information about their content in them, which is used to construct a header for the message. Next to that, more HEADERS can be specified. No headers are obligatory. No extra headers are fabricated automatically.
my $multi = Mail::Message::Body::Multipart->new; my $part = Mail::Message::Part->buildFromBody($body, $multi);
Transforms a BODY or MESSAGE to a real message part. The MULTIPART refers to the parental body.
When ta BODY is specified, extra HEADERS can be supplied as well. Bodies are coerced into message parts by calling buildFromBody(). If you specify a MESSAGE residing in a folder, this message will automatically be cloned.
Message parts can not be destructed per part: only whole messages can be forcefully freed from memory. Of course, you can delete() separate parts, which only sets a flag not to write a part again. Furthermore, you may cosider rebuild() to get rit of deleted parts.
Message parts can not be destructed per part: only whole messages can be forcefully freed from memory. Consider delete() or rebuild().