Daniele and  I are looking for  examples of corrupted X-DEL  jobs or mail
files to  help in our  investigations. However  (you had guessed  it), we
don't want  just ANY  corrupted job.  The ones we  are interested  in are
those which:
 
1. Did NOT travel through  the FRMOP22-FRORS13-FRORS12 path. We know this
   path is deadly.  We don't know why, unfortunately, but  since there is
   only one LISTSERV on  this path we will never be able  to say for sure
   which  component on  which node  is  failing -  not unless  we find  a
   matching bug or APAR.
 
2. Have been received by LISTSERV uncorrupted. That is, the list archives
   or the  console log trace  (for X-DEL jobs) show  a clean copy  of the
   data;  however, some  of the  direct recipients  received a  corrupted
   copy.
 
Our problem is  that so far, in  all but one case, it  is totally unknown
whether LISTSERV got a corrupted copy  from RSCS, or corrupted it itself.
One  case (an  EEPG-BB  distribution on  the SEARN->HEARN->IRLEARN  path)
seems to suggest  that LISTSERV@HEARN got a clean copy  (one recipient in
.NL confirmed  that his copy was  uncorrupted), but the copy  received by
LISTSERV@IRLEARN was  corrupted. Whether this was  done by LISTSERV@HEARN
or by RSCS  is unsure (the former seems more  likely). Anyway, any useful
example (as described above) is welcome.
 
  Eric