mail::spamassassin::plugin::hashcash(3) [suse 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 add@ress.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.12.1 2010-03-16 Mail::SpamAssassin::Plugin::Hashcash(3)
Check Out this Related Man Page
Mail::SpamAssassin::Plugin::SPF(3) User Contributed Perl Documentation Mail::SpamAssassin::Plugin::SPF(3) NAME
Mail::SpamAssassin::Plugin::SPF - perform SPF verification tests SYNOPSIS
loadplugin Mail::SpamAssassin::Plugin::SPF DESCRIPTION
This plugin checks a message against Sender Policy Framework (SPF) records published by the domain owners in DNS to fight email address forgery and make it easier to identify spams. USER SETTINGS
whitelist_from_spf user@example.com Works similarly to whitelist_from, except that in addition to matching a sender address, a check against the domain's SPF record must pass. The first parameter is an address to whitelist, and the second is a string to match the relay's rDNS. Just like whitelist_from, multiple addresses per line, separated by spaces, are OK. Multiple "whitelist_from_spf" lines are also OK. The headers checked for whitelist_from_spf addresses are the same headers used for SPF checks (Envelope-From, Return-Path, X-Envelope- From, etc). Since this whitelist requires an SPF check to be made, network tests must be enabled. It is also required that your trust path be correctly configured. See the section on "trusted_networks" for more info on trust paths. e.g. whitelist_from_spf joe@example.com fred@example.com whitelist_from_spf *@example.com def_whitelist_from_spf user@example.com Same as "whitelist_from_spf", but used for the default whitelist entries in the SpamAssassin distribution. The whitelist score is lower, because these are often targets for spammer spoofing. ADMINISTRATOR OPTIONS
spf_timeout n (default: 5) How many seconds to wait for an SPF query to complete, before scanning continues without the SPF result. do_not_use_mail_spf (0|1) (default: 0) By default the plugin will try to use the Mail::SPF module for SPF checks if it can be loaded. If Mail::SPF cannot be used the plugin will fall back to using the legacy Mail::SPF::Query module if it can be loaded. Use this option to stop the plugin from using Mail::SPF and cause it to try to use Mail::SPF::Query instead. do_not_use_mail_spf_query (0|1) (default: 0) As above, but instead stop the plugin from trying to use Mail::SPF::Query and cause it to only try to use Mail::SPF. ignore_received_spf_header (0|1) (default: 0) By default, to avoid unnecessary DNS lookups, the plugin will try to use the SPF results found in any "Received-SPF" headers it finds in the message that could only have been added by an internal relay. Set this option to 1 to ignore any "Received-SPF" headers present and to have the plugin perform the SPF check itself. Note that unless the plugin finds an "identity=helo", or some unsupported identity, it will assume that the result is a mfrom SPF check result. The only identities supported are "mfrom", "mailfrom" and "helo". use_newest_received_spf_header (0|1) (default: 0) By default, when using "Received-SPF" headers, the plugin will attempt to use the oldest (bottom most) "Received-SPF" headers, that were added by internal relays, that it can parse results from since they are the most likely to be accurate. This is done so that if you have an incoming mail setup where one of your primary MXes doesn't know about a secondary MX (or your MXes don't know about some sort of forwarding relay that SA considers trusted+internal) but SA is aware of the actual domain boundary (internal_networks setting) SA will use the results that are most accurate. Use this option to start with the newest (top most) "Received-SPF" headers, working downwards until results are successfully parsed. perl v5.16.3 2011-06-06 Mail::SpamAssassin::Plugin::SPF(3)