-> so in your processing scripts, you should be able to copy the new outbound   
   -> bundles over to a save directory so you can look inside them...   
   -> IIUC, iREX is simply acting as a mailer so it shouldn't be futzing    
   -> about with the PKTs...   
      
   -> of course, we can also wait and see what kim has to say ;)   
      
    RW> Yeah, it seems that the part of the entire setup that is having an   
    RW> issue is Platinum Xpress for WINServer.     
      
   from what your log snippet showed, it did properly catch the problem but i   
   suspect that it miscalled the reason (dupe) when it wasn't...   
      
   but the above is the second time that i've pointed that you should be able to   
   grab a copy of those PKTs and/or bundles for analysis /before/ iREX glombs   
   onto them and sends them to the other machine... this way you/we can see what   
   bbbs is actually putting in the PKTs for the MSGID control line... then you   
   will know, without a doubt, where the fault lies ;)   
      
   actually, it is even easier than that... just stop iREX long enough to grab a   
   copy of those outbound files ;)   
      
   )\/(ark   
      
    * Origin:  (1:3634/12)