REPLY: 4:900/733 68d6e047
MSGID: 1:154/10 68d7369a
CHRS: UTF-8 4
TZUTC: -0500
TID: hpt/lnx 1.9 2024-03-02
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@fidone































                                                                              
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@fidone




























                                                                              
26 Sep 00:05:24 [72510] 1:153/757.21@fsxnet busy, skippin






















                                                                              
26 Sep 00:05:24 [72513] call to 2:221/1.58@fidone






























                                                                              
26 Sep 00:05:24 [72510] 2:221/1.58@fsxnet busy, skippin
























                                                                              
26 Sep 00:05:24 [72510] 21:3/100@fsxnet busy, skippin


























                                                                              
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)
SEEN-BY: 4/0 88/0 90/0 93/1 103/705 104/119 105/81 106/201 114/10
SEEN-BY: 120/302 616 124/5016 128/187 129/14 215 305 153/757 7715
SEEN-BY: 154/10 30 50 110 700 203/0 218/700 220/30 90 221/0 6 226/18
SEEN-BY: 226/30 44 50 227/114 229/110 200 206 275 300 307 310 317
SEEN-BY: 229/426 428 470 664 700 705 240/1120 5832 263/1 266/512 280/464
SEEN-BY: 280/5003 5006 5555 291/111 292/854 8125 301/1 310/31 320/219
SEEN-BY: 322/757 341/66 200 234 342/200 343/107 396/45 423/120 460/58
SEEN-BY: 467/888 633/280 712/848 770/1 900/0 102 106 733 902/0 19
SEEN-BY: 902/26 904/13 905/0 2320/105 3634/12 5020/400
PATH: 154/10 280/464 341/66 902/26 229/426