* Originally in points
* Crossposted in mystic

Hi Jay.

So the difference to my netmail was that my .pkt did not contain
password.

I'll send you one more crashmail, with pkt.password 12345678.

Bingo! This one failed:

So it seems that Mystic doesn't like .pkt's with password in unsecure inbound. It is not necessarily a bad thing. :)

+ Jan 12 10:24:21 Process: Importing EchoMail
+ Jan 12 10:24:21 Waiting for BUSY nodes
+ Jan 12 10:24:21 Importing 12172411.PKT (2:221/1.2 to 1:229/664)
! Jan 12 10:24:21 No echomail node configured for 2:221/1.2
! Jan 12 10:24:21 Moving /home/pi/mystic/echomail/in/unsecure/12172411.PKT to
/home/pi/mystic/echomail/bad/12172411.PKT + Jan 12 10:24:21 Results: 0 echo, 0 net, 0 dupes, 0 tossed
in 0.09s

'Tommi

---
* Origin: IPv6 Point at [2001:470:1f15:cb0:2:221:1:1] (2:221/1.1)

On 12 Jan 2021 at 06:53p, Tommi Koivula pondered and said...

I'll send you one more crashmail, with pkt.password 12345678.

Bingo! This one failed:

So it seems that Mystic doesn't like .pkt's with password in unsecure inbound. It is not necessarily a bad thing. :)

+ Jan 12 10:24:21 Process: Importing EchoMail
+ Jan 12 10:24:21 Waiting for BUSY nodes
+ Jan 12 10:24:21 Importing 12172411.PKT (2:221/1.2 to 1:229/664) ! Jan 12 10:24:21 No echomail node configured for 2:221/1.2
! Jan 12 10:24:21 Moving /home/pi/mystic/echomail/in/unsecure/12172411.PKT to /home/pi/mystic/echomail/bad/12172411.PKT + Jan 12 10:24:21 Results: echo, 0 net, 0 dupes, 0 tossed
in 0.09s

'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)

Hmm... I think (Jame's correct me if I'm wrong here) the intention is thatnetmail will always toss but tossing unsecure echomail is optionally toggedon/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 :)

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)

I am guessing we might have discussed making tossing echomail an opti 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?

Yeah I'm foggy on the details too but I'm picking that's what this switch is/was for?

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

That option enables whether it will toss unsecure PKT/bundles but it will only process netmail, not echomail. From what I can see there is no longer a way to import unsecure echomail (which is probably a good thing?).

We're all getting older and erm .. wiser I think :)

Agreed!

Best wishes to you for the year ahead. I hope family and yourself are safeand well during these crazy times.

Thanks and same to you!

--- Mystic BBS v1.12 A47 2021/01/05 (Windows/32)
* Origin: Sector 7 | Mystic WHQ (1:129/215)