Greetings Kai!

Wednesday April 26 2023 12:55, you wrote to me about an urgent matter!:

 KR> Hello Rick!

 KR> 24 Apr 23, Rick Smith wrote to Alan Ianson:

 RS>> although I have the point in my links file

 RS>> A 20:08:36  pkt: /mystic/echomail/in/64386143.tos No Link for
 RS>> 1:105/10.1,

 KR> Remove/comment the link definition, see if log changes.
 KR> Rebuild the link config line per line.

 RS>> Link Fido point

 KR> Are spaces allowed there?

I believe so yes, I just uncommented this area when I wanted to start using point again, it worked just as it is last year.

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

A 08:41:51   Invalid pkt version 0!
0069000a.sec: Corrupt packet
rick@abacus:/mystic/echomail/in/unsecure$ pktinfo 46d19900.sec
PktInfo/lnx 1.9 2023-01-07

A 08:42:05   Invalid pkt version 325!
46d19900.sec: Corrupt packet



----
Regards,


 Rick Smith (Nitro)

... There's a fine line between BBSing and beebling
--- GoldED+/LNX 1.1.5-b20220504