Hi Nicholas,
On 2015-10-05 16:22:44, you wrote to me:
WV>> So I contacted his host Michael Luko. And he has lost contact too...
WV>> So sending a routed netmail wouldn't have worked either.
NB> I think by the way it's sounding, Michael Luko is going to start routing
NB> netmail through me that is host-routed to James. James has been feeding
NB> here for over a year now, and I had thought that he still kept a direct
NB> link with his NC exacly for this purpose.. but apparantly I was wrong.
Maybe he should change to a nodenumber in your net!?
WV>>>> Anyway the nodelist entry should be fixed!
NB> The CM definitely should be removed. He hasn't been up 24x7 in quite some
NB> time now, but picks up mail from me once or twice a week for more than one
NB> network.
He isn't reachable by the information provided in the nodelist at all (the host
name doesn't resolve).
If he wants to be directly reachable he should fix that. Or if that's not an
option his nodelist entry should become Pvt, or he should become a point.
WV>> I think this case is quite simple: If there is contact, James can
WV>> provide a working host name (or other resolution). Otherwise his node
WV>> should be put on Hold, for the moment...
NB> Doesn't need to be put on HOLD,
There are several solutions, but as it is, the current nodelist entry is wrong,
and should be fixed.
NB> just route the netmail through me if you really want to get it to him
NB> before Michael Luko starts sending that stuff to me. I was just
NB> contacted about it today, so it may take until the next time Michael
NB> checks mail for my reply.
I've already send him an email.
Bye, Wilfred.
--- FMail-W32-1.69.10.141-B20151003
* Origin: FMail development HQ (2:280/464)
|