Subj : hpt bug: Missing seen+by's in echomails send to same zone links
To   : Wilfred van Velzen
From : Michael Dukelsky
Date : Wed Jan 31 2024 10:41 pm

Hello Wilfred,

Wednesday January 31 2024, Wilfred van Velzen wrote to Developers:

 WV> I'm receiving some dupes that shouldn't happen. For echomail messages
 WV> that originate or go through systems using hpt 1.9, which have
 WV> -sbkeepall in their config set.


 WV> For instance here's a routing diagram of what I see for messages
 WV> generated on 3:770/1 in the STATS area:

 WV>   +----------+   A    +-----------+
 WV>   + 3:770/1  |------->| 3:712/848 |
 WV>   +----------+        +-----------+
 WV>        |                   |
 WV>      B |   +-----------+   | C
 WV>        +-->| 2:280/464 |<--+
 WV>            +-----------+

 WV> A: Only Z3 downlinks of 3:770/1 in the seenby's
 WV> B: All downlinks (in all zones) of 3:770/1 in the seenby's
 WV> C: Unnecessary dupes received through 3:712/848, because my node
 WV> should be in the seen+by's of the message received by 3:712/848 from
 WV> 3:770/1.


 WV> An example for today:

 WV>  From : 3:770/1             2024-01-31 23:59:16
 WV>  To   : All
 WV>  Subj : Daily Areas Summary
 WV> @MSGID: 3:770/1 65ba2805

 WV> Has the following seen+by's and path when received directly from
 WV> 3:770/1 by my system:

 WV> SEEN+BY: 218/840 220/70 226/17 267/800 280/464 712/848 770/1 100 330
 WV> 340 SEEN+BY: 772/220 230
 WV> PATH: 770/1

 WV> And these when received through 3:712/848 as dupe:

 WV> SEEN+BY: 229/426 280/464 301/1 633/267 712/620 848 770/1 100 330 340
 WV> 772/220 SEEN+BY: 772/230
 WV> PATH: 770/1 712/848

 WV> Notice that all the Z1 downlinks of 3:770/1 (218/840 220/70 226/17
 WV> 267/800) present in the direct message, are missing from the seen+by's
 WV> in the message that is received as dupe from 3:712/848.

 WV> I have confirmation it's the originating hpt system where this is
 WV> happening, and there is no seen+by stripping taking place on the
 WV> system in between.

 WV> 3:770/1 Seems to be using hpt/lnx 1.9 2022-07-03

It is more important to know whether 3:712/848 uses hpt.

 WV> I've also confirmed the same thing happening on another system using
 WV> hpt/lnx 1.9 2023-02-24.

I cannot promise I'll be able to address this issue any time soon, but to do it I must have the hpt configuration from 3:712/848 and two messages: the message he receives from 3:770/1 and the message he sends to you. My email address is in the tagline.

Michael

.... node (at) f1042 (dot) ru
--- GoldED+/LNX 1.1.5-b20231008
 * Origin: Moscow, Russia (2:5020/1042)

.