NB> On Sat May 16 2020 20:51:50, Rick Smith wrote to g00r00:

 G>>> Yep, so if I am understanding you then 1:340/400 is sending you
 G>>> duplicate messages and Mystic is catching them as a duplicate.
 G>>> The question is why is 340/400 sending you messages that
 G>>> originated from you as it should not be.   What system is
 G>>> 340/400? It sounds like the issue is with 340/400, and Mystic is
 G>>> properly catching the duplicate loop.


 RS>> So it goes  message written -----> Mystic BBS
 RS>> (340/202)-------> SBBS 340/400 SBBS 340/400 ----->Mystic BBS
 RS>> 340/202-------> point 340/202.1 (DUPE)

 NB> 1) 340/400 shouldn't send the message back to 340/202 first off.

 NB> 2) 340/202 should catch it as a dupe before it is sent back to the
 NB> point.

 NB> From what I've gathered from previous postings, 340/202.1 (Golded) is
 NB> using the same message base files as 340/202 (Mystic)? Or was this
 NB> changed recently?
Rick and I have basicly the same setup

uplink 340/400
our main fidonet 201 for me and 202 for Rick both running Mystic

point configuration
binkd for mailer
hpt (husky) for tosser
golded for message editor

I think the problem is with 400 or hpt, something somewhere I think is
stripping off the seenbys or just ignoring them.

everytime I enter a message on my point (201.2), it does the same thing, it
comes back as a dupe, but, I do not see a dupe mystic (a46)

but shouldn't mystic be stopping a dupe from continuing down the line??

Micheal

... Please Captain not in front of the Klingons
--- GoldED+/LNX 1.1.5-b20180707