Hello everybody!

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.

In hpt config I've got:

LogLevels 123456789

name s2r
sysop JAS
location CABA

address 4:900/733

inbound /var/spool/ftn/inb/unsecure
protinbound /var/spool/ftn/inb
outbound /var/spool/ftn/outb

tempinbound /var/spool/ftn/tmp/inb
tempoutbound /var/spool/ftn/tmp/outb
[...]

How is this usually managed?


JAS


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hey Javier!

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.

In hpt config I've got:

LogLevels 123456789

name s2r
sysop JAS
location CABA

address 4:900/733

inbound /var/spool/ftn/inb/unsecure
protinbound /var/spool/ftn/inb
outbound /var/spool/ftn/outb

tempinbound /var/spool/ftn/tmp/inb
tempoutbound /var/spool/ftn/tmp/outb
[...]

How is this usually managed?

What are your route definitions for the node you're trying to send direct to? Assuming this/these are correct...

If you're trying to send direct netmail, your HPT route config should probably have a line like this (this is what I do):

route direct <link> <what to route>

So, if you want to send direct to 1:2/3, and you only want to send mail addressed to them, directly to them (ie, not route anything else):

route direct 1:2/3 1:2/3.*

Otherwise, if you want to route 1:2/* to 1:2/3:

route direct 1:2/3 1:2/*

First address is the one you want to send the mail to, and the second address is what you want to send to the first address (wildcards are accepted). You need to define something like this for every separate link you have, unless you route 1:* 2:* 3:* 4:* to one link. Also, put any direct links /above/ the 'catch-all' (1:* 2:* 3:* 4:*). For example:

route direct 1:154/10 1:154/10.*
route direct 1:229/426 1:* 2:* 3:* 4:*

Anything you netmail to 1:154/10.* would go directly to 1:154/10. Anything you netmail anywhere else, would route through 1:229/426 and let that system route it however they have setup to get it where it needs to go.

If the above is all correct and understood, and it still doesn't work.. then binkd is the next to check:

Did you setup a node definition for the node you want to send direct to? If not, are you using binkp.net? If neither, binkd won't know where to send it.

Hope that helps.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

19 Sep 25 19:20, you wrote to me:

This is my route config:

#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.

Hey Javier!

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.

In hpt config I've got:

LogLevels 123456789

name s2r
sysop JAS
location CABA

address 4:900/733

inbound /var/spool/ftn/inb/unsecure
protinbound /var/spool/ftn/inb
outbound /var/spool/ftn/outb

tempinbound /var/spool/ftn/tmp/inb
tempoutbound /var/spool/ftn/tmp/outb
[...]

How is this usually managed?

What are your route definitions for the node you're trying to send
direct to? Assuming this/these are correct...

If you're trying to send direct netmail, your HPT route config should probably have a line like this (this is what I do):

route direct <link> <what to route>

So, if you want to send direct to 1:2/3, and you only want to send
mail addressed to them, directly to them (ie, not route anything
else):

route direct 1:2/3 1:2/3.*

Otherwise, if you want to route 1:2/* to 1:2/3:

route direct 1:2/3 1:2/*

First address is the one you want to send the mail to, and the second address is what you want to send to the first address (wildcards are accepted). You need to define something like this for every separate
link you have, unless you route 1:* 2:* 3:* 4:* to one link. Also, put
any direct links /above/ the 'catch-all' (1:* 2:* 3:* 4:*). For
example:

route direct 1:154/10 1:154/10.*
route direct 1:229/426 1:* 2:* 3:* 4:*

Anything you netmail to 1:154/10.* would go directly to 1:154/10.
Anything you netmail anywhere else, would route through 1:229/426 and
let that system route it however they have setup to get it where it
needs to go.

If the above is all correct and understood, and it still doesn't
work.. then binkd is the next to check:

Did you setup a node definition for the node you want to send direct
to? If not, are you using binkp.net? If neither, binkd won't know
where to send it.

Hope that helps.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/10)

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hey Javier!

On Fri, 19 Sep 2025 22:22:22 -0300, you wrote:

# 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:*

For what it's worth, Fidonet doesn't have a zone 5 any more, so no need for '5:*' there. However, this has nothing to do with your issue.

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.

Seems as though hpt is doing it's job so far. Post your binkd.conf next (without passwords). I predict you may be trying to use some sort of 5D addressing when you may not need to.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

Here yo have my binkd.conf. Doesn't HPT support 5D addressing?

=== Cut ===
# Binkd sample configuration file for unix-like enviroment
# Copyright (C) 1996-1997 by Dima Maloff, 2:5047/13
# Copyright (C) 2013 by Binkd development team
# $Id$

#
# Path and name for the logfile, loglevel
#
log /var/log/binkd.log
loglevel 4

#
# Your FTN domains:
# domain <name> <main-outbound> <default-zone> [<root-domain>]
# or
# domain <new-name> alias-for <name>
# The first variant specifies a domain as a default domain for 3D/4D addresses. #
domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

#
# Aliases to support known wrong 5D configurations
#domain fido alias-for fidonet
#domain fsx alias-for fsxnet

#
# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet domain")
domain fidonet.org alias-for fidonet
domain fidonet.net alias-for fidonet
domain fsxnet.nz alias-for fsxnet

#
# Your addresses, 5D or 4D or 3D:
# address <addr1> ...
# If the first address is specified as a 3D/4D address, its domain will be
# taken from the domain defined in the first "domain" line. If more addresses
# are specified as 3D/4D ones, their domain will be taken from the first
# address.
#
address 4:900/733@fidonet 21:3/100.2@fsxnet
#
# Hide or present the specified AKAs if remote AKAs match the address mask
# hide-aka <my-aka> [!]<mask>
# present-aka <add-aka> [!]<mask>
# Mask is compared to the 5d-form of address string, '*' matches any number
# of any symbols (so you have to write '2:5020/*' but not '5020/*')
# Use '!' to invert the mask
# These rules apply in the same order as in config, you can present any address #
#hide-aka 2:5020/999.* !2:*@fidonet # hide aka from all but fido zone 2 #present-aka 2:5047/999.1 2:5047/*.0* # present aka to all nodes in 2:5047

#
# The name of your system, its location and your name
#
sysname "FIDONODO JAS | ¯\_(ツ)_/¯"
location "Ciudad de Buenos Aires, Argentina"
sysop "jas"

#
# System capabilities
#
nodeinfo 115200,TCP,BINKP

#
# Uncomment it if you want binkd log at your console
#
conlog 0

#
# If a log message matches one of these masks, it won't be written to log
# (masks are in shell/glob style, case-insensitive)
#
#nolog "*socket # [0-9]*"
#nolog "*.[bc]sy"

#
# Uncomment if you want T-Mail(FrontDoor)-style binary log
# (Will work and have sense on PCs only?)
#
#binlog binkd.sts
#fdinhist in.his
#fdouthist out.his

#
# TCP settings. Leave this unchanged if not sure.
#
# Suffixes for time intervals are w for weeks, d for days,
# h for hours, m for minutes, s or no suffix for seconds.
# You can mix the suffixes, i.e. 1d12h is the same as 36h.
#
#iport binkp
#oport binkp
#oblksize 4096
#timeout 5m
#connect-timeout 5m
#bindaddr 192.168.0.3
#listen *

#
# Zlib compression parameters (if built with zlib support)
# zlevel - compression level (zlib only, bzlib2 uses 100kb always),
# set to 0 to use default value of 6
# zminsize <size> - files smaller than <size> won't be compressed anyway
# Rules:
# zallow <mask1>[ <mask2>... <maskN>] - allow compression for the masks
# zdeny <mask1>[ <mask2>... <maskN>] - deny compression for the masks
# If remote accepts compressed blocks (OPT GZ), its name will be checked
# against these rules before sending each file. If the name matches a zallow
# rule, the file will be sent with compression. If the name matches a zdeny rule,
# it will be sent as-is. The rule matched first is applied. If a file doesn't
# match any rule, zdeny will be assumed.
#
#zminsize 1024
#
#zallow *.pkt
#zdeny *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa?
#zdeny *.zip *.rar *.arj *.ha *.gz *.tgz *.bz2 *.z[0-9][0-9] *.r[0-9][0-9] #zallow *

#
# Delay of calls and outbound rescans in seconds
#
call-delay 1m
rescan-delay 1m

#
# Max. number of inbound/outbound connections
#
#maxservers 2
#maxclients 2

#
# Binkd will try to call a node N times. If failed, it will
# hold the node for S seconds. The feature is off by default.
#
try 10
hold 10m

#
# Binkd will remove .try files after successful session.
# The feature is off by default.
#
remove-try-files

#
# hold-skipped <S>
# Binkd will hold for S seconds all mail skipped by a node. (Def. -- 1h)
#
#hold-skipped 1h

#
# Don't send (only receive) files if no password for an inbound session
#
send-if-pwd

# Tzoff corrects UTC time returned by time() under DOS-derived OS
# Using system TZ variable or tzselect(8) is preferred.
#tzoff 3h

#
# Use syslog (Only if made with -DHAVE_VSYSLOG and -DHAVE_FACILITYNAMES)
#
#syslog local0

#
# Print percents while sending or receiving
#
percents

#
# List queue after rescans
#
printq

#
# Perform reverse resolving (for logging only)
#
#backresolv

#
# Log pid:
#
#pid-file /usr/local/fido/ftn/binkd.pid
pid-file /var/run/binkd/binkd.pid

#
# Inbound directories for secure and non-secure links
#

inbound /var/spool/ftn/inb
inbound-nonsecure /var/spool/ftn/inb/unsecure

#
# Directory for incomplete receiving files (.hr and .dt),
# default to inbound for the node
#
temp-inbound /var/spool/ftn/inbound-temp

#
# Binkd will skip all files from a node if
# size_of_the_next_file_for_us_there + minfree < free_space_in_inbound
# The zero value and the value 4294967295 (2**32-1) are equivalent to infinity. #
minfree 2048
minfree-nonsecure 2048

#
# When trying to receive a new file: remove partial files with this
# name but different size or time from inbound. (If commented out, binkd
# will left old parts as .dt and .hr in the inbound directory).
#
kill-dup-partial-files

#
# Remove all old partial files from inbound. (OFF if commented out)
# kill-old-partial-files <max-age-in-seconds>
#
kill-old-partial-files 1d

#
# Remove old .bsy/.csy files (If some are left after a system crash). It would # be wise to set this to 12h on almost any system. (Note that binkd always
# touches .bsy's/.csy's for active sessions)
#
# kill-old-bsy is OFF by default.
#
kill-old-bsy 12h

#
# Create a flag file after receiving a file
#
#flag toss!.now *.pkt
#flag toss!.now *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa?

#
# Run an external program.
# The "*S" macro in command line substed with S.R.I.F., see !SRIF.TXT
# The "!" before program pathname means immediate program execution
# after receiving the file.
# *** win32 only:
# The "@" before program pathname means execute program in separate console
# The "@@" before program pathname means execute program in hidden console
# ***
# Macros: *F - complete name of received file,
# *A0..*A9 - first 10 AKA of remote system,
# *A*, *A@ - list of all remote AKA separated by spaces
# *P - password protected [0|1],
# *L - listed system [0|1]
# *H - remote hostname or IP,
# *N - short file name (win32 only).
#
#exec "!my-freq-processor /options *S" *.req
exec "!~/ftn/binkd/srifreq *S" *.req
#exec "my-pkt-unpacker /options *P *A* *F" *.[pP][kK][tT]
#exec "my-tosser /options" /opt/ftn/inbound-secure/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z]
exec "nice -n 19 /usr/local/bin/hpt -c /usr/local/fido/fidoconfig/config toss link" /var/spool/ftn/inb/*.[STFWMstfwm][ouaherOUAHER][0-9A-Za-z] *.[pP][kK][tT]
exec "nice -n 19 /usr/local/bin/htick -c /usr/local/fido/fidoconfig/config toss" /var/spool/ftn/inb/*.[Tt][Ii][Cc]
#exec "nice -n 19 /usr/local/bin/htick -c /usr/local/fido/fidoconfig/config toss link"

#
# Scan node outbound while connecting and send mail size to remote
#
prescan

# t-mail or ifcico (qico) password file.
# Format of the password file:
# [password] <FTN address> <inpwd>[,[<pktpwd>][,<outpwd>]]
# where:
# [password] optional "password" token;
# <FTN address> address of a link in the form 1:2/3.4@domain
# or 1:2/3@domain or 1:2/3 or 1:2/3.4;
# <inpwd> password for incoming sessions;
# <pktpwd> packet password, used when "share" token
# is handled;
# <outpwd> password for outgoing sessions.
# Any password is one word without spaces or tabs. If <pktpwd> or <outpwd>
# is omitted, it will be assumed equal to <inpwd>. If a password is defined for # a node by the "node" token, then the passwords for the node in the password
# file will be ignored.
#
#passwords ~/ftn/binkd/passwords

#
# Skip files:
# skip [all|listed|unlisted|secure|unsecure] [!]<sizeKb>|- <mask>...
#
# 'all' applies to all sessions (default)
# 'listed' applies to sessions with the nodes defined by 'node' keyword
# 'secure' applies to password-protected sessions
#
# Use '!' before size for destructive skip, default is non-destructive one.
# If <size> > 0, then only files larger than <size> in kilobytes will be skipped;
# zero <size> applies to all files;
# if the <size> is set to '-', then the rule will allow
# any file matching the <mask>.
#
# <mask> is a shell-style mask, case-insensitive (except for symbols in []),
# multiple masks for a rule are permitted.
#
# Policy for rule processing is first-match
#
#skip all 0 *.mp3 *.avi
#skip unsecure 256 *.pkt
#skip unsecure !0 *

#
# Overwrite the existing file by the new received,
# do not save with the changed extension
#
#overwrite net_*.*

#
# Inbound filename case:
# inboundcase [save(default)|upper|lower|mixed]
#
# 'save' don't change filename case (default)
# 'upper' uppercase filename (FILE-NAME.EXT)
# 'lower' lowercase filename (file-name.ext)
# 'mixed' make filename pretty (File-Name.Ext)
#
# * tested only with english filenames
#
#inboundcase save

#
# Should binkd send empty files?
# dont-send-empty [no(default)|arcmail|yes]
#
# 'no' inhibit only sending *.?ut (netmail) with size <=60 bytes
# 'arcmail' do not send zero-size arcmail and pkt <= 60 bytes
# 'yes' do not send all zero-size files and pkt <= 60 bytes
#
#dont-send-empty no

#
# Should binkd delete empty point dirs in BSO?
# Uncomment the following line if yes
#
deletedirs

# Define shared aka
# Add a shared-address as aka for any node from this list, so that
# uncompessed netmail for shared aka will be sent in the first session with # any node listed in shares; packet header will be updated to match this
# node's main aka and pkt password
# share <shared-address> <node1> [<node2> ...]
# example:
#share 2:999/999 2:5020/52 2:5020/238

#
# Check the sender's address in incoming pkt's, change the file extension
# to <ext> if the check failed.
# check-pkthdr [all|secure|unsecure|listed|unlisted] <ext>
#
# 'all' applies to all nodes;
# 'listed' will be applied if at least one aka is defined by 'node' keyword;
# 'secure' will be applied if at least one aka is password-protected.
#
# It's ok to specify .<ext> as well as <ext> - the dot before ext is ignored.
# The policy set by check-pkthdr may be overridden by -hc or -nohc flags
# in a 'node' definition (see below).
# Flag order: -nohc (for any aka), -hc (for any aka), check-pkthdr flag
#
#check-pkthdr secure .sec

#
# Define a link:
# node [[z:]n/]n[.p][@domain] [-nr|-nd] [-md] [-hc|-nohc] [-ip|-sip] [-bw <send_rate>[/<recv_rate>]] [-pipe <cmd>] [-4|-6] [{hosts|-} [{<inpwd>[,[<pktpwd>][,<outpwd>]]|-} [flavour [{obox|-} [{ibox|-}]]]]]
#
# * All non-"-" fields will redefine the values specified for the same node
# earlier in config.
# * The meaning of <inpwd>, <pktpwd> and <outpwd> is the same as in
# the description of the "passwords" token. Any password is one word
# without spaces or tabs. If <pktpwd> or <outpwd> is omitted, it will be
# assumed equal to <inpwd>.
# * Flavour is one of i, c, d, -, h and is the flavour for the outbound
# filebox ("obox").
# * Binkd sends from obox all non-dir entries NOT matching ".*" wildcard.
# EVERY TIME YOU PUT A FILE INTO OBOX, CHECK IF BINKD IS ABLE TO
# UNLINK IT. Otherwise, the session will never end.
# * Default for ibox is inbound or inbound-nosecure depending on the pwd field. # * Default for port is oport.
# * '-nr' stands for 'Not Reliable Link', this works only on outbound calls
# with another binkp/1.1 mailer. The option solves the only problem with
# binkd having not enough time to start receiving a file from
# non-zero offset before IP link's down, so don't use it unless you
# have this problem -- really not effective
# * '-nd' means "No Dupe Mode", this works only on outbound calls with
# another binkd 0.9.3 or higher. The option solves the problem with
# duplicating files when connection is lost but link is a bit slower
# than it is with "-nr" option.
# * '-md' means "Must have CRAM-MD5". This works only with the nodes using
# versions of binkd or argus supporting this method. Do not set it if
# your link can use an old version of binkd.
# * '-nomd' - do not use CRAM-MD5 for this node (send plain text password)
# * '-hc' enables check of sender address in pkt header for this node/aka
# (overrides the setting of the 'check-pkthdr' statement)
# * '-nohc' disables check of sender address in pkt header for this node/aka
# (overrides the setting of the 'check-pkthdr' statement)
# * '-ip' means "Remote IP check". In this case the node will be
# rejected if it comes not from one of its IP-addresses.
# Remote AKAs with bad IP-address will be dropped on outgoing calls.
# * '-sip' means "Strict remote IP check". Like "-ip", but node will be
# rejected if no IP-addresses are allowed ("-" or not resolved).
# Remote AKAs with bad IP-address will be dropped on outgoing calls.
# * '-bw' specifies bandwidth (rate) limit for this node.
# If one value is specified, it will be used as both send and recv limit. # If two values are specified, the first one will be for send and the
# second one for recv.
# The rate values are expected to be in the format '<rate>[kM%]|-'
# (see limit-rate keyword for detailed description).
# * '-noproxy' disables usage of proxy/socks server when calling this node
# (the node is expected to be inside local network).
# * '-pipe' means "run an external command for building a tunnel to the node". # '*H' macro is substituted by host and '*I' by port number.
# * '-4' only connect via IPv4
# * '-6' only connect via IPv6
# * '-64' binkd will first try to connect over IPv6, and in case of failure,
# it will try again over IPv4. Attention! To use the option, you need
# to compile binkd with the "--with-af-force" option.
# * '-46' binkd will first try to connect over IPv4, and in case of failure,
# it will try again over IPv6. Attention! To use the option, you need
# to compile binkd with the "--with-af-force" option.
# * Hosts is a list in form
# host1[:port1][;host2[:port2]] ...
# * Asterisk ('*') in the host list forces Binkd to perform
# 1:2/3.4 --> p4.f3.n2.z1.binkp.net translation for a node's
# Fido-address and IP lookup for the resulting FQDN in DNS.
# Root domain part ("binkp.net") can be changed with root-domain
# keyword.
#

#node 5047/999 -md hostname;* password i ~/ftn/personalboxes/to999 ~/ftn/personalboxes/from999
node 4:902/26@fidonet -md bbs.docksud.com.ar sdasdadsa
node 21:3/100@fsxnet -md n3.z21.bbs.dege.au daosdj31

#
# Default node flags. Binkd will call an unlisted node if "defnode" is defined. #
#defnode -nd *
=== Cut ===

20 Sep 25 06:23, you wrote to me:

Seems as though hpt is doing it's job so far. Post your binkd.conf
next (without passwords). I predict you may be trying to use some sort
of 5D addressing when you may not need to.

Regards,
Nick

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hey Javier!

On Sat, 20 Sep 2025 16:52:08 -0300, you wrote:

Here yo have my binkd.conf. Doesn't HPT support 5D addressing?

It looks like you don't have any means of contacting anyone in zone 2.

- No 'node' definitions.
- Not using binkp.net
- No binkd compatible nodelist included

You're going to have to pick one of the three, or binkd won't know where to connect.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

* Originally in fidosoft.husky
* Crossposted in binkd

Hi Javier.

20 Sep 25 16:52, you wrote to Nick Boel:

# The first variant specifies a domain as a default domain for 3D/4D addresses.
#
domain fidonet /var/spool/ftn/outb 4 fidonet

=======

You should use binkp.net here or just remove it. Now your binkd tries to resolve the domain .fidonet, which may not exist.

'Tommi

---
* Origin: nntps://news.fidonet.fi (2:221/1)

Hello Tommi!

22 Sep 25, Tommi Koivula wrote to Javier Sturman:

# The first variant specifies a domain as a default domain for
3D/4D addresses. # domain fidonet /var/spool/ftn/outb 4 fidonet

=======

You should use binkp.net here or just remove it. Now your binkd tries
to resolve the domain .fidonet, which may not exist.

Hm, sure? This config is working for me since my binkd installation. As far as i remember the domain is a fidonet "domain" and not an internet domain.

Those domain definition may be part of the 5D ftn style address.
I found an old btxe doc with:

Password 2:2476/7@fidonet passed valid, defines password "passed"
only for a node "2:2476/7" with
the CORRECT domain ("fidonet"). A
node 2:2476/7@anynet would get a
password failure.

This is an extension of password protection, 'cause with passwords only in
compiled nodelists binkley can normally not distinguish between a password
for "2:2476/7@anynet" and "2:2476/7@fidonet".



The main purpose of fidonet domains is to run different networks on the same zone number with overlapping net/node entries.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Javier!

20 Sep 25, Javier Sturman wrote to Nick Boel:

# domain <name> <main-outbound> <default-zone> [<root-domain>]

# The first variant specifies a domain as a default domain for 3D/4D addresses.

domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

The path for both domains is the same. Mail for net/node@fidonet goes to outb and mail for net/node@fsxnet goes to outb. Please check your outb for files, do they have a clear differency for domains within the file names?

As far as i remember the domains were made compatible for DOS and FAT 8.3 outbound file name conventions. The filename contains hex net/node adresses that's why the zone is defined in the config.

Scanning mail to that outb would result in one target node only. The *.?lo flowfile is for 40/441 and the directory for zone 4. Because both domains dive into the same outbound outb whoever 4:40/441 connects first will get the mail on hold.

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

address 4:900/733@fidonet 21:3/100.2@fsxnet

Above you set the fsxnet zone outbound to zone 4. If 21 is correct then it should be 21. In that case no domain is needed. As long you have seperate zones there is no need for domains.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai!

24 Sep 25 01:59, you wrote to me:

domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

The path for both domains is the same. Mail for net/node@fidonet goes
to outb and mail for net/node@fsxnet goes to outb. Please check your
outb for files, do they have a clear differency for domains within the file names?

The only way I see the files for fsxnet (21:*) is that the outbound directory has 21 in it.

fido:/var/spool/ftn$ ls -al
total 31
drwxrwx--- 14 fido fido 14 Sep 26 14:59 .
drwxr-xr-x 10 root wheel 10 May 18 19:50 ..
drwxrwx--- 2 fido fido 34 Sep 19 15:44 dupebase
drwxrwx--- 5 fido fido 5 Sep 15 12:50 filebase
drwxrwx--- 2 fido fido 2 May 18 19:50 fileboxes
drwxrwx--- 2 fido fido 2 May 18 19:10 flags
drwxrwx--- 3 fido fido 5 Sep 26 15:25 inb
drwxrwx--- 2 fido fido 2 Sep 26 15:25 inbound-temp
drwxrwx--- 5 fido fido 5 Jun 8 22:08 msgbase
drwxrwx--- 3 fido fido 3 Sep 26 15:25 outb
drwxr-xr-x 3 fido fido 3 Sep 26 07:35 outb.002
drwxrwx--- 3 fido fido 5 Sep 26 16:36 outb.015
drwxrwx--- 4 fido fido 4 Sep 16 11:47 tmp
drwxrwx--- 2 fido fido 2 May 18 19:50 transit
fido:/var/spool/ftn$ ls -ald outb.015/*
-rw-r--r-- 1 fido fido 0 Sep 26 15:00 outb.015/00030064.dlo
drwxrwx--- 2 fido fido 2 Sep 19 18:36 outb.015/00030064.sep
-rw-r--r-- 1 fido fido 23 Sep 26 16:36 outb.015/00030064.try fido:/var/spool/ftn$ cat outb.015/00030064.try
Cannot getaddrinfofid

It seems that binkd doesn't seem to resolv 21:3/100 however if I do a ns lookup it resolves.

fido:/var/spool/ftn$ drill f100.n3.z21.fsxnet.nz
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 13460
;; flags: qr rd ra ; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; f100.n3.z21.fsxnet.nz. IN A

;; ANSWER SECTION:
f100.n3.z21.fsxnet.nz. 21597 IN CNAME clrghouz.bbs.dege.au. clrghouz.bbs.dege.au. 3597 IN CNAME ip4.bbs.dege.au. ip4.bbs.dege.au. 3597 IN A 139.99.135.199

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 5011 msec
;; SERVER: 10.10.20.150
;; WHEN: Fri Sep 26 16:40:22 2025
;; MSG SIZE rcvd: 107

As far as i remember the domains were made compatible for DOS and FAT
8.3 outbound file name conventions. The filename contains hex net/node adresses that's why the zone is defined in the config.

Scanning mail to that outb would result in one target node only. The
*.?lo flowfile is for 40/441 and the directory for zone 4. Because
both domains dive into the same outbound outb whoever 4:40/441
connects first will get the mail on hold.

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

address 4:900/733@fidonet 21:3/100.2@fsxnet

Above you set the fsxnet zone outbound to zone 4. If 21 is correct
then it should be 21. In that case no domain is needed. As long you
have seperate zones there is no need for domains.

I will try removing both 4s from the config and keep trying.

Also I don't understand why does the tosser packer create a directory for the point although it should have been for the bossnode of that point.

fido:/var/spool/ftn$ ls -ald outb.002/*
drwxr-xr-x 3 fido fido 6 Sep 26 16:41 outb.002/00dd0001.pnt fido:/var/spool/ftn$ ls -ald outb.002/*/*
-rw------- 1 fido fido 767 Sep 26 00:28 outb.002/00dd0001.pnt/0000003a.dut -rw-r--r-- 1 fido fido 10 Sep 26 16:41 outb.002/00dd0001.pnt/0000003a.hld drwxr-xr-x 2 fido fido 2 Sep 26 00:28 outb.002/00dd0001.pnt/0000003a.sep -rw-r--r-- 1 fido fido 23 Sep 26 16:41 outb.002/00dd0001.pnt/0000003a.try fido:/var/spool/ftn$ cat outb.002/00dd0001.pnt/0000003a.try

