Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!nike!ucbcad!ucbvax!VTMATH.BITNET!JARRELLRA
From: JARRELLRA@VTMATH.BITNET (Ronald A. Jarrell)
Newsgroups: mod.computers.vax
Subject: mailing lists
Message-ID: <8610291117.AA12427@ucbvax.berkeley.edu>
Date: Wed, 29-Oct-86 06:35:54 EST
Article-I.D.: ucbvax.8610291117.AA12427
Posted: Wed Oct 29 06:35:54 1986
Date-Received: Wed, 29-Oct-86 21:49:23 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 32
Approved: info-vax@sri-kl.arpa



Does anyone besides us set up userid's with in authorize or mailuaf that
forward to mailing lists?  In other words sending mail to STAFF
would cause mail to be distributed to half a dozen people?  I have a problem
with doing it across networks.  If STAFF is on VAX1, and I'm on VAX2,
and I send mail from VAX2 to VAX1::STAFF the first 2 people on the list
get the message, and anyone who had forwarding set gets the message regardless
of where they were. No one else does.  The nonpriv account gets a timeout
error (actually I only got a timeout once).  Usually it gets ABORTED LINK with
no indication as to why.  After 4 and half months of explaining this
to DEC, the last month of it to a very helpful person in colorado who spent
a week calling my system, DEC decided the following 2 things:

        a) It's broke.
        b) It's not supported so they could care less.

Any ideas on a way to fix this?  It only happens when the transport is
DECNET, i.e. bitnet mail, csnet mail, etc all work fine with the forwarded
lists, cause they are executed locally.  Also the following syntax works:

@vax1::staff.lis  (if list contains host::user addresses, ours doesn't)

The above syntax executes the list processing on vax2.

The following doesn't work:

vax1::@staff.lis

(execution done by vax 2).

-Ron Jarrell