Subj : Re: 1:14/0
To   : Michiel van der Vlist
From : Nodelist Police Commissioner
Date : Sat Dec 18 2021 12:41:11

Hello Michiel,

On 2021-12-18 11:38:51, you wrote to me:

 MvdV>>> That amounts to rewarding bad behaviour. I say it is better to
 MvdV>>> dump the undeliverable mail for R14 into the Z1C's inbound.
 MvdV>>> Thereby droppng the problem on the plate of the one responsible
 MvdV>>> for having an incompetent Z1 RC.

 NC>> I have little hope that will help. It won't get noticed that way. It
 NC>> will probably just get delivered when the R14 system polls the Z1
 NC>> system. Or the Z1 doesn't use the nodelist for polling R14, because he
 NC>> has him setup in his config...

 MvdV> I am afraid you are right. It is unlikely that it will trigger action. It
 MvdV> is very unlikely that ZC1 is unaware of the problem and if he were inclined
 MvdV> to do something about it, he would have done it long ago.

Maybe "Educating and helping other *C's" and being responsible for the complete content of your segment should be added to the job description of any *C...

Maybe the IC can/should intervene? ;-)

 MvdV> OTOH, creating work arounds on the sender side, as you do, is
 MvdV> certainly not going the solve the problem.

I think we should separate these things:

1) The (automatic) reporting on technical nodelist issues should be as strict as possible.
2) The processing of the nodelist, should be as flexible and auto-correcting as possible.

I think we need 2 because of the declining knowledge, skills and numbers to keep this network going.

 MvdV> How about bouncing the 'undeliverable' mail back to the originator
 MvdV> of the message? (With an explanation.)

It's a good thing in general to bounce undeliverable mail, but it's a different matter. Besides this discussion started because some can't crash 1:14/0. Bouncing is more a routing thing...

What can be done is what we are doing right now, trying to make the responsible people aware of the problems. This can be done in escalating steps. First in private, second in public, repeat until fixed... The private and public steps have already been taken in this case... :-(

Regards, NPC.

--- FMail-lnx64 2.1.0.18-B20170815
 * Origin: NPC Station (2:280/464)

.