Re: point system
  By: Rick Smith to Alan Ianson on Sun Apr 30 2023 07:57 am

 > Hello Alan!
 >
 > Saturday April 29 2023 18:28, you wrote to me:
 >
 >  AI>  * Forwarded from area 'FIDOSOFT.HUSKY'
 >  >>>> 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 would check that that 0069000a.sec is a plain packet and not a
 >  AI> compressed mail bundle as Carlos suggested. If it is a mail bundle you
 >  AI> may need to decompress it.
 >
 >  >>> I don't see that here. Here is what pktinfo says about a packet
 >
 >  >> Now I have no idea, I tried a new point on synchronet and I get the
 >  >> same behavior...
 >
 >  AI> I would suggest that you grab fresh husky source from github and
 >  AI> rebuild just to be sure your husky tools are up to date.
 >
 > I think that it is something to do with archivers perhaps?  On the mystic
 > system I unzipped all the .sec files and they were indeed pkt's and hpt
 > tossed them just fine.  On the synchronet test it renames them to .bad and I
 > am unable to unarchive those to test.

If you're able to unzip the file, then it's not a packet, it's a bundle (which will usually contain one or more packets).

The latest builds of SBBSecho can include the *reason* a packet is bad when renaming it (configured in echocfg). Or you can just search the sbbsecho.log for "Bad packet detected" and the log lines before that msg will say *why* the packet file was considered bad.
-- 
                                            digital man (rob)

This Is Spinal Tap quote #41:
Ian Faith: It says "Memphis show cancelled due to lack of advertising funds."
Norco, CA WX: 61.2øF, 86.0% humidity, 8 mph ESE wind, 0.00 inches rain/24hrs
--- SBBSecho 3.20-Linux