>We have multiple web servers (as a hosting company).
>
>1. Each web server runs it's own (Microsoft IIS) smtp server to relay mail
>generated by web sites. This mail is usually feeding to their accounts on
>the iMail server. Running everything through a central smtp relay server
>would create a "single point of failure" that would not be acceptable from
>our point of view.
>
>2. Some customers using mail components (ASPMail, SmartMail, DMail, etc) are
>delivering mail straight to the iMail server from their web site,
>generating mail from various Class B's and C's.
In this case, you can just use the whitelist to accomplish this (IE
"WHITELIST IP 192.168.112.0/24"). Unless there are MX records pointing to
these servers, spammers won't be sending mail to them, so you wouldn't need
to scan the E-mail.
>(Our big issue is Declude scanning every piece of mail when we only junk
>mail scan for 2% of our customers. The processing load would seem to be 50
>times higher then necessary.)
True, but the processing load for Declude JunkMail is quite low (compared
to Declude Virus, which uses a lot of CPU time for E-mails that are scanned).
-Scott
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". You can E-mail
[EMAIL PROTECTED] for assistance. You can visit our web
site at http://www.declude.com .