And in binkd.log
-+-
26 Sep 16:32:17 [72994] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:32:17 [74073] rc(72994)=0
26 Sep 16:33:17 [73201] call to 2:221/1.58@fidonet
26 Sep 16:33:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:33:17 [73202] call to 21:3/100@fidonet
26 Sep 16:33:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:33:17 [73201] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:33:17 [73202] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:33:17 [74073] rc(73202)=0
26 Sep 16:33:17 [74073] rc(73201)=0
26 Sep 16:34:17 [73399] call to 2:221/1.58@fidonet
26 Sep 16:34:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:34:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:34:17 [73400] call to 21:3/100@fidonet
26 Sep 16:34:17 [73399] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:34:17 [73400] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:34:17 [74073] rc(73399)=0
26 Sep 16:34:17 [74073] rc(73400)=0
26 Sep 16:35:17 [73605] call to 2:221/1.58@fidonet
26 Sep 16:35:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:35:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:35:17 [73606] call to 21:3/100@fidonet
26 Sep 16:35:17 [73605] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:35:17 [73606] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:35:17 [74073] rc(73605)=0
26 Sep 16:35:17 [74073] rc(73606)=0
26 Sep 16:36:17 [73813] call to 2:221/1.58@fidonet
26 Sep 16:36:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:36:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:36:17 [73814] call to 21:3/100@fidonet
26 Sep 16:36:17 [73813] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:36:17 [73814] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:36:17 [74073] rc(73814)=0
26 Sep 16:36:17 [74073] rc(73813)=0
26 Sep 16:37:17 [74014] call to 2:221/1.58@fidonet
26 Sep 16:37:17 [74073] 2:221/1.58@fsxnet busy, skipping
26 Sep 16:37:17 [74015] call to 21:3/100@fidonet
26 Sep 16:37:17 [74073] 21:3/100@fsxnet busy, skipping
26 Sep 16:37:17 [74014] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:37:17 [74015] getaddrinfo failed: Name does not resolve (8)
26 Sep 16:37:17 [74073] rc(74015)=0
26 Sep 16:37:17 [74073] rc(74014)=0
-+-

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hey Kai!

