TID: Mystic BBS 1.12 A47   
   MSGID: 1:129/215 c3aedef3   
   REPLY: 3:770/100 243dce02   
   TZUTC: -0500   
    PH> Hmm... I think (Jame's correct me if I'm wrong here) the intention is   
    PH> thatnetmail will always toss but tossing unsecure echomail is optionally   
    PH> toggedon/off in the MUTIL ini.   
    PH>    
    PH> In the back of my mind I'm fairly sure the intention was to always allow   
    PH> netmail to be tossed in.   
    PH>    
    PH> But I could be wrong too :)   
      
   My memory of the details might be a little foggy too! :)   
      
   Mystic will process netmail but not echomail from unsecured packets as you   
   said.  I think initially it always allowed echomail too, but based on your   
   feedback I stopped that from happening.   
      
   I am guessing we might have discussed making tossing echomail an option but I   
   don't see it in the code, so maybe we just didn't get to it or ended up saying   
   it wasn't needed?   
      
   When a unsecure PKT has an password assigned to it, Mystic will never process   
   it under any circumstance.  To do so would mean Mystic is ignoring the   
   assigned password to the PKT, so off to the BAD PKT directory it goes!   
      
   I am of course open to ideas on how to handle these better if you guys think   
   there is a better way to do these things!   
      
   --- Mystic BBS v1.12 A47 2021/01/05 (Windows/64)   
    * Origin: Sector 7 | Mystic WHQ (1:129/215)   
   SEEN-BY: 1/123 90/1 103/705 105/81 120/340 123/10 131 124/5016 129/215   
   SEEN-BY: 129/305 154/10 30 40 50 700 203/0 220/80 221/0 6 226/30 227/114   
   SEEN-BY: 227/201 702 229/101 310 424 426 452 550 664 981 1016 1017   
   SEEN-BY: 240/1120 5411 5832 5853 6309 249/206 307 317 400 280/464   
   SEEN-BY: 280/5003 292/854 8125 317/3 320/219 322/757 342/200 396/45   
   SEEN-BY: 633/280 770/1 2452/250 2454/119 3634/12   
   PATH: 129/215 154/10 280/464 240/5832 229/426