Fortunately the cure for #3 is pretty easy, or at least it was for me... Advise clients that your systems are not development or experiment servers, they are production servers, and they are shared, and anything they put up there must be tested outside of that environment, like on their own test network, or on a test server you'll be glad to rent them time on by appointment. With that said, if they crash your systems you send them a bill, fat enough to compensate all the other customers that suffered plus your recovery time. It's not much different than digging up a power line with your backhoe - you have to pay the local power company for the repair AND the loss of revenue AND damages. Not a single one of my clients has any doubt that getting me out of bed at 3 am because they brought down one of my machines is gonna cost them dearly. I've sold them low-end test boxes and cast-offs that I've retired, and set up copies of their sites on a test server for a nominal fee that they can bang on and if they break it it's not a big deal.
Then I modified the IISHelp ASP script to toss me an email for EVERY IIS error that is tripped. You'll get a bunch in the first few days, but generally forwarding them on to your customers gets them cleaned up, and after that you can deal with the occasional mishap and your webservers and mail server will all be a lot happier. Chris ----- Original Message ----- From: Tom G To: [EMAIL PROTECTED] Sent: Thursday, May 06, 2004 5:28 PM Subject: RE: [IMail Forum] Filtering Attachs Scott: In my environment, "Joe-jobs" is a bigger problem than 1%. If someone made a product that would put a limit on incoming emails TO a single email address, or FROM a single email address, I suspect most of my server crahses would go away. Here are a few reasons for email server crash (for me anyway) 1. My email server is just too busy. This can be fixed by moving domains to other servers. 2. One of my customers tries to set up aspemail (or similar) code in their web site to scroll thru a list of email addresses and send (aspemail supports smtp auth programatically). This is rare because: A. I have imail set up to limit recipients to 100, and B, I have my customers educated that this is a "no no". 3. I have a customer who sets up his web site to email himself for whatever reason, and when his code freaks out and he sends himself 10,000 emails, my email server may crash. 4. I have a spammer spoof an email address (as John said) and I get thousands of bounce backs. Believe it or not, #3 is the most common reason my queue fills up and my phone starts ringing! # Thanks Tom >>>>>>[3] Joe-jobs. That's the final 1% of complaints. That's what you're referring to above, and nothing can stop it (although SPF can help, by blocking the spam on servers using SPF; see http://spf.pobox.com for details). The undeliverable E-mails can be handled by filters using your favorite anti-spam tool. -Scott 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/
