Wirt wrote (with a VERY long URL :)

>If you want to see the difference, see Kevin's original reply in the
HP3000-L
>archives:
>
>  http://raven.utc.edu/cgi-bin/WA.EXE?A2=ind0206b&L=hp3000-l&D=0&P=4734
>
>...and compare that to Kevin's reply as it is stored on the Google groups
>archive:
>
>http://groups.google.com/groups?hl=en&lr=&threadm=ae3b48010dc%40enews3.news
guy
>.com&rnum=1&prev=/groups%3Fq%3D%2522RUN%2BRUNPSMON.PRED.SYS%253BXL%253D%27X
L.P
>RED.SYS,DIAGXL.PRED.SYS%27%253BPARM%253D-65%2522%2Bgroup:comp.sys.hp.mpe%26
hl%
>3Den%26lr%3D%26selm%3Dae3b48010dc%2540enews3.newsguy.com%26rnum%3D1
>
>The message of interest is number 7 in the thread. Kevin's reply there is
>only contains the headers.

  The two messages mentioned so far were posted at approximately the same
time of day.  As one of Wirt's other messages was also posted yesterday
immediately preceding Kevin's, and it came out fine, I don't think that's
it, but I'm looking!  If anyone knows of any other specific examples, or
it happens again, please email me privately.
  I've seen the posting process fail in cases where the actual message
body does not contain any record terminators and the contents are quite
large (I don't have any actual numbers on "quite large", but a few of the
HTML spam messages of last week qualified), but in those cases I'm notified
of the problem.  In these cases, the posting process receives a good status
back from the server so I'm not sure whether the problem was in retrieving
the body of the message in the first place, or with the posting of it.
There are no tell-tale errors, and my re-posting worked just fine.

Regards,
Michael L Gueterman
Easy Does It Technologies LLC
http://www.editcorp.com
voice: 888.858.EDIT or 573.368.5478
fax:   573.368.5479
--

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *