Mail::SpamAssassin::Plugin::DCC man page on YellowDog

Man page or keyword search:  
man Server   18644 pages
apropos Keyword Search (all sections)
Output format
YellowDog logo
[printable version]

Mail::SpamAssassin::PlUser:Contributed Perl Mail::SpamAssassin::Plugin::DCC(3)

NAME
       Mail::SpamAssassin::Plugin::DCC - perform DCC check of messages

SYNOPSIS
	 loadplugin	Mail::SpamAssassin::Plugin::DCC

DESCRIPTION
       The DCC or Distributed Checksum Clearinghouse is a system of servers
       collecting and counting checksums of millions of mail messages. The
       counts can be used by SpamAssassin to detect and reject or filter spam.

       Because simplistic checksums of spam can be easily defeated, the main
       DCC checksums are fuzzy and ignore aspects of messages.	The fuzzy
       checksums are changed as spam evolves.

       Note that DCC is disabled by default in "init.pre" because it is not
       open source.  See the DCC license for more details.

       See http://www.rhyolite.com/anti-spam/dcc/ for more information about
       DCC.

USER OPTIONS
       use_dcc (0⎪1)	   (default: 1)
	   Whether to use DCC, if it is available.

       dcc_body_max NUMBER
       dcc_fuz1_max NUMBER
       dcc_fuz2_max NUMBER
	   This option sets how often a message's body/fuz1/fuz2 checksum must
	   have been reported to the DCC server before SpamAssassin will con‐
	   sider the DCC check as matched.

	   As nearly all DCC clients are auto-reporting these checksums, you
	   should set this to a relatively high value, e.g. 999999 (this is
	   DCC's MANY count).

	   The default is 999999 for all these options.

ADMINISTRATOR OPTIONS
       dcc_timeout n	   (default: 8)
	   How many seconds you wait for DCC to complete, before scanning con‐
	   tinues without the DCC results.

       dcc_home STRING
	   This option tells SpamAssassin specifically where to find the dcc
	   homedir.  If "dcc_path" is not specified, it will default to look‐
	   ing in "dcc_home/bin" for dcc client instead of relying on SpamAs‐
	   sassin to find it in the current PATH.  If it isn't found there, it
	   will look in the current PATH. If a "dccifd" socket is found in
	   "dcc_home", it will use that interface that instead of "dccproc".

       dcc_dccifd_path STRING
	   This option tells SpamAssassin specifically where to find the
	   dccifd socket.  If "dcc_dccifd_path" is not specified, it will
	   default to looking in "dcc_home" If a "dccifd" socket is found, it
	   will use it instead of "dccproc".

       dcc_path STRING
	   This option tells SpamAssassin specifically where to find the
	   "dccproc" 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.

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

	   The default is "undef".

       dccifd_options options
	   Specify additional options to send to the dccifd(8) daemon. Please
	   note that only characters in the range [0-9A-Za-z ,._/-] are
	   allowed for security reasons.

	   The default is "undef".

perl v5.8.8			  2008-06-10Mail::SpamAssassin::Plugin::DCC(3)
[top]

List of man pages available for YellowDog

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net