=head1 NAME Mail::Message::Field::Unstructured - smart unstructured field =head1 INHERITANCE Mail::Message::Field::Unstructured is a Mail::Message::Field::Full is a Mail::Message::Field is a Mail::Reporter =head1 SYNOPSIS my $f = Mail::Message::Field::Unstructured->new(Comments => 'hi!'); =head1 DESCRIPTION Unstructured fields do contain information which is not restricted in any way. RFC2822 defines some unstructured fields, but by default all unknown fields are unstructured as well. Things like attributes and comments have no meaning for unstructured fields, but encoding does. =head1 OVERLOADED overload: B<""> =over 4 See L =back overload: B<+0> =over 4 See L =back overload: B<<=>> =over 4 See L =back overload: B =over 4 See L =back overload: B =over 4 See L =back overload: B =over 4 See L =back =head1 METHODS =head2 Constructors $obj-EB =over 4 See L =back Mail::Message::Field::Unstructured-EB(FIELD, OPTIONS) =over 4 See L =back Mail::Message::Field::Unstructured-EB(DATA) =over 4 When the DATA is specified as single line, the content part is considered to be correcly (character) encoded and escaped. Typically, it is a line as read from file. The folding of the line is kept as is. In case more than one argument is provided, the second is considered the BODY. Attributes and other special things are not defined for unstructured fields, and therefore not valid options. The BODY can be a single string, a single OBJECT, or an array of OBJECTS. The objects are stringified (into a comma separated list). Each BODY element is interpreted with the specified encoding. When the BODY is empty, the construction of the object fails: C is returned. Option --Defined in --Default charset Mail::Message::Field::Full undef encoding Mail::Message::Field::Full 'q' force Mail::Message::Field::Full false language Mail::Message::Field::Full undef log Mail::Reporter 'WARNINGS' trace Mail::Reporter 'WARNINGS' . charset => STRING . encoding => 'q'|'Q'|'b'|'B' . force => BOOLEAN . language => STRING . log => LEVEL . trace => LEVEL example: my $s = Mail::Message::Field::Unstructured->new('Comment', 'Hi!'); # Use autodetect my $s = Mail::Message::Field::Full->new('Comment', 'Hi!'); my $s = Mail::Message::Field::Full->new('Comment: Hi!'); =back =head2 The field $obj-EB Mail::Message::Field::Unstructured-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([FILEHANDLE]) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([WRAP]) =over 4 See L =back $obj-EB =over 4 See L =back =head2 Access to the name $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([STRING]) =over 4 See L =back =head2 Access to the body $obj-EB =over 4 See L =back $obj-EB(OPTIONS) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([BODY]) =over 4 See L =back $obj-EB([STRING]) Mail::Message::Field::Unstructured-EB([STRING]) =over 4 See L =back $obj-EB([BODY, [WRAP]]) =over 4 See L =back =head2 Access to the content $obj-EB =over 4 See L =back $obj-EB(NAME [, VALUE]) =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 $obj-EB(STRING, OPTIONS) Mail::Message::Field::Unstructured-EB(STRING, OPTIONS) =over 4 See L =back $obj-EB(STRING, OPTIONS) Mail::Message::Field::Unstructured-EB(STRING, OPTIONS) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([TIME]) Mail::Message::Field::Unstructured-EB([TIME]) =over 4 See L =back $obj-EB =over 4 See L =back =head2 Other methods $obj-EB(STRING) Mail::Message::Field::Unstructured-EB(STRING) =over 4 See L =back =head2 Internals $obj-EB(LINE | (NAME,BODY|OBJECTS)) =over 4 See L =back $obj-EB(STRING, OPTIONS) Mail::Message::Field::Unstructured-EB(STRING, OPTIONS) =over 4 See L =back $obj-EB([LENGTH]) =over 4 See L =back $obj-EB(STRING, OPTIONS) =over 4 See L =back $obj-EB(NAME, BODY, [MAXCHARS]) Mail::Message::Field::Unstructured-EB(NAME, BODY, [MAXCHARS]) =over 4 See L =back $obj-EB([LENGTH]) =over 4 See L =back $obj-EB(STRING|ARRAY|OBJECTS) =over 4 See L =back $obj-EB(STRING) =over 4 See L =back =head2 Parsing $obj-EB(STRING) Mail::Message::Field::Unstructured-EB(STRING) =over 4 See L =back $obj-EB(STRING) =over 4 See L =back $obj-EB(STRING) Mail::Message::Field::Unstructured-EB(STRING) =over 4 See L =back $obj-EB(STRING) =over 4 See L =back $obj-EB =over 4 See L =back =head2 Error handling $obj-EB =over 4 See L =back $obj-EB(OBJECT) =over 4 See L =back $obj-EB([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK]) Mail::Message::Field::Unstructured-EB([LEVEL]|[LOGLEVEL, TRACELEVEL]|[LEVEL, CALLBACK]) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([LEVEL [,STRINGS]]) Mail::Message::Field::Unstructured-EB([LEVEL [,STRINGS]]) =over 4 See L =back $obj-EB(LEVEL) Mail::Message::Field::Unstructured-EB(LEVEL) =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back $obj-EB([LEVEL]) =over 4 See L =back $obj-EB([LEVEL]) =over 4 See L =back $obj-EB([LEVEL]) =over 4 See L =back $obj-EB =over 4 See L =back =head2 Cleanup $obj-EB =over 4 See L =back $obj-EB =over 4 See L =back =head1 DETAILS =head1 DIAGNOSTICS Warning: Field content is not numerical: $content =over 4 The numeric value of a field is requested (for instance the C or C fields should be numerical), however the data contains weird characters. =back Warning: Illegal character in charset '$charset' =over 4 The field is created with an utf8 string which only contains data from the specified character set. However, that character set can never be a valid name because it contains characters which are not permitted. =back Warning: Illegal character in field name $name =over 4 A new field is being created which does contain characters not permitted by the RFCs. Using this field in messages may break other e-mail clients or transfer agents, and therefore mutulate or extinguish your message. =back Warning: Illegal character in language '$lang' =over 4 The field is created with data which is specified to be in a certain language, however, the name of the language cannot be valid: it contains characters which are not permitted by the RFCs. =back Warning: Illegal encoding '$encoding', used 'q' =over 4 The RFCs only permit base64 (C or C) or quoted-printable (C or C) encoding. Other than these four options are illegal. =back Error: Package $package does not implement $method. =over 4 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. =back =head1 SEE ALSO This module is part of Mail-Box distribution version 2.079, built on November 28, 2007. Website: F =head1 LICENSE Copyrights 2001-2007 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 F