=head1 NAME Mail::Box::Message - manage one message within a mail-folder =head1 INHERITANCE Mail::Box::Message is a Mail::Message is a Mail::Reporter Mail::Box::Message is extended by Mail::Box::Dir::Message Mail::Box::File::Message Mail::Box::Message::Destructed Mail::Box::Net::Message =head1 SYNOPSIS # Usually these message objects are created indirectly use Mail::Box::Manager; my $manager = Mail::Box::Manager->new; my $folder = $manager->open(folder => 'Mail/Drafts'); my $msg = $folder->message(1); $msg->delete; $msg->size; # and much more =head1 DESCRIPTION These pages do only describe methods which relate to folders. If you access the knowledge of a message, then read L. During its life, a message will pass through certain stages. These stages were introduced to reduce the access-time to the folder. Changing from stage, the message's body and head objects may change. =head1 METHODS =head2 Constructors $obj-EB(OPTIONS) =over 4 See L =back Mail::Box::Message-EB(OPTIONS) =over 4 Option --Defined in --Default body Mail::Message undef body_type deleted Mail::Message field_type Mail::Message undef folder head Mail::Message undef head_type Mail::Message Mail::Message::Head::Complete labels Mail::Message {} log Mail::Reporter 'WARNINGS' messageId Mail::Message undef modified Mail::Message size undef trace Mail::Reporter 'WARNINGS' trusted Mail::Message . body => OBJECT . body_type => CODE|CLASS =over 4 If the body of a message is used delay-loaded, the message must what type of message to become when it finally gets parsed. The folder which is delaying the load must specify the algorithm to determine that type. =back . deleted => BOOLEAN . field_type => CLASS . folder => FOLDER =over 4 The folder where this message appeared in. The argument is an instance of (a sub-class of) a L. =back . head => OBJECT . head_type => CLASS . labels => ARRAY|HASH . log => LEVEL . messageId => STRING . modified => BOOLEAN . size => INTEGER =over 4 The size of the message, which includes head and body, but without the message separators which may be used by the folder type. =back . trace => LEVEL . trusted => BOOLEAN =back =head2 Constructing a message $obj-EB([RG-OBJECT|OPTIONS]) =over 4 See L =back Mail::Box::Message-EB([MESSAGE|PART|BODY], CONTENT) =over 4 See L =back Mail::Box::Message-EB(BODY, [HEAD], HEADERS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB(STRING) =over 4 See L =back Mail::Box::Message-EB(FILEHANDLE|SCALAR|REF-SCALAR|ARRAY-OF-LINES, OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB([STRING|FIELD|ADDRESS|ARRAY-OF-THINGS]) =over 4 See L =back $obj-EB(STRING) Mail::Box::Message-EB(STRING) =over 4 See L =back =head2 The message $obj-EB =over 4 See L =back $obj-EB(FOLDER, OPTIONS) =over 4 Copy the message to the indicated opened FOLDER, without deleting the original. The coerced message (the clone in the destination folder) is returned. Option --Default shallow shallow_body shallow_head share . shallow => BOOLEAN =over 4 Used for L. =back . shallow_body => BOOLEAN =over 4 Used for L. =back . shallow_head => BOOLEAN =over 4 Used for L. =back . share => BOOLEAN =over 4 Try to share the physical storage of the message between the two folders. Sometimes, they even may be of different types. When not possible, this options will be silently ignored. =back example: my $draft = $mgr->open(folder => 'Draft'); $message->copyTo($draft, share => 1); =back $obj-EB([FOLDER]) =over 4 In with folder did we detect this message/dummy? This is a reference to the folder-object. =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB(FOLDER, OPTIONS) =over 4 Move the message from this folder to the FOLDER specified. This will create a copy using L first. Then, this original message is flagged to get deleted. So until the source folder is closed, two copies of the message may stay in memory. The newly created message clone (part of the destination folder) is returned. All OPTIONS are passed to L Option --Default shallow_body share . shallow_body => BOOLEAN =over 4 Only create a shallow body, which means that the header can not be reused. A message can therefore not be shared in storage unless explicitly stated. =back . share => BOOLEAN =over 4 When there is a chance that the original message can be undeleted, then this must be set to false. Otherwise a shallow clone will be made, which will share the header which can be modified in the undeleted message. =back example: of moving a message my $t = $msg->moveTo('trash'); is equivalent to my $t = $msg->copyTo('trash', share => 1); $msg->delete; =back $obj-EB([FILEHANDLE]) =over 4 See L =back $obj-EB([MAILER], OPTIONS) =over 4 See L =back $obj-EB([INTEGER]) =over 4 Get the number of this message is the current folder. It starts counting from zero. Do not change the number. =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([FILEHANDLE]) =over 4 See L =back =head2 The header $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB(FIELDNAME) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([HEAD]) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB(FIELDNAME) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back =head2 The body $obj-EB([BODY]) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB(['ALL'|'ACTIVE'|'DELETED'|'RECURSE'|FILTER]) =over 4 See L =back =head2 Flags $obj-EB =over 4 See L =back $obj-EB([BOOLEAN]) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB