Re: [vps-mail] spamassassin

[Scott Wiersdorf <scott@xxxxxxxxxxxx>]

On Tue, Oct 14, 2003 at 10:35:58AM -0500, Jaime Gabay wrote:
> can anyone help in the best and easy way to teach/show our clients how to
> add recepies to spamassasin,
> editing the files and how to block emails for content rather than sender.

The Mail::SpamAssassin::Conf(3) manpage has several examples of
this. Here are a few relevant sections from the manpage:

       body SYMBOLIC_TEST_NAME /pattern/modifiers
           Define a body pattern test.  "pattern" is a Perl regu-
           lar expression.

           The 'body' in this case is the textual parts of the
           message body; any non-text MIME parts are stripped,
           and the message decoded from Quoted-Printable or
           Base-64-encoded format if necessary.  All HTML tags
           and line breaks will be removed before matching.

       describe SYMBOLIC_TEST_NAME description ...
           Used to describe a test.  This text is shown to users
           in the detailed report.

       score SYMBOLIC_TEST_NAME n.nn [ n.nn n.nn n.nn ]
           Assign scores (the number of points for a hit) to a
           given test. Scores can be positive or negative real
           numbers or integers. "SYMBOLIC_TEST_NAME" is the sym-
           bolic name used by SpamAssassin for that test; for
           example, 'FROM_ENDS_IN_NUMS'.

Here's an example of one you could add:

    body     BODY_HAS_REM0VE    /rem0ve/i
    describe BODY_HAS_REM0VE    Body has "remove" misspelled with zero
    score    BODY_HAS_REM0VE    1.2

There may be other settings (allow_user_rules or something like that)
that I'm not very familiar with. Perhaps someone else on the list can
comment. Allowing end users the ability to add their own custom rules
can be dangerous (according to the manpage) since their rules are
actual pieces of Perl code that are run. You need to evaluate your
clients and their abilities for allowing end-users to customize their
own rules.

Scott
-- 
Scott Wiersdorf
scott@xxxxxxxxxxxx
======================================================================
Technical questions regarding this list may be sent to
<vps-mail-owner@xxxxxxxxxxxx>. You may request an automated help
response by sending an email with the word 'help' (w/o quotes) in the
BODY of the message (subject is ignored) to <vps-mail-request@xxxxxxxxxxxx>.
======================================================================