Subj : Re: Weird problem with another network...
To   : Starstorm
From : Avon
Date : Sun Mar 14 2021 08:57 pm

On 13 Mar 2021 at 11:20p, Starstorm pondered and said...
 
 St> ! Mar 13 22:46:56    Dupe base (Amateur Radio) must be local

 St> The Dupe base issue I fixed that, but, see what else is happening, why
 St> is the packet going to the unsecure directory and why is it getting
 St> skipped?

 St> ! Mar 13 22:46:56    Import from /mystic/echomail/in/unsecure/
 St> + Mar 13 22:46:56    Extracting 3B37D0E1.SA1
 St> - Mar 13 22:46:56    unzip -oqqjC
 St> "/mystic/echomail/in/unsecure/3B37D0E1.SA1" "*.pkt" -d /mystic/temputil/
 St> + Mar 13 22:46:56    Importing 4825DD6E.PKT (25:25/0 to 25:25/25)
 St> ! Mar 13 22:46:56    Skip unsecure echomail in METSYSOP

The packet will land there when you receive it from a node you don't have set
up as an known echomail node in your mystic config. So it says. Hmm dont know
this node, the session is not secure, I'll place it in the unsec dir.

Now if it's netmail that lands there Mystic will always try to import it
(that's my understanding) but it won't normally try to toss the echomail
unless you have

    ; Toss packets from unsecure directory in addition to inbound?
    
    unsecure_dir = true

set up in your ImportEchomail stanza.

Why Mystic continue to reject importing the echomail tag I'm not 100% sure.
It may be (and I went looking for this but couldn't find where I thought I'd
read it) that g00r00 set things up now so unsec echomail just won't be tossed
ever... not 100% sure on that

But the quick fix is to define the node that is sending you these packets as
an echomail node and set a session password so packets fall in the
echomail\in folder

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
 * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

.