Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!husc6!think!ames!oliveb!pyramid!prls!philabs!micomvax!musocs!mcgill-vision!mouse From: mouse@mcgill-vision.UUCP (der Mouse) Newsgroups: comp.mail.uucp Subject: Re: whether to prefix myhost! onto the From: or not.. Message-ID: <771@mcgill-vision.UUCP> Date: Mon, 11-May-87 03:52:16 EDT Article-I.D.: mcgill-v.771 Posted: Mon May 11 03:52:16 1987 Date-Received: Sat, 16-May-87 13:01:35 EDT References: <16238@amdcad.AMD.COM> <600@vixie.UUCP> <870@xanth.UUCP> <603@vixie.UUCP> Organization: McGill University, Montreal Lines: 33 In article <603@vixie.UUCP>, paul@vixie.UUCP (Paul Vixie Esq) writes: > In article <870@xanth.UUCP> kyle@xanth.UUCP (kyle jones) writes: [stuff about host!user] >> paul@vixie.uucp seems the best alternative. > As others will no doubt point out, this is bad and evil. [...] Many > older sendmail.cf's use .UUCP as their mock domain for UUCP traffic > -- so an address input as vixie.UUCP can cause confusion -- it > becomes vixie.UUCP.UUCP internally, and after that, chaos. Then it's even buggier than usual. Most would produce vixie.uucp.uucp only if you give vixie.uucp!paul, which I certainly hope nobody is crazy enough to do (but see paragraph after next, as well). If the host is running software so old that it can't live with paul@vixie.uucp, it's best to admit that it's broken and either fix it or live with and use vixie!paul. If your machine is handing stuff to another host, it should use something the other host can understand - host!stuff for ancient hosts, user@x.y.z for intelligent machines. Something that seems to be getting commoner is interpretation of foo.bar!user as meaning the same thing as user@foo.bar - the .uucp gets added only if there are no dots in the "host" part. This allows two intelligent hosts to speak to one another using a dumb !-only host as their link. What I shudder to see are things like netnews postings with messes like From: user@host.dept.univ.edu.UUCP der Mouse (mouse@mcgill-vision.uucp)