NAME
Mail::Box::MH::Message - one message in an MH-folder
INHERITANCE
Mail::Box::MH::Message
is a Mail::Box::Dir::Message
is a Mail::Box::Message
is a Mail::Message
is a Mail::Reporter
SYNOPSIS
my $folder = new Mail::Box::MH ...
my $message = $folder->message(10);
DESCRIPTION
A Mail::Box::MH::Message
represents one message in an Mail::Box::MH folder . Each message is stored in a separate file, as for all Mail::Box::Dir folder types.
METHODS
Constructors
$obj->clone(OPTIONS)
Mail::Box::MH::Message->new(OPTIONS)
Constructing a message
$obj->bounce([RG-OBJECT|OPTIONS])
Mail::Box::MH::Message->build([MESSAGE|PART|BODY], CONTENT)
Mail::Box::MH::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::MH::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::MH::Message->replySubject(STRING)
The message
$obj->container
$obj->copyTo(FOLDER, OPTIONS)
$obj->filename([FILENAME])
$obj->folder([FOLDER])
$obj->isDummy
$obj->isPart
$obj->messageId
$obj->moveTo(FOLDER, OPTIONS)
$obj->print([FILEHANDLE])
$obj->send([MAILER], OPTIONS)
$obj->seqnr([INTEGER])
The order of this message in the folder, counted from zero. Do not change the number (unless you understand the implications).
WARNING: This sequence number has nothing to do with the message's filename, which in case of MH folders are also numbers! If you need that one, use the File::Basename subroutine basename of the filename.
$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::MH::Message->coerce(MESSAGE, OPTIONS)
$obj->create(FILENAME)
$obj->diskDelete
$obj->isDelayed
$obj->loadBody
$obj->loadHead
$obj->parser
$obj->readBody(PARSER, HEAD [, BODYTYPE])
$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::MH::Message->defaultTrace([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK])
$obj->errors
$obj->log([LEVEL [,STRINGS]])
Mail::Box::MH::Message->log([LEVEL [,STRINGS]])
$obj->logPriority(LEVEL)
Mail::Box::MH::Message->logPriority(LEVEL)
$obj->logSettings
$obj->notImplemented
$obj->report([LEVEL])
$obj->reportAll([LEVEL])
$obj->shortSize([VALUE])
Mail::Box::MH::Message->shortSize([VALUE])
$obj->shortString
$obj->trace([LEVEL])
$obj->warnings
Cleanup
$obj->DESTROY
$obj->destruct
$obj->inGlobalDestruction
DETAILS
Labels
The .mh_sequences file
Typically, the file which contains the labels is called .mh_sequences
. The MH messages are numbered from 1
. As example content for .mh_sequences
:
cur: 93
unseen: 32 35-56 67-80
To generalize labels on messages, two are treated specially:
cur
The
cur
specifies the number of the message where the user stopped reading mail from this folder at last access. Internally in these modules referred to as labelcurrent
.unseen
With
unseen
is listed which message was never read. This must be a mistake in the design of MH: it must be a source of confusion. People should never use labels with a negation in the name:if($seen) if(!$unseen) #yuk! if(!$seen) if($unseen) unless($seen) unless($unseen) #yuk!
So: label
unseen
is translated intoseen
for internal use.
DIAGNOSTICS
Error: Cannot coerce a $class object into a $class object
Error: Cannot create parser for $filename.
For some reason (the previous message have told you already) it was not possible to create a message parser for the specified filename.
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: Cannot write message to $filename: $!
When a modified or new message is written to disk, it is first written to a temporary file in the folder directory. For some reason, it is impossible to create this file.
Error: Failed to move $new to $filename: $!
When a modified or new message is written to disk, it is first written to a temporary file in the folder directory. Then, the new file is moved to replace the existing file. Apparently, the latter fails.
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: Unable to read delayed body.
For some reason, the header of the message could be read, but the body cannot. Probably the file has disappeared or the permissions were changed during the progress of the program.
Error: Unable to read delayed head.
Mail::Box tries to be lazy with respect to parsing messages. When a directory organized folder is opened, only the filenames of messages are collected. At first use, the messages are read from their file. Apperently, a message is used for the first time here, but has disappeared or is unreadible for some other reason.
Error: coercion starts with some object
SEE ALSO
This module is part of Mail-Box distribution version 2.080, built on January 15, 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