On 2019 Jul 14 22:57:20, you wrote to Frank Linhares:

 DR>>> That's true. But, it would still cause dupes... :)

 FL>> How would it cause dupes? If one of my peer hubs sends me a message
 FL>> that has another peer hubs node number in the seen-by then my system
 FL>> won't export it to theres, plain and simple.

 DR> If the seen-bys are read and processed correctly, there wouldn't be
 DR> any dupes.

ummm... yes, there could be... but that depends on what is defined as a
dupe... is it duplicated MSGID? is it duplicate message body even with a
different MSGID? is it a duplicate message body that has been reformatted
in transit (which should never be done)??

 DR> But, not all systems do that, as I found out previously with Mystic. I
 DR> was receiving messages from one hub, they would get sent out to my
 DR> other hub, and caused a mess in those echos.

mystic is known to have problems in a couple of areas... some versions are
known to reformat messages that should not be reformatted... that
reformatting will absolutely throw off tossers that hash the message bodies
in addition to tracking MSGID control lines and headers... we've seen
messages passing through mystic systems coming out the other side with EOLs
added where there were none before, characters stripped that should not
have been and similar problems... this stuff was all working perfectly in
v1.11 when i was using mystic and providing feedback but something has
changed that should not have and well... it just ain't right...

)\/(ark

And to this end they built themselves a stupendous super-computer which was
so amazingly intelligent that even before its data banks had been connected
up it had started from "I think therefore I am" and got as far as deducing
the existence of rice pudding and income tax before anyone managed to turn
it off.
... No woman ever shot a man while he was doing the dishes.
---