.\" -*- mode: troff; coding: utf-8 -*- .\" Automatically generated by Pod::Man 5.0102 (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 .\" ======================================================================== .\" .IX Title "Mail::SpamAssassin::Message::Metadata 3" .TH Mail::SpamAssassin::Message::Metadata 3 2024-09-01 "perl v5.40.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::SpamAssassin::Message::Metadata \- extract metadata from a message .SH DESCRIPTION .IX Header "DESCRIPTION" This class is tasked with extracting "metadata" from messages for use as Bayes tokens, fodder for eval tests, or other rules. Metadata is supplemental data inferred from the message, like the examples below. .PP It is held in two forms: .PP 1. as name-value pairs of strings, presented in mail header format. For example, "X\-Languages" => "en". This is the general form for simple metadata that's useful as Bayes tokens, can be added to marked-up messages using "add_header", etc., such as the trusted-relay inference and language detection. .PP 2. as more complex data structures on the \f(CW$msg\fR\->{metadata} object. This is the form used for metadata like the HTML parse data, which is stored there for access by eval rule code. Because it's not simple strings, it's not added as a Bayes token by default (Bayes needs simple strings). .SH "PUBLIC METHODS" .IX Header "PUBLIC METHODS" .IP \fBnew()\fR 4 .IX Item "new()"