NetNews Usenet Archive 1992 #16/NN_1992_16.iso/spool/bit/listserv/pmdfl/1619

Text File | 1992-07-22 | 1.8 KB | 43 lines

Comments: Gated by [e-mail]
Path: sparky!uunet!paladin.american.edu!auvm!SIGURD.INNOSOFT.COM!NED
Errors-to: [e-mail]
X-Envelope-to: [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
Message-ID: <[e-mail]>
Date:         Wed, 22 Jul 92 17:14:38 GMT
Sender:       PMDF Distribution List <PMDF-L@IRLEARN>
From:         "Ned Freed (Postmaster)" <[e-mail]>
Subject:      RE: stuck message in bit_gateway channel
X-To:         [e-mail], IPMDF@YMIR
Newsgroups: bit.listserv.pmdf-l
Lines: 24

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