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)