Xref: utzoo news.admin:11599 comp.mail.misc:4617 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!ig!mcb From: mcb@reason.ig.com (Michael C. Berch) Newsgroups: news.admin,comp.mail.misc Subject: Re: Bogus addresses Summary: Register a domain! Message-ID: Date: 26 Dec 90 18:22:34 GMT References: <1990Dec24.025350.26945@mthvax.cs.miami.edu> <2983@polari.UUCP> Followup-To: comp.mail.misc Distribution: na Organization: IntelliGenetics, Inc., Mountain View, California, USA Lines: 21 In the referenced article, tronix@polari.UUCP (David Daniel) writes: > I use rn at my site and will relate my experience: > > I've had instances where our DNS (sumax) will mangle my From: line to > read something like @polari@sumax or @sumax@polari.UUCP. In any case > it's unusable. By using the .RNINIT option one may customize a header > to read any way one wants it to. I've added my return address to the > Reply-To: line so that I can get mail replies even if sumax mangles my > From: line. The best way to assure that your From: line doesn't get mangled is to register and use a FQDN. If you registered as "polari.seattle.wa.us" or "polari.com" or whatever, mailers would be much less likely to want to gratuitously rewrite your headers (it *does* happen, as the current thread in comp.mail.misc shows). So long as you remain in the .UUCP pseudo-domain, mailers seem to take this as license to rewrite your sender fields. -- Michael C. Berch mcb@presto.ig.com / mcb@postmodern.com / uunet!presto.ig.com!mcb