Yes, Sandy's solution would be the best in a large installation if you
wanted to limit this.
Personally I have found that a large majority of my customers keep their
default settings enabled, and this is every 30 minutes in Outlook
Express, every 5 minutes in Outlook, and every 10 minutes in Thunderbird
if I recall correctly. Having a few do it once a minute doesn't cause
any difficulties. Having many hundreds doing it every minute though could.
I'm not in the business of providing bulk-hosting and generic E-mail
services, and everything that comes along with that such as script
kiddies and people with massive MP3 libraries that eat up bandwidth for
pennies on the dollar. I provide true value-added business-class
services, and I believe it is my job to provide for any and all
reasonable business use, custom or otherwise, and maintain a high QoS.
So my choice in not worrying about checking frequency until it presents
a big load issue makes sense in my environment. If I was an ISP with
10,000+ mostly residential accounts on one server, I would probably
approach this differently. I don't have any domains that are
excessively large, so when my server runs out of capacity, I can add
another box with ease. I may never get to that point. If I do, I'll be
swimming in cash :)
As far as delaying E-mail for spam control, I have opted to avoid
greylisting thus far despite having the capabilities of doing so because
of QoS concerns. I don't want to be delaying someone's legitimate
E-mail for up to an hour or more as a method of spam prevention.
However, if this can be done selectively to only suspicious hosts based
on tight criteria, it can be a big benefit to a system with very limited
impact on legitimate use.
Matt
Nick Hayer wrote:
Email is not instant messaging - and that is the point. In reality as
many have pointed out if email could be _delayed_ it would sure help
with spam control - but that is a different subject.
Thanks all for the ideas, I think Sandy's post makes the most sense in
my world - "the best idea isn't to tell them there's a limit, but
simply to bit-bucket any requests that come in under your threshold"
It would be transparent to the users and accomplish my goal. Now if
I could just do it! ;)
Thanks again
-Nick
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive:
http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
