TID: FMail-lnx64 2.1.0.18-B20170815
RFC-X-No-Archive: Yes
TZUTC: 0200
CHRS: UTF-8 2
PID: GED+LNX 1.1.5-b20161221
MSGID: 2:280/464 62769204
REPLY: 2:250/1@fidonet 62767a9d
Hi Vincent,

On 2022-05-07 14:53:13, you wrote to me:

 VC>>> Is there a tool that will check any outbound / forwarding
 VC>>> netmails for valid addresses using the nodelist ?

 VC>>> mbse does not do this.

 >> And it's a good thing it doesn't! The nodelist never is 100% accurate
 >> or up-to-date...

 >> I think you are trying to solve/prevent the bouncing issue that
 >> happend this week. But that is a routing issue, not a matter of
 >> someone using the wrong address!

 VC> Nope, in most cases it was an invalid address and the nodelist I use is
 VC> 100% up to date assuming RC's are updating their segment and sending it up
 VC> the chain.

RC's are involved too, but it starts with the NC's, to get the right
information to the RC's.

 VC> I do use the Z2DAILY node list as it IS updated daily !

Well, good that you use the most up-to-date version of the nodelist. But
that's not what I'm saying. Even if you use the latest nodelist, that nodelist
is never 100% up-to-date with reality... So for instance you might block
routed netmail for nodes that are already active, but are not yet in the
nodelist, because the NC/RC has not yet send in their update...

Routing issues should be solved in the routing table, not by blocking possible
legit netmail with a netmail tracker...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: FMail development HQ (2:280/464)
SEEN-BY: 1/123 15/0 18/200 90/1 103/705 105/81 106/201 120/340 123/131
SEEN-BY: 124/5016 129/305 330 331 153/757 7715 154/10 203/0 218/700
SEEN-BY: 221/0 226/30 227/114 229/110 111 206 317 400 424 426 428
SEEN-BY: 229/452 470 550 664 700 240/5832 266/512 280/464 5003 282/1038
SEEN-BY: 292/854 8125 301/1 317/3 320/219 322/757 341/234 342/200
SEEN-BY: 396/45 423/120 460/58 633/280 712/620 848 770/1 2452/250
PATH: 280/464 712/848 229/426