🚀 go-pugleaf

> We currently run with psulias.bitnet as our local host alias; we have both JNET
> for BITNET access and Multinet for SMTP/Internet access.  We've been asked to
> combine with all other nodes within the university and use Internet, not
> BitNet, as the preferred interface.  That is, change our local host alias to
> psulias.psu.edu, but then some....  If a node is not suffixed by a domain
> specification, we want it to default to .psu.edu, making it required that any
> BitNet Email have the pseudo-domain specification of .BITNET on it in order to
> not be mapped to a local (and probably non-existant) Penn State node.
>
> What's the simplest way to do this?  What of the things we're doing now (e.g.,
> processing Bitnet XMAILER.NAMES files every month, would change?

Nothing special.  If you run CONFIGURE.COM and tell it you are on Internet and
BITNET and use your Internet hostname for the official local host then this is
exactly the configuration you will get.  After all, nothing unusual here, this
is what most Internet+BITNET sites want.

CONFIGURE also asks if you want a default domain appended to TCP/IP host names
which can make shortform names default to .PSU.EDU.  Finally, PMDF knows about
all BITNET nodes and will not confuse them with local shortform host names.

Both the HOST and HOST.BITNET forms will continue to work.  This is part of
the reason why PMDF uses XMAILER.NAMES.  If you want to make .BITNET required
so that USER@HOST can never be directed to a BITNET host even if there
is one named "HOST" then you can easily do that as well (but it isn't the
default).  To do this, run CONFIGURE, answer the questions as I outlined
above (taking the defaults to nearly all questions will get you what you're
looking for) but say "NO" when it asks if BITNET_DOMAINS should be run "now".
Once CONFIGURE finishes, edit PMDF_ROOT:[TABLE]BITNET_DOMAINS_DRIVER.COM and
add a parameter setting:

    $ BITNET_LOCAL_CHANNELS == "bit_local/bit_gateway"

This makes BITNET shortform names valid only on the channels that handle
incoming BITNET messages, where shortform names must be recognized.
Messages originating on any other channel will require the .BITNET suffix.

	/Kevin Carosso
	 Innosoft