Well, this doesn't really have anything to do with owning lists, but...
what the heck!
 
In article <[log in to unmask]>, "Kathryn Wright"
      <[log in to unmask]> says:
 
>Recommendation: Tell subscribers to my Listserv'd list to sub under
>their Internet addresses if they have any.  (The Listserv in question
>being INDYCMS, it does also have its own Internet address.)
 
It all depends on what "unreliable" link you're trying to avoid.  If
it's the INDYCMS-INDST link, then yes, this'll probably work.  But if
it's the INDYCMS-PURCCVM link, then it probably won't.
 
>                                                             I've also
>seen mail go out of the way to a gateway when it only needed to go one
>Bitnet hop away.  No Internet alias registered, as you explained.
 
If I'm remembering the asker and the question correctly, the last time
this came up, you were asking for information about why
LISTSERV@INDYCMS was sending mail (using DIST2) via UICVM to get to
[log in to unmask]  The conclusion then was that this was
because LISTSERV@INDYCMS believed the indstate.edu gateway was
[log in to unmask]  If this is still the case (aside: Does anyone know how
to get LISTSERV to tell you the contents of its copy of DOMAIN NAMES?
I'm looking for an equivalent to MAILER's command: SHOW DOMAINS
indstate.edu.  Thanks.) then telling your users to subscribe using
their internet address will cause LISTSERV@INDYCMS to send mail
destined for [log in to unmask] to [log in to unmask]  This will
cause the mail to avoid the INDYCMS-INDST link.  But that means that
it will *always* avoid this link, and will *always* travel via UICVM.
Probably not something your users really want.
 
What you *really* want is for LISTSERV@INDYCMS to figure out that the
gateway for .indstate.edu is *not* SMTP@INTERBIT, but [log in to unmask]  That
way the mail will go via Internet directly from INDYCMS TO INDST and still
avoid the BITNET link.
 
There is no *official* way to do this (unless SMTP@INDYCMS is willing to
take on the BITNET gateway functions for indstate.edu, and you register
that in DOMAIN NAMES).
 
About the only (unofficial) way I can think of that you can do this is
to contact the Maintainer for LISTSERV@INDYCMS, and ask him to modify
LISTSERV's copy of DOMAIN NAMES to add this information.  He may or
may not.  But it would be tough to keep it up-to-date across monthly
changes in DOMAIN NAMES.
 
Actually, it looks like MAILER@INDYCMS is *already* running with a
modified copy of DOMAIN NAMES (based on the SHOW DOMAINS results I'm
getting).  Maybe you could talk the LISTSERV Maintainer into making
this already modified copy available to LISTSERV.  The problem with
this is that INDYCMS has a backbone LISTSERV, and this would probably
dramatically increase the traffic through their gateway.
 
Bottom line is that your INDST users probably won't like the results of
registering using their domain name.
 
Unless I've made some glaring technical mistakes here, or there's some
other expressed interest, it would probably be better to move this
conversation to email.
Bill
 
>We have been having delays on the Indiana net, and INDYCMS is among
>the guilty.  Just trying to figure an end run around the frustration.
>
>Kathryn Wright
>Indiana State University