REPLY: 2:240/77 60a0cac2   
   MSGID: 2:423/39 60a130e9   
   CHRS: CP895 2   
   TZUTC: 0200   
   TID: CrashMail II/Linux 0.62   
   Hello Kai!   
      
   16 May 21 09:20, you wrote to me:   
      
    KR> That's why i think the real write access time to the msgbase is very   
    KR> short. On the other hand the question is what the tosser would do on a   
    KR> locked msgarea. Wait for access? Skip? Where is the skipped mail?   
    KR> Still in the pkt? In some temp spools? In the badmail area?   
      
   It is probably very specific. I checked source code for Crashmail (ok, version   
   1.6 here, file src/jamlib/jamlib.doc - but OK):   
      
   -------   
                      if ( Result_I == JAM_LOCK_FAILED )   
                          /* base locked by someone else, wait for unlock */   
                          sleep( 1 );   
   -------   
   So Crashmail should wait until GoldEd unlock it...   
      
   Karel   
   --- GoldED+/LNX 1.1.5-b20180707   
    * Origin: Plast DATA (2:423/39)   
   SEEN-BY: 1/123 18/200 30/0 90/1 105/81 120/340 123/131 129/305 203/0   
   SEEN-BY: 221/1 6 360 226/30 227/114 229/101 424 426 452 664 700 1016   
   SEEN-BY: 229/1017 240/1120 5832 249/206 317 400 280/464 5003 282/1038   
   SEEN-BY: 292/854 301/0 1 101 103 113 123 812 317/3 322/757 342/200   
   SEEN-BY: 420/33 333 421/79 83 423/39 81 120 121 633/280 5058/104   
   PATH: 423/39 81 221/1 301/1 229/426