>> Will this new release still use only *.msg format?  
 > Yes. If you want something else in the future, please advise 
 > the OOWK.  
My 2 cents worth on this:  The *.MSG format has many things going for it, not 
the least of which is simplicity, which equates to ease of access to each 
message for utility authors.  I'd rather write a utility and concentrate on 
getting the utility to work right than have to spend days figuring out how to 
access and read a message text, let alone figuring out how to add or delete a 
message from some fancy-dan database.  (The offset from the last accessed 
message is stored where?  And if I change it, then what else goes kerflup?)  
And the *.MSG format is relatively bulletproof; data corruption of whatever 
kind generally affects only one message rather than an entire message area 
(or the whole message database).  The main objection to the *.MSG format, 
i.e. it wastes space, is really kind of a non-issue with today's large hard 
drives and the wide availability of software like DOUBLESPACE for folks who 
need to squeeze every possible message into a smaller space.
--- Msgedsq 2.2e
---------------