qmail ldap users

Hugo Monteiro | 2 May 2007 12:29

Re: poll: spam filtering per-user

Toni Mueller wrote:
> Hi,
>
> I've come to need spam-filtering to be switched on and off on a
> per-user basis. So, the alternatives seemed to be to switch to qpsmtpd
> (postponed), hack qmail-scanner to add LDAP support and then use a
> modified scheme, or utilize deliveryProgramPath after the message has
> been accepted. One of our users has this requirement for his mail
> server and argues with legal problems (German law has become very
> strict on email filtering, tagging etc.). In his case, also email
> forwarding to a different server which isn't directly on the Internet
> is a requirement. The usual message flow looks like this:
>
> Internet ->
>
>   qmail-smtpd -> qmail-local -> filter-program(s) -> qmail-remote
>   
> -> other mail server
>
> So, I hacked together a script (currently 200 lines in Python) that
> does all that, based on its command line arguments from the
> deliveryProgramPath attribute of a given user. But I don't feel too
> comfortable with it (it's _fat_ and _slow_) and wanted to know if there
> might be a simpler solution.  Filtering everything via QS (what I
> normally do, at least on our internal servers) is disallowed in this
> case.
>
> How are you solving this case?
>
> TIA!

(Continue reading)

headers

Felipe Augusto van de Wiel | 2 May 2007 15:08

Re: poll: spam filtering per-user


On 05/02/2007 07:29 AM, Hugo Monteiro wrote:
> Toni Mueller wrote:
>> Hi,
>>
>> I've come to need spam-filtering to be switched on and off on a
>> per-user basis. So, the alternatives seemed to be to switch to qpsmtpd
>> (postponed), hack qmail-scanner to add LDAP support and then use a
>> modified scheme, or utilize deliveryProgramPath after the message has
>> been accepted. One of our users has this requirement for his mail
>> server and argues with legal problems (German law has become very
>> strict on email filtering, tagging etc.). In his case, also email
>> forwarding to a different server which isn't directly on the Internet
>> is a requirement. The usual message flow looks like this:
>>
>> Internet ->
>>
>>   qmail-smtpd -> qmail-local -> filter-program(s) -> qmail-remote
>>   
>> -> other mail server
>>
>> So, I hacked together a script (currently 200 lines in Python) that
>> does all that, based on its command line arguments from the
>> deliveryProgramPath attribute of a given user. But I don't feel too
>> comfortable with it (it's _fat_ and _slow_) and wanted to know if there
>> might be a simpler solution.  Filtering everything via QS (what I
>> normally do, at least on our internal servers) is disallowed in this
>> case.
>>
>> How are you solving this case?

(Continue reading)

headers

Toni Mueller | 4 May 2007 12:40

Re: poll: spam filtering per-user

Hi,

On Wed, 02.05.2007 at 10:08:46 -0300, Felipe Augusto van de Wiel <felipe <at> 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

(Continue reading)