> 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

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

alan [ ~ ]$ pktinfo -h 64495166.pkt PktInfo/lnx 1.9 2023-02-24

Packet header
==============================================================================
Filename       : 64495166.pkt
OrigAddr       : 1:153/757.1
DestAddr       : 1:153/757.0
AuxNet         : 0
CapWord        : 0x0001
DateCreation   : Wed 2023-04-26 10:29:26
Password       : "SECRET"
ProdCode       : 1bff
ProdVersion    : 0.1

Message header
------------------------------------------------------------------------------
From           : "Alan Ianson"
To             : "All"
Subject        : "Test post"
DateTime       : "26 Apr 23  09:29:20"
Attr           : 0x0008 -> Sent
OrigAddr       : 153/757
DestAddr       : 153/757

Can you examine one of those packets before you toss it?

Hopefully you'll get a similar result.

I'm not sure what is causing your bad packets, but that is the cause of your issue.

--- BBBS/Li6 v4.10 Toy-6