[Kroupware] HOWTO: amavisd-new, spam assassin, sophos

[Ivaylo Toshev]

In my humble opinion, the right way to do SMTP filtering, access-control
and eventually load-balancing is to use SMTP Relay Gateway. So, for
example:

[INTERNET] <-> [ Firewall with SMTP Relay] -> [DMZ with KOLAB Server]

And if one use this schema , then he can use Sendmail as SMTP Relay +
MailScanner.


На ?, 2003-07-21 в 18:58, Jon Bendtsen записа:
> Jason A. Pattie wrote:
> > It is more efficient and safer than having the MTA delivering through 
> > SMTP/LMTP, like amavisd does.  Mailscanner does not want to be an MTA.  
> > It reads a file, processes it, and only deletes it from the incoming 
> > queue after it successfully writes it to the outgoing queue.  This way 
> > it never loses an e-mail.  Since it is not involved in the getting or 
> > sending of the e-mails, it cannot lose e-mail that way, either.  It 
> > supports more MTAs than amavisd does.
> > 
> > Setting up MailScanner is easier because you don't have to configure the 
> > MTA to know about MailScanner.  You don't have to touch any 
> > configuration files for your MTA to use MailScanner.  MailScanner takes 
> > care of starting the instances it needs.  Also, you don't have to 
> > reconfigure your delivery agent.  As long as you don't have your MTA 
> > starting automatically, MailScanner takes care of properly starting the 
> > incoming and outgoing MTA instances using command line arguments to 
> > configure them.
> 
> This sounds much more like how i want it done. Does the default 
> MailScanner documentation work for the kolab postfix ?
> 
> 
> 
> JonB
> 
> _______________________________________________
> Kroupware mailing list
> Kroupware at mail.kde.org
> http://mail.kde.org/mailman/listinfo/kroupware