Newsgroups: vmsnet.mail.pmdf
Subject: "MESSAGE DAMAGED IN TRANSIT" messages
From: "Terry Kennedy, Operations Mgr" <terry@spcvxa.spc.edu>
Date: 08 Oct 1992 20:44:39 -0400 (EDT)
Organization: St. Peter's College, US
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 08 Oct 1992 20:44:39 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GPPSF444GM8WWZ1A@YMIR.CLAREMONT.EDU>
X-Vms-To: IPMDF@YMIR.CLAREMONT.EDU
X-Vms-Cc: TERRY
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

  I've received a few messages with null bodies, except for the "MESSAGE
DAMAGED IN TRANSIT" message. I was under the impression that this was
generated by the local PMDF when the message was missing the ^A's on the
end. I don't really know why I think that - perhaps Ned mentioned some-
thing about it on the list a few years ago?

  Anyway, my two questions are:

  1) What can I do to prevent this problem (if it's a local problem)?

  2) Can this message be changed in V4.2 to read something like:

     ****** MESSAGE DAMAGED IN TRANSIT ******
     This condition was detected at host.name.dom at dd-mmm-yyyy hh:mm:ss
     and indicates that the message was received in an incomplete state.
     Please contact the sender (see the From: line) to request another copy.

  That would cut down on the "Huh?" questions I get from my users when they
get one of these.

  By the way, here is the original "DAMAGED" message - did anyone else get
this in damaged condition?

	Terry Kennedy		Operations Manager, Academic Computing
	terry@spcvxa.bitnet	St. Peter's College, Jersey City, NJ USA
	terry@spcvxa.spc.edu	+1 201 915 9381

From:	IN%"MAC@gvg34.gvg.tek.com"  8-OCT-1992 20:28:19.49
To:	IN%"ipmdf@YMIR.CLAREMONT.EDU"
CC:
Subj:

Return-path: <epmdf@YMIR.CLAREMONT.EDU>
Received: from ymir.claremont.edu by spcvxa.spc.edu (PMDF #2329 ) id
 <01GPPW32I4EO8WW21X@spcvxa.spc.edu>; Thu, 8 Oct 1992 20:26:13 EDT
Received: from YMIR.CLAREMONT.EDU by YMIR.CLAREMONT.EDU (PMDF #2326 ) id
 <01GPPODTWY008WX0SY@YMIR.CLAREMONT.EDU>; Thu, 8 Oct 1992 16:45:58 PDT
Received: from CUNYVM.BITNET (MAILER@CUNYVMV2) by YMIR.CLAREMONT.EDU (PMDF
 #2326 ) id <01GPPOAAGW8W8WX0SO@YMIR.CLAREMONT.EDU>; Thu,
 8 Oct 1992 16:43:01 PDT
Received: from CUNYVM by CUNYVM.BITNET (Mailer R2.08) with BSMTP id 5549; Thu,
 08 Oct 92 17:24:27 EDT
Received: from relay.tek.com by CUNYVM.CUNY.EDU (IBM VM SMTP V2R2) with TCP;
 Thu, 08 Oct 92 17:23:24 EDT
Received: by relay.tek.com id <AA03075@relay.tek.com>; Thu,
 8 Oct 92 14:12:09 -0700
Received: from gvgpsa.gvg.tek.com by tektronix.TEK.COM (4.1/8.0) id AA15545;
 Thu, 8 Oct 92 14:16:01 PDT
Received: by gvgpsa.gvg.tek.com (5.57/9204230) id AA27555; Thu,
 8 Oct 92 14:11:22 PDT
Received: from gvg34.gvg.tek.com by gvg47.gvg.tek.com (PMDF #2374 ) id
 <01GPPIZ0HL8WCIRFKZ@gvg47.gvg.tek.com>; Thu, 8 Oct 1992 14:11:09 PST
Date: 08 Oct 1992 14:11:09 -0800 (PST)
Date-warning: Date header was inserted by gvg47.gvg.tek.com
From: MAC@gvg34.gvg.tek.com
To: ipmdf@YMIR.CLAREMONT.EDU
Errors-to: epmdf@YMIR.CLAREMONT.EDU
Resent-message-id: <01GPPODU4PPU8WX0SY@YMIR.CLAREMONT.EDU>
Message-id: <01GPPIZ741CYCIRFKZ@gvg47.gvg.tek.com>
X-VMS-To: IN%"ipmdf@YMIR.CLAREMONT.EDU"
Content-type: TEXT/PLAIN; CHARSET=US-ASCII
Content-transfer-encoding: 7BIT

****** MESSAGE DAMAGED IN TRANSIT ******