Re: Dupeloops   
     By: mark lewis to John McCoy on Tue Jun 19 2018 09:34 am   
      
    >   
    >  On 2018 Jun 19 04:02:48, you wrote to me:   
    >   
    >  ml>> that's a different problem... messages so marked should not be   
    >  ml>> packaged and sent to other links...   
    >   
    >  JM> It's more that the last one was also triggered by a rescan. Not   
    >  JM> specifically where it was rescanned from.   
    >   
    > my point is specifically that messages with a ^aRESCANNED control line   
    > should  not be passed on to other links... ever... that will stop them from   
    > triggering  what looks like a regurge or "dupe dump"... they will be   
    > different than the  original message because of the ^aRESCANNED control line   
    > so they will not be  caught by most dupe detection techniques... that's the   
    > real problem...   
      
   Is that true? Synchronet/SBBSecho uses 2 methods of dupe messge detection:   
      
   1. Message-ID (in the case of FTN, that's everything between "\1MSGID: " and   
      the CR) - the Message-ID doesn't change when messages a re-scanned   
   2. Message body text (not including kludge/control lines, paths/seen-bys,   
      and tear/tag/origin lines)   
      
   Rescanned messages would (should) be caught as dupes just fine.   
      
                                               digital man   
      
   This Is Spinal Tap quote #36:   
   Bobbi Flekman: Money talks, and bullshit walks.   
   Norco, CA WX: 74.4øF, 56.0% humidity, 2 mph E wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.05-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)