On Sun Jan-08-2017 11:43, Nicholas Boel (1:154/10) wrote to Nick Andre:   
      
    NB> Hello Nick,   
      
    NB> On Sun Jan 08 2017 10:42:28, Nick Andre wrote to Nicholas Boel:    
      
    NA> I know... but in this case, what it appears people are freaking about   
    NA> is a system is running software with a bug or in a way where it could   
    NA> be fixed by changing versions, but the operator of that system refuses   
    NA> to do so.   
      
    NB> You may even be misunderstanding that whole ordeal. Allen Prunty is   
    NB> not running Mystic, yet both are seemingly being blamed at the same   
    NB> time. If it is indeed a fault of Mystic causing all of Roger's   
    NB> dupes, then it is not Allen Prunty. If Allen Prunty is causing all   
    NB> of Roger's dupes, then it is not Mystic.    
      
   Let me say this about that and I'm not writing this to cause friction or to be   
   mean, but want to point out the facts as I remember them: I don't recall ever   
   placing the blame on anyone's software.  I read a lot of speculation on some   
   BBS software being the cause and I wasn't buying that, nor did I respond to   
   it.  That left the possibility of it happening, but usually the cause is   
   misconfiguring a system, regardless of what system it is.  What I did was   
   point out that there were dupes and printed the paths along with the headers   
   and in many cases, the MSGID was exactly the same.  Naturally, some took   
   afront to this and blamed D'Bridge simply because they don't know better.    
   That's on them.  In all the months I used D'Bridge on a trial basis before   
   finally buying it in 1991, Chris was an active participant here, just as Nick   
   is.  Even though most of the naysaying, anti D'Bridge troublemakers have faded   
   into the past, there are still a few around who want to cause trouble for 2   
   reasons.  1) they can, and 2) they don't have an inkling of what D'Bridge is   
   about.   
      
    NB> That's why I stayed out of the whole ordeal in the first place.   
    NB> People pointing fingers in every direction and not actually taking   
    NB> the time to figure out what the actual problem is. :/   
      
    NB>> Obviously with this option you're giving in to the possibility   
    NB>> that once i bluish-purple with pink polka-dots friggin moon there   
    NB>> may be a "false positive" that may slip by and never be seen.   
      
    NA> How come I'm not seeing you in the DR echo?   
      
    NB> What's the DR echo? I may vaguely remember you netmailing me about   
    NB> this. Wasn't it originally local to your system? Sorry, it's been   
    NB> an unfortunate and busy end to 2016 and beginning to 2017 so far   
    NB> and I haven't had much time to do anything productive in this   
    NB> hobby.   
      
    NB> I haven't added many new echos to my system (maybe besides   
    NB> Fidonet's UTF-8 echo) in quite some time. In any case, I've   
    NB> actually been pondering removing a bunch, rather than adding more.   
    NB> :)   
      
   Most of mine are gone simply because I tired of reading the same old stuff.   
      
   ...At the end of the day, it gets dark.   
      
      
   Regards,   
      
   Roger    
   --- timEd/386 1.10.y2k+ W10 (1607)   
    * Origin: NCS BBS - Houma, LoUiSiAna - (1:3828/7)