You could log errors into a database table and have a scheduled task E-mail them out in a controlled way. I find it helps to send errors to a dedicated error E-mail account so my real accounts do not get flooded when something bad happens.
-Mike Chabot On 7/17/06, Scott Newsome <[EMAIL PROTECTED]> wrote: > Thanks in advance for any assistance. > > I am researching away to throttle the creation of email messages used to > notify system admins when ColdFusion throws an error. We have had a problem > of over-loading our exchange server when there is a database failure or some > other error that effects a lot of users and our current error handling > solution starts sending out cfmail by the hundreds or thousands. Does any > one or has anyone handled a similar problem? If so, would you mind sharing > your solution? > > > Regards, > > > > Scott Newsome > > The Seattle Times > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/cf_lists/message.cfm/forumid:4/messageid:246759 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
