So, do u suggest this:

SMTP Server: Postfix
POP/IMAP Server: Courier-imap
Anti-Virus/Anti-Spam: Amavisd-new 2.2.0 w/SpamAssassin 3.0.1 & ClamAV 0.80
Webmail: SquirrelMail 1.4.3 (if needed)

And configure Postfix for DNSRBL (blocking lists). 

Do you mean to say, this should work right? I'm very curious and cautious b'cos if it works well and with stand the high-volume email load then I'm going to persuade administration here to move away from exchange :-) , this will be followed by few more exchange boxes:-)


Thank you




-----Original Message-----
From: plug-discuss-admin@lists.plug.phoenix.az.us on behalf of Darin Wayrynen
Sent: Mon 12/20/2004 2:06 PM
To: plug-discuss@lists.plug.phoenix.az.us
Subject: Re: Opinion on high-volume Email server!
 
> 
> At least one person I know has claimed good success via bogofilter for
> some high volume mail. He's also running debian.
> 
> Maybe what you can do is:
> 
> 1. reject mail for non-existant email addies
> 2. filter with bogofilter
> 3. do anti-virus checks
> 4. use spamassassin and its learning bayesian databases
> 5. deliver
> 
> I just made up that sequence, so don't be surprised if there are problems
> in getting it implemented :). I think I like it, though, so might start
> putting it in place after the holidays. Well, except 3 because I don't
> care about viruses.

[snip]

> der.hans

Adding one step before Der.hans' suggessted list above will give you
an excellent bang for your buck.  By using a carefully chosen set of
DNS real time blocking lists in step zero above you can block a
majority of the spam before it gets to the resource intensive
spamassassin.

You can either block on the initial tcp/ip connection or when
processing the first header lines.  There are advantages to both -
blocking on connect will save your system from having to process any
part of the email, but will give valid senders no reason for being
blocked (ie it's hard for them to debug), their mail will just be
returned to them days later as undelivered - while blocking during
header processing will allow your smtp server to spit back an error,
such as "1.2.3.456 blocked due to being listed in cbl.abuseat.org
which will let them seen an error immediately.

I mention careful chosen above, because you don't want to use some
Nazi organization's list where your valid email senders could get
listed but never unlisted.  You'll want to use lists that have
automated removal mechanisms so you can just tell your friends,
family, and clients to correct whatever got them listed and let
them/their ISP deal with it.  This is critical if you are dealing with
lots of volume as you will end up spending a lot of time adding
exceptions to your filters to work around broken RBLs.

Darin

ps - using bogofilter and spamassassin seems a bit redundant, but I
still do it - probably because I trained bogofilter with many gigs of
spam and ham and don't want to retrain spamassasin with the same info.  :-)
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change  you mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss