Hi Bob,

 BJ> If you try to use "ROUTE NOARC NORMAL 1:234/567.8 1:234/*"
 BJ> and then have a line that does something like default 
 BJ> route (from memory, something line "ROUTE CRASH 1:140/1 
 BJ> 1:ALL 2:ALL 3:ALL 4:ALL 5:ALL 6:ALL"), then the mail 
 BJ> that you packed for 1:234/567.8 gets retargted and sent 
 BJ> to 1:140/1 (in this example).  Actually, it doesn't 
 BJ> need to be a default route.  It just needs to be a 
 BJ> command that ends up reprocessing node 1:234/567.8's 
 BJ> outbound mail packets.....

I think I know what you are talking about. Have you noted this section of
the Squish32 docs -

=======================================================================

          In general, ROUTE.CFG starts off with a section of global routing
          commands (which are run every time Squish scans the netmail
          area), followed by a set of zero or more schedules.  The commands
          within the global section and each schedule all use the same
          format; the only difference is when the commands are executed.

          No matter what, commands in the global section of the routing
          control file are ALWAYS executed.  Even when explicitly running a
          different schedule, the global commands are still run first.


                       Squish v1.10 Reference Manual - Page 29





          Therefore, the global section should contain commands that you
          want to run every time that Squish is executed.  Everything
          between the first line of ROUTE.CFG and the first 'Sched'
          statement is considered to be a global command and is treated
          accordingly.

=======================================================================

It doesn't DIRECTLY address YOUR problem, but it may help to understand
what I am saying below...

In MY ROUTE.CFG file, I split the PACKING and SENDING of mail into two
distinct sections of the file, as hinted at in the Docs above. The BIG
difference, is that in the GLOBAL section of the file, I do all the PACKING
work, placing ALL the resultant files into the required bundles with a
SINGLE OUTPUT FLAVOUR of HOLD. Then for each Schedule, I set about and
CHANGE the resultant file from HOLD into the correct FLAVOUR that I want. I
do not pack directly into the end result Flavour.

If you mix FLAVOUR statements within the PACKING section of your file, then
you are in fact asking Squish to start re-processing ALL files again using
that SPECIFIC FLAVOUR, so you end up with the result you see of combining
packets. If all Mail packing takes place using just ONE Flavour (HOLD),
then you don't get the combination of packing methodologies being attempted
because previous statements using the SAME flavour are not re-processed
UNLESS you explicitly say so. It seems to be a very subtle
"feature" of Squish.

I manage my outbound data by placing all my ROUTE and SEND contructs to use
the HOLD status in the "Common" section of the file. Then the
last thing I do within each SCHEDULE section of the file is CHANGE the HOLD
to whatever Flavour I want, and I DONT do any packing at that point (its
aleady done).

I think the logic of this is there, its just not actually stated clearly (IMHO).

Does that help?

Cheers...............pk.


--- Maximus/2 3.01