Bo:

I'm not sure what you are using in squish.cfg (GateRoute or ZoneGate type
keywords) for handling netmail between different zones, but I don't use
either keyword and process netmail for all fidonet zones.

If I want to send netmail direct, to a different zone, I just use the
normal route commands.  I am setup with several outbound directories. 
Since I'm in zone 1, my default outbound covers that zone.  Zone 2 adds a
.002, zone three adds a .003, etc, to the outbound directory name.  Squish
generates the alternate outbound directories on the fly, when needed.  This
is using Binkley Style Outbound (BSO).

If I want to route the net mail using a Zone Gate, then I handle that with
my routing statements in ROUTE.CFG.

Typically, I route all zone gate mail via 1:140/1 with a line like:

ROUTE CRASH 1:140/1 1:ALL 2:ALL 3:ALL 4:ALL 5:ALL 6:ALL

as the last route command in my route.cfg file.  This is why Squish's
handling of 'SEND NOARC NORMAL' causes me trouble, and why I have to use a
different any flavor except NORMAL for that type of mail handling or add
appropriate CHANGE lines at the beginning of ROUTE.CFG and after the final
ROUTE statement (to switch NORMAL to something else (DIRECT) and then back
to NORMAL at the end) if I actually want a NORMAL packet....

If I were to use the current zone gates in the nodelist, I would have to
look them up, but then my route statements (for using the zone 1 outbound
zone gaates) would be something like:

ROUTE CRASH 1:1/2 2:ALL
ROUTE CRASH 1:1/3 3:ALL
ROUTE CRASH 1:1/4 4:ALL
ROUTE CRASH 1:1/5 5:ALL
ROUTE CRASH 1:1/6 6:ALL

Since you are in zone 2 (if I remember correctly), I believe your last
route commands for netmail in zones 1, 3, 4, 5 and 6 in your route.cfg file
for using the zone 2 zone gates would be:

ROUTE CRASH 2:2/1 1:ALL
ROUTE CRASH 2:2/3 3:ALL
ROUTE CRASH 2:2/4 4:ALL
ROUTE CRASH 2:2/5 5:ALL
ROUTE CRASH 2:2/6 6:ALL

If you need to send the zone gated mail to a different address, just change
your route command to point to the other address.  You might want to do
this, because all zone gate addresses are a.k.a. addresses, and you might
be set up with session passwords using the remote nodes primary address,
but not their zone gate a.k.a. address.

Now, you will want to replace CRASH with the type of flavor you want to
use.  You will also need to make sure that your mailer is properly
configured to connect to those addresses.  The reason I route zonegated
netmail to 1:140/1, is that a few of the zone 1 netmail zone gate addresses
are a.k.a.'s of 1:140/1, and I have a password protected link to
1:140/1....  I could do a similar trick with at least one of the other zone
1 netmail zone gates, since I have direct connections with two of the three
zone 1 netmail zone gates (the last I actually looked up the zone gate info
in the nodelist).

So, you do NOT use ZONEGATE or GATEROUTE key words in SQUISH.CFG to zone
gate netmail in  Squish.  You use ROUTE statements like I have shown above.

Does this make sense?

As Peter commented, the ZONEGATE and GATEROUTE keywords are for dealing
with ECHO MAIL note NET MAIL!

Take care.....

Bob Jones, 1:343/41


 PK>> What doesn't work about Zonegating (with unix), or more specficaly,
 PK>> what part of Zonegating is not working?

 BS>> The gateroute thing, it created a new message, whitch 
 BS>> it marked sent, but it forgot to mark the original 
 BS>> message sent too, to it keeps sending that message...

 PK> Hold on, Zonegating and GateRouting are 2 quite different things,
 PK> are you perhaps trying to mix them? Also note that "A ZoneGate" is
 PK> a specific system, but "ZoneGating" is the act of moving traffic
 PK> between Zones. The first is a Nodelisted system, whereas anyone can
 PK> perform the second. In brief -  

 BS> Well the GateRouting statement is routing mail to other 
 BS> zone to the zonegate, but still keep the original 
 BS> reciptent in the INTL line, and that does not work 
 BS> well, i try so late as yesterday to work out the 
 BS> problem, i did take some of it.

 PK> GateRouting was primarily used for non-3D aware systems where the
 PK> Zone info was not able to be understood and handled correctly.
 PK> Traffic could be routed via a Zonegate that ensured the Zone detail
 PK> was handled correctly between such systems. Are you SURE you really
 PK> need to use GateRoute these days, its highly unusual to find
 PK> someone using code that is not 3D aware these days... 

 BS> Most editors can make the Gating by their self, but fx. 
 BS> if a netmail is sent by maximus it can't.

 BS> But yes i don't guess it matter if you use Zonegating 
 BS> or not. Sometimes i can be good to not use it.

 BS> I should sent a netmail to 4:930/1, i sent it by 
 BS> zonegate but i got on Hold at his ZC, and he wasn't 
 BS> pollable, if i did sent it routed, it got catched up by 
 BS> another node. Whitch was a ip node, there put it on 
 BS> Hold.

 PK> I have never
 PK> had to use GateRoute so I can't be sure, but it sounds like you may
 PK> be generating your 2D output back into a 3D area and creating Dups
 PK> as a result. 

 BS> No?

 PK> Zonegating is simply used to trim Seen-by's for Echomail exporting
 PK> to another Zone, where Seen-by's can be duplicated and does not
 PK> necessarily relate to using "official" Zonegates at all. ZoneGating
 PK> reduces message sizes as well. 

 BS> It's _netmail_ zonegating.

--- Maximus/2 3.01