header mangling at ucla-cs

[do...@cs.ucla.edu]

reference to he...@cuae2.UUCP 's suspicion that ucla-cs was mangling
headers by replacing the message-id with its own.... guilty as
charged.

i noticed this a couple of days ago, but cannot figure out why it
happened. it now seems to have stopped. if anyone has any ideas, i'd
appreciate them letting me know via email. we're running nntp and
uucp. according to the header of the article in question, it came in
via nntp from rutgers and went out (mangled) via uucp to sdcrdcf.

sorry for the problems.

'dorab
do...@cs.ucla.edu or {ihnp4,ucbvax,rutgers,sdcrdcf}!ucla-cs!dorab