spamassassin-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Spamassassin Wiki] Update of "BetterDocumentation/ReadmeTxt" by LorenWilton
Date Sat, 27 Aug 2005 02:04:49 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Spamassassin Wiki" for change notification.

The following page has been changed by LorenWilton:
http://wiki.apache.org/spamassassin/BetterDocumentation/ReadmeTxt

------------------------------------------------------------------------------
  Locali[sz]ation
  ---------------
  
+ All text displayed to users is taken from the configuration files.  This means that you
can translate messages, test descriptions, and templates into other languages.
- All text displayed to users is taken from the configuration files.  This
- means that you can translate messages, test descriptions, and templates
- into other languages.
  
  If you do so, we would *really* appreciate if you could send a copy back of the updated
messages; mail them to
- <spamassassin-users@incubator.apache.org> .  Hopefully if it takes off, I can add
them to the distribution as "official" translations and build in support for this.  You will,
of course, get credited for this work ;)
+ <users /at/ spamassassin.apache.org> .  Hopefully if it takes off, I can add them
to the distribution as "official" translations and build in support for this.  You will, of
course, get credited for this work ;)
  
  
  Help With SpamAssassin
  ----------------------
  
+ There's a mailing list for support or discussion of SpamAssassin.  It lives at <users
/at/ spamassassin.apache.org>.  See
- There's a mailing list for support or discussion of SpamAssassin.  It
- lives at <spamassassin-users /at/ incubator.apache.org>.  See
- http://wiki.apache.org/spamassassin/MailingLists for the sign-up address
+ http://wiki.apache.org/spamassassin/MailingLists for the sign-up address and a link to the
archive of past messages.
- and a link to the archive of past messages.
  
  Much more info is at http://wiki.apache.org/spamassassin/
  
@@ -263, +259 @@

  
  There are some tests and code in SpamAssassin that are turned off by
  default: experimental code, slow code, or code that depends on
- non-open-source software or services that are not always free.  These
+ non-open-source software or services that are not always free.  These disabled tests include:
- disabled tests include:
  
    - DCC: depends on non-open-source software (disabled in init.pre)
    - DomainKeys: experimental (disabled in init.pre)
@@ -273, +268 @@

    - Razor2: depends on service that is not always free (disabled in init.pre)
    - TextCat: slow (disabled in init.pre)
  
+ To turn on tests disabled in 50_scores.cf, simply assign them a non-zero score, e.g. by
adding score lines to your ~/.spamassassin/user_prefs file.
- To turn on tests disabled in 50_scores.cf, simply assign them a non-zero
- score, e.g. by adding score lines to your ~/.spamassassin/user_prefs file.
  
  To turn on tests disabled by commenting out the required plugin in
+ init.pre, you need to uncomment the loadplugin line and make sure the prerequisites for
proper operation of the plugin are present.
- init.pre, you need to uncomment the loadplugin line and make sure the
- prerequisites for proper operation of the plugin are present.
  
  
  Automatic Whitelist System
  --------------------------
  
+ SpamAssassin includes automatic whitelisting; The current iteration is considerably more
complex than the original version.  The way it works is by tracking for each sender address
the average score of messages so far seen from there.  Then, it combines this long-term average
score for the sender with the score for the particular message being evaluated, after all
other rules have been applied.
- SpamAssassin includes automatic whitelisting; The current iteration is
- considerably more complex than the original version.  The way it works is
- by tracking for each sender address the average score of messages so far
- seen from there.  Then, it combines this long-term average score for the
- sender with the score for the particular message being evaluated, after
- all other rules have been applied.
  
- This functionality is on by default, and is enabled or disabled with the
+ This functionality is on by default, and is enabled or disabled with the "use_auto_whitelist"
option.
- "use_auto_whitelist" option.
  
  A system-wide auto-whitelist can be used, by setting the
- auto_whitelist_path and auto_whitelist_file_mode configuration commands
+ auto_whitelist_path and auto_whitelist_file_mode configuration commands appropriately, e.g.
- appropriately, e.g.
  
      auto_whitelist_path        /var/spool/spamassassin/auto-whitelist
      auto_whitelist_file_mode   0666
  
+ The spamassassin -W and -R command line flags provide an API to add and remove entries 'manually',
if you so desire.  They operate based on an input mail message, to allow them to be set up
as aliases which users can simply forward their mails to.  See the spamassassin manual page
for more details.
- The spamassassin -W and -R command line flags provide an API to add and
- remove entries 'manually', if you so desire.  They operate based on an
- input mail message, to allow them to be set up as aliases which users can
- simply forward their mails to.  See the spamassassin manual page for more
- details.
  
  The default address-list implementation,
  Mail::SpamAssassin::DBBasedAddrList, uses Berkeley DB files to store

Mime
View raw message