Outbound email Diagnostics

[Shal Jain <sh...@intertechsys.com>]

James ver: 2.0a2
OS:  Win2K Server

This past sat/sun, a whole bunch of outbound emails never got delivered.  I havent' found any thing that stands out in the logs (not to say there isn't - the logs are large)
but the emails just sat there.  I moved them out of the outgoing folder and then try to put them back in there one at a time (properly paired FILESTREAMSTORE, FILEOBJECTSTORE files), but the email wouldn't be processed.
I did notice there were a couple of 0 byte files and I deleted those but the rest of the emails didn't get processed.
What should I look for in the logs that will indicate that these emails didn't get processed.

My users have some fairly serious legal liabilites if these emails don't get processed.  I need to guarantee my users that James tried to deliver these emails. Its not a problem if the
destination mail server is not responding, because James deals with that adequately.

I currently have a monitor that will alert me if the var\mail\outgoing folder accumulates files that don't disappear after a while.  Is there a better mechansim to do so.
What do other folks do regarding monitoring James's health. ?
Should I setup a custom mailet that will get called as the last step in any outbound email processing.  That mailet can atleast log that the email was handled by James ?

I believe the 0 byte file being created is an issue w/ the version of James I'm using - something to do with retries and overwriting a file. 
Has this problem been fixed in 2.0a3 or is it only 2.1a1 ?

I hesitate to upgrade to 2.1a1 until its been marked as released.

I'd appreciate any feedback 
-shal