The long version: .NET framework has a bug that they have been promising to fix for 3 years now. The bug is - the .NET Framework's SmtpClient class never closes its connection to the SMTP-server. After hours of email-intensive work your server has thousands of open TCP-connections to the email server. That leads to another problem called "too many open connections" causing your server to response slowly. The workaround is to lower the idle timeout for the connection so it closes automatically. But the workaround sometimes does not work if the timeout is configured BEFORE you set up a host for the SmtpObject...
Anyway. Our server has stopped sending out email notifications. We have not tested the "workaround" before deploying it to our server.
Now Patrick McKenzie has a great list of standard industry responses to outages:
- "Outage? What outage?"
- "Please see our status page, which we’ve conveniently located in electronic Siberia."
- "ATTENTION ALL USERS! 0.7% of you were affected by some very serious sounding things yesterday! Please be worried unnecessarily even if you weren’t affected, and swamp our support line, who we will provide no effective tools to tell you whether you’ve been affected or not!"
We admit the error and apologize to you. Sorry. We screwed up. But we're still here to help in case you need us.