Subj : Re: Mystic tosser?
To   : Micheal Pierce
From : g00r00
Date : Sun May 17 2020 01:48 pm

 MP> everytime I enter a message on my point (201.2), it does the same thing,
 MP> it comes back as a dupe, but, I do not see a dupe mystic (a46)
 MP> 
 MP> but shouldn't mystic be stopping a dupe from continuing down the line??

PATH and SEEN-BY dupe checking will not be applied in this case because its a
point, and point addressing is not supported in PATH and SEEN-BY.

The remaining method for dupe checking then would be CRC checks against
messages that previous arrived.  But since this message never arrived before,
it will not be seen as a duplicate.

The issue is the uplink system should not be sending a message back to its
origin system.  So we need to start there and figure out why that is happening.
If I could look at that PKT file sent back from 340 with the duplicate message
I may be able to see what is happening.

--- Mystic BBS v1.12 A46 2020/05/16 (Windows/64)
 * Origin: Sector 7 | Mystic WHQ (1:129/215)

.