Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill From: bill@twwells.com (T. William Wells) Newsgroups: comp.mail.uucp Subject: Re: Vicious rewriting of From: lines Message-ID: <1989Dec10.193410.6761@twwells.com> Date: 10 Dec 89 19:34:10 GMT References: <1107891037263761@thelake.UUCP> Organization: None, Ft. Lauderdale, FL Lines: 34 In article karl@giza.cis.ohio-state.edu (Karl Kleinpaste) writes: : The bottom line is: Advertise RFC-conformant addresses in your From: : line in the first place, and I will happily leave it unmolested; hand : me something RFC-invalid, and I'll make my own personal best guess as : to how to return to RFC conformance, and you're bound to lose in the : process. You are not the only one who does this. When my mail goes through uflorida, it turns at least some unqualified names into user@bikini.cis.ufl.edu; imagine my mailing list members' surprise when list mail from me appeared to come from objectivism@bikini.cis.ufl.edu! Here's what happens: when I send mail to a local name from this machine, the To: line is just a local address. If that mail gets forwarded outside the machine, the To: line is, of course, bogus. So, if I personally sent e-mail to the list, it would go out from here without any kind of system name on the To: line and uflorida would rewrite it. I've put in a hack to prevent this, but I really should arrange that all mail addresses have a system name before they leave this system. There are probably other things that could be done to make the headers more conformant, but that appears to be the biggie. I'm running smail2.5 here; has anyone heard of a fix that will add my domain name to unqualified addresses? Sooner or later, I'm going to have to fix this and I'd rather not reinvent the wheel. And, while I'm at it, are there any other things that smail2.5 fails to get right? --- Bill { uunet | novavax | ankh | sunvice } !twwells!bill bill@twwells.com