N>   By: mark lewis to Netsurge on Fri Oct 07 2011 11:42 pm   
      
    > the main thing i see is that the messageid and MSGID are different and/or   
    > not being calculated as the same... other than that, it may be due   
    > to other   
    > things in the gating process...   
      
    N> I wonder if I can force a different type of dupe check for only this   
    N> echo. Time to try, lol.   
      
   i dunno... i realized some time back that this echo was being gated and that's   
   why they were coming back... i get the same thing with messages that get   
   posted to newsgroups... this is how folks can make sure their post actually   
   made it thru the gate...    
      
   but there is a big difference between the gates and their methods, though...   
   if i try to respond via netmail to a message that has come thru your gate, it   
   gets addressed to the user at your system... even if the user doesn't have an   
   account on your system... and so the private netmail reply doesn't make it   
   back thru the gate and on to the destination...    
      
   in other words, if i try to netmail myself from one of my returned messages   
   thru your gate, my netmail would go to your machine, get gated to that other   
   network and then regated back to fidonet addressed to me at my fidonet   
   address... my gating software is GIGO and GIGO calls this fastreturn and   
   forces it for fidonet traffic... GIGO forces it to eliminates the double   
   gating unless you are in more than one domain like rbbsnet and you need to   
   send mail from rbbsnet.net to fidonet.org or whatever... i've included at the   
   bottom of this message the comments from the GIGO configs concerning this... i   
   know that many things have changed since then... especially the fidonet domain   
   as well as loosing other domains...   
      
   from what others and myself have been seeing over the years and as more and   
   more synchronet boards come into fidonet and start doing more and more gating,   
   this is a problem in synchronet but i don't know why or how it can or should   
   be handled... sadly, i don't remember how stuff should be addressed to pass   
   thru a FTN node to a QWK fed node and that adds yet another layer of   
   complication to the whole shooting match :?   
      
   anyway, here's the text from the GIGO configs...   
      
    8/1/95   
    The FASTRETURN option has changed a bit!   
      
    The following command allows for "fast return" of mail that is addressed   
    to the internet, but is actually supposed to be processed by your system.   
    In these cases, the gateway will generate _incomming_ bundles instead of   
    outgoing bundles, making the messages never even leave your system.   
    Best use for this is "fidonet.org" addresses, since we are not allowed   
    to send from fidonet, to fidonet, via the internet backbone (as part of   
    our charter to get .fidonet.org).   
      
    Note, to force compliance with this charter, "fidonet.org" is a forced issue   
    with GIGO.  If you do not want GIGO to FASTRETURN anything for fidonet.org,   
    contact me.  I will only grant the key to disable this function to very   
    special circumstances that do not violate fidonet.org's charter.   
    An example of this exception would be if you are the gateway for a   
    different (and registered) organization, ie rbbsnet.org, where it _is_   
    desirable to be able to email someone@*.fidonet.org ..   
      
   FASTRETURN fidonet.org   
      
      
   )\/(ark   
      
    * Origin:  (1:3634/12)