Re: [Evolution] Query: spam filter for use with Evolution in a Fedora Core 5 environment

[Marc Schwartz <MSchwartz mn rr com>]

Jeffrey Stedfast wrote:
> the only spam filter we ship is the SpamAssassin spam filter. any others
> are added by the distro maintainers and so you'd have to ask them.
>
> On Thu, 2006-05-25 at 03:10 -0700, H.M. Gladney wrote:
> >  Please, what is the recommended spam filter for use with Evolution in 
> > a Fedora Core 5 environment?

There are additional tools that will work with SA to enhance it's 
functionality.

These include RBL's (ie. SpamCop), Razor, Pyzor and DCC and constitute 
what are known as "remote tests" since they require online access to the 
aforementioned services to compare an inbound e-mail to known spam. 
Thus, they do tend to add to the overhead of scanning e-mails.

Note that:

1. In SA 3.1, which is what FC5 is using, DCC and Razor are disabled by 
default. They need to be enabled in /etc/mail/spamassassin/v310.pre and 
appropriate settings configured in ~/.spamassassin/user_prefs. You will 
also have to adjust iptables settings to permit such access through the 
firewall.

2. There are RPMs in Fedora Extras for Pyzor and Razor, but DCC needs to 
be downloaded from their web site and installed manually. The RBL 
functionality is done via the SA user_prefs file settings.

3. There are substantial issues with some of the remote tests, at least 
when run via a procmail recipe when SELinux is running on FC5 in 
Enforcing mode.  I am in the midst of lengthy exchanges with Paul 
Howarth on the FC SELinux list to work through resolving these. Most 
have to do with the current default SELinux policies for DCC and Razor 
and security context labelling for the involved files and processes. 
procmail and postfix policies also appear to be involved here.

Thus, if you are running FC5 with SELinux in Enforcing mode, which is 
the default on FC5 now, I would stick with just running SA and wait 
until we make more progress on the other tools.

SA can be enabled via both the Evolution Plug-In Manager AND the 
Preferences Menu.

Otherwise, you will want to drop SELinux to Permissive mode to let the 
other remote tools run in the mean time if you want them.

HTH,

Marc Schwartz