On Wed, 24 Sep 2025 01:59:32 , you wrote:

# domain <name> <main-outbound> <default-zone> [<root-domain>]

# The first variant specifies a domain as a default domain for
3D/4D addresses.

domain fidonet /var/spool/ftn/outb 4 fidonet
domain fsxnet /var/spool/ftn/outb 4 fsxnet

The path for both domains is the same. Mail for net/node@fidonet goes to outb and mail for net/node@fsxnet goes to outb. Please check your outb
for files, do they have a clear differency for domains within the file names?

This is how 4D addressing works. binkd will automatically create the "outb" folder for zone 4, and then the fsxnet folder will be outb.015

As far as i remember the domains were made compatible for DOS and FAT
8.3 outbound file name conventions. The filename contains hex net/node adresses that's why the zone is defined in the config.

Only when using 5D addressing.

Scanning mail to that outb would result in one target node only. The
*.?lo flowfile is for 40/441 and the directory for zone 4. Because both domains dive into the same outbound outb whoever 4:40/441 connects first will get the mail on hold.

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

Just as well, and in his case, he mixed up the "root-domain" with "domain". The last option should not be 'fidonet' or 'fsxnet'. In Fidonet's case, it should be binkp.net. If fsxnet has a root-domain that can be looked up, that should be there instead.

