@MSGID: 2:5001/100@fidonet 6a6784ea
@REPLY: 2:203/910 6a672ff2
@CHRS: CP866 2
@TZUTC: 0000
@PID: FidoMail dev
Hello Alexey!

In a message of 27 Jul 26 12:16, Alexey wrote to Dmitry:

 AM> Hello Dmitry,

 AM> I noticed that my system`s status in the reachability table at
 AM> https://nodelist.fidonet.cc/reachability/node was marked as FAILED
 AM> for the entire period from 20/07 to 25/07, as an example.
 AM> However, the system was actually up and running during that time.

 AM> Log analysis shows that the system accepted incoming from
 AM> 2:5001/5001.
 AM> Could you have a look and see what might be the cause?

At some point (after 2026-07-02 08:49:34), your binkd started answering
with significant delay. Initially it was 269ms, but then increased to
around 10 seconds (the successful results show 8-9 seconds, unsuccessful
were > 10 seconds). My timeout was configured for 10 seconds, so I`ve
increased it now to 30 seconds, it should help.

Could DNS be the reason? 132.145.41.221 (main IP of nodelistdb) doesn`t
have PTR and it was done intentionally, because an average Fidonet user
doesn`t necessarily have it.



See you,
        dp.
--- FidoMail dev
 * Origin: livin` on the edge (2:5001/100)
SEEN-BY: 30/0 50/279 124/5016 203/0 221/0 1 230/0
240/1120 5832 250/1 263/1
SEEN-BY: 275/100 280/464 1043 5003 5006 5555
292/789 854 8125 301/1 310/31
SEEN-BY: 320/219 331/51 335/364 341/66 234 410/9
421/790 423/120 455/19
SEEN-BY: 460/58 463/68 467/70 469/122 712/848
5001/100 5015/46 5019/400
SEEN-BY: 5020/290 329 400 545 715 848 921 1146
2992 4441 5452 8912 9696 12000
SEEN-BY: 5022/2 128 5023/24 5025/3 75 5030/1081
1474 1499 1957 2104 2404
SEEN-BY: 5034/13 5035/85 5042/18 5051/44 5054/1
5055/73 5057/19 5059/37
SEEN-BY: 5061/15 5066/18 5075/35 128 5080/102
5085/13 5095/20 6035/3 6090/1
@PATH: 5001/100 5020/715 292/854 280/464 5020/545
4441