.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man v6.0.2 (Pod::Simple 3.45) .\" .\" Standard preamble: .\" ======================================================================== .de Sp \" Vertical space (when we can't use .PP) .if t .sp .5v .if n .sp .. .de Vb \" Begin verbatim text .ft CW .nf .ne \\$1 .. .de Ve \" End verbatim text .ft R .fi .. .\" \*(C` and \*(C' are quotes in nroff, nothing in troff, for use with C<>. .ie n \{\ . ds C` "" . ds C' "" 'br\} .el\{\ . ds C` . ds C' 'br\} .\" .\" Escape single quotes in literal strings from groff's Unicode transform. .ie \n(.g .ds Aq \(aq .el .ds Aq ' .\" .\" If the F register is >0, we'll generate index entries on stderr for .\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index .\" entries marked with X<> in POD. Of course, you'll have to process the .\" output yourself in some meaningful fashion. .\" .\" Avoid warning from groff about undefined register 'F'. .de IX .. .nr rF 0 .if \n(.g .if rF .nr rF 1 .if (\n(rF:(\n(.g==0)) \{\ . if \nF \{\ . de IX . tm Index:\\$1\t\\n%\t"\\$2" .. . if !\nF==2 \{\ . nr % 0 . nr F 2 . \} . \} .\} .rr rF .\" .\" Required to disable full justification in groff 1.23.0. .if n .ds AD l .\" ======================================================================== .\" .IX Title "Mail::Box::Parser 3" .TH Mail::Box::Parser 3 2025-12-14 "perl v5.42.0" "User Contributed Perl Documentation" .\" For nroff, turn off justification. Always turn off hyphenation; it makes .\" way too many mistakes in technical documents. .if n .ad l .nh .SH NAME Mail::Box::Parser \- reading and writing messages .SH INHERITANCE .IX Header "INHERITANCE" .Vb 2 \& Mail::Box::Parser \& is a Mail::Reporter \& \& Mail::Box::Parser is extended by \& Mail::Box::Parser::C \& Mail::Box::Parser::Lines \& Mail::Box::Parser::Perl .Ve .SH SYNOPSIS .IX Header "SYNOPSIS" .Vb 1 \& # Not instatiatiated itself .Ve .SH DESCRIPTION .IX Header "DESCRIPTION" The \f(CW\*(C`Mail::Box::Parser\*(C'\fR manages the parsing of folders. Usually, you won\*(Aqt need to know anything about this module, except the options which are involved with this code. .PP There are currently three implementations of this module: .IP \(bu 4 Mail::Box::Parser::C .Sp A fast parser written in \f(CW\*(C`C\*(C'\fR. This package is released as separate module on CPAN, because the module distribution via CPAN can not handle XS files which are not located in the root directory of the module tree. If a C compiler is available on your system, it will be used automatically. .IP \(bu 4 Mail::Box::Parser::Perl .Sp A slower parser when the message is in a file, like mbox, which only uses plain Perl. This module is a bit slower, and does less checking and less recovery. .IP \(bu 4 Mail::Box::Parser::Lines .Sp Useful when the message is already in memory. When you plan to use this yourself, you probably need to use Mail::Message::Construct::Read. .PP Extends "DESCRIPTION" in Mail::Reporter. .SH METHODS .IX Header "METHODS" Extends "METHODS" in Mail::Reporter. .SS Constructors .IX Subsection "Constructors" Extends "Constructors" in Mail::Reporter. .ie n .IP $class\->\fBnew\fR(%options) 4 .el .IP \f(CW$class\fR\->\fBnew\fR(%options) 4 .IX Item "$class->new(%options)" Create a parser object which can handle one file. For mbox\-like mailboxes, this object can be used to read a whole folder. In case of MH\-like mailboxes, each message is contained in a single file, so each message has its own parser object. Improves base, see "Constructors" in Mail::Reporter .Sp .Vb 3 \& \-Option \-\-Default \& fix_header_errors false \& trusted false .Ve .RS 4 .IP "fix_header_errors => BOOLEAN" 2 .IX Item "fix_header_errors => BOOLEAN" When header errors are detected, the parsing of the header will be stopped. Other header lines will become part of the body of the message. Set this flag to have the erroneous line added to the previous header line. .IP "trusted => BOOLEAN" 2 .IX Item "trusted => BOOLEAN" Is the input from the file to be trusted, or does it require extra tests. Related to Mail::Box::new(trusted). .RE .RS 4 .RE .SS Attributes .IX Subsection "Attributes" Extends "Attributes" in Mail::Reporter. .ie n .IP "$any\->\fBdefaultParserType\fR( [$class] )" 4 .el .IP "\f(CW$any\fR\->\fBdefaultParserType\fR( [$class] )" 4 .IX Item "$any->defaultParserType( [$class] )" Returns the parser to be used to parse all subsequent messages, possibly first setting the parser using the optional argument. Usually, the parser is autodetected; the \f(CW\*(C`C\*(C'\fR\-based parser will be used when it can be, and the Perl\-based parser will be used otherwise. .Sp The \f(CW$class\fR argument allows you to specify a package name to force a particular parser to be used (such as your own custom parser). You have to \f(CW\*(C`use\*(C'\fR or \f(CW\*(C`require\*(C'\fR the package yourself before calling this method with an argument. The parser must be a sub\-class of \f(CW\*(C`Mail::Box::Parser\*(C'\fR. .ie n .IP "$obj\->\fBfixHeaderErrors\fR( [BOOLEAN] )" 4 .el .IP "\f(CW$obj\fR\->\fBfixHeaderErrors\fR( [BOOLEAN] )" 4 .IX Item "$obj->fixHeaderErrors( [BOOLEAN] )" If set to \f(CW\*(C`true\*(C'\fR, parsing of a header will not stop on an error, but attempt to add the erroneous this line to previous field. Without \f(CW\*(C`BOOLEAN\*(C'\fR, the current setting is returned. .Sp » example: .Sp .Vb 2 \& $folder\->parser\->fixHeaderErrors(1); \& my $folder = $mgr\->open(\*(Aqfolder\*(Aq, fix_header_errors => 1); .Ve .ie n .IP $obj\->\fBtrusted\fR() 4 .el .IP \f(CW$obj\fR\->\fBtrusted\fR() 4 .IX Item "$obj->trusted()" Trust the source of the data: do not run additional tests. .SS Parsing .IX Subsection "Parsing" .ie n .IP "$obj\->\fBbodyAsFile\fR( $fh [$chars, [$lines]] )" 4 .el .IP "\f(CW$obj\fR\->\fBbodyAsFile\fR( \f(CW$fh\fR [$chars, [$lines]] )" 4 .IX Item "$obj->bodyAsFile( $fh [$chars, [$lines]] )" Try to read one message\-body from the file, and immediately write it to the specified file\-handle. Optionally, the predicted number of CHARacterS and/or \f(CW$lines\fR to be read can be supplied. These values may be \&\f(CW\*(C`undef\*(C'\fR and may be wrong. .Sp The return is a list of three scalars: the location of the body (begin and end) and the number of lines in the body. .ie n .IP "$obj\->\fBbodyAsList\fR( [$chars, [$lines]] )" 4 .el .IP "\f(CW$obj\fR\->\fBbodyAsList\fR( [$chars, [$lines]] )" 4 .IX Item "$obj->bodyAsList( [$chars, [$lines]] )" Try to read one message\-body from the file. Optionally, the predicted number of CHARacterS and/or \f(CW$lines\fR to be read can be supplied. These values may be \&\f(CW\*(C`undef\*(C'\fR and may be wrong. .Sp The return is a list of scalars, each containing one line (including line terminator), preceded by two integers representing the location in the file where this body started and ended. .ie n .IP "$obj\->\fBbodyAsString\fR( [$chars, [$lines]] )" 4 .el .IP "\f(CW$obj\fR\->\fBbodyAsString\fR( [$chars, [$lines]] )" 4 .IX Item "$obj->bodyAsString( [$chars, [$lines]] )" Try to read one message\-body from the file. Optionally, the predicted number of CHARacterS and/or \f(CW$lines\fR to be read can be supplied. These values may be \&\f(CW\*(C`undef\*(C'\fR and may be wrong. .Sp Returned is a list of three scalars: the location in the file where the body starts, where the body ends, and the string containing the whole body. .ie n .IP "$obj\->\fBbodyDelayed\fR( [$chars, [$lines]] )" 4 .el .IP "\f(CW$obj\fR\->\fBbodyDelayed\fR( [$chars, [$lines]] )" 4 .IX Item "$obj->bodyDelayed( [$chars, [$lines]] )" Try to read one message\-body from the file, but the data is skipped. Optionally, the predicted number of CHARacterS and/or \f(CW$lines\fR to be skipped can be supplied. These values may be \f(CW\*(C`undef\*(C'\fR and may be wrong. .Sp The return is a list of four scalars: the location of the body (begin and end), the size of the body, and the number of lines in the body. The number of lines may be \f(CW\*(C`undef\*(C'\fR. .ie n .IP $obj\->\fBlineSeparator\fR() 4 .el .IP \f(CW$obj\fR\->\fBlineSeparator\fR() 4 .IX Item "$obj->lineSeparator()" Returns the character or characters which are used to separate lines in the folder file. This is based on the first line of the file. UNIX systems use a single LF to separate lines. Windows uses a CR and a LF. Mac uses CR. .ie n .IP $obj\->\fBreadHeader\fR() 4 .el .IP \f(CW$obj\fR\->\fBreadHeader\fR() 4 .IX Item "$obj->readHeader()" Read the whole message\-header and return it as list of field\-value pairs. Mind that some fields will appear more than once. .Sp The first element will represent the position in the file where the header starts. The follows the list of header field names and bodies. .Sp » example: .Sp .Vb 1 \& my ($where, @header) = $parser\->readHeader; .Ve .ie n .IP $obj\->\fBstop\fR() 4 .el .IP \f(CW$obj\fR\->\fBstop\fR() 4 .IX Item "$obj->stop()" Stop the parser. .PP \fIAdministering separators\fR .IX Subsection "Administering separators" .PP The various "separators" methods are used by Mail::Message::Body::Multipart to detect parts, and for the file based mailboxes to flag where the new message starts. .ie n .IP $obj\->\fBactiveSeparator\fR() 4 .el .IP \f(CW$obj\fR\->\fBactiveSeparator\fR() 4 .IX Item "$obj->activeSeparator()" .ie n .IP $obj\->\fBpopSeparator\fR() 4 .el .IP \f(CW$obj\fR\->\fBpopSeparator\fR() 4 .IX Item "$obj->popSeparator()" Remove the last\-pushed separator from the list which is maintained by the parser. This will return \f(CW\*(C`undef\*(C'\fR when there is none left. .ie n .IP $obj\->\fBpushSeparator\fR(STRING|Regexp) 4 .el .IP \f(CW$obj\fR\->\fBpushSeparator\fR(STRING|Regexp) 4 .IX Item "$obj->pushSeparator(STRING|Regexp)" Add a boundary line. Separators tell the parser where to stop reading. A famous separator is the \f(CW\*(C`From\*(C'\fR\-line, which is used in Mbox\-like folders to separate messages. But also parts (\fIattachments\fR) is a message are divided by separators. .Sp The specified \f(CW\*(C`STRING\*(C'\fR describes the start of the separator\-line. The Regexp can specify a more complicated format. .ie n .IP $obj\->\fBreadSeparator\fR(%options) 4 .el .IP \f(CW$obj\fR\->\fBreadSeparator\fR(%options) 4 .IX Item "$obj->readSeparator(%options)" Read the currently active separator (the last one which was pushed). The line (or \f(CW\*(C`undef\*(C'\fR) is returned. Blank\-lines before the separator lines are ignored. .Sp The return are two scalars, where the first gives the location of the separator in the file, and the second the line which is found as separator. A new separator is activated using \fBpushSeparator()\fR. .ie n .IP $obj\->\fBresetSeparators\fR() 4 .el .IP \f(CW$obj\fR\->\fBresetSeparators\fR() 4 .IX Item "$obj->resetSeparators()" .ie n .IP $obj\->\fBseparators\fR() 4 .el .IP \f(CW$obj\fR\->\fBseparators\fR() 4 .IX Item "$obj->separators()" .ie n .IP $obj\->\fBstripGt\fR() 4 .el .IP \f(CW$obj\fR\->\fBstripGt\fR() 4 .IX Item "$obj->stripGt()" .SS "Error handling" .IX Subsection "Error handling" Extends "Error handling" in Mail::Reporter. .ie n .IP $obj\->\fBAUTOLOAD\fR() 4 .el .IP \f(CW$obj\fR\->\fBAUTOLOAD\fR() 4 .IX Item "$obj->AUTOLOAD()" Inherited, see "Error handling" in Mail::Reporter .ie n .IP $obj\->\fBnotImplemented\fR() 4 .el .IP \f(CW$obj\fR\->\fBnotImplemented\fR() 4 .IX Item "$obj->notImplemented()" Inherited, see "Error handling" in Mail::Reporter .SS Cleanup .IX Subsection "Cleanup" Extends "Cleanup" in Mail::Reporter. .ie n .IP $obj\->\fBDESTROY\fR() 4 .el .IP \f(CW$obj\fR\->\fBDESTROY\fR() 4 .IX Item "$obj->DESTROY()" Inherited, see "Cleanup" in Mail::Reporter .SH DIAGNOSTICS .IX Header "DIAGNOSTICS" .ie n .IP "Error: class $package does not implement method $method." 4 .el .IP "Error: class \f(CW$package\fR does not implement method \f(CW$method\fR." 4 .IX Item "Error: class $package does not implement method $method." Fatal error: the specific \f(CW$package\fR (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. Cast by \f(CWnotImplemented()\fR .ie n .IP "Error: parser $type does not extend $pkg." 4 .el .IP "Error: parser \f(CW$type\fR does not extend \f(CW$pkg\fR." 4 .IX Item "Error: parser $type does not extend $pkg." Cast by \f(CWdefaultParserType()\fR .ie n .IP "Warning: unexpected end of header in $source: $line" 4 .el .IP "Warning: unexpected end of header in \f(CW$source:\fR \f(CW$line\fR" 4 .IX Item "Warning: unexpected end of header in $source: $line" While parsing a message from the specified source (usually a file name), the parser found a syntax error. According to the MIME specification in the RFCs, each header line must either contain a colon, or start with a blank to indicate a folded field. Apparently, this header contains a line which starts on the first position, but not with a field name. .Sp By default, parsing of the header will be stopped. If there are more header lines after the erroneous line, they will be added to the body of the message. In case of new(fix_header_errors) set, the parsing of the header will be continued. The erroneous line will be added to the preceding field. Cast by \f(CWreadHeader()\fR .SH "SEE ALSO" .IX Header "SEE ALSO" This module is part of Mail\-Message version 4.01, built on December 13, 2025. Website: \fIhttp://perl.overmeer.net/CPAN/\fR .SH LICENSE .IX Header "LICENSE" For contributors see file ChangeLog. .PP This software is copyright (c) 2001\-2025 by Mark Overmeer. .PP This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.