Greetings,

I have poured over the logs for both my point setup and mystic. The only errors I find are in the mutil log at or about the time I was supposed to receive a Netmail from an outside source. Please find them below, there were more but this should give you the gist.

9db62811.pkt does not match an AKA (1:340/202.1)
Import from c:\mystic\echomail\in\unsecure\
! Apr 21 06:10:10 9db62811.pkt does not match an AKA (1:340/202.1

If you know how to fix id love to know!

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/09 (Windows/64)
* Origin: Abacus BBS (77:1/130)

9db62811.pkt does not match an AKA (1:340/202.1)

Do you have 1:340/212.1 defined as an address in the system that is
processing that?

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/64)
* Origin: Sector 7 (77:1/138)

Do you have 1:340/212.1 defined as an address in the system that is processing that?

That message is from my mystic logs. That 1:340/202.1 is a point I use on
with binkd husky golded. I have the point address setup in mystic as a node but not in echomail addresses as the way I understood it that was for
addresses used on mystic? Should I have my point address in there as well?
I can send my point netmail from mystic and vice versa but noone else can
send me netmail to my point.

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/09 (Windows/64)
* Origin: Abacus BBS (77:1/130)

Do you have 1:340/212.1 defined as an address in the system that is processing that?

That message is from my mystic logs. That 1:340/202.1 is a point I use
on with binkd husky golded. I have the point address setup in mystic as
a node but not in echomail addresses as the way I understood it that was for addresses used on mystic? Should I have my point address in there as well? I can send my point netmail from mystic and vice versa but noone else can send me netmail to my point.

Ok so if I understand you 1:340/212.1 is a non-Mystic system that uses BINKD and Husky and 1:340/212 is your Mystic BBS that uses all Mystic stuff?

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/64)
* Origin: Sector 7 (77:1/138)

Ok so if I understand you 1:340/212.1 is a non-Mystic system that uses BINKD and Husky and 1:340/212 is your Mystic BBS that uses all Mystic stuff?

well you have the address wrong its 202 but yes you are correct. Been trying to sort this out for some time..

Thank you for any help

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/09 (Windows/64)
* Origin: Abacus BBS (77:1/130)

well you have the address wrong its 202 but yes you are correct. Been trying to sort this out for some time..

Thank you for any help

Thanks for the clarification. I'll set up a similar test here and see what I can figure out. Its possible that its a bug.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (77:1/138)

Thanks for the clarification. I'll set up a similar test here and see what I can figure out. Its possible that its a bug.

I sure do appreciate your time.. As a note I did just upgrade to 04/20 on a suggestion from someone else,

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/64)
* Origin: Abacus BBS (77:1/130)

Thanks for the clarification. I'll set up a similar test here and se what I can figure out. Its possible that its a bug.

I sure do appreciate your time.. As a note I did just upgrade to 04/20
on a suggestion from someone else,

I've been doing a bunch of tosser changes lately. I've asked someone with
HPT to netmail a point system I setup so we'll see how that goes. I'll get
to the bottom of it.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (77:1/138)

I've been doing a bunch of tosser changes lately. I've asked someone
with HPT to netmail a point system I setup so we'll see how that goes. I'll get to the bottom of it.

Just sent it to you.

|15frank |08// |15netsurge
|07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

--- Mystic BBS/QWK Gate v1.12 A46 2020/04/13 (Linux/64)
* Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (77:1/100)

9db62811.pkt does not match an AKA (1:340/202.1)

So I just tested this with Netsurge who also uses HPT and its working fine
for my setup. I wanted to confirm that I wasn't mistaken before I answered
and it looks like I am correct.

Basically whoever is sending you that .PKT file is addressing it to the point system but sending it to your non-point which to my knowledge it should not be doing.

When Netsurge sends a point netmail through my system I get this in my logs:

+ Apr 21 16:06:12 Importing 82ab6bb6.pkt (77:1/100 to 77:1/138)
+ Apr 21 16:06:12 Route (77:1/100 to 77:1/138.1) via 77:1/138.1

Notice that the PKT from him is addressed to 77:1/138 *not* the point node like the PKT you are getting is? Its the message inside of the PKT that should be addressed to the point but the PKT itself should be addressed to the system intended to process it next. When its addressed to the system processing it, then Mystic sees and routes the contents as needed to the appropriate point system.

So it seems at the very least Mystic and HPT work this way and that the issue might be the PKT you're receiving.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (77:1/138)

So it seems at the very least Mystic and HPT work this way and that the issue might be the PKT you're receiving.

It makes sense, however I cannot get any netmail from anyone, could you
please send one to me and see if it shows up? Those two packets I think mark send me on purpose routed differently as we were trying to sort it out, but
no netmail comes through.

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/20 (Windows/64)
* Origin: Abacus BBS (77:1/130)

So it seems at the very least Mystic and HPT work this way and that t issue might be the PKT you're receiving.

It makes sense, however I cannot get any netmail from anyone, could you please send one to me and see if it shows up? Those two packets I think mark send me on purpose routed differently as we were trying to sort it out, but no netmail comes through.

Looks like a few others are sending you tests.

One thing that you might want to do is to upgrade to the April 21st release
and then set up your "bad_packet" directory in your import .ini file. This will copy those bad packets to a directory so you have a copy of them.

We can then take a look at them and see what looks wrong with it.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (77:1/138)

Looks like a few others are sending you tests.

Still nothing has come through.//

One thing that you might want to do is to upgrade to the April 21st release and then set up your "bad_packet" directory in your import .ini file. This will copy those bad packets to a directory so you have a
copy of them.

Ok done, I didnt see any bad_Packet option in the .ini so I added bad_packet the the path will that suffice?

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Abacus BBS (77:1/130)

Looks like a few others are sending you tests.

Still nothing has come through.//

You should see it in your logs as a bad address at the very least when they arrive assuming they're addressed wrong again.

Ok done, I didnt see any bad_Packet option in the .ini so I added bad_packet the the path will that suffice?

Yes if in your ImportEchoMail area you have something like:

bad_packet = c:\mystic\echomail\badpkt

Then it will move PKTs there that fail because of addressing or a bad PKT password or if it doesn't have a proper PKT header.

--- Mystic BBS v1.12 A46 2020/04/21 (Windows/64)
* Origin: Sector 7 (77:1/138)