Subj : *.pkt
To   : Mike Tripp
From : Richard Webb
Date : Fri Mar 19 2010 10:05 pm

HI Mike,

On Fri 2038-Mar-19 12:08, Mike Tripp (1:382/61) wrote to Richard Webb:

 RW> this thread of splitting large messages works because I"m
 RW> using the large buffers setting.  OTherwise ymmv.  I think
 RW> the docs mention something about the behavior changing
 RW> according to buffer size, i.e. squish will behave as it did
 RW> with earlier versions if you use medium or small buffers.

MT> Squish does not do any message splitting...though I do not recall
MT> whether it renames the PKT to LNG or BAD for later reprocessing. 
MT> The only change I'm aware of between versions was new numeric values
MT> for Small/Medium/Large and the ability to assign them (or explicit
MT> numeric values) to the 3 individual buffers. 


Okay, they might be split upstream of me, been a long time.
I know stuff originated here is split before I even let
squish see it if I think it's going to be overlong.


MT> I did all sorts of convolutions to get a utility called PKTSort to
MT> do the splitting by pre-processing the inbound directory while it
MT> was actually designed to post-process the outbound directory. I
MT> eventually found a newsgroup gating util called NGate which bypasses
MT> tossing and transfers messages directly between NNTP server and
MT> squishbase...and still did a batch manipulation of the Buffers
MT> statement in SQUISH.CFG just for scanning the newsgroups out to
MT> downlinks. 

YEp, I got pktsort to be happy by using gus to break open
the archive bundles first then ran pktsort across the
incoming packets back in my busy hub days.  That was my
workaround anyway.
Worked well, just invoke gus after receiving compressed mail on the appropriate 
inbound with the /m command line switch,
then run pktsort.

Regards,
           Richard
--- timEd 1.10.y2k+
 * Origin: Radio REscue net operations BBS       (1:116/901)

.