🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: vmsnet.mail.pmdf
Article #699

Options for dealing with Mail-11 delivery errors

#699
From: Bob Tinkelman
Date: Mon, 21 Dec 1992 13:22
51 lines
3390 bytes
This is a followup to my previous posting regarding problems with
deliveries to the local channel failing due to one of the various
problems with VMSmail and/or the Mail-11 protocol.

We have the following situation.  We used to have a set of large
mailing list (some with several hundred entries).  These used to be
normal VMSmail distribution lists.  We've changed them to be PMDF
lists.  We're having an unanticipated problem which may cause us to
revert back, something I'd prefer not to do.

There have always been occasional problems with these lists. However,
the impact has changed since the changeover.

Once, one list member on another node forwarded his mail to his
secretary, who was on some of the same lists.  This caused mail to
hang when sending to the list.  There have been other problems,
probably not all caused by exactly the same situations.

The following is my analysis/guess at our current situation.  When a
problem like the above occured before, the sender would be using MAIL
interactively, MAIL would hang, and the user would eventually ^C.  At
that point he/she would figure that the mail had been actually sent,
possibly noticing his/her own delivery had arrived, and would just go
on about his/her business.

Now, when the same situation occurs, the PMDF batch job is running
mail/protocol=in_mailshr and it hangs.  Either
   (1) PMDF recognizes the problem and aborts the delivery, or
   (2) the job hangs forever.
[I'm not sure how often the first occurs.  I've seen the second.]

Following the second scenario, eventually I notice the hung batch job
and abort it.  If I forget to rename the problem queue entry, the
situation repeats, and each time the message is delivered to the list.
So people get multiple copies of the message.  I suspect that the
first case is happening also based on the number of cases of people
reporting receiving many copies of the same message.

My first question:  Is my guess correct that PMDF will time out in
certain cases (I think this is what you [Ned] posted in response to my
first question) and treat the delivery as a `temporary failure',
requeuing it for later?

My second question:  If that's the case, would it make sense for PMDF
to provide an option for treating this case differently?  At our site
we'd prefer to get Postmaster involvement ASAP in cases like this,
rather than waiting for user complaints about multiple deliveries.

And my third question:  Short of convincing the other VMS systems to
run PMDF, are there any suggestions as to how we can deal with this,
short of going back to VMSmail distibution lists?
Technical Details
Message-ID: <01GSKLP8W26S8ZDVVS@camb.com>
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!ux1.cso.uiuc.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list

Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!sdd.hp.com!ux1.cso.uiuc.edu!moe.ksu.ksu.edu!mccall!ipmdf-newsgate!list
Newsgroups: vmsnet.mail.pmdf
Subject: Options for dealing with Mail-11 delivery errors
Message-ID: <01GSKLP8W26S8ZDVVS@camb.com>
From: Bob Tinkelman <bob@camb.com>
Date: 21 Dec 1992 09:22:48 -0400 (EDT)
Organization: Cambridge Computer Associates, Inc.
Return-Path: <epmdf@YMIR.CLAREMONT.EDU>
Resent-Date: 21 Dec 1992 09:22:48 -0400 (EDT)
Resent-From: epmdf@YMIR.CLAREMONT.EDU
Errors-To: epmdf@YMIR.CLAREMONT.EDU
Resent-Message-ID: <01GSKG80F74Y8WW5P0@INNOSOFT.COM>
X-Vms-To: IN%"info-pmdf"
X-Vms-Cc: TINKELMAN
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Lines: 51