Mail::Message::Part - a part of a message, but a message by itself
Mail::Message::Part is a Mail::Message is a Mail::Reporter
my Mail::Message $message = ...; if($message->isMultipart) { my Mail::Message::Part $part; foreach $part ($message->body->parts) { $part->print(\*OUT); my $attached_head = $part->head; my $attached_body = $part->body; # encoded as read my $attached_body = $part->decoded; # transfer-encoding removed } }
A Mail::Message::Part object contains a message which is included in the body of an other message. For instance attachments are parts.
Mail::Message::Part
READ Mail::Message FIRST. A part is a special message: it has a reference to its parent message, and will usually not be sub-classed into mail folder specific variants.
Extends "DESCRIPTION" in Mail::Message.
Extends "METHODS" in Mail::Message.
Extends "Constructors" in Mail::Message.
Inherited, see "Constructors" in Mail::Message
Create a message part.
-Option --Defined in --Default body Mail::Message undef body_type Mail::Message Mail::Message::Body::Lines container <required> deleted Mail::Message <false> field_type Mail::Message undef head Mail::Message <empty header> head_type Mail::Message Mail::Message::Head::Complete labels Mail::Message {} log Mail::Reporter 'WARNINGS' messageId Mail::Message undef modified Mail::Message <false> trace Mail::Reporter 'WARNINGS' trusted Mail::Message <false>
Reference to the parental Mail::Message::Body object where this part is a member of. That object may be a Mail::Message::Body::Multipart or a Mail::Message::Body::Nested.
Extends "Constructing a message" in Mail::Message.
Inherited, see "Constructing a message" in Mail::Message::Construct::Bounce
Inherited, see "Constructing a message" in Mail::Message::Construct::Build
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.
example:
my $multi = Mail::Message::Body::Multipart->new; my $part = Mail::Message::Part->buildFromBody($body, $multi);
Inherited, see "Constructing a message" in Mail::Message::Construct::Forward
Inherited, see "Constructing a message" in Mail::Message::Construct::Read
Inherited, see "Constructing a message" in Mail::Message::Construct::Rebuild
Inherited, see "Constructing a message" in Mail::Message::Construct::Reply
Extends "The message" in Mail::Message.
Inherited, see "The message" in Mail::Message
Prints the message part, but all lines which start with 'From ' will get a leading >. See Mail::Message::Body::printEscapedFrom().
Extends "The header" in Mail::Message.
Inherited, see "The header" in Mail::Message
Extends "The body" in Mail::Message.
Inherited, see "The body" in Mail::Message
Extends "Flags" in Mail::Message.
Inherited, see "Flags" in Mail::Message
Extends "The whole message as text" in Mail::Message.
Inherited, see "The whole message as text" in Mail::Message::Construct::Text
Extends "Internals" in Mail::Message.
Inherited, see "Internals" in Mail::Message
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.
Inherited, see "Internals" in Mail::Message::Construct::Rebuild
Extends "Error handling" in Mail::Message.
Inherited, see "METHODS" in Mail::Message::Construct
Inherited, see "Error handling" in Mail::Reporter
Inherited, see "Error handling" in Mail::Message
Extends "Cleanup" in Mail::Message.
Inherited, see "Cleanup" in Mail::Reporter
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.
Extends "DETAILS" in Mail::Message.
Unknown alternative for the forward(include). Valid choices are NO, INLINE, ATTACH, and ENCAPSULATE.
NO
INLINE
ATTACH
ENCAPSULATE
Unknown alternative for the include option of reply(). Valid choices are NO, INLINE, and ATTACH.
include
The message bounce() method forwards a received message off to someone else without modification; you must specified it's new destination. If you have the urge not to specify any destination, you probably are looking for reply(). When you wish to modify the content, use forward().
If a forward message is created, a destination address must be specified.
The message send() mechanism had not enough information to automatically find a mail transfer agent to sent this message. Specify a mailer explicitly using the via options.
via
You may wish to construct a message to be stored in a some kind of folder, but you need to do that in two steps. First, create a normal Mail::Message, and then add it to the folder. During this Mail::Box::addMessage() process, the message will get coerce()-d into the right message type, adding storage information and the like.
Fatal error: the specific package (or one of its superclasses) does not implement this method where it should. This message means that some other related classes do implement this method however the class at hand does not. Probably you should investigate this and probably inform the author of the package.
Message parts can not be destructed per part: only whole messages can be forcefully freed from memory. Consider delete() or rebuild().
This module is part of Mail-Box distribution version 2.118, built on February 26, 2015. Website: http://perl.overmeer.net/mailbox/
Copyrights 2001-2015 by [Mark Overmeer]. For other contributors see ChangeLog.
This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See http://www.perl.com/perl/misc/Artistic.html
To install Mail::Box, copy and paste the appropriate command in to your terminal.
cpanm
cpanm Mail::Box
CPAN shell
perl -MCPAN -e shell install Mail::Box
For more information on module installation, please visit the detailed CPAN module installation guide.