The Question:
What does NODE in the configuration really do?

The Problem:
We just installed LISTSERV 1.8e, are a brand new LISTSERV site, and still
run Majordomo.  Over the next year we plan to convert our 1,000 Majordomo
lists to LISTSERV.  As part of this conversion we would like to keep the
list names the same, i.e., [log in to unmask] (now on Majordomo) would
still be [log in to unmask] after we migrate it to LISTSERV.  We also
want all new LISTSERV lists to start as [log in to unmask]

Majordomo runs on AIX Unix.
LISTSERV runs in Windows 2000.

Our unix systems person has agreed to add aliases to Sendmail for each list
to point it to the new Windows server each time we  add a new list or move
an old one.  Mail sent to [log in to unmask] would get rerouted to
[log in to unmask]

We are unsure as to the best way  to get LISTSERV or LSMTP (if needed)  to
address its mail as from: [log in to unmask]

I suggested that we just change the NODE in the LISTSERV configuration file
to "list.uiowa.edu" even though this really is the domain name of the AIX
Majordomo host.  That would also solve the problem of the name on the
LISTSERV web pages.  (Now they should up as itsnt131.uiowa.uiowa.edu, which
I really do not want anyone to ever see.)

And thus the question "What does NODE really do?" Can I set it to
list.uiowa.edu even though that really is another server on our
network?  What problems might this cause?  Any other ideas of how to solve
this problem?

Thanks again,
Feather