mail::spamassassin::logger(3pm) [debian man page]

Mail::SpamAssassin::Logger(3pm) 			User Contributed Perl Documentation			   Mail::SpamAssassin::Logger(3pm)

NAME

       Mail::SpamAssassin::Logger - SpamAssassin logging module

SYNOPSIS

	 use Mail::SpamAssassin::Logger;

	 $SIG{__WARN__} = sub {
	   log_message("warn", $_[0]);
	 };

	 $SIG{__DIE__} = sub {
	   log_message("error", $_[0]) if $_[0] !~ /in eval/;
	 };

METHODS

       add_facilities(facilities)
	   Enable debug logging for specific facilities.  Each facility is the area of code to debug.  Facilities can be specified as a hash
	   reference (the key names are used), an array reference, an array, or a comma-separated scalar string. Facility names are case-
	   sensitive.

	   If "all" is listed, then all debug facilities are implicitly enabled, except for those explicitly disabled.	A facility name may be
	   preceded by a "no" (case-insensitive), which explicitly disables it, overriding the "all".  For example: all,norules,noconfig,nodcc.
	   When facility names are given as an ordered list (array or scalar, not a hash), the last entry applies, e.g. 'nodcc,dcc,dcc,noddc' is
	   equivalent to 'nodcc'.  Note that currently no facility name starts with a "no", it is advised to keep this practice with newly added
	   facility names to make life easier.

	   Higher priority informational messages that are suitable for logging in normal circumstances are available with an area of "info".
	   Some very verbose messages require the facility to be specifically enabled (see "would_log" below).

       log_message($level, @message)
	   Log a message at a specific level.  Levels are specified as strings: "warn", "error", "info", and "dbg".  The first element of the
	   message must be prefixed with a facility name followed directly by a colon.

       dbg("facility: message")
	   This is used for all low priority debugging messages.

       info("facility: message")
	   This is used for informational messages indicating a normal, but significant, condition.  This should be infrequently called.  These
	   messages are typically logged when SpamAssassin is run as a daemon.

       add(method => 'syslog', socket => $socket, facility => $facility)
	   "socket" is the type the syslog ("unix" or "inet").	"facility" is the syslog facility (typically "mail").

       add(method => 'file', filename => $file)
	   "filename" is the name of the log file.

       add(method => 'stderr')
	   No options are needed for stderr logging, just don't close stderr first.

       remove(method)
	   Remove a logging method.  Only the method name needs to be passed as a scalar.

       would_log($level, $facility)
	   Returns 0 if a message at the given level and with the given facility would be logged.  Returns 1 if a message at a given level and
	   facility would be logged normally.  Returns 2 if the facility was specifically enabled.

	   The facility argument is optional.

       close_log()
	   Close all logs.

perl v5.14.2							    2011-06-06					   Mail::SpamAssassin::Logger(3pm)

Check Out this Related Man Page

Mail::SpamAssassin::PersistentAddrList(3)		User Contributed Perl Documentation		 Mail::SpamAssassin::PersistentAddrList(3)

NAME

       Mail::SpamAssassin::PersistentAddrList - persistent address list base class

SYNOPSIS

	 my $factory = PersistentAddrListSubclass->new();
	 $spamtest->set_persistent_addr_list_factory ($factory);
	 ... call into SpamAssassin classes...

       SpamAssassin will call:

	 my $addrlist = $factory->new_checker($spamtest);
	 $entry = $addrlist->get_addr_entry ($addr);
	 ...

DESCRIPTION

       All persistent address list implementations, used by the auto-whitelist code to track known-good email addresses, use this as a base class.

       See "Mail::SpamAssassin::DBBasedAddrList" for an example.

METHODS

       $factory = PersistentAddrListSubclass->new();
	   This creates a factory object, which SpamAssassin will call to create a new checker object for the persistent address list.

       my $addrlist = $factory->new_checker();
	   Create a new address-list checker object from the factory. Called by the SpamAssassin classes.

       $entry = $addrlist->get_addr_entry ($addr);
	   Given an email address $addr, return an entry object with the details of that address.

	   The entry object is a reference to a hash, which must contain at least two keys: "count", which is the count of times that address has
	   been encountered before; and "totscore", which is the total of all scores for messages associated with that address.  From these two
	   fields, an average score will be calculated, and the score for the current message will be regressed towards that mean message score.

	   The hash can contain whatever other data your back-end needs to store, under other keys.

	   The method should never return "undef", or a hash that does not contain a "count" key and a "totscore" key.

       $entry = $addrlist->add_score($entry, $score);
	   This method should add the given score to the whitelist database for the given entry, and then return the new entry.

       $entry = $addrlist->remove_entry ($entry);
	   This method should remove the given entry from the whitelist database.

       $entry = $addrlist->finish ();
	   Clean up, if necessary.  Called by SpamAssassin when it has finished checking, or adding to, the auto-whitelist database.

perl v5.16.3							    2011-06-06				 Mail::SpamAssassin::PersistentAddrList(3)

Linux and UNIX Man Pages

mail::spamassassin::logger(3pm) [debian man page]

Check Out this Related Man Page