Qmail-LDAP
[Top] [All Lists]

Re: poll: spam filtering per-user

To: qmail-ldap@qmail-ldap.org
Subject: Re: poll: spam filtering per-user
From: Toni Mueller <support@oeko.net>
Date: Fri, 4 May 2007 12:40:27 +0200
Delivered-to: sp-com-lists@consult.net
Delivered-to: qmail-ldap-list@securepoint.com
Delivered-to: mailing list qmail-ldap@qmail-ldap.org
In-reply-to: <46388D5E.60301@paranacidade.org.br>
Mailing-list: contact qmail-ldap-help@qmail-ldap.org; run by ezmlm
References: <20070502093717.7146.qmail@oak.oeko.net> <463867F3.1070905@fct.unl.pt> <46388D5E.60301@paranacidade.org.br>
User-agent: Mutt/1.5.4i
Hi,

On Wed, 02.05.2007 at 10:08:46 -0300, Felipe Augusto van de Wiel 
<felipe@paranacidade.org.br> wrote:
>       Toni, SpamAssassin is able to save preferences and user
> options in the LDAP, that could help you.

thanks for the hint, but last I looked, the LDAP functionality in SA
was far behind the SQL functionality, and it still couldn't be removed
from the message path. As far as said client puts it, he views that as
a legal oblication on his part.

> The other thing, using simscan you can enable/disable SPAM or Virus
> checking on a per-email basis using ~qmail/control/simcontrol.

Thanks, I'll probably have a look at simscan, too, BUT:

Opening another can of worms in terms of separate configuration is
exactly what I want to avoid. Ie, having LDAP and then not using it is
a very much broken idea, imho.

>       I'm using qmail-ldap + simscan + spamassassin + clamav on
> a Debian Sarge (3.1) machine,

I usually use qmail-ldap + qmail-scanner + spamassassin + clamav on
Debian or OpenBSD and filter incoming emails. Only that qmail-scanner
is a hack which doesn't let me easily apply individual filter
configurations (eg. no virus checking for this user, different spam
checking (not only different options, I already know spamc's '-u'
option) for that user etc.pp.) to individual mails. Also, per-user
based checking is difficult when receiving the email because all
recipients get the same filter set and results due to the way it has to
work.


Best,
--Toni++


<Prev in Thread] Current Thread [Next in Thread>