* Original Area: Netmail
* Original From: Scott Dudley (1:249/106.1)
* Original To  : Peter Fitzsimmons (1:259/414)

Re: Martin Pollard's message about MsgAPI messages

 PF> stupid status messages all over the place ("MsgAPI init",
"MsgAPI
 PF> terminated", "MsgAPI opened area", "MsgAPI
closed area", ad nauseum).

In normal operation, it should only print "MsgAPI init" and
"MsgAPI termination" messages.

If MsgAPI ever prints out "MsgAPI closed an open area", one of
two things has happened:

1) You have a bug in your program and forgot to close an area or message handle.

2) The user pressed ^C or ^brk, causing the program to exit in the middle
of performing a message operation.  If you don't want this message to
appear, you should handle the break yourself with an exception handler.  In
any case, if the app is forced to exit abnormally (which would leave the
msgapi resources in an undesired state), it tries to fix things -- and will
complain when it has to do so.

 PF> would clutter up our formerly elegant-looking programs with such slop?

What is so inelegant about a one line start-up message?  Most programs do
this in some form or another, whether it be a copyright message, trademark
notice, or something similar.


--- Maximus/2 2.01