Subj : Netmail Point
To   : Kai Richter
From : mark lewis
Date : Wed Apr 22 2020 15:09:40

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


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

 KR> 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...


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

.