Subj : hpt + binkd direct messages to different zone
To   : Javier Sturman
From : Nick Boel
Date : Fri Sep 26 2025 07:51 pm

Hey Javier!

On Fri, 26 Sep 2025 15:48:04 -0300, you wrote:

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

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.

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

.