I was reading the wiki today, trying to figure out how to use the echolist keys and not getting anywhere when I stumbled across something I have been meaning to ask about. Using the example below, which is from the wiki but modified somewhat:

[node:1:218/700]
Comment = My Hub
AreafixPwd =
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
[node:1:2320/105]
Comment = Another node I connect with
AreafixPwd =
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
[node:1:ALL]
Comment = Everyone in FidoNet Zone 1
AreafixPwd =
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
Route = 1:218/700

With this example, what happens to packets that are created for 1:2320/105? Do they wait for 1:2320/105 to pick them up/for them to get delivered, or will it see the "Route" keyword and send everything to 1:218/700?

I don't have that issue for other zones (othernets) I connect with, and I have never really thought I had reason to use "Route," but I have two connections for FIDO and sometimes do need to send netmail to nodes I don't connect with.
I don't want netmail/packets for connection #2 going to connection #1, but I do want ALL other Zone 1 traffic going to connection #1.

Thanks!

---
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

Re: sbbsecho.ini ROUTE keyword
By: Dumas Walker to All on Tue Jul 24 2018 12:47 pm

With this example, what happens to packets that are created for 1:2320/105? Do they wait for 1:2320/105 to pick them up/for them to get delivered, or will it see the "Route" keyword and send everything to 1:218/700?

Mail for any unlisted (in sbbsecho.ini) nodes will go to #1 but mail for #2 will be set to normal status and sent on the next binkout or binkpoll (if set to true) event.

I don't have that issue for other zones (othernets) I connect with, and I have never really thought I had reason to use "Route," but I have two connections for FIDO and sometimes do need to send netmail to nodes I don't connect with. I don't want netmail/packets for connection #2 going to connection #1, but I do want ALL other Zone 1 traffic going to connection #1.

I think this config will do what you want. However, standard disclaimers apply.. :)

Ttyl :-),
Al


... All those updates, and still imperfect!

---
þ Synchronet þ The Rusty MailBox - Penticton, BC Canada

Re: sbbsecho.ini ROUTE keyword
By: Dumas Walker to All on Tue Jul 24 2018 12:47 pm

I was reading the wiki today, trying to figure out how to use the echolist keys and not getting anywhere when I stumbled across something I have been meaning to ask about. Using the example below, which is from the wiki but modified somewhat:

[node:1:218/700]
Comment = My Hub
AreafixPwd =
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
[node:1:2320/105]
Comment = Another node I connect with
AreafixPwd =
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
[node:1:ALL]
Comment = Everyone in FidoNet Zone 1
AreafixPwd =
PacketPwd =
PacketType = 2+
Archive = ZIP
Inbox =
Outbox =
Passive = false
Direct = false
Notify = false
Keys =
Status = Normal
Route = 1:218/700

With this example, what happens to packets that are created for 1:2320/105? Do they wait for 1:2320/105 to pick them up/for them to get delivered, or will it see the "Route" keyword and send everything to 1:218/700?

It would use the normal delivery (not crash or hold) and not routed. Whether its "waits" or not is a function of the mailer and how you handle that link in your mailer configuration.

Since the 1:2320/105 address is specifically listed, that's the configuration it'll use. The 1:ALL is a "fall-through" for any *other* 1:* node and in that case, the mail (netmail) would be routed through 1:218/700.

I don't want netmail/packets for connection #2 going to connection #1, but I do want ALL other Zone 1 traffic going to connection #1.

That's what you have. :-)

digital man

Synchronet/BBS Terminology Definition #54:
UART = Universal Asynchronous Receiver/Transmitter
Norco, CA WX: 99.6øF, 33.0% humidity, 9 mph ENE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

With this example, what happens to packets that are created for
1:2320/105? Do they wait for 1:2320/105 to pick them up/for them to get >DW> delivered, or will it see the "Route" keyword and send everything to
1:218/700?

Mail for any unlisted (in sbbsecho.ini) nodes will go to #1 but mail for #2 will be set to normal status and sent on the next binkout or binkpoll (if set to true) event.

[...]

I think this config will do what you want. However, standard disclaimers apply.. :)

Awesome! I thought it would but was not certain I was reading it
correctly. Thanks!

---
þ SLMR 2.1a þ http://www.indyracing.com
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net

I don't want netmail/packets for connection #2 going to connection #1, but I >> do want ALL other Zone 1 traffic going to connection #1.

That's what you have. :-)

Wooo-hoo! Thanks!

---
þ SLMR 2.1a þ ???
þ Synchronet þ CAPCITY2 * CCO BBS * capcity2.synchro.net