Servus Russell!

Am 13 Jan 07, Russell Tiedt schrieb an All:

 RT> Route all traffic for nodes  5:7211/1 and all points i.e. 5:7211/* to
 RT> 5:7211/1 and all other mail to 5:7105/1 out to the rest of fidonet.

 RT> Currently,
 RT> route crash 5:7105/1 1:* 2:* 3:* 4:* 5:* 6:*

 RT> how do I make an exception for 5:7211/1?

You can not. The concept of routing do not have a "do not".
The routing have "do" actions only.

Sorry, my makeinfo does not work, but here is the part out of the hpt.texi
documentation of the source:

....
Syntax:
route    [ ...]

linkWW is a dos pattern with ? and *.

Route statements are parsed in descending order:
Pseudo-code:

  1) actual = first statement

  2) if linkWWW = msg-destination using pattern matching

  2a) take this routing and return

  2b) else actual = next statement

  3) jump to 2)
....

This logic shows the way the routing work. If you have exceptions you must
define them first.

hpt takes the message and check the destination until one condition matches.

You have to define the routing from the most detail to more general.

route crash 5:7211/1   5:7211/1.*
route crash 5:7105/1   1:* 2:* 3:* 4:* 5:* 6:*

The first line routes all mail of 7211/1.* (*=including 0 == 7211/1) to 7211/1.

You can say that after that line there is no mail left for 7211/1 because
it is already send. That may be technically wrong, but logically easy to
understand.

At the second line there is no mail left for 7211/1 and if you don't have
mail you can not send it to 7105/1. But if there is other mail left it will
match the wildcard * and send to 7105/1.

If you put the second line first, all mail will be send to 7105/1 and if
the routing to 7701/1 applies there is no mail left at all.

That is why the "first condition hit" and the detailed routes
must defined first.

For your and my example mail to zones 7:* 8:* n:*.... will not be send any
way, because no condition match.

Tschuess

Kai

--- GoldED+/LNX 1.1.4.7