Subj : Weekly nodelist report on noteworthy changes (097)
To   : Wilfred van Velzen
From : Tommi Koivula
Date : Fri Apr 07 2023 19:36:00

Hi Wilfred.

07 Apr 23 18:15:40, you wrote to me:

 SM>>> It works also at 2:460/0 with proper AKA in returning receipt
 SM>>> message. ;)

 TK>> Hmm.. I routed a ping message to 2:460/5858 via 2:460/0, but got
 TK>> the pong/trace message from 2:460/58.

 WV> 2:460/0 and 2:460/58 are AKA's on the same system. And you can't know
 WV> the routed to address from the unpacked message sitting in the
 WV> netmail directory.

This is the case when the msg has been stored into the msg base. Happens like this in my 2:221/0 aka /1 aka /360.

 WV> So only the tosser that unpacks the received
 WV> message from the .pkt file knows where the message inside the .pkt
 WV> file was routed to from the pkt header.

 WV> So if the PING/TRACE responder is a separate script, which seems to
 WV> be the case for Stas's system, it would be hard to know what the
 WV> routed to address was...

However, the pong perl script runs inside hpt, so it might be possible to know the destination address of the .pkt. But I don't know...

'Tommi

---
 * Origin: - rbb.fidonet.fi - Finland - (2:221/6)

.