TID: Mystic BBS 1.12 A46   
   MSGID: 3:770/100 243dce02   
   REPLY: 2:221/1.1 5ffdd3fd   
   TZUTC: 1300   
   On 12 Jan 2021 at 06:53p, Tommi Koivula pondered and said...   
       
    TK>  TK>> I'll send you one more crashmail, with pkt.password 12345678.   
    TK>    
    TK>  JH> Bingo!  This one failed:   
    TK>    
    TK> So it seems that Mystic doesn't like .pkt's with password in unsecure   
    TK> inbound. It is not necessarily a bad thing. :)   
    TK>    
    TK>  JH> + Jan 12 10:24:21  Process: Importing EchoMail   
    TK>  JH> + Jan 12 10:24:21    Waiting for BUSY nodes   
    TK>  JH> + Jan 12 10:24:21    Importing 12172411.PKT (2:221/1.2 to 1:229/664)   
    TK>  JH> ! Jan 12 10:24:21    No echomail node configured for 2:221/1.2   
    TK>  JH> ! Jan 12 10:24:21    Moving   
    TK>  JH> /home/pi/mystic/echomail/in/unsecure/12172411.PKT to   
    TK>  JH> /home/pi/mystic/echomail/bad/12172411.PKT + Jan 12 10:24:21  Results:   
    TK>  JH> echo, 0 net, 0 dupes, 0 tossed   
    TK>  JH> in 0.09s   
    TK>    
    TK> 'Tommi   
      
   Hmm... I think (Jame's correct me if I'm wrong here) the intention is that   
   netmail will always toss but tossing unsecure echomail is optionally togged   
   on/off in the MUTIL ini.   
      
   In the back of my mind I'm fairly sure the intention was to always allow   
   netmail to be tossed in.   
      
   But I could be wrong too :)   
      
   Best, Paul   
      
   --- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)   
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)   
   SEEN-BY: 1/123 57/0 90/1 105/81 114/705 120/340 123/120 131 129/305   
   SEEN-BY: 154/10 220/70 226/17 30 100 227/114 702 229/101 424 426 452   
   SEEN-BY: 229/550 664 981 1016 1017 240/5832 249/206 307 317 400 250/5   
   SEEN-BY: 250/8 267/800 292/854 298/25 305/2 3 317/3 322/757 340/1000   
   SEEN-BY: 342/200 633/280 712/848 770/0 1 3 100 340 772/0 1 210 220   
   SEEN-BY: 772/230   
   PATH: 770/100 1 317/3 229/426