Hello Maxim.

19 Oct 08 00:42, you wrote to me:

 RT>> As HPT has no idea what to do with the message, it will
 RT>> effectively get trashed somewhere ... , and stay there until a
 RT>> route is provided for it

 MS>  now more clear, thank you

Good ...

 RT>> For my system my route would be as follows;
 RT>> route crash 1:140/1 1:* 3:* 4:*
 RT>> route crash 2:292/854 2:*
 RT>> route crash 8:8/2 8:*
 RT>> route crash 110:110/2 110:*
 RT>> route crash 5:7106/22 5:7106/*
 RT>> route crash 5:7122/1 5:7122/*
 RT>> Traffic/mail/files for zones 1, 3, and 4 get routed via node
 RT>> 1:140/1 Traffic/mail/files for zone 2 get routed via node
 RT>> 2:292/854 Traffic/mail/files for zone 110 get routed via node
 RT>> 110:110/2 Traffic/mail/files for zone 8 get routed via node 8:8/2
 RT>> Traffic for each of the nets that are part of Zone5 are routed to
 RT>> each net controler.

 RT>> Hope this is helping you understand what I am getting at ...

 MS> thank you very much for deep explaination. i undestand it in general
 MS> it much simpler then sendmail.cf file rules L).

That is so ... :-)

 MS> could you clarify couple concrete items regarding the future default
 MS> configs of fidoip?

 MS> regarging hpt config

 MS> in windows part of fidoip i have:

 MS> route crash 2:5020/828 *

That might work ... ,tho I have never tried it ...

Write a netmail and address it to my node number and see if it gets here ...

 MS> in unix part i have:

 MS> Route normal 2:5020/828.0 2:*

 MS> if in a new version i would set for both parts as:

 MS> Route normal 2:5020/828.0 *

Hmmm  ... , not sure, wildcards, sometimes act very differently in 
Linux/FreeBSD than in Windows, i.e. they are expanded differently ...

 MS> or

 MS> Route normal 2:5020/828.0 1:* 2:* 3:* 4:* 5:* N:*
 MS> (by the way - how many alive zones are now?)

In FidoNet there are currently 5 zones ...

 MS> or set it for both parts as:

 MS> route crash 2:5020/828 *

 MS> which way is better for point with one link connection to boss'es
 MS> node?

If that allows you to send netmail to all current Zones, then it is all right, 
I would prefer the examples I showed ... , as the one above might work, but 
will also send netmail destined for other Zones via node 2:5020/828 
regardless, whether that node has any connection to those zones or not ....

 MS> (the prefix "2:5020/828" here is just pattern or sample,
please do not
 MS> take it in consideration.)

In this example is is of no consequence what node number you use for the 
examples ...

 MS> and last question regarding binkd.cfg

 MS> now I have

 MS> domain fidonet \\home\\fido\\outbound  2
 MS> domain fidonet /home/fido/outbound 2

 MS> in both parts.

 MS> Could I set this as:

 MS> domain fidonet \\home\\fido\\outbound  *
 MS> domain fidonet /home/fido/outbound *

 MS> ?

Again I have not tried this, it might work, and if it does, the same problem 
exists as described above, that it will route all mail for ll zones, FidoNet 
FamilyNet, LinuxNet etc via you BOSS node regardless if he has connections to 
those networks ...

I do not believe that it will work, but you are welcome to try it and see what 
BinkD does ... , you might also ask these questions in BINKD.RU ...

 MS> Will such configuration work well or not?

 MS> i could set in config additional variable $VAR_ZONE

 MS> domain fidonet /home/fido/outbound $VAR_ZONE
 MS> domain fidonet \\home\\fido\\outbound  $VAR_ZON

 MS> and change $VAR_ZON after user input his ftn address in configurator.

 MS> but may be * for zone number suite fine? Or not?

As I have said, above, a lot of nodes/points are members of more than FidoNet, 
and as a result, the use of wildcards such as "*" are not
desirable for that 
reason ... , and thus safer to not use them, for FidoNet only systems ... , if 
they work, then no harm done ...

Russell

--- GoldED+/LNX 1.1.5