> Yet, I am still concerned. I have tried the "tips" Len indicated, but
> there seems no way to really isolate an internal spammer without
> added equipment, cost, or labor.
That is correct.
> This should not be such a "drudgery" process.
That, too, is correct. There shouldn't be any spam. But, life isn't that simple.
> Could not a "patch" be developed to alert Host Managers of
> the "symptoms" occuring with an internal subscriber who is
> likely spamming -- and taking bandwidth in the process.
Certainly. But at a cost. If IMail adds such functionality, it's going to cost them
money, just as it cost us money to develop it for our Declude JunkMail product.
Determining a "likely spammer" isn't an easy task. If someone sends out 1,000 E-mails
in a minute, they are a likely spammer, right? Not necessarily -- it could just be a
mailing list. Scan the E-mail to see if it is similar to spam? That's a very
difficult and time consuming task.
Then, you have to realize that Ipswitch must take demand into consideration. There
are certainly quite a few people who would appreciate such a feature and some might
pay more for it. But, there are also lots of people who have closed relays and can
trust (or track down if need be) their customers/users/employees.
--
-Scott
Declude: Anti-virus and Anti-spam 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/
