Hello Rick,
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 340/400?
G>> It sounds like the issue is with 340/400, and Mystic is properly
G>> 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)
1) 340/400 shouldn't send the message back to 340/202 first off.
2) 340/202 should catch it as a dupe before it is sent back to the point.
From what I've gathered from previous postings, 340/202.1 (Golded) is using the
same message base files as 340/202 (Mystic)? Or was this changed recently?
Regards,
Nick
... "Take my advice, I don't use it anyway."
--- GoldED+/LNX 1.1.5-b20181215
* Origin: thePharcyde_ distribution system (Wisconsin) (1:154/10)
|