Greetings Alan!

Wednesday April 26 2023 09:46, you wrote to me about an urgent matter!:

 AI>  * Forwarded from area 'FIDOSOFT.HUSKY'
 >> I found the packets that got renamed to .sec and put in unsecure
 >> folded so I ran pktinfo on them and here are the results..

 >> PktInfo/lnx 1.9 2023-01-07

 >> A 08:41:35   Invalid pkt version 272!
 >> 47e8bc00.sec: Corrupt packet
 >> rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 0069000a.sec
 >> PktInfo/lnx 1.9 2023-01-07

 AI> I don't see that here. Here is what pktinfo says about a packet
 AI> created at my point..

This is so bizarre I have run points of this setup in the past with these exact cfgs, I just commented them out when I stopped using the point.  Is it possible that updated or changed code in todays hpt/binkd have broke this somehow?  I did move the BBS to a different server about three months ago so I did a fresh build of hpt/binkd.  I set up binkd/hpt on my linux laptop and I get the same problems that I have with aftershock so it is for sure my mystic bbs setup that is causing the issue.


----
Regards,


 Rick Smith (Nitro)

... BBSing is like sex, except for not wanting to get off.
--- GoldED+/LNX 1.1.5-b20220504