kevin@kosman.UUCP (Kevin O'Gorman) (05/31/90)
I've been running fine in most respects since I first installed mush
a year ago or so. However, when I started accessing a certain mail
server, one of the intermediate sites started to complain.
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
This is bogus because any address with an '@' must have a domain, and
some internet mailers, on seeing such a thing, assume it's local and
add their own domain. This happened, and something very awkward
happened after the messages got to the server: the server believed
what it saw.
Anyway, it seems to me there could be something in config.h to indicate
this sort of case, or at least some documentation to help folks like
me avoid annoying the neighbors. What I did was add a line to .mushrc:
set hostname=${hostname}.uucp # give it a fake domain
and it looks like it's working. It avoids confusing most sendmail
configurations, and does the right thing in a lot of other cases,
even though .uucp is not strictly speaking a domain.
--
Kevin O'Gorman ( kevin@kosman.UUCP, kevin%kosman.uucp@nrc.com )
voice: 805-984-8042 Vital Computer Systems, 5115 Beachcomber, Oxnard, CA 93035
Non-Disclaimer: my boss is me, and he stands behind everything I say.schaefer@ogicse.ogi.edu (Barton E. Schaefer) (06/01/90)
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