OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: mail flow architecture

From: Barbara M. (barbararfx.it)
Date: Wed Mar 12 2008 - 14:04:26 CDT


On Wed, 12 Mar 2008, Ralf Hildebrandt wrote:

> * Barbara M. <barbararfx.it>:
>>
>> This is the situation:
>>
>>
>> Internet
>> |
>> |
>> | (a.b.c.d)
>> FW
>> | (192.168.1.1)
>> |
>> |
>> SWITCH (DMZ)
>> |
>> |
>> |-SMTP-IN (192.168.1.2) (Postfix 2.1.x, spamassassin, clamav, sqlgrey)
>
> Use amavisd-new with spamassassin+clamav
> Use policyd-weight instead of RBLs

policyd-weight seems dead ;-)
policyd old
policyd V2 seems in alpha stage

>> |
>> |-MAIL (192.168.1.3) (Postfix 2.1.x, dovecot, procmail)
>
> Why not use sieve instead? Much better than procmail, since dovecot's
> deliver speaks sieve AND will update the index files in the users'
> mailboxes.

Because this are old servers that have over 3.000 active users over
2.000 domains, mostly with personalized procmail filters/settings ... :-(

>> |
>> |-SMTP-OUT (192.168.1.4) (Postfix 2.1.x, spamassassin, clamav)
>
> Same here: amavisd-new with spamassassin + clamav

As I say, Our FIRTS need is:
- some hints for using RBL "safely" (NO great chances of experiments in
production box). Or any other way to limit the incoming mail traffic, but
simple to implement because the server is old and busy ...

NEXT:

- hints/links/config-examples to build new box that replace our SMTP-IN
(and the others boxes including the list-server)

Regards, B.