| spamassassin - mail filter to identify spam using text analysis |
spamassassin - mail filter to identify spam using text analysis
spamassassin [options] < mailmessage > output
spamassassin -d < mailmessage > <output>
spamassassin -r [-w addr] < mailmessage
spamassassin -k [-w addr] < mailmessage
spamassassin -W|-R < mailmessage
Options:
-P, --pipe Deliver to STDOUT (now default)
-L, --local Local tests only (no online tests)
-r, --report Report message as spam
-k, --revoke Revoke message as spam
-w addr, --warning-from=addr Send a warning mail to sender from addr
-d, --remove-markup Remove spam reports from a message
-C file, --config-file=file Path to standard configuration dir
-p prefs, --prefs-file=file Set user preferences file
-x, --nocreate-prefs Don't create user preferences file
-e, --exit-code Exit with a non-zero exit code if the
tested message was spam
-l filename, --log-to-mbox=file Log messages to a mbox file
-t, --test-mode Pipe message through and add extra
report to the bottom
--lint Lint the rule set: report syntax errors
-a, --auto-whitelist Use auto-whitelists
-W, --add-to-whitelist Add addresses in mail to whitelist
--add-to-blacklist Add addresses in mail to blacklist
-R, --remove-from-whitelist Remove all addresses found in mail
from whitelist
--add-addr-to-whitelist=addr Add addr to whitelist
--add-addr-to-blacklist=addr Add addr to blacklist
--remove-addr-from-whitelist=addr Remove addr from whitelist
-M, --whitelist-factory Select whitelist factory
-D, --debug [area=n,...] Print debugging messages
-V, --version Print version
-h, --help Print usage message
If you run tests with the -a option, the scores will be added to the AWL. This may not be what you want to do. If it is not, then don't use -a -t.
If the message contains SpamAssassin markup, this will be stripped out automatically before submission. The support modules for DCC, Razor and/or Pyzor must be installed for spam to be reported to each service.
The message will also be submitted to SpamAssassin's learning systems;
currently this is the internal Bayesian statistical-filtering system (the BAYES
rules). (Note that if you only want to perform statistical learning, and
do not want to report mail to a third-party server, you should use the
sa-learn command directly instead.)
Revocation support for the Distributed Checksum Clearinghouse ( http://www.rhyolite.com/anti-spam/dcc/ ), and Pyzor is not currently available.
If the message contains SpamAssassin markup, this will be stripped out automatically before submission. The support modules for Razor must be installed for spam to be revoked from the service.
The message will also be submitted as 'ham' (non-spam) to SpamAssassin's
learning systems; currently this is the internal Bayesian statistical-filtering
system (the BAYES rules). (Note that if you only want to perform
statistical learning, and do not want to report mail to a third-party server,
you should use the sa-learn command directly instead.)
spamassassin
or spamd with the -a switch for this to work.
spamassassin or spamd
with the -a switch.
Note that you must be running spamassassin or spamd with the -a switch.
spamassassin or spamd with the -a switch.
spamassassin or spamd with the -a switch.
spamassassin or spamd with the -a switch.
(Note: the message will not be exactly identical; some headers will be reformatted due to some features of the Mail::Internet package, but the body text will be.)
spamassassin -D rulesrun=255
SpamAssassin is a mail filter to identify spam using text analysis and several internet-based realtime blacklists.
Using its rule base, it uses a wide range of heuristic tests on mail headers and body text to identify ``spam'', also known as unsolicited commercial email.
Once identified, the mail is then tagged as spam for later filtering using the user's own mail user-agent application.
SpamAssassin also includes support for reporting spam messages to collaborative filtering databases, such as Vipul's Razor ( http://razor.sourceforge.net/ ).
The default tagging operations that take place are detailed in TAGGING.
The rule base, text templates, and rule description text are loaded from the configuration files.
By default, configuration data is loaded from the first existing directory in: C:\Perl/share/spamassassin; C:\Perl/share/spamassassin; /usr/local/share/spamassassin; /usr/share/spamassassin.
The configuration data in the first existing directory in: /etc/mail/spamassassin; C:\Perl/etc/mail/spamassassin; C:\Perl/etc/spamassassin; /usr/local/etc/spamassassin; /usr/pkg/etc/spamassassin; /usr/etc/spamassassin; /etc/mail/spamassassin; /etc/spamassassin are used to override any values which had already been set
Spamassassin will read *.cf in these directories, in alphanumeric order within each directory (similar to SysV-style startup scripts). In other words, it will read 10_misc.cf before 50_scores.cf and 20_body_tests.cf before 20_head_test.cf. Options in later files will override earlier files.
The user preferences (such as scores to attach to each rule), are loaded from
the file specified in the -p argument. If this is not specified,
~/.spamassassin/user_prefs is used if it exists. spamassassin will create this
file if it does not exist, using user_prefs.template as a template. This file will be looked for in:
/etc/mail/spamassassin;
C:\Perl/etc/mail/spamassassin;
C:\Perl/share/spamassassin;
/etc/spamassassin;
/etc/mail/spamassassin;
/usr/local/share/spamassassin;
/usr/share/spamassassin.
The following two sections detail the tagging that takes place for messages.
Note that if you use the -t argument, all mails will be tagged as if they are spam messages.
If an incoming message is tagged as spam, instead of modifying the original message, SpamAssassin will create a new report message and attach the original message as a message/rfc822 MIME part (ensuring the original message is completely preserved and easier to recover).
The new report message inherits the following headers (if they are present) from the original spam message:
*****SPAM***** is also prepended to the subject,
unless the rewrite_subject 0 configuration option is given.
And these headers are added:
Yes, hits=nn required=nn is set in this header to reflect
the filter status.
YES.
No, hits=nn required=nn is set in this header to reflect
the filter status.
Quite often, if you've been on the internet for a while, you'll have accumulated a few old email accounts that nowadays get nothing but spam.
SpamAssassin lets you set them up as aliases, as follows:
This will add any incoming mail messages straight into spam-tracking databases, such as Vipul's Razor; send an explanatory reply message to the sender, from the spamtrap1 address; then drop the mail into the bit-bucket.
The explanatory reply text is taken from the SpamAssassin configuration file,
where it is stored in the spamtrap lines.
If you want to keep a copy of the mails, use something like this:
It is suggested you familiarise yourself with how MTAs run programs specified in aliases, if you plan to do this; for one thing, spamassassin will not run under your user id in this case. If you are nervous about this, create a user for spamtrapping, and set up spamassassin in its .forward file.
The spamassassin command is part of the Mail::SpamAssassin Perl module.
Install this as a normal Perl module, using perl -MCPAN -e shell, or by
hand.
For further details on how to install, please read the INSTALL file
from the SpamAssassin distribution.
No environment variables, aside from those used by perl, are required to be set.
sa-learn(1)
Mail::SpamAssassin(3)
Mail::SpamAssassin::Conf(3)
Mail::Audit(3)
Razor(3)
http://bugzilla.spamassassin.org/
Justin Mason <jm /at/ jmason.org>
Mail::Audit
Net::DNS
Razor
| spamassassin - mail filter to identify spam using text analysis |