Hello All!

Here are some things I think might help folks that are having problems with
the y2k squish version.  I don't profess to have any great knowledge here,
but neither do I have any problems with the software.

My system usually only has to process 250-300 messages at a time.  This is
not because that's all I get in a day but that is what I get every hour
when I ftp the mail.  Not that it hasn't processed more than that in the
past, but not since changing versions.

Don't have Squish unarchive the bundles.  I use GUS (General Unpack Shell)
to do this job before calling Squish.  This saves a shell from Squish to
run the unarc program.

To keep Squish from jumping from echo tag to echo tag every other message I
use PackSort before Squish to sort the messages by area and subject. 
PackSort does this by reading the packets, sorting and writing a new
packet.

I can then run in a single pass:

          Sq386 In Out Squash -fEchoToss.log
          QLink -fEchoToss.log
          del EchoToss.log

And the above is another place to ease Squish's memory by doing multipass mode:
          Squish In  -fEchoToss.log
          Squish Out -fEchoToss.log
          Squish Squash
          Squish Link -fEchoToss.log
          del EchoToss.log

And yes, I do have a lot of memory even though it is divided up between
three DESQview windows and a 2meg ramdisk where my Swap g:\$$squish.swp
points.  Only one DV window tosses mail and that has 4megs extended memory,
ample memory for Sq386 to work with.  But I believe it's the lower mail to
be tossed, unarchiving bundles and sorting the mail before running Squish
that is the key as that all worked when I only ran one mailer straight from
DOS with only 4megs of total memory.

Just my point of view on these problems.


    [shb]
    cades{at}nashville.com

--- timEd-B11