address 4:900/733@fidonet 21:3/100.2@fsxnet

Above you set the fsxnet zone outbound to zone 4. If 21 is correct then
it should be 21. In that case no domain is needed. As long you have
seperate zones there is no need for domains.

Only when using 5D addressing, which he is not. Please don't confuse him more than he already is. :/

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hey Javier!

On Fri, 26 Sep 2025 16:36:02 -0300, you wrote:

The only way I see the files for fsxnet (21:*) is that the outbound directory has 21 in it.

If you are already going to change your configuration without trying my previous suggestion(s), don't bother trying those suggestions, as they probably won't work since you've changed your config... again.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (1:154/10)

Hello Nick!

26 Sep 25 20:08, you wrote to me:

I deleted all outbound directories and then modified my binkd.conf based on this config file I was directed in another network.
Now it works. (https://nrbbs.net/binkd-linux.txt)

Hey Javier!

On Fri, 26 Sep 2025 16:36:02 -0300, you wrote:

The only way I see the files for fsxnet (21:*) is that the outbound
directory has 21 in it.

If you are already going to change your configuration without trying
my previous suggestion(s), don't bother trying those suggestions, as
they probably won't work since you've changed your config... again.

Regards,
Nick

... Sarcasm: because beating people up is illegal.
--- GoldED+/LNX 1.1.5-b20250409
* Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
(1:154/10)

Javier


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hi Kai.

24 Sep 25 01:42:32, you wrote to me:

# The first variant specifies a domain as a default domain for
3D/4D addresses. # domain fidonet /var/spool/ftn/outb 4 fidonet

=======

You should use binkp.net here or just remove it. Now your binkd
tries to resolve the domain .fidonet, which may not exist.

Hm, sure?

Yes.

'Tommi

---
* Origin: Point One (2:221/1.1)

Hello Nick!

26 Sep 25, Nick Boel wrote to Kai Richter:

# domain <name> <main-outbound> <default-zone> [<root-domain>]

# Aliases to support known DNS domain zones
# (some people mix up the terms "FTN domain" and "DNS internet
domain")

That's the key element. Do not mix up.

Just as well, and in his case, he mixed up the "root-domain" with "domain". The last option should not be 'fidonet' or 'fsxnet'. In Fidonet's case, it should be binkp.net. If fsxnet has a root-domain
that can be looked up, that should be there instead.

Then root-domain does stand for "DNS internet domain"?

Above you set the fsxnet zone outbound to zone 4. If 21 is correct
then it should be 21. In that case no domain is needed. As long you
have seperate zones there is no need for domains.

Only when using 5D addressing, which he is not. Please don't confuse
him more than he already is. :/

I do apologize. I think there are three issues within the config. I would choose different outbounds for the domains, then each domain could have it's own zone breakdown subdirs.

The DNS lookups was already explained by Tommi but i did not understand fully because there was no root-domain reference mentioned.

The third one is point to bossnode routing. I think that could be fixed later.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Tommi!

27 Sep 25, Tommi Koivula wrote to Kai Richter:

# The first variant specifies a domain as a default domain for
3D/4D addresses. # domain fidonet /var/spool/ftn/outb 4 fidonet

=======

+++++++

You should use binkp.net here or just remove it. Now your binkd
tries to resolve the domain .fidonet, which may not exist.

Hm, sure?

Yes.

Sorry, the position of the originating underscore (+++) and domain fidonet pointed me to the first fidonet keyword. Now it does make sense.

Maybe we could turn to fully edited config lines to avoid confusion. ;-)

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

