On Wednesday February 10 2021 20:06, you wrote to me:
MvdV>> But why bother the Fidonet receiver of the message with the burden MvdV>> of this transalation? Why not let the gate handle it? I am not MvdV>> familiar with the inner workings of the Telegram system, but what I MvdV>> glean is that users are identified by a 9? digit decimal number. So MvdV>> why not let the gate do the translation? The Fidonet end need never MvdV>> know about it.
SM> It is much more pleasant to receive a message from John Carpenter, but SM> not from 31254657345 and at the same time be able to answer SM> automatically.
For a human reader: sure. But you got me wrong. What I proposed was letting the gateway do the translation the other way for the other direction. For the (netmail) message FROM Fidonet TO Telegram. Translate Fidonet "John Carpenter" to "31254657345". The Fidonet user will only have to deal with "John Carpenter.
But if for some reason that is not doable...
SM> It is much more pleasant to receive a message from John Carpenter, but SM> not from 31254657345 and at the same time be able to answer SM> automatically.
For a human, sure. But a robot does not care. A PING robot will just as happily process and answer a message originating from user "31254657345" as a message originating from "John Carpenter".
If you configure your gate to translate "Jon Carpenter" into "31254657345" for message to user Ping and only for messages to user Ping, then it will work as you desire without the PING robot having to recongnise @REPLYTO.
SM> I think this is not a necessary toy. It is quite enough that my ping SM> will recognize the name substitution when responding.
But then it will only work for Pings processed by YOUR ping robot. Ping messages coming from Telegram will not usually be addressed to your PING robot. PING is designed for testing the routing in Fidonet. Sendig a ping message from Telegram to your PING robot which is the gateway does not make much sense, there is no Fidonet routing to test that way. What does make sense in your scenario is to send a PING message to a Fidonet node that is not your Telegram gateway. And that will work as desired if you configure your gateway as I propose.
