Hi Bill,
On 2015-04-21 09:31:00, you wrote to me:
WvV>> It doesn't matter, because SBBSecho's dupe checking is flawed
WvV>> anyway.
WvV>> It only checks for dupes when it imports messages into the message
WvV>> base. Arriving echomail is never checked by SBBSecho before it
WvV>> forwards it to its links.
WvV>> That's why you get Path lines like this (from my dupe area):
WvV>> @PATH: 249/303 203/0 320/119 123/500 261/38 249/303
WvV>> When for instance Joe writes a message on his synchronet system, and
WvV>> on the way a system strips the seen-by's. So when it arrives at
WvV>> Joe's
WvV>> system again (with the same MSG-ID), Joe's SBBSecho happily forwards
WvV>> it again (without dupe checking) to its links for the second time...
BM> I will bring this up with Rob....
Rob already is aware of this. It's how synchronet is designed, and it would be
difficult to fix, or so I understand... But it wouldn't hurt to put some extra
pressure on him, about this issue! ;)
Bye, Wilfred.
--- FMail-W32-1.69.4.102-B20150403
* Origin: FMail development HQ (2:280/464)
|