🚀 go-pugleaf

We converted a very large VMSmail distribution list (one with 100s of
entries) into a PMDF list by defining a PMDF alias that pointed to
an the existing file.  [It's maintained by a complex set of programs
that I didn't want to touch.]  The mailing list consists of single
lines of the format node::usename.

A mail msg to this list hung for over 24 hours.  When we killed the
job the last lines were
	$   mail /protocol=pmdf_mailshr
	%MAIL-E-NOSUCHUSR, no such user XXXXX at node XXXXX
(with actual user name and node)

First Question:

A dump of the queued msg shows lots of envelope destination addresses
of the form node::user.  This surprised me.  Is it an indication that
I did something wrong in setting up the list?

Second Question:

I know there is a bug in the Mail-11 protocol which gets triggered
when distinct distribution list entries (distinct on the local node)
getting collapsed into common addresses based on forwarding at
destination nodes.  Could this bug explain the msg getting hung?
If so, is there a recommended method to avoid the problem or at least
reduce the likelyhood of its occurance?  Finally, is there someway to
place a timeout on delivery through VMSmail?  I'd be willing to take
responsibility for maintaining the value of a locally specified
time-out value if that would be appropriate.
--
Bob Tinkelman <bob@camb.com>