Menu

LISTSERV List Owners' Forum


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font


Subject:

Re: Managing a redistribution list for Internet addresses

From:

Eric Thomas <[log in to unmask]>

Reply-To:

ListServ list owners list <[log in to unmask]>

Date:

Sat, 5 Jan 91 19:11:50 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (23 lines)

On Fri, 4 Jan 91 14:10:54 PST Melvin Klassen <[log in to unmask]> said:
>P.S. Note that "SUVM.bitnet" == "SUVM.ACS.SYR.EDU". So, it's possible
>     for them  to be an  Internet gateway. Does  "Mail-via=DIST" inhibit
>     this?
 
It's really very simple. You can put  a REROUTE command in the profile of
your RSCS to cause it to  intercept all mail for INTERBIT flowing through
the local node and redirect it to  the local SMTP, and you will be acting
as an  Internet gateway  as far as  mail from your  local mailer  and any
other  site routing  INTERBIT through  you  is concerned.  It is  however
clearly unreasonable to expect LISTSERV to "know" that you have done that
if it is not  told in some way. It reads DOMAIN NAMES  and finds out that
the gateway is  at BITNET node INTERBIT,  so it looks at  the topology to
find out  what is the  closest LISTSERV to  node INTERBIT; as  things are
now, INTERBIT is defined  as being a leaf node off  CUNYVMV2, so it tries
to get as close to CUNY as  possible. This is clearly stupid, but this is
because the  proper topology information  is not present in  the INTERBIT
entry: it should have other links to  all the sites which run an INTERBIT
gateway, so that  LISTSERV routes to the closest  *actual* INTERBIT site,
and not to CUNY.
 
  Eric

Top of Message | Previous Page | Permalink


ATOM RSS1 RSS2