#EN# Don`t route mail to zone adresses
route no-pack *:0/*
# Mails an Points auf "hold" setzen
route hold noroute 4:900/733.*
## ruteo para points va a nodos
route crash boss *:*/*.*
# Mails an 1:*, 2:*, 3:*, 4:* und 5:* sofort an
route crash 4:902/26 1:* 2:* 3:* 4:* 5:*
route crash 21:3/100 21:*
#EN# Don`t route 0:, 32767:, etc.
route no-pack *
I don`t have a node definition for the bossnode of the point I`d
like to contact however the node is listed in the nodelist.
NB> Hey Javier!
NB> On Fri, 19 Sep 2025 15:51:26 -0300, you wrote:
>> I was wondering if somebody could help me with what it looks like a
>> routing problem with hpt. When I create compose a netmail and would
>> like to send it direct hpt creates a new outbound directory for the
>> destination zone but that directory is not where binkd look for.
NB> What are your route definitions for the node you`re trying to send NB> direct to? Assuming this/these are correct...
NB> If you`re trying to send direct netmail, your HPT route config should NB> probably have a line like this (this is what I do):
NB> route direct
NB> So, if you want to send direct to 1:2/3, and you only want to send NB> mail addressed to them, directly to them (ie, not route anything NB> else):
NB> route direct 1:2/3 1:2/3.*
NB> Otherwise, if you want to route 1:2/* to 1:2/3:
NB> route direct 1:2/3 1:2/*
NB> First address is the one you want to send the mail to, and the second NB> address is what you want to send to the first address (wildcards are NB> accepted). You need to define something like this for every separate NB> link you have, unless you route 1:* 2:* 3:* 4:* to one link. Also, put NB> any direct links /above/ the `catch-all` (1:* 2:* 3:* 4:*). For NB> example:
NB> route direct 1:154/10 1:154/10.* NB> route direct 1:229/426 1:* 2:* 3:* 4:*
NB> Anything you netmail to 1:154/10.* would go directly to 1:154/10. NB> Anything you netmail anywhere else, would route through 1:229/426 and NB> let that system route it however they have setup to get it where it NB> needs to go.
NB> If the above is all correct and understood, and it still doesn`t NB> work.. then binkd is the next to check:
NB> Did you setup a node definition for the node you want to send direct NB> to? If not, are you using binkp.net? If neither, binkd won`t know NB> where to send it.
NB> Hope that helps.
NB> Regards, NB> Nick
NB> ... Sarcasm: because beating people up is illegal. NB> --- GoldED+/LNX 1.1.5-b20250409 NB> * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) NB> (1:154/10)