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 (1:340/202)

Re: Netmail Point
By: Rick Smith to All on Tue Apr 21 2020 08:03:25

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

i just replied to this in another area... please don't ask the same question in
more than one area ;)


)\/(ark
--- SBBSecho 3.10-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Greetings mark!

21 Apr 20 15:14, you wrote to me about an urgent matter!:

Re: Netmail Point
By: Rick Smith to All on Tue Apr 21 2020 08:03:25

i just replied to this in another area... please don't ask the same question in more than one area ;)

Not everyone that is available to help reads all relevant echos. So I will post where I need to get responses hence why there is a forward command. Just skip over it if you have already read it.. You seem cranky to me, I long for the good old days when sysops were kind and less judgemental.



-+-
Regards,

Rick // (Nitro)

... Life: The space between BBSing.
--- GoldED+/LNX 1.1.5--b20170303
* Origin: ----> Abacus Sysop Point (1:340/202.1)

Greetings Rob!

21 Apr 20 17:29, you wrote to me about an urgent matter!:
`Re: Netmail Point

By: Rick Smith to mark lewis on Tue Apr 21 2020 01:42 pm

Maybe wait a day or two after posting the question in one area and
then if you get no reply, then start restating the question in another area, wait, and so on. That's what I'd do anyway.

Fair enough.

In my experience, sysops have (mostly) always been cranky. It's like
part of the job description. :-)

I generally get cranky at myself for not figuring something out or not being able to help others, its generally bad form to take it out on others... just a humble opinion.

PS I am enjoying getting to know synchro


-+-
Regards,

Rick // (Nitro)

... Taglines..........The bumper stickers of BBSing
--- GoldED+/LNX 1.1.5--b20170303
* Origin: ----> Abacus Sysop Point (1:340/202.1)

Hello Rick!

21 Apr 20, Rick Smith wrote to mark lewis:

Not everyone that is available to help reads all relevant echos.

Just a few seconds ago i deleted this reply:
(and fetched it from goldeds last message emergency buffer)

###############
Hello Rick!

21 Apr 20, Rick Smith wrote to All:

I have poured over the logs for both my point setup and mystic. The
only errors I find are in the mutil log

I think mutil is a software of Mystic which is not part of the husky software. That's why i can't help. No have no can do.

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

Looks like 202 does not know that it has a point 202.1 .

Regards

Kai
###########

So I will post where I need to get responses

I deleted my mail because i haven't found useful information in it.

For mystic your are definitly in the wrong echo here. Your next question is what exactly does mutil did not match. That question can be answered by people with internal knowledge of mutil.

hence why there is a forward command.

Hence why there is a brain? ;-)

Just skip over it if you have already read it.. You seem cranky to
me, I long for the good old days when sysops were kind and less judgemental.

The good old days of fidonet are now. Isn't there a generic FIDOSOFT echo?

I do use the husky suite and that's why i can give help for husky only.

I'm sure sometimes you're right but this time your mystic related question did not fit here. And i'm annoyed by mystic far too often. I can't imagine why there is proud between the lines of "upgrade to the latest pre-alpha, that's fixed there". In your good old times what would happen if a sysop uses a pre-alpha amok running software? If you're tared and featherd they would be kind in those good old days. ;-)

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: MOnobox (2:240/77)

Greetings mark!

22 Apr 20 15:09, you wrote to Kai Richter about an urgent matter!:

Re: Netmail Point
By: Kai Richter to Rick Smith on Wed Apr 22 2020 19:43:26

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

Looks like 202 does not know that it has a point 202.1 .

the error is my fault... the packet was sent from my system by
manually renaming it in the BSO to the boss node's address instead of properly unpacking it and repacking it with the proper destination
address in the PKT header... i could also have used a hex editor on it
to fix the PKT destination address... sadly, i didn't think about
that...

the reason i renamed it manually is because the message arrived here
with the crash bit set and due to a bug in the tosser i use, it tried
to follow the crash bit directions which were to pack the message
directly to the destination system... since the destination system is
a point system and my system has no idea about the connection details
for it, the packet and messages inside were stuck in my BSO... there
is a reason BSO is also known as a blackhole ;)

so we got with the maintainer of the tosser and looked at what was happening... originally we were concerned about something being broken
in the routing capabilities... then we discovered the crash bit and switched directions... now the tosser properly strips crash, hold, and local bits on incoming netmail so it can properly apply routing when needed...

FWIW: instead of manually renaming or doing the unpack/repack dance, i could just as easily of asked the destination point system to simply
poll here and pick it up themselves... hind sight, 20/20, and all
that...

I wish I had the appitude to understand one bit of that, but it certainly appears you do thankfully. Does this mean things should work normally now? Ive
stopped posting about it so that I wouldnt annoy anyone further.


-+-
Regards,

Rick // (Nitro)

... BBSing at least keeps SOME drunks off the street.
--- GoldED+/LNX 1.1.5--b20170303
* Origin: ----> Abacus Sysop Point (1:340/202.1)

On 2020 Apr 22 13:34:42, you wrote to me:

I wish I had the appitude to understand one bit of that, but it certainly appears you do thankfully.

with some 30+ years in fidonet, one picks up on the intricacies at times... especially if they are a developer ;)

Does this mean things should work normally now?

yes... your tests helped to find a bug in a package that may be used by intermediate systems... that bug has been fixed and as other systems using the package update, the bug (in this package) will go completely away and mail flow
should be fine... it is possible that some systems with the bug or systems using a different package with a similar bug may have mail hung up in their outbounds... eventually, they will be found and either sent on, deleted, or properly bounced back to the originator...

Ive stopped posting about it so that I wouldnt annoy anyone further.

you're fine and we're good AFAIAC ;)

)\/(ark

"The soul of a small kitten in the body of a mighty dragon. Look on my majesty,
ye mighty, and despair! Or bring me catnip. Your choice. Oooh, a shiny thing!" ... My Go amn keyboar oesn't have any 's!
---
* Origin: (1:3634/12.73)