Way ahead of you Gavin. Problem is, a bunch of stuff always gets bounced in there when users enter the incorrect mail address, or let their cat walk on the keyboard or whatever it is that users do, so it might be necessary to also open up the cfmail files in the undelivr directory and check for the appropriate error message.
I guess you could add functionality to have it dump any bounced "connect refused" messages into the mapped spool directory of an alternate server (that points at an alternate mail server..we have plenty of redundant machines). I normally notify myself of stuff by cfexecuting a net send. SMS would be better, but it's not a go at the moment. Your idea of a CFC is a good one except I don't normally run a local copy of CF. Guess I could publish it as XML and grab it with my feed reader or something --- You are currently subscribed to cfaussie as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED] Aussie Macromedia Developers: http://lists.daemon.com.au/
