diff options
author | Vsevolod Stakhov <vsevolod@highsecure.ru> | 2015-04-28 18:59:30 +0100 |
---|---|---|
committer | Vsevolod Stakhov <vsevolod@highsecure.ru> | 2015-04-28 18:59:30 +0100 |
commit | de2d8b59458719c77976db16292956e85d59c265 (patch) | |
tree | 3452243dbcd21b2f4d26b7cd30059cbca7a4dd9d /doc | |
parent | 6aa19ec1d89b5fd93c74347c74186aedde101d4c (diff) | |
download | rspamd-de2d8b59458719c77976db16292956e85d59c265.tar.gz rspamd-de2d8b59458719c77976db16292956e85d59c265.zip |
Add spamassassin module documentation.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/markdown/modules/spamassassin.md | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/doc/markdown/modules/spamassassin.md b/doc/markdown/modules/spamassassin.md new file mode 100644 index 000000000..ce3eae877 --- /dev/null +++ b/doc/markdown/modules/spamassassin.md @@ -0,0 +1,63 @@ +# Spamassassin rules module + +This module is designed to read and adopt spamassassin rules for rspamd. + +## Overview + +Spamassassin provides an excellent set of rules that are useful in some relatively +low volume environments. The goal of this plugin is to re-use the existing set +of spamassassin rules natively within rspamd. The configuration of this plugin +is very simple: just glue all your SA rules into a single file and feed it to +spamassassin module: + +~~~nginx +spamassassin { + ruleset = "/path/to/file"; +} +~~~ + +Rspamd can read multiple files containing SA rules, however it doesn't support +glob patterns so far. All rules are parsed to the same structure, so individual +rules might be overwritten if they occurs in multiple times. + +## Limitations and principles of work + +Rspamd tries to optimize SA rules quite aggressively. Some of that optimizations +are described in the following [presentation](http://highsecure.ru/ast-rspamd.pdf). +To achieve this goal, rspamd counts all rules as `expression atoms`. Meta rules are +**real** rspamd rules that can have their symbol and score. Other rules are normally +hidden. However, it is possible to specify some minimum score that is needed for a rule +to be treated as normal rule: + + alpha = 0.1 + +With this setting in `spamassassin` section, all rules whose scores are higher than +`0.1` are treated not as atoms but as the complete rules and evaluated accordingly. + +Currently, rspamd supports the following functions: + +* body, rawbody, meta, header, uri and other rules +* some header functions, such as `exists` +* some eval functions +* some plugins: + - Mail::SpamAssassin::Plugin::FreeMail + - Mail::SpamAssassin::Plugin::HeaderEval + - Mail::SpamAssassin::Plugin::ReplaceTags + +Rspamd does **not** support network plugins, HTML plugins and some other plugins. +This is planned for the next releases of rspamd. + +Nevertheless, the vast majority of spamassassin rules can work in rspamd making +the migration process much smoother for those who decide to replace SA with rspamd. + +The overall performance of rspamd, of course, goes down since SA rules contain a lot +of inefficient regular expressions that scan large text bodies. However, the optimizations +performed by rspamd can significantly reduce the amount of work required to process +SA rules. Moreover, if your PCRE library is built with JIT support, rspamd can benefit +from this by a significant grade. On start, rspamd tells if it can use JIT compilation and +warns if it cannot. + +Spamassassin plugin is written in lua with many functional elements. Hence, to speed +it up you might want to build rspamd with [luajit](http://luajit.org) that performs +blazingly fast and is almost as fast as plain C. Luajit is enabled by default since +rspamd 0.9.
\ No newline at end of file |