Re: simscan/spamc with per-user spam config stored in ldap

Hugo Monteiro <[email protected]> Tue, 12 Jul 2011 23:47:53 +0100
Newsgroups gmane.mail.qmail.ldap
Message-ID <[email protected]>
On 07/12/2011 09:59 PM, Bob Miller wrote:
> To the whole list this time...
>
> Hi Hugo,
> Thank you for your reply
>>> So, having read a great deal of this mailing list's archives, I did
> not
>>> find any solutions suggested.  But I have come to realize that there
> is
>>> more than one genius on this list.  Hopefully one of you has run
> across
>>> this already and would share your approach to this problem...
>>>
>> Hello Bob,
>>
>> What are you going to do with the messages that are flagged as spam?
>> Reject them at smtp talk time or just tag them (subject/message
> headers)
>> and let the user decide what to do with them?
> The way I do it on my current (non-ldap) servers is to tag anything with
> a score between 5 and 10 and let it pass, and immediately reject
> anything with score over 10, with no per-user config.  For a global
> config, this has been working very well for me for several years, so I
> would like to model this system based on that.  But as the range of
> users on my systems increase, so does the need for some people to be
> able to adjust their score threshold up or down.  If I need to rethink
> the way I am doing things now in order to accomplish the goal, I am okay
> with that...
>
>


Have you considered DSPAM instead of spamassassin? I don't know 
spamassassin that well, but i'm aware that DSPAM is highly configurable, 
supports per user settings, including separate spam dictionaries, 
quarantine, etc ... and it's highly accurate if configured/trained right 
and it's FAST. I would also advise you to setup your content scanning 
(spamc, dspam, etc) at the delivery time, and not at message acceptance. 
For that particular stage i would advise other tools such as early 
talker disconnection, greylisting and helo checking, or even rbls if 
that rocks your boat.
Content analysis is usually a costly operation and can lead to false 
timouts, when accepting mail, making the remote server retry the 
delivery and causing duplicate message delivery. That said, IMHO i would 
leave simscan to work with clamav only and handle spam later in the process.

Although it's a bit out date, you could take some ideas from a web page 
where i explain a possible setup.

http://hmonteiro.net/howtos/qmail-ldap/start

That link is for an empty page, but it will show you 4 sub pages on the 
left menu regarding several aspects i talk about above. By no means 
that's the only way to setup things, nor it's the best in every case, 
but i'm sure it will give you a couple of ideas to work on.

Regards,

Hugo Monteiro.

-- 
fct.unl.pt:~# cat .signature

Hugo Monteiro
Email	 : [email protected]
Telefone : +351 212948300 Ext.15307
Web      : http://hmonteiro.net

Divisão de Informática
Faculdade de Ciências e Tecnologia da
		   Universidade Nova de Lisboa
Quinta da Torre   2829-516 Caparica   Portugal
Telefone: +351 212948596   Fax: +351 212948548
www.fct.unl.pt                [email protected]

fct.unl.pt:~# _