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)

See Mail::Message/"Constructors"

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])

See Mail::Message::Construct::Bounce/"Constructing a message"

Mail::Box::Message->build([MESSAGE|PART|BODY], CONTENT)

See Mail::Message::Construct::Build/"Constructing a message"

Mail::Box::Message->buildFromBody(BODY, [HEAD], HEADERS)

See Mail::Message::Construct::Build/"Constructing a message"

$obj->forward(OPTIONS)

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardAttach(OPTIONS)

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardEncapsulate(OPTIONS)

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardInline(OPTIONS)

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardNo(OPTIONS)

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardPostlude

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardPrelude

See Mail::Message::Construct::Forward/"Constructing a message"

$obj->forwardSubject(STRING)

See Mail::Message::Construct::Forward/"Constructing a message"

Mail::Box::Message->read(FILEHANDLE|SCALAR|REF-SCALAR|ARRAY-OF-LINES, OPTIONS)

See Mail::Message::Construct::Read/"Constructing a message"

$obj->rebuild(OPTIONS)

See Mail::Message::Construct::Rebuild/"Constructing a message"

$obj->reply(OPTIONS)

See Mail::Message::Construct::Reply/"Constructing a message"

$obj->replyPrelude([STRING|FIELD|ADDRESS|ARRAY-OF-THINGS])

See Mail::Message::Construct::Reply/"Constructing a message"

$obj->replySubject(STRING)

Mail::Box::Message->replySubject(STRING)

See Mail::Message::Construct::Reply/"Constructing a message"

The message

$obj->container

See Mail::Message/"The message"

$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

See Mail::Message/"The message"

$obj->isPart

See Mail::Message/"The message"

$obj->messageId

See Mail::Message/"The message"

$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])

See Mail::Message/"The message"

$obj->send([MAILER], OPTIONS)

See Mail::Message/"The message"

$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

See Mail::Message/"The message"

$obj->toplevel

See Mail::Message/"The message"

$obj->write([FILEHANDLE])

See Mail::Message/"The message"

The header

$obj->bcc

See Mail::Message/"The header"

$obj->cc

See Mail::Message/"The header"

$obj->date

See Mail::Message/"The header"

$obj->destinations

See Mail::Message/"The header"

$obj->from

See Mail::Message/"The header"

$obj->get(FIELDNAME)

See Mail::Message/"The header"

$obj->guessTimestamp

See Mail::Message/"The header"

$obj->head([HEAD])

See Mail::Message/"The header"

$obj->nrLines

See Mail::Message/"The header"

$obj->sender

See Mail::Message/"The header"

$obj->study(FIELDNAME)

See Mail::Message/"The header"

$obj->subject

See Mail::Message/"The header"

$obj->timestamp

See Mail::Message/"The header"

$obj->to

See Mail::Message/"The header"

The body

$obj->body([BODY])

See Mail::Message/"The body"

$obj->contentType

See Mail::Message/"The body"

$obj->decoded(OPTIONS)

See Mail::Message/"The body"

$obj->encode(OPTIONS)

See Mail::Message/"The body"

$obj->isMultipart

See Mail::Message/"The body"

$obj->isNested

See Mail::Message/"The body"

$obj->parts(['ALL'|'ACTIVE'|'DELETED'|'RECURSE'|FILTER])

See Mail::Message/"The body"

Flags

$obj->delete

See Mail::Message/"Flags"

$obj->deleted([BOOLEAN])

See Mail::Message/"Flags"

$obj->isDeleted

See Mail::Message/"Flags"

$obj->isModified

See Mail::Message/"Flags"

$obj->label(LABEL|PAIRS)

See Mail::Message/"Flags"

$obj->labels

See Mail::Message/"Flags"

$obj->labelsToStatus

See Mail::Message/"Flags"

$obj->modified([BOOLEAN])

See Mail::Message/"Flags"

$obj->statusToLabels

See Mail::Message/"Flags"

The whole message as text

$obj->file

See Mail::Message::Construct::Text/"The whole message as text"

$obj->lines

See Mail::Message::Construct::Text/"The whole message as text"

$obj->printStructure([FILEHANDLE|undef],[INDENT])

See Mail::Message::Construct::Text/"The whole message as text"

$obj->string

See Mail::Message::Construct::Text/"The whole message as text"

Internals

$obj->clonedFrom

See Mail::Message/"Internals"

Mail::Box::Message->coerce(MESSAGE, OPTIONS)

See Mail::Message/"Internals"

$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

See Mail::Message/"Internals"

$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])

See Mail::Message/"Internals"

$obj->readHead(PARSER [,CLASS])

See Mail::Message/"Internals"

$obj->recursiveRebuildPart(PART, OPTIONS)

See Mail::Message::Construct::Rebuild/"Internals"

$obj->storeBody(BODY)

See Mail::Message/"Internals"

$obj->takeMessageId([STRING])

See Mail::Message/"Internals"

Error handling

$obj->AUTOLOAD

See Mail::Message::Construct/"METHODS"

$obj->addReport(OBJECT)

See Mail::Reporter/"Error handling"

$obj->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])

Mail::Box::Message->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])

See Mail::Reporter/"Error handling"

$obj->errors

See Mail::Reporter/"Error handling"

$obj->log([LEVEL [,STRINGS]])

Mail::Box::Message->log([LEVEL [,STRINGS]])

See Mail::Reporter/"Error handling"

$obj->logPriority(LEVEL)

Mail::Box::Message->logPriority(LEVEL)

See Mail::Reporter/"Error handling"

$obj->logSettings

See Mail::Reporter/"Error handling"

$obj->notImplemented

See Mail::Reporter/"Error handling"

$obj->report([LEVEL])

See Mail::Reporter/"Error handling"

$obj->reportAll([LEVEL])

See Mail::Reporter/"Error handling"

$obj->shortSize([VALUE])

Mail::Box::Message->shortSize([VALUE])

See Mail::Message/"Error handling"

$obj->shortString

See Mail::Message/"Error handling"

$obj->trace([LEVEL])

See Mail::Reporter/"Error handling"

$obj->warnings

See Mail::Reporter/"Error handling"

Cleanup

$obj->DESTROY

See Mail::Message/"Cleanup"

$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

See Mail::Reporter/"Cleanup"

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