(doh, forgot to set my alias... again.  Apologies for any duplicates).

I suggest looking at Zimbra Community Edition for the entire setup.  

Under the very accessible hood it uses postfix, openldap, spamassasin, clamav 
and the like. They also include DSPAM though disabled by default.

If you don't want to do a lot of customization, you can literally just run the 
install script, configure your domains and be done.  If you want to add all 
types of bells and whistles to postfix or any of the other components you can 
do that too, without much hassle.

Their wiki (wiki.zimbra.com) has a lot of customizations people of have done 
over the years. For example: 
http://wiki.zimbra.com/wiki/Improving_Anti-spam_system which includes info 
about adding Pyzor and Razor.   

The only annoying part of this is, any configuration you do to their 
configuration templates will be replaced blindly during an upgrade.  However 
it's easy enough to backup those files and diff them after the upgrade.  I do 
that at work for a few settings and domain white listing in spamassasin.

Since you host multiple domains, if you want, there is a way to delegate admin 
access to people for just their objects (user accounts, distribution lists, 
etc).  You can give them access over their entire domain, just enough access to 
their individual user account definition and anything in between.

I run the Community edition at $HOME (with Linode), and the Network Edition @ 
$WORK. I honestly don't see myself going back to running the individual 
components manually ever again after working with Zimbra.

Version 7 is in beta now and should see release within the next month or two. 

I'd be happy to answer any questions.  Helps me finish my zimbra talk for the 
upcoming lug meeting :) .  (I would still recommend Zimbra even if I wasn't 
giving a talk on it)

Damion
 

----- Original Message -----
> I'm researching a new build of my mailserver. I'd like to figure out
> what's the best option for dealing w/ Antispam / AV, as well as the
> other processes..
> 
> I know of 2 major choices- do it your self, or outsource. I'm not
> looking to outsource the entire thing, though.. just AV/AS.
> 
> 1. Outsource: Postini, or other providers. I'm open to suggestions -
> do people like them? Do they price based on inbound address, or
> domain, or volume?
> (I've got very few actual addresses, but that's mostly because there
> are a bunch of aliases. Aliases will likely show up as email addresses
> to them, though.)
> 
> There are 2 non-profits being hosted, which might make it easier to
> justify going outside, if there are discounts for them.
> 
> 
> 2. Do it myself. I'm fairly happy to do it myself, and will need most
> of it anyways - but am trying to figure out which policy daemon to use
> for postfix. Have people started using the multi instance postfix
> support? Milters? or just use amavisd-new, etc. Or maybe Mailscanner..
> 
> I suspect that dovecot is the way I'll go, just for a change from
> Courier on the old server.
> 
> 
> Yes, it's somewhat silly to do this myself. But I can't go ahead and
> keep up w/ the tech for mailservers at work if I don't keep running
> one at home. Plus I host a few other domains for friends, and
> nonprofits. We would likely use Postini for mail at work, so it's not
> so bad to use it at "home"..
> 
> 
> Matthew
> 
> _______________________________________________
> Tech mailing list
> Tech@lists.lopsa.org
> https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
> This list provided by the League of Professional System Administrators
> http://lopsa.org/
_______________________________________________
Tech mailing list
Tech@lists.lopsa.org
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to