Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 8886  |
|  Javier Sturman to Tommi Koivula  |
|  hpt + binkd direct messages to different  |
|  26 Sep 25 15:48:04  |
 REPLY: 2:221/360.0 68d63bf8 MSGID: 4:900/733 68d6e047 CHRS: LATIN-1 2 TZUTC: -0300 Hello Tommi! 26 Sep 25 10:08, you wrote to me: TK> Javier Sturman wrote: JS>> f360.n221.z2.binkp.net:24554 [51.38.115.207] TK> Now your binkd here is using the standard binkp port instead of what TK> is in the nodelist and in the binkp.net dns srv record. :( TK> I've seen this happening in windows... I'm running binkd in a FreeBSD jail. 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> -+- TK> Routing direct for points not your own might not be the best idea. ;) 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 * -+- TK> 'Tommi TK> --- FastEcho/2 1.46.1 Revival TK> * 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) SEEN-BY: 4/0 88/0 90/0 93/1 105/81 106/201 128/187 129/14 305 153/7715 SEEN-BY: 154/110 218/700 226/30 227/114 229/110 200 206 275 300 307 SEEN-BY: 229/317 426 428 470 664 700 705 266/512 280/464 291/111 292/854 SEEN-BY: 320/219 322/757 341/66 342/200 396/45 633/280 712/848 900/0 SEEN-BY: 900/102 106 733 902/0 19 26 904/13 905/0 PATH: 900/733 902/26 229/426 |
[ << oldest | < older | list | newer > | newest >> ]