> The big problem with declude is the spam is still tying up resources - in
fact it ties up a little
> more with declude. When I used slmail - it had realtime blackhole and
just killed the mail
> at the point of entry. Sorry but that's my big problem with declude.
Well, the real question is: Do you receive enough incoming spam that you
need a new mail server?
If so, you're probably going to need another server in front, such as Len's
IMGate solution.
If not, there should be no problem running Declude, as the incoming spam can
be deleted/held rather than delivered, saving a lot of processing time. We
haven't encountered any situations where the resources were an issue (even
on 100,000+ E-mails/day systems).
We are looking into ways to offer a "REJECT" action, which will stop the
mail while it is being delivered, which minimizes resource usage as you
mentioned. But, it requires extra overhead -- either intercepting port 25
and communicating with IMail on a different port, or a LSP that Winsock2
allows. But, there is very little documentation on LSP and the overhead
needed to use it. The program we are working on to stop dictionary attacks
intercepts port 25, and doesn't appear to be very resource intensive, but
haven't done any stress testing on it yet. If that works well, we may use
the same technique for Declude JunkMail.
-Scott
Declude: Anti-spam and Anti-virus solutions for IMail.
http://www.declude.com
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/
