13 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Spam Filtering & ...
FromSent OnAttachments
Lisa MuirFeb 6, 2007 3:34 am 
Harry DuncanFeb 6, 2007 6:48 am 
Lisa MuirFeb 6, 2007 8:32 am 
Peter FordFeb 6, 2007 9:18 am 
Vini EngelFeb 6, 2007 4:21 pm 
Lisa MuirFeb 7, 2007 4:19 am 
"Schalk W. Cronjé"Feb 7, 2007 5:16 am 
Lisa MuirFeb 7, 2007 7:07 am 
Harry DuncanFeb 7, 2007 7:14 am 
"Schalk W. Cronjé"Feb 7, 2007 9:11 am 
Harry DuncanFeb 7, 2007 9:41 am 
Sergiy ZhukFeb 7, 2007 10:31 am 
Bill MerriamFeb 8, 2007 4:03 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Spam Filtering & CourierActions...
From:Lisa Muir (34.2@gmail.com)
Date:Feb 7, 2007 4:19:33 am
List:net.sourceforge.lists.courier-users

On 2/7/07, Vini Engel <vi@fugspbr.org> wrote:

Hi Lisa,

I would like to perform spam and virus filtering using a combination of Mailscanner, Spamassassin and ClamAV.

I had originally intended building a scanning gateway, but having read the archives here I don't think this is a good idea.

In my opinion if you have a very high volume of messages it is a good way to go. You could for example centralise your user database and use LDAP to connect the various components of your email "cluster." This way you can distribute the load across as many servers as you need and with courier it is very easy to implement as the LDAP support in courier is *excellent*.

So if you do have a very high volume of emails do consider building a scanning gateway.

The gateway approach appeals to me on more grounds than just scalability, because I'm migrating the mailserver from a postfix/cyrus setup to courier, and I can use the gateway to cleanly decommission the old mailserver too.

There is just a backscatter risk to avoid, eg, if the mailserver is down, make sure that the gateway actually queue's the messages if it accepts them.

The maildroprc given here doesn't make any sense to me at all.

What doesn't make sense there? The way he calls spamassassin seems pretty normal to me. You can use xfilter to call an external program and then you can do further processing on the message based on the score. I put the messages with score higher than 6.5 in a folder called spam. Messages on this folder expire in fifteen days.

I was looking for a hand off to spamassassin and a re-entry to courier / maildrop. Too much reading into mailscanner I'm afraid, makes perfect sense now.

2) Archive spam on the other machine for release 3) Automatically return what is determined to be ham back to courier.

You can use DSPAM to do what you want as well, it is pretty good. I am implementing it at the moment, it has quarantine.

Is there documentation that someone could point me to for this, or a setup that I can research. I'm getting nowhere with google apart from the above link but its more like a recipe that I won't understand than a documented approach.

If you read Courier's documentation and DSPAM's and learn LDAP if you haven't yet you will get enough background to do what you want.

I'm well in touch with ldap and ldap admin. This DSPAM looks like a much better solution than mailscanner even if it doesn't handle blacklists and virus scanning, but i can fill those two gaps easily enough myself directly with courier, and DSPAM works with courier, so i can make my gateway with courier and drop postfix.

Many thanks for the heads up on this!

Lisa.