On 20 Jun 17  15:18:14, Mark Lewis said the following to Nick Andre:   
      
   ML> i doubt they would want the entire code base :)  but yeah, i hear ya... you   
   ML> have quite a bit of documentation about it, though... i remember reading it   
   ML> while back... especially the queue stuff... i think as long as MSG is still   
   ML> use, they should still work together... the question is if sbbsecho needs s   
   ML> more work for MSG mailers or not... with the new rewrite, it may...   
      
   Writing a *.MSG tosser is very simple for the average programmer. Its   
   the easiest storage format to work with. Its only the mess of kludge lines,   
   the Seen-by's, path's, etc that gets tricky.   
      
   But its already nice and neat in the DB code and has not been changed in years   
   with the exception of MSGID/REPLY I added for the internal editor.   
      
   The procedure-calls in DB for tossing mail to Hudson/Goldbase is almost twice    
   if not three times the size of the same procedure to toss to *.MSG... as once   
   you start dealing with multiple database files for indexes, headers, etc it    
   becomes a convoluted mess.   
      
   The code is not calling API's either. It was all written meticulously from    
   scratch. There is NO way to rewrite everything to use an API without seriously   
   rewriting the mail tosser and thats just something I'm NOT going to reinvent.   
      
   I did wrote code for Squish in DB, from scratch, but the Netmail flags and    
   some other things in the code I thought were just "not right" and would of    
   been show stoppers if I published a DB-Squish version with glaring mistakes.   
      
   Nick   
      
   --- Renegade vY2Ka2   
    * Origin: Joey, do you like movies about gladiators? (1:229/426)