NAME
Mail::Box::Message - manage one message within a mail-folder
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
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
DESCRIPTION
These pages do only describe methods which relate to folders. If you access the knowledge of a message, then read Mail::Message.
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.
METHODS
Constructors
$obj->clone(OPTIONS)
Mail::Box::Message->new(OPTIONS)
Option --Defined in --Default
body Mail::Message undef
body_type <from folder>
deleted Mail::Message <false>
field_type Mail::Message undef
folder <required>
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 <false>
size undef
trace Mail::Reporter 'WARNINGS'
trusted Mail::Message <false>
. body => OBJECT
. body_type => CODE|CLASS
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.
. deleted => BOOLEAN
. field_type => CLASS
. folder => FOLDER
The folder where this message appeared in. The argument is an instance of (a sub-class of) a Mail::Box.
. head => OBJECT
. head_type => CLASS
. labels => ARRAY|HASH
. log => LEVEL
. messageId => STRING
. modified => BOOLEAN
. size => INTEGER
The size of the message, which includes head and body, but without the message separators which may be used by the folder type.
. trace => LEVEL
. trusted => BOOLEAN
Constructing a message
$obj->bounce([RG-OBJECT|OPTIONS])
Mail::Box::Message->build([MESSAGE|PART|BODY], CONTENT)
Mail::Box::Message->buildFromBody(BODY, [HEAD], HEADERS)
$obj->forward(OPTIONS)
$obj->forwardAttach(OPTIONS)
$obj->forwardEncapsulate(OPTIONS)
$obj->forwardInline(OPTIONS)
$obj->forwardNo(OPTIONS)
$obj->forwardPostlude
$obj->forwardPrelude
$obj->forwardSubject(STRING)
Mail::Box::Message->read(FILEHANDLE|SCALAR|REF-SCALAR|ARRAY-OF-LINES, OPTIONS)
$obj->rebuild(OPTIONS)
$obj->reply(OPTIONS)
$obj->replyPrelude([STRING|FIELD|ADDRESS|ARRAY-OF-THINGS])
$obj->replySubject(STRING)
Mail::Box::Message->replySubject(STRING)
The message
$obj->container
$obj->copyTo(FOLDER, OPTIONS)
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 <false>
shallow_body <false>
shallow_head <false>
share <false>
. shallow => BOOLEAN
Used for clone(shallow).
. shallow_body => BOOLEAN
Used for clone(shallow_body).
. shallow_head => BOOLEAN
Used for clone(shallow_head).
. share => BOOLEAN
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.
example:
my $draft = $mgr->open(folder => 'Draft');
$message->copyTo($draft, share => 1);
$obj->folder([FOLDER])
In with folder did we detect this message/dummy? This is a reference to the folder-object.
$obj->isDummy
$obj->isPart
$obj->messageId
$obj->moveTo(FOLDER, OPTIONS)
Move the message from this folder to the FOLDER specified. This will create a copy using clone() 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 copyTo()
Option --Default
shallow_body <undef>
share <true unless shallow_body exists>
. shallow_body => BOOLEAN
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.
. share => BOOLEAN
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.
example: of moving a message
my $t = $msg->moveTo('trash');
is equivalent to
my $t = $msg->copyTo('trash', share => 1);
$msg->delete;
$obj->print([FILEHANDLE])
$obj->send([MAILER], OPTIONS)
$obj->seqnr([INTEGER])
Get the number of this message is the current folder. It starts counting from zero. Do not change the number.
$obj->size
$obj->toplevel
$obj->write([FILEHANDLE])
The header
$obj->bcc
$obj->cc
$obj->date
$obj->destinations
$obj->from
$obj->get(FIELDNAME)
$obj->guessTimestamp
$obj->head([HEAD])
$obj->nrLines
$obj->sender
$obj->study(FIELDNAME)
$obj->subject
$obj->timestamp
$obj->to
The body
$obj->body([BODY])
$obj->contentType
$obj->decoded(OPTIONS)
$obj->encode(OPTIONS)
$obj->isMultipart
$obj->isNested
$obj->parts(['ALL'|'ACTIVE'|'DELETED'|'RECURSE'|FILTER])
Flags
$obj->delete
$obj->deleted([BOOLEAN])
$obj->isDeleted
$obj->isModified
$obj->label(LABEL|PAIRS)
$obj->labels
$obj->labelsToStatus
$obj->modified([BOOLEAN])
$obj->statusToLabels
The whole message as text
$obj->file
$obj->lines
$obj->printStructure([FILEHANDLE|undef],[INDENT])
$obj->string
Internals
$obj->clonedFrom
Mail::Box::Message->coerce(MESSAGE, OPTIONS)
$obj->diskDelete
Remove a message from disk. This is not from the folder, but everything else, like parts of the message which are stored outside from the folder.
$obj->isDelayed
$obj->readBody(PARSER, HEAD [, BODYTYPE])
Read the body of one message. The PARSER gives access to the folder file. The HEAD has been read with readHead(). The optional BODYTYPE supplies the class name of the body to be created, or a code reference to a routine which can produce a body type based on the head (passed as first argument).
By default, the BODYTYPE will call Mail::Box::determineBodyType() where the message will be added to.
$obj->readFromParser(PARSER, [BODYTYPE])
$obj->readHead(PARSER [,CLASS])
$obj->recursiveRebuildPart(PART, OPTIONS)
$obj->storeBody(BODY)
$obj->takeMessageId([STRING])
Error handling
$obj->AUTOLOAD
$obj->addReport(OBJECT)
$obj->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])
Mail::Box::Message->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])
$obj->errors
$obj->log([LEVEL [,STRINGS]])
Mail::Box::Message->log([LEVEL [,STRINGS]])
$obj->logPriority(LEVEL)
Mail::Box::Message->logPriority(LEVEL)
$obj->logSettings
$obj->notImplemented
$obj->report([LEVEL])
$obj->reportAll([LEVEL])
$obj->shortSize([VALUE])
Mail::Box::Message->shortSize([VALUE])
$obj->shortString
$obj->trace([LEVEL])
$obj->warnings
Cleanup
$obj->DESTROY
$obj->destruct
Removes most of the memory occupied by the message by detaching the header and body. Then, the object changes into a Mail::Box::Message::Destructed which will catch all attempts to access the header and body. Be careful with the usage of this method.
$obj->inGlobalDestruction
DETAILS
DIAGNOSTICS
Error: Cannot coerce a $class object into a $class object
Error: Cannot include forward source as $include.
Unknown alternative for the forward(include). Valid choices are NO
, INLINE
, ATTACH
, and ENCAPSULATE
.
Error: Cannot include reply source as $include.
Unknown alternative for the include
option of reply(). Valid choices are NO
, INLINE
, and ATTACH
.
Error: Method bounce requires To, Cc, or Bcc
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().
Error: Method forwardAttach requires a preamble
Error: Method forwardEncapsulate requires a preamble
Error: No address to create forwarded to.
If a forward message is created, a destination address must be specified.
Error: No default mailer found to send message.
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.
Error: No rebuild rule $name defined.
Error: Only build() Mail::Message's; they are not in a folder yet
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.
Error: Package $package does not implement $method.
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.
Error: coercion starts with some object
SEE ALSO
This module is part of Mail-Box distribution version 2.082, built on April 28, 2008. Website: http://perl.overmeer.net/mailbox/
LICENSE
Copyrights 2001-2008 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