Hello Kai!

27 Sep 25 18:03, you wrote to Nick Boel:

Above you set the fsxnet zone outbound to zone 4. If 21 is correct
then it should be 21. In that case no domain is needed. As long
you have seperate zones there is no need for domains.

Only when using 5D addressing, which he is not. Please don't
confuse him more than he already is. :/

I do apologize. I think there are three issues within the config. I
would choose different outbounds for the domains, then each domain
could have it's own zone breakdown subdirs.

At first tried to do that but HPT doesn't allow to specify an outbound directory for each link. I has support for 5D addressing but not everywhere.

The DNS lookups was already explained by Tommi but i did not
understand fully because there was no root-domain reference mentioned.

The third one is point to bossnode routing. I think that could be
fixed later.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)

s2r


--- GoldED+/BSD 1.1.5-b20170303-b20170303 + HPT 1.9.0 + Binkd 1.1a-115
* Origin: FIDONODO DE JAS | ¯\_(O,O)_/¯ (4:900/733)

Hello Javier!

30 Sep 25, Javier Sturman wrote to Kai Richter:

At first tried to do that but HPT doesn't allow to specify an outbound directory for each link.

What about "Filebox"? I used it for my points "hold" directory. Each point had it's own.

Regards

Kai

--- GoldED+/LNX 1.1.4.7
* Origin: Monobox (2:240/77)