12.2. Configuration

The interface for this option is conceptually the same as the described in the sections "Custom Article Filtering" and "Faster Spam filtering with Cyclone". The main difference is that rather than using software command line options, you instead use software configuration directives to configure per feed filtering.

This option is illustrated below, which also introduces the per feed directives.

Example of a feed article using the non-shared memory API, using all per feed filtering options (as described in the "Configurations Directives Section").

<Feed>
        IncomingFeedName   feed_name1
        FilterProgram   ../spam_filters/cleanfeed
        FilterProgramBody true
        FilterProgramMultiFilter 3
</Feed>

Example of a feed article using the shared memory API, using all per feed filtering options (as described in the "Configurations Directives Section").

<Feed>
        IncomingFeedName   feed_name2
        FilterProgram   ../spam_filters/fast-filter-sample.pl
        FilterProgramFastFilterKey 100
        FilterProgramBody true
        FilterProgramMultiFilter 5
</Feed>

Various combinations of per feed filtering are supported. For example, you can configure one feed to do shared memory API filtering, and another feed to do non-shared memory API filtering. You can configure multiple feeds to use the same filter program, and other feeds to share a different filter program.

In addition, you can configure a single Cyclone server wide filter program (as described in the previous sections using command start options), and have one or more feeds use a different program. Something like this may be desirable if you want all feeds, except for one, or a few, to use the same filtering programs. The ones you configure per feed would then "over ride" the one configured for the server wide Cyclone.