Hello All!

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

mbse does not do this.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hi Vincent,

On 2022-05-06 18:12:34, you wrote to All:

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

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!

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

Friday May 06 2022 21:07, you wrote to me:

Hi Vincent,

On 2022-05-06 18:12:34, you wrote to All:

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

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!

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

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

I stopped using the other some months ago although I did try the Z1DAILY but it
is not updated daily with z2 - 4 let alone z1 again that may be down to RC's routing for updates - no idea why that should be.

Vincent

--- Mageia Linux v8 X64/Mbse v1.0.8/GoldED+/LNX 1.1.5-b20180707
* Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)

Hi Vincent,

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

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

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!

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

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

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)