I'm running a dozen servers with postfix, amavisd-new, and sa3.0.2. I'm having 
no problems whatsoever with any aspect of the system, including BerkeleyDB.  I 
just want to throw that in to let people know it's quite possible to run a 
stable system with amavisd-new.

RO

        -----Original Message----- 
        From: Andrew Ott [mailto:[EMAIL PROTECTED] 
        Sent: Mon 1/31/2005 7:58 AM 
        To: '[EMAIL PROTECTED] Apache. Org' 
        Cc: 
        Subject: RE: [OT] Replacement for amavisd-new?
        
        

        We are moving from mailscanner to amavisd-new because of lots more
        flexibility. Currently we are running sendmail to amavisd-new to 
sendmail to
        dbmail, is working great processing about 120,000 messages a day broke 
out
        over 2 servers and a database server for dbmail.  Initially we had some
        hang-ups do to BerkeleyDB but in the new version of amavisd-new you can 
turn
        off BerkeleyDB and that solved all of the issues we were having with it.
        
        Andrew
        Action Communications
        
        -----Original Message-----
        From: Michael W Cocke [mailto:[EMAIL PROTECTED]
        Sent: Sunday, January 30, 2005 5:01 PM
        To: [EMAIL PROTECTED]
        Subject: [OT] Replacement for amavisd-new?
        
        A serious bug seems to have crept into amavis somewhere, or maybe 
BerkeleyDB
        - stability has gone to hell.  In any case, I'm starting to think about
        replacing Amavisd. I can't afford to futz around with my email server - 
it
        needs to work.
        
        Currently I run postfix, amavisd, spamassassin, clam & fprot (most 
recent
        stable versions of all).
        
        Recommendations?
        
        Thanks!
        
        Mike-
        
        --
        Mornings:  Evolution in action.  Only the grumpy will survive.
        --
        
        Please note - Due to the intense volume of spam, we have installed 
site-wide
        spam  filters at catherders.com.  If email from you bounces, try 
non-HTML,
        non-encoded, non-attachments.
        
        

Reply via email to