Article View: comp.mail.mush
Article #382Re: Getting a bad hostname for smart UUCP system
From: Barton E. Schaefer
Date: Thu, 31 May 1990 18:46
Date: Thu, 31 May 1990 18:46
45 lines
2525 bytes
2525 bytes
In article <1179@kosman.UUCP> kevin@kosman.UUCP (Kevin O'Gorman) writes:
}
} We tracked it down. I have a SYSV UUCP-only system with enough other
} software that I'm happy with domain addresses. In this case, MUSH
} wants to believe that the correct From: line for my system is my login
} name, an '@', and the results of uname(2). This gives me the bogus
} header
} From: kevin@kosman
Actually, its the results of running "uuname -l". Would I be correct to
infer from your statement that you are "happy with domain addresses" that
you don't want the UUCP address-rewriting to happen on reply, so you did
not (and don't want to) compile with -DUUCP? If this is the case, I
suggest that you recompile mail.o (and *only* mail.o) with UUCP defined,
then relink. This will cause your From: header to appear as
From: kosman!kevin
without affecting other domain addresses in replies etc. (which are
handled in addrs.c). Your UUCP neighbors should be happier with that.
Alternately, you could compile with PICKY_MAILER defined, in which case
mush will require that your MTA supply the From: header (it will place
a From: header in the message temporarily for editing but then remove
it before passing the message to the MTA).
I might comment in passing that the contents of the From: header are
not intended for use by the MTA when delivering mail; delivery info
is all supposed to be contained in the message "envelope" that is
passed from your MTA to your neighbor's, so this problem should never
have come up. Of course, fixing your headers is probably easier than
convincing your neighbor that his MTA is wrong. :-/
} What I did was add a line to .mushrc:
} set hostname=${hostname}.uucp # give it a fake domain
This is pretty much equivalent, though what I'd recommend is using the
my_hdr command to specify the entire From: header as
my_hdr From: kosman!$LOGNAME
(or kosman!$USER if you don't have $LOGNAME). The other option is to
get a "real" domain name for your system and set $hostname to that.
--
Bart Schaefer schaefer@cse.ogi.edu
Technical Details
Message-ID:
<9630@ogicse.ogi.edu>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ogicse!schaeferReferences:
<1179@kosman.UUCP>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!ucsd!ogicse!schaefer From: schaefer@ogicse.ogi.edu (Barton E. Schaefer) Newsgroups: comp.mail.mush Subject: Re: Getting a bad hostname for smart UUCP system Message-ID: <9630@ogicse.ogi.edu> Date: 31 May 90 18:46:37 GMT References: <1179@kosman.UUCP> Organization: Oregon Graduate Institute (formerly OGC), Beaverton, OR Lines: 45