|
Hopefully, this page is exactly what you are looking for, but if not, you can always find further assistance on Unix/Linux Forum!
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_timeout n (default: 8)
How many seconds you wait for DCC to complete, before scanning con-
tinues without the DCC results.
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_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 2006-08-29Mail::SpamAssassin::Plugin::DCC(3)
Man(1) output converted with
man2html and wrapped by fishsponge
This page was generated on Sat Sep 8 16:38:51 GMT 2007
|
Your favourite pages:
No pages logged yet.
Trying to save cookie... Top 10 most popular pages:
svn man page (6163 hits)
(FreeBSD 6.2)
sqlite3 man page (5598 hits)
(openSUSE 10.2)
adv_cap_autoneg man page (5045 hits)
(Solaris 10 11_06)
CPAN man page (4791 hits)
(Suse Linux 10.1)
ssh man page (4439 hits)
(Suse Linux 10.1)
ssh-socks5-proxy-connect man page (3525 hits)
(Solaris 10 11_06)
signal man page (3395 hits)
(Suse Linux 10.1)
netcat man page (3377 hits)
(Suse Linux 10.1)
pprosetup man page (2886 hits)
(Solaris 10 11_06)
startproc man page (2738 hits)
(Suse Linux 10.1)
|
Man Pages 
