* 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 19:52, you wrote to me:

I changed it to binkp.net

#
domain fidonet /var/spool/ftn/outb 4 binkp.net
domain fsxnet /var/spool/ftn/outb 4 fsxnet.nz

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

Still doesn't send messages to other zones.

fido:~/fidoconfig$ ls -ald /var/spool/ftn/outb*/*
drwxr-xr-x 3 fido fido 4 Sep 22 16:32 /var/spool/ftn/outb.001/009902f5.pnt -rwxr-xr-x 1 fido fido 6317 Sep 24 00:30 /var/spool/ftn/outb.002/00dd0001.cut drwxr-xr-x 3 fido fido 4 Sep 22 16:06 /var/spool/ftn/outb.002/00dd0001.pnt drwxr-xr-x 2 fido fido 2 Sep 19 13:31 /var/spool/ftn/outb.002/00dd0001.sep -rw------- 1 fido fido 392 Sep 22 15:47 /var/spool/ftn/outb.002/00dd0168.cut drwxr-xr-x 2 fido fido 2 Sep 22 15:47 /var/spool/ftn/outb.002/00dd0168.sep drwxr-xr-x 2 fido fido 2 Sep 19 18:36 /var/spool/ftn/outb.015/00030064.sep drwxr-xr-x 2 fido fido 2 Sep 24 21:16 /var/spool/ftn/outb/0386001a.sep

* 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)

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

24 Sep 25 21:17, you wrote to me:

I changed it to binkp.net

#
domain fidonet /var/spool/ftn/outb 4 binkp.net

Still doesn't send messages to other zones.

How is your defnode setting?

# Default node flags. Binkd will call an unlisted node if "defnode" defined. defnode -nr *

'Tommi

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

Hello Tommi!

25 Sep 25 07:10, you wrote to me:

At first I had it uncommented but binkd tried to contact sometimes to invented hosts mixing for example a zone for fidonet and the hub for fsxnet. Then I commented it out.
Now I enabled it again, this are the created directories still no outgoing connection initiated.


---hpt scan/pack log---
1 09:01:57 Scanning area: fsx_gen
1 09:01:57 Scanning area: fsx_gaming
1 09:01:57 Scanning area: fsx_tst
1 09:01:57 Scanning area: fsx_retro
1 09:01:57 Scanning area: fidosoft.husky
1 09:01:57 Start packing...
1 09:01:57 EchoTossLogFile not found -> Scanning all areas
1 09:01:57 Scanning NetmailArea NETMAIL
7 09:01:57 Msg packed with flavour 'direct': 4:900/733 -> 2:221/1.58
1 09:01:57 End
-+-


fido:/var/spool/ftn$ ls -ald outb.002/00dd0001.pnt/
drwxr-xr-x 3 fido fido 4 Sep 25 09:01 outb.002/00dd0001.pnt/ fido:/var/spool/ftn$ ls -ald outb.002
drwxr-xr-x 5 fido fido 7 Sep 25 01:06 outb.002
fido:/var/spool/ftn$ ls -ald outb.002/*
-rwxr-xr-x 1 fido fido 6317 Sep 24 00:30 outb.002/00dd0001.cut
drwxr-xr-x 3 fido fido 4 Sep 25 09:01 outb.002/00dd0001.pnt
drwxr-xr-x 2 fido fido 2 Sep 19 13:31 outb.002/00dd0001.sep
-rw------- 1 fido fido 392 Sep 22 15:47 outb.002/00dd0168.cut
drwxr-xr-x 2 fido fido 2 Sep 22 15:47 outb.002/00dd0168.sep fido:/var/spool/ftn$ ls -ald outb.002/00dd0001.pnt/*
-rwxr-xr-x 1 fido fido 3458 Sep 25 09:01 outb.002/00dd0001.pnt/0000003a.dut drwxr-xr-x 2 fido fido 2 Sep 19 13:25 outb.002/00dd0001.pnt/0000003a.sep

Hi Javier.

24 Sep 25 21:17, you wrote to me:

I changed it to binkp.net

#
domain fidonet /var/spool/ftn/outb 4 binkp.net

Still doesn't send messages to other zones.

How is your defnode setting?

# Default node flags. Binkd will call an unlisted node if "defnode" defined. defnode -nr *

'Tommi

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

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)

Hello Tommi!

25 Sep 25 09:04, I wrote to you:

I kept troubleshooting and I found that the binkd process was not getting properly shutdown. After starting it cleanly I see on the error log many outgoind connections but with undesired netowrks and zones combination.

---------------
26 Sep 00:05:24 [72508] BEGIN, binkd/1.1a-115/FreeBSD -D /usr/local/etc/binkd.conf
26 Sep 00:05:24 [72510] clientmgr started
26 Sep 00:05:24 [72509] servmgr started
26 Sep 00:05:24 [72509] servmgr listen on *:24554
26 Sep 00:05:24 [72510] 2:221/360@fsxnet busy, skipping
26 Sep 00:05:24 [72511] call to 2:221/360@fidonet
26 Sep 00:05:24 [72511] trying f360.n221.z2.binkp.net [51.38.115.207]...
26 Sep 00:05:24 [72512] call to 1:153/757.21@fidonet
26 Sep 00:05:24 [72510] 1:153/757.21@fsxnet busy, skipping
26 Sep 00:05:24 [72513] call to 2:221/1.58@fidonet
26 Sep 00:05:24 [72510] 2:221/1.58@fsxnet busy, skipping
26 Sep 00:05:24 [72510] 21:3/100@fsxnet busy, skipping
26 Sep 00:05:24 [72514] call to 21:3/100@fidonet
26 Sep 00:05:24 [72513] getaddrinfo failed: Name does not resolve (8)
26 Sep 00:05:24 [72512] getaddrinfo failed: Name does not resolve (8)
26 Sep 00:05:24 [72514] getaddrinfo failed: Name does not resolve (8)
26 Sep 00:05:24 [72510] rc(72513)=0
26 Sep 00:05:24 [72510] rc(72512)=0
26 Sep 00:05:24 [72510] rc(72514)=0
26 Sep 00:05:24 [72511] connected
26 Sep 00:05:24 [72511] outgoing session with f360.n221.z2.binkp.net:24554 [51.38.115.207]
26 Sep 00:05:25 [72511] OPT CRAM-MD5-3ddd7d18814bc8fce99c684810644bee
26 Sep 00:05:25 [72511] Remote requests MD mode
26 Sep 00:05:25 [72511] SYS news.fidonet.fi
26 Sep 00:05:25 [72511] ZYZ Tommi Koivula
26 Sep 00:05:25 [72511] LOC EU
26 Sep 00:05:25 [72511] NDL CM,IBN
26 Sep 00:05:25 [72511] TIME Fri, 26 Sep 2025 06:05:25 +0300
26 Sep 00:05:25 [72511] VER binkd/1.1a-115/Linux binkp/1.1
26 Sep 00:05:25 [72511] addr: 2:221/6@fidonet
26 Sep 00:05:25 [72511] called 2:221/360@fidonet, but remote has no such AKA
26 Sep 00:05:25 [72511] done (to 2:221/360@fidonet, failed, S/R: 0/0 (0/0 bytes))
26 Sep 00:05:25 [72511] session closed, quitting...
26 Sep 00:05:25 [72510] rc(72511)=0

---------------

Hello Tommi!

25 Sep 25 07:10, you wrote to me:

At first I had it uncommented but binkd tried to contact sometimes to invented hosts mixing for example a zone for fidonet and the hub for fsxnet. Then I commented it out. Now I enabled it again, this are the created directories still no outgoing connection initiated.

---hpt scan/pack log---
1 09:01:57 Scanning area: fsx_gen
1 09:01:57 Scanning area: fsx_gaming
1 09:01:57 Scanning area: fsx_tst
1 09:01:57 Scanning area: fsx_retro
1 09:01:57 Scanning area: fidosoft.husky
1 09:01:57 Start packing...
1 09:01:57 EchoTossLogFile not found -> Scanning all areas
1 09:01:57 Scanning NetmailArea NETMAIL
7 09:01:57 Msg packed with flavour 'direct': 4:900/733 -> 2:221/1.58
1 09:01:57 End
-+-

fido:/var/spool/ftn$ ls -ald outb.002/00dd0001.pnt/
drwxr-xr-x 3 fido fido 4 Sep 25 09:01 outb.002/00dd0001.pnt/ fido:/var/spool/ftn$ ls -ald outb.002
drwxr-xr-x 5 fido fido 7 Sep 25 01:06 outb.002
fido:/var/spool/ftn$ ls -ald outb.002/*
-rwxr-xr-x 1 fido fido 6317 Sep 24 00:30 outb.002/00dd0001.cut
drwxr-xr-x 3 fido fido 4 Sep 25 09:01 outb.002/00dd0001.pnt
drwxr-xr-x 2 fido fido 2 Sep 19 13:31 outb.002/00dd0001.sep
-rw------- 1 fido fido 392 Sep 22 15:47 outb.002/00dd0168.cut
drwxr-xr-x 2 fido fido 2 Sep 22 15:47 outb.002/00dd0168.sep fido:/var/spool/ftn$ ls -ald outb.002/00dd0001.pnt/*
-rwxr-xr-x 1 fido fido 3458 Sep 25 09:01 outb.002/00dd0001.pnt/0000003a.dut drwxr-xr-x 2 fido fido 2 Sep 19 13:25 outb.002/00dd0001.pnt/0000003a.sep

Hi Javier.

24 Sep 25 21:17, you wrote to me:

I changed it to binkp.net

#
domain fidonet /var/spool/ftn/outb 4 binkp.net

Still doesn't send messages to other zones.

How is your defnode setting?

# Default node flags. Binkd will call an unlisted node if
"defnode" defined. defnode -nr *

'Tommi

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

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)

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)

Javier Sturman wrote:

25 Sep 25 09:04, I wrote to you:

I kept troubleshooting and I found that the binkd process was not
getting properly shutdown. After starting it cleanly I see on the
error log many outgoind connections but with undesired netowrks and
zones combination.

...

f360.n221.z2.binkp.net:24554 [51.38.115.207]

...

26 Sep 00:05:25 [72511] ZYZ Tommi Koivula
26 Sep 00:05:25 [72511] LOC EU
26 Sep 00:05:25 [72511] NDL CM,IBN
26 Sep 00:05:25 [72511] TIME Fri, 26 Sep 2025 06:05:25 +0300
26 Sep 00:05:25 [72511] VER binkd/1.1a-115/Linux binkp/1.1
26 Sep 00:05:25 [72511] addr: 2:221/6@fidonet
26 Sep 00:05:25 [72511] called 2:221/360@fidonet, but remote has no
such AKA 26 Sep 00:05:25 [72511] done (to 2:221/360@fidonet,
failed, S/R: 0/0 (0/0 bytes))
26 Sep 00:05:25 [72511] session closed, quitting...
26 Sep 00:05:25 [72510] rc(72511)=0

Now your binkd here is using the standard binkp port instead of what is
in the nodelist and in the binkp.net dns srv record. :(

I've seen this happening in windows...

1 09:01:57 Scanning NetmailArea NETMAIL
7 09:01:57 Msg packed with flavour 'direct': 4:900/733 ->
2:221/1.58 1 09:01:57 End
-+-

Routing direct for points not your own might not be the best idea. ;)

How about "route crash boss ..."

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)

Hello Tommi!

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

Javier Sturman wrote:

f360.n221.z2.binkp.net:24554 [51.38.115.207]

Now your binkd here is using the standard binkp port instead of what
is in the nodelist and in the binkp.net dns srv record. :(

I've seen this happening in windows...

I'm running binkd in a FreeBSD jail.

1 09:01:57 Scanning NetmailArea NETMAIL
7 09:01:57 Msg packed with flavour 'direct': 4:900/733 ->
2:221/1.58 1 09:01:57 End
-+-

Routing direct for points not your own might not be the best idea. ;)

How about "route crash boss ..."

This is what I've got for my routing in HPT, exactly that.

-+-
fido:~/fidoconfig$ cat route
#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:*
route crash 21:3/100 21:*

#EN# Don't route 0:, 32767:, etc.
route no-pack *
-+-

'Tommi

--- FastEcho/2 1.46.1 Revival
* Origin: nntp://rbb.fidonet.fi - Finland (2:221/360.0)

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, 26 Sep 2025 15:48:04 -0300, you wrote:

1 09:01:57 Scanning NetmailArea NETMAIL
7 09:01:57 Msg packed with flavour 'direct': 4:900/733 ->
2:221/1.58 1 09:01:57 End
-+-

Seems to me as though you've changed settings /since/ creating that netmail. One of your original binkd logs was this:

26 Sep 00:05:24 [72510] 2:221/360@fsxnet busy, skipping
26 Sep 00:05:24 [72511] call to 2:221/360@fidonet 26 Sep 00:05:24 [72511] trying f360.n221.z2.binkp.net [51.38.115.207]...
26 Sep 00:05:24 [72512] call to 1:153/757.21@fidonet 26 Sep 00:05:24 [72510] 1:153/757.21@fsxnet busy, skipping 26 Sep 00:05:24 [72513] call to 2:221/1.58@fidonet 26 Sep 00:05:24 [72510] 2:221/1.58@fsxnet busy, skipping 26 Sep 00:05:24 [72510] 21:3/100@fsxnet busy, skipping 26 Sep 00:05:24 [72514] call to 21:3/100@fidonet

Which seems that at some point you were trying to route directly to point systems.

How about "route crash boss ..."

This is what I've got for my routing in HPT, exactly that.

-+-
fido:~/fidoconfig$ cat route
#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:*
route crash 21:3/100 21:*

#EN# Don't route 0:, 32767:, etc.
route no-pack *
-+-

I'd suggest you backup and delete your netmails that are stuck in your outbound directories, as well as your .?ut files, and when everything is clear and binkd stops trying to connect to systems it shouldn't be.. write 1 new netmail with these current settings and watch your logs to see if there are any more errors.

binkd is definitely seeing these outbound folders now, which was one of your original issues. I think you created these netmails before you even had binkd working, and then you changed settings, and now binkd is having issues with old routing statements.

Am I close? ;)

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)

Hi Javier.

26 Sep 25 15:48:04, you wrote to me:

f360.n221.z2.binkp.net:24554 [51.38.115.207]

Now your binkd here is using the standard binkp port instead of
what is in the nodelist and in the binkp.net dns srv record. :(

I've seen this happening in windows...

I'm running binkd in a FreeBSD jail.

tommi@mxo:~$ dig +short SRV _binkp._tcp.f360.n221.z2.binkp.net
0 0 360 f360.n221.z2.rbb.fidonet.fi.
=== <- There is the port to poll by binkp.

Your FreeBSD must be based on windows then! :D

'Tommi

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

Hello Tommi!

27 Sep 25 09:11, you wrote to me:

It's showing the same result as yours.

fido:/var/spool/ftn/filebase/nodelist$ drill SRV _binkp._tcp.f360.n221.z2.binkp.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 48424
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; _binkp._tcp.f360.n221.z2.binkp.net. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f360.n221.z2.binkp.net. 14400 IN SRV 0 0 360 f360.n221.z2.rbb.fidonet.fi.

;; AUTHORITY SECTION:

;; ADDITIONAL SECTION:

;; Query time: 390 msec
;; SERVER: 10.10.20.150
;; WHEN: Sat Sep 27 10:19:46 2025
;; MSG SIZE rcvd: 99

Hi Javier.

26 Sep 25 15:48:04, you wrote to me:

f360.n221.z2.binkp.net:24554 [51.38.115.207]

Now your binkd here is using the standard binkp port instead of
what is in the nodelist and in the binkp.net dns srv record. :(

I've seen this happening in windows...

I'm running binkd in a FreeBSD jail.

tommi@mxo:~$ dig +short SRV _binkp._tcp.f360.n221.z2.binkp.net
0 0 360 f360.n221.z2.rbb.fidonet.fi.
=== <- There is the port to poll by binkp.

Your FreeBSD must be based on windows then! :D

'Tommi

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

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)

On 29.09.2025 1:53, Javier Sturman wrote:

27 Sep 25 09:11, you wrote to me:

It's showing the same result as yours.

As it should.

The question is, why is your binkd (as well as the windows version of mine) not using the correct port?

fido:/var/spool/ftn/filebase/nodelist$ drill SRV _binkp._tcp.f360.n221.z2.binkp.net
;; ->>HEADER<<- opcode: QUERY, rcode: NOERROR, id: 48424
;; flags: qr rd ra ; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;; _binkp._tcp.f360.n221.z2.binkp.net. IN SRV

;; ANSWER SECTION:
_binkp._tcp.f360.n221.z2.binkp.net. 14400 IN SRV 0 0 360 f360.n221.z2.rbb.fidonet.fi.

'Tommi

---
* Origin: nntp://news.fidonet.fi (2:221/360.0)

Hello Tommi,

On Tuesday September 30 2025 08:15, you wrote to Javier Sturman:

It's showing the same result as yours.

As it should.

The question is, why is your binkd (as well as the windows version of mine) not using the correct port?

Because the Windows version of binkd does no read the SERV record when using binkd.net. My version of binkd - running on Win7 - has the same - annoying - shortcoming. It does not look this is going to be fixed any time soon. Let's get rid of IPv4. With IPv6 there is no need to meddle with non standard ports any more...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hi Michiel.

30 Sep 25 10:12:40, you wrote to me:

It's showing the same result as yours.

As it should.

The question is, why is your binkd (as well as the windows version
of mine) not using the correct port?

Because the Windows version of binkd does no read the SERV record when using binkd.net.

No shit Sherlock! :D

'Tommi

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

Good ${greeting_time}, Tommi!

30 Sep 25 08:15, you wrote to Javier Sturman:

The question is, why is your binkd (as well as the windows version of mine) not using the correct port?

IIRC, I tried it a couple of years ago on Linux and it didn't work. Does your binkp look up SRV records?

* Origin: kakistocracy (2:280/464.47)

Hi Oli.

30 Sep 25 09:58, you wrote to me:

IIRC, I tried it a couple of years ago on Linux and it didn't work. Does your
binkp look up SRV records?

It does.

grep f360 /var/log/named/query.log
30-Sep-2025 12:25:34.206 client @0x7f66fc2f2d48 127.0.0.1#36838 (_binkp._tcp.f360.n221.z2.binkp.net): query: _binkp._tcp.f360.n221.z2.binkp.net IN SRV + (127.0.0.1)
30-Sep-2025 12:25:34.206 client @0x7f66fc2f2d48 127.0.0.1#43829 (f360.n221.z2.rbb.fidonet.fi): query: f360.n221.z2.rbb.fidonet.fi IN A + (127.0.0.1)
30-Sep-2025 12:25:34.206 client @0x7f66fc01d1a8 127.0.0.1#43829 (f360.n221.z2.rbb.fidonet.fi): query: f360.n221.z2.rbb.fidonet.fi IN AAAA + (127.0.0.1)

'Tommi

--- GoldED+/LNX 1.1.5-b20250409
* Origin: nntps://news.fidonet.fi (2:221/1)