NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/vmsnet/mail/pmdf/1957

Internet Message Format | 1992-07-22 | 1.8 KB

Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!mips!swrinde!elroy.jpl.nasa.gov!decwrl!decwrl!infopiz!mccall!ipmdf-newsgate!list
From: [e-mail] (Ned Freed (Postmaster))
Newsgroups: vmsnet.mail.pmdf
Subject: RE: stuck message in bit_gateway channel
Message-ID: <[e-mail]>
Date: 22 Jul 92 16:24:59 GMT
Organization: The Internet
Lines: 24
Resent-Date: 22 Jul 1992 08:24:59 -0800 (PST)
Resent-From: [e-mail]
Errors-To: [e-mail]
Resent-Message-Id: <[e-mail]>
X-Vms-To: IN%"[e-mail]"
X-Vms-Cc: IPMDF
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT

First of all, while the log is helpful, it is not sufficient to determine
if this is a known problem or not. A log with master_debug and slave_debug
enabled on the channel would allow for a much more precise determination.

With this much information and no more I'm reduce to making guesses. This
looks like a known problem with PMDF V4.0 and bit_gateway channels that
are marked nosendpost. One workaround is to mark the channel errsendpost
or sendpost. errsendpost is actually the right thing to mark this channel,
since nosendpost results in situations where nobody at all gets copies
of some failed messages.

This problem is fixed in PMDF V4.1.

Now, it is possible that there is something else wrong. I have made a
bunch of assumptions here. If this is not what happening I'll need (1)
a more detailed log, (2) a copy of your PMDF.CNF, (3) precise information
about what version you're running, and (4) a copy of the message that's
causing the problem.

Finally, you might want to continue this discussion with [e-mail]
rather than info-pmdf, especially if large logs and configurations are
involved.

                Ned