mail::spamassassin::plugin::spamcop(3) [suse man page]
Mail::SpamAssassin::Plugin::SpamCop(3) User Contributed Perl Documentation Mail::SpamAssassin::Plugin::SpamCop(3) NAME
Mail::SpamAssassin::Plugin::SpamCop - perform SpamCop reporting of messages SYNOPSIS
loadplugin Mail::SpamAssassin::Plugin::SpamCop DESCRIPTION
SpamCop is a service for reporting spam. SpamCop determines the origin of unwanted email and reports it to the relevant Internet service providers. By reporting spam, you have a positive impact on the problem. Reporting unsolicited email also helps feed spam filtering systems, including, but not limited to, the SpamCop blacklist used in SpamAssassin as a DNSBL. Note that spam reports sent by this plugin to SpamCop each include the entire spam message. See http://www.spamcop.net/ for more information about SpamCop. USER OPTIONS
spamcop_from_address add@ress.com (default: none) This address is used during manual reports to SpamCop as the From: address. You can use your normal email address. If this is not set, a guess will be used as the From: address in SpamCop reports. spamcop_to_address add@ress.com (default: generic reporting address) Your customized SpamCop report submission address. You need to obtain this address by registering at "http://www.spamcop.net/". If this is not set, SpamCop reports will go to a generic reporting address for SpamAssassin users and your reports will probably have less weight in the SpamCop system. spamcop_max_report_size (default: 50) Messages larger than this size (in kilobytes) will be truncated in report messages sent to SpamCop. The default setting is the maximum size that SpamCop will accept at the time of release. perl v5.12.1 2010-03-16 Mail::SpamAssassin::Plugin::SpamCop(3)
Check Out this Related Man Page
Mail::SpamAssassin::Plugin::Pyzor(3) User Contributed Perl Documentation Mail::SpamAssassin::Plugin::Pyzor(3) 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.12.1 2010-03-16 Mail::SpamAssassin::Plugin::Pyzor(3)