N> If anyone can offer suggestions on fixing this dupe issue, I would   
    N> greatly appreciate it. Here is what's happening..   
      
    N> I'm using Irex to pull this echo from a news group on   
    N> news.bbs-scene.org.  Irex pulls messages just fine and posts them   
    N> fine as well.  What it also does is pull down the message it just   
    N> posted as if it was new and then HPT from the Husky project (which   
    N> is what I use to toss mail) doesn't think it's a dupe and tosses it   
    N> back into the echo.   
      
   what is HPT using for dupe detection?   
      
   i just looked at my last post and the dupe (i'm on the fido side only) and the    
   MSGID is properly preserved... however, there's a few other control lines    
   inserted about those in my original... it may be that those additional lines   
   are    
   pushing the MSGID line outside a buffer that HPT is using... i dunno but i ran    
   into such when developing my own messaging packages years ago... once this was    
   figured out, i took steps to ensure that my code placed the MSGID as near as   
   it    
   could to the binary message header in the packed message...   
      
   if HPT is doing header matching, then it will fail because the header has    
   changed such that my address is changed to that of the gateway...   
      
   what news server is that site using? is it locally hosted? what message base    
   format does it use?   
      
   my site offers the echos i carry in nntp format but my news server interfaces    
   directly with my local bbs message bases... i only use my tosser to toss in   
   and    
   scan out messages...   
      
    N> Driving my insane over here.   
      
   i don't doubt that one bit... i lost quite a bit of hair back in the day    
   developing FTN stuff... i rather know where you are coming from but i'm not    
   familiar with your tools other than their names...   
      
   )\/(ark   
   --- SBBSecho 2.12-Linux   
    * Origin: >> diskshop >> bbs.diskshop.ca >> http.telnet.nntp (1:250/501)