Greetings -
In the near future the subdomain I (and other OSF/1 machines) are currently
in becomes obsolete (reorganization), and I'm currently looking at ways to
ease the transition as outlined below:
current: icefog.uacn.alaska.edu
transition: icefog.alaska.edu
future: icefog.???.alaska.edu
RE: sendmail
It would appear that the DOMAINTABLE macro would do this, but so could the
HIDDENHOST, HIDDENNET, and HIDDENDOMAIN macros, plus declaring a class and
writing a couple of rules could also accomplish this. Any other ways?
Advice anyone?
Currently sending mail to icefog.alaska.edu has the following problem:
----- Transcript of session follows -----
While talking to icefog.alaska.edu:
>>> HELO icefog.uacn.alaska.edu
<<< 553 Local configuration error, hostname not recognized as local
554 <haymanr_at_icefog.alaska.edu>... Service unavailable
What I'm looking to achieve is that the first two (current and transition) will
work simultaneously for mail, then when I know what the future subdomain will
be, then I can allow the latter two entries to work. The mail gateway and mail
hub systems are other machines.
What I've found thus far is that changing it from one to another is trivial
using the mailsetup script, but haven't yet run across how *best* to accept
mail addressed to to both icefog.alaska.edu and icefog.uacn.alaska.edu as
unqualified host names.
I could set myself up as a mail hub, but would rather not. I can get all the
aliases entered into our domain name server(s) easy enough.
Looking for advice on the best way and the reasons why.
Thank you very much. Summary pending responses.
Randy M. Hayman
haymanr_at_icefog.uacn.alaska.edu
Received on Wed Feb 01 1995 - 13:26:13 NZDT