The following is strictly to represent the scenario - Goal: Replacing our Windows based filter (if you could call it
that) that is using a program named Mail Essentials. It does not provide anywhere near the
throughput we need (~120/min) and I have been hoping to show our IT director it
is time to switch to *nix based solutions on the back end. Currently we are processing our mail as such: Several of our domain mx records
all point to our "Traffic Cop" - it then directs between 2 of our
Mail Essentials machines - on to our virus scanning machine - then to
our primary Exchange server. Internet -> "MX traffic cop" -> "ME1"
or "ME2" (aka. Horribly slow and inefficient
content filters) -> Antivirus -> Exchange ______________________________________________________ I have set up a Suse 7.3 machine
and basically at this point need to know what components I am going to need -
I'm not looking for a detailed how-to, just more along the lines of "this
connects to this which connects to this and outputs to this" This is what I have been trying, without much luck, and I'm
sure I'm barking up the wrong tree now Smptd (receive mail
from our mx gateway) -> procmail
(to run spamc/spamassassin -p) -> sendmail(?)
to forward through to our Antivirus server Again, I apologize for being a newbie in regards to this,
and I'm not looking for a handout - aside from knowing which
components I'll need, from that point I have no problem reading man pages
until my eyes bleed. Any other
advice that can be given will be greatly appreciated, and when I'm done I
will provide a write-up of my experience to share with others that may have the
same problem. |
- Re: [SAtalk] Just what you never wanted - another n... Harlan Limajliew - MIS
- Re: [SAtalk] Just what you never wanted - anot... mis
- Re: [SAtalk] Just what you never wanted - anot... Jan Schreckenbach
- [SAtalk] Just what you never wanted - another ... Quentin Krengel