Declude and IMGate are not mutually exclusive.
One Declude customer came to me to install IMGate because at 30K mgs/day,
on his particular IMail box, there weren�t enough mips to go around. His
Imail box was very sluggish, Webmail a syrupy pain, Imail queue way too big.
So he wanted to off load as much as possible from Imail/Declude to IMgate,
with no intention of dropping Declude with which he was/is afaik as
sastisfied as other users, and no desire to move his IMail/declude box to a
more powerful box.
Fast forward to climax: he�s happy with the combo, as I predicted when he
came to me. His Imail/Declude box is zippy again.
>The above may seem anti-IMGate, but it's not. Some IMGate advantages:
>
>1: Processing is offloaded from the iMail box. If the IMail box is already
>stressed, Declude might be too much for it. Declude is actually very
>efficient, but if the box is already being pushed...
this was exactly the case above.
>2: Even though there is a bit more of a learning curve, once mastered you can
>drop in as many IMGates as you want/need with minimal cost.
>
>3: IMGate would supply a secondary MX for mail queuing and relay if your
>Declude box is down.
IMGate, by rejecting 20% to 30% of all incoming mail, precludes Declude�s
having to scan that 20% to 30%, freeing up Declude for the real nasty stuff.
>4: IMGate can drop the spam sooner in some instances. Declude works off the
>queue files, which means the server has already received the spam, but Declude
>stops it before it can get to your user's mailbox or be relayed back out.
>IMGate can look at the RBL/Orbs type lists and drop some connections before
>the message is received.
Not just MAPS, but SMTP protocol violations (esp unauthorized SMTP command
pipelining used by harvesters), ip subnet blocking, max message size
enforcement, DNS validations of mail servers and envelope headers,
single-point global RegEx filtering on headers and body (catch
viruses/worms with the non-AV IMGate), IMGate bounces msgs to unknown users
before IMail has to, off-loading of all authorized relaying and ETRN from
IMail.
If Imail�s list manager is sufficient but Imail�s queue processing and list
delivery isn�t (as we see repeatedly on this smallish but active list),
then IMGate will also solve your IMail list delivery pb�s and for much
greater volumes than this list sees.
Some people think erroneously that IMGate requires them to be a veteran
*nix sysadmin, but the vast majority of IMGate admins have had only Win32
admin experience, and get along just fine with building their own IMGate
machines. Others ask me to build IMGate and put it into production, and
then they get along fine with just operating it. They often go on to build
their 2nd, etc machines themselves.
Len
http://MenAndMice.com/DNS-training
http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K
http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
An Archive of this list is available at:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
