I joined a second network, and both I and the "hub" are having a hard time figuring out what is going on here. Here is my Mutil log when it last tried
to import a packet.

----------------- MUTIL v1.12 A46 2020/08/26 Sat, Mar 13 2021 (loglevel 3)
+ Mar 13 22:46:56 Startup using mailin.ini
- Mar 13 22:46:56 EXEC ImportEchoMail
- Mar 13 22:46:56 EXEC FileToss
+ Mar 13 22:46:56 Process: Toss FDN/TIC Files
+ Mar 13 22:46:56 Waiting for BUSY nodes
+ Mar 13 22:46:56 Scanning Hatches
+ Mar 13 22:46:56 Results: 0 import, 0 toss, 0 hatch, 0 bad in 0.00s
+ Mar 13 22:46:56 Process: Importing EchoMail
! Mar 13 22:46:56 Dupe base (Amateur Radio) must be local
+ Mar 13 22:46:56 Waiting for BUSY nodes
! Mar 13 22:46:56 Import from /mystic/echomail/in/
! Mar 13 22:46:56 Import from /mystic/echomail/in/unsecure/
+ Mar 13 22:46:56 Extracting 3B37D0E1.SA1
- Mar 13 22:46:56 unzip -oqqjC "/mystic/echomail/in/unsecure/3B37D0E1.SA1" "*.pkt" -d /mystic/temputil/
+ Mar 13 22:46:56 Importing 4825DD6E.PKT (25:25/0 to 25:25/25)
! Mar 13 22:46:56 Skip unsecure echomail in METSYSOP
+ Mar 13 22:46:56 Results: 0 echo, 0 net, 0 dupes, 0 tossed in 0.02s
+ Mar 13 22:46:56 Shutdown Normal (0)

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

My packets go out fine. I have the passwords set right as far as I can tell.
Is this something I did wrong? I'm confused.

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Ground Control (21:3/140)

On 13 Mar 2021 at 11:20p, Starstorm pondered and said...

! Mar 13 22:46:56 Dupe base (Amateur Radio) must be local

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

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

On 14 Mar 2021, Avon said the following...

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

That's what's particularly weird. I did define the node. I even double
checked the nodelist. I will check again, maybe it's not what I think it is.
As far as session password,I was told there isn't one. Could that be the problem?

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Ground Control (21:3/140)

On 14 Mar 2021, Starstorm said the following...

On 14 Mar 2021, Avon said the following...

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 fal in the echomail\in folder

That's what's particularly weird. I did define the node. I even double checked the nodelist. I will check again, maybe it's not what I think it is. As far as session password,I was told there isn't one. Could that be the problem?

I think I fixed it. *crossing fingers*

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: Ground Control (21:3/140)

On 14 Mar 2021 at 12:09p, Starstorm pondered and said...

is. As far as session password,I was told there isn't one. Could that be the problem?

Yes, you need a BinkP session password to determine a secure session and
hence packets drop into the echomail\in folder then get tossed without issue
:)

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

is. As far as session password,I was told there isn't one. Could that the problem?

Yes, you need a BinkP session password to determine a secure session and hence packets drop into the echomail\in folder then get tossed without issue :)

I just got bit by the same "bug" and posted an email on here about it! LOL - glad I browsed backwards a little and saw this!.

-- Nuke

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: westwoodbbs.net (21:3/134)

On 15 Mar 2021 at 11:44p, Nuke pondered and said...

I just got bit by the same "bug" and posted an email on here about it!
LOL - glad I browsed backwards a little and saw this!.

Good stuff :)

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