Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ncar!husc6!ogccse!schaefer
From: schaefer@ogccse.ogc.edu (Barton E. Schaefer)
Newsgroups: comp.mail.mush
Subject: Re: From: problem in Mush6.5
Message-ID: <2873@ogccse.ogc.edu>
Date: 23 May 89 22:25:48 GMT
References: <2260@aecom.yu.edu> <2857@ogccse.ogc.edu> <2263@aecom.yu.edu>
Reply-To: schaefer@ogccse.UUCP (Barton E. Schaefer)
Organization: Oregon Graduate Center, Beaverton, OR
Lines: 48

In article <2263@aecom.yu.edu> naftoli@aecom.yu.edu (Robert N. Berlinger) writes:
} In article <2857@ogccse.ogc.edu>, schaefer@ogccse.ogc.edu (Barton E. Schaefer) writes:
} > If you know of a completely portable way (system call or whatever) to
} > find out what the domain name *is*, please, please tell us.
} 
} Well I don't know of any portable call, but I don't think a "set
} domain = ..." call wouldn't be too bad (with .UUCP disallowed :-)).
} Then hostname could be prepended (which you already have),
} making it less of a job for the system administrator (only
} different domains would have to have different setups).  Just a
} thought.

Not good enough.  It might be feasible to add a $domain variable, but it
would have to be the ENTIRE domain, not just the .organization.type part.
The official domain name of the host named "ogccse" is "cse.ogc.edu" --
it just happens that our MX record server (thank you, csnet) recognizes
"ogccse.ogc.edu" as an equivalent.  The upshot is that it may not be
sufficient to append .something.other to the hostname.

} > Mush relies on the hostname because that's the best it can do by
} > itself (at the moment, anyway).  If you tell it your domain name (via
} > "set hostname"), it'll use it.
} 
} I tried this and came up with some related funniness.  If I set
} my hostname to, for example, aecom.yu.edu, and I send a message
} to a local user, my autosign2 won't be used even though I have
} @aecom.yu.edu in autosign2.  I think it's because the signing
} code uses the external "ourname" instead of the value of the
} hostname variable.  Maybe when hostname is set ourname should be
} set too?  Otherwise, this does seem to do the trick.

Try using "!aecom.yu.edu" as well.

Ourname does get set when hostname changes.  That's actually part of
the problem you are having -- the rest of your list of local identities
gets tossed out when you change $hostname.  You can salvage part of it
by using
	set hostname="aecom.yu.edu $hostname"
which at the moment shifts ourname[0] to ourname[1], throws out ourname[2]
through ourname[N] (whatever N is), and sets ourname[0] to "aecom.yu.edu".

Perhaps a "hostname" command could be added, that works like "ignore" --
that is, it adds the new host to ourname[] without scrapping the rest.
-- 
Bart Schaefer       "And if you believe that, you'll believe anything."
							-- DangerMouse
CSNET / Internet                schaefer@cse.ogc.edu
UUCP                            ...{sequent,tektronix,verdix}!ogccse!schaefer