mail::spamassassin::plugin::hashcash(3) [centos man page]

Mail::SpamAssassin::Plugin::Hashcash(3) 		User Contributed Perl Documentation		   Mail::SpamAssassin::Plugin::Hashcash(3)

NAME

       Mail::SpamAssassin::Plugin::Hashcash - perform hashcash verification tests

SYNOPSIS

	 loadplugin	Mail::SpamAssassin::Plugin::Hashcash

DESCRIPTION

       Hashcash is a payment system for email where CPU cycles used as the basis for an e-cash system.	This plugin makes it possible to use valid
       hashcash tokens added by mail programs as a bonus for messages.

USER SETTINGS

       use_hashcash { 1 | 0 }	(default: 1)
	   Whether to use hashcash, if it is available.

       hashcash_accept user@example.com ...
	   Used to specify addresses that we accept HashCash tokens for.  You should set it to match all the addresses that you may receive mail
	   at.

	   Like whitelist and blacklist entries, the addresses are file-glob-style patterns, so "friend@somewhere.com", "*@isp.com", or
	   "*.domain.net" will all work.  Specifically, "*" and "?" are allowed, but all other metacharacters are not.	Regular expressions are
	   not used for security reasons.

	   The sequence %u is replaced with the current user's username, which is useful for ISPs or multi-user domains.

	   Multiple addresses per line, separated by spaces, is OK.  Multiple "hashcash_accept" lines is also OK.

       hashcash_doublespend_path /path/to/file	 (default: ~/.spamassassin/hashcash_seen)
	   Path for HashCash double-spend database.  HashCash tokens are only usable once, so their use is tracked in this database to avoid
	   providing a loophole.

	   By default, each user has their own, in their "~/.spamassassin" directory with mode 0700/0600.  Note that once a token is 'spent' it is
	   written to this file, and double-spending of a hashcash token makes it invalid, so this is not suitable for sharing between multiple
	   users.

       hashcash_doublespend_file_mode		 (default: 0700)
	   The file mode bits used for the HashCash double-spend database file.

	   Make sure you specify this using the 'x' mode bits set, as it may also be used to create directories.  However, if a file is created,
	   the resulting file will not have any execute bits set (the umask is set to 111).

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

Mail::SpamAssassin::Plugin::Pyzor(3pm)			User Contributed Perl Documentation		    Mail::SpamAssassin::Plugin::Pyzor(3pm)

NAME

       Mail::SpamAssassin::Plugin::Pyzor - perform Pyzor check of messages

SYNOPSIS

	 loadplugin	Mail::SpamAssassin::Plugin::Pyzor

DESCRIPTION

       Pyzor is a collaborative, networked system to detect and block spam using identifying digests of messages.

       See http://pyzor.sourceforge.net/ for more information about Pyzor.

USER OPTIONS

       use_pyzor (0|1)		(default: 1)
	   Whether to use Pyzor, if it is available.

       pyzor_max NUMBER 	(default: 5)
	   This option sets how often a message's body checksum must have been reported to the Pyzor server before SpamAssassin will consider the
	   Pyzor check as matched.

	   As most clients should not be auto-reporting these checksums, you should set this to a relatively low value, e.g. 5.

ADMINISTRATOR OPTIONS

       pyzor_timeout n		(default: 3.5)
	   How many seconds you wait for Pyzor to complete, before scanning continues without the Pyzor results.

	   You can configure Pyzor to have its own per-server timeout.	Set this plugin's timeout with that in mind.  This plugin's timeout is a
	   maximum ceiling.  If Pyzor takes longer than this to complete its communication with all servers, no results are used by SpamAssassin.

	   Pyzor servers do not yet synchronize their servers, so it can be beneficial to check and report to more than one.  See the pyzor-users
	   mailing list for alternate servers that are not published via 'pyzor discover'.

	   If you are using multiple Pyzor servers, a good rule of thumb would be to set the SpamAssassin plugin's timeout to be the same or just
	   a bit more than the per-server Pyzor timeout (e.g., 3.5 and 2 for two Pyzor servers).  If more than one of your Pyzor servers is always
	   timing out, consider removing one of them.

       pyzor_options options
	   Specify additional options to the pyzor(1) command. Please note that only characters in the range [0-9A-Za-z ,._/-] are allowed for
	   security reasons.

       pyzor_path STRING
	   This option tells SpamAssassin specifically where to find the "pyzor" client instead of relying on SpamAssassin to find it in the
	   current PATH.  Note that if taint mode is enabled in the Perl interpreter, you should use this, as the current PATH will have been
	   cleared.

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