I was under the impression that an entry such as:
 
Service= Local
Local= *vt.edu
 
would effectively keep subscription requests and list activity within in
the "bounds" of our institution.  All of the computers (and workstations
for that matter) here have a domain name ending in "vt.edu".  We run two
LISTSERV's here, on two different VM systems.  When I send a subscription
request from the VM system where the list resides (called VTVM1) everything
goes as expected.  However, if I send one from our other VM system (known
as VTVM2) I get the message from LISTSERV@VTVM1 that:
 
  Your node is outside this LISTSERV's service area
  Your subscription request has been denied.
 
Obviously, LISTSERV@VTVM1 is not recognizing VTVM2 as being within its
"service area", but my question is why?  Do I need to include the BITNET
node in the SERVICE keyword also?  Shouldn't the way I have this entered
above be sufficient to include any computer at Virginia Tech?  Since the
obvious answer to this last question is NO, what is the correct entry to
accomplish what I'm after?
 
Incidentally, the addresses for the two mentioned systems are:
 
VTVM1  Bitnet: VTVM1.BITNET   Internet: VTVM1.CC.VT.EDU
VTVM2  Bitnet: VTVM2.BITNET   Internet: VTVM2.CC.VT.EDU
 
Thanks in advance for any advice.
 

--Greg Kroll