Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!psuvax1!psuvm!!"MUNNARI!UCSVC.UNIMELB.EDU.AU!C.H.CHAUNDY"
From: munnari!ucsvc.unimelb.edu.au!C.H.Chaundy@UUNET.UU.NET (munnari!ucsvc.unimelb.edu.au!C.H.Chaundy)
Newsgroups: bit.listserv.pmdf-l
Subject: RE: Problems with DSMTP_SLAVE
Message-ID: <9002110513.AA25015@muwaya.ucs.unimelb.edu.au>
Date: 11 Feb 90 05:28:00 GMT
Sender: PMDF Distribution List <PMDF-L@IRLEARN>
Reply-To: PMDF Distribution List <PMDF-L@IRLEARN>
Lines: 25
Approved: NETNEWS@PSUVM Gateway
Errors-to: postmast@YMIR.BITNET
X-Envelope-to: PMDF-L@IRLEARN.BITNET
X-VMS-To: IN%"ipmdf@ymir.claremont.edu"
Comments:     Warning -- original Sender: tag was
              munnari!ucsvc.unimelb.edu.au!CHRIS@UUNET.UU.NET
X-To:         ipmdf@YMIR

>I'd very much like to see a log from the other side. Can you get one? One
>possibility is that there's a corrupted file in the PMDF queue that the
>remote system cannot get past. I've seen this happen with JNET a couple of
>times but never with PMDF. (With JNET it is usually one of the .LOG files,
>and if it gets corrupted the associated daemons just won't start.)
>
>Another possibility is some condition we're not equipped to handle, such as
>a line that exceeds the maxuimum line length. Naah, not likely since it is
>PMDF on the other side -- it would never have allowed such a file in the
>queue in the first place.

Very occasionally, I have had a problem with a message with records which are
near to or at the maximum line length which have come into our system via
PMDF but need to be forwarded on and are not due to the length of the record.
I have experienced this with PMDF V3.0 but cannot comment on V3.1 as we have
not yet installed it.

Chris Chaundy

Manager, Networks and Communications,
University Computing Services, The University of Melbourne
Internet: C.H.Chaundy@unimelb.EDU.AU    (DTE 505233430003)
Phone:    +61 3 344 7045  Cables Unimelb
Fax:      +61 3 347 4803  Telex AA35185
Post:     Parkville, Victoria 3052 Australia