Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!lll-lcc!styx!ptsfa!vixie!paul From: paul@vixie.UUCP (Paul Vixie Esq) Newsgroups: comp.mail.misc,comp.mail.uucp Subject: Re: whether to prefix myhost! onto the From: or not.. Message-ID: <609@vixie.UUCP> Date: Thu, 30-Apr-87 02:53:10 EDT Article-I.D.: vixie.609 Posted: Thu Apr 30 02:53:10 1987 Date-Received: Sat, 2-May-87 06:30:30 EDT References: <16238@amdcad.AMD.COM> <600@vixie.UUCP> <524@hadron.UUCP> Reply-To: paul@vixie.UUCP (Paul Vixie Esq) Organization: Vixie Enterprises, San Francisco Lines: 44 Xref: mnetor comp.mail.misc:244 comp.mail.uucp:515 In article <524@hadron.UUCP> jsdy@hadron.UUCP (Joseph S. D. Yao) writes: >In article <600@vixie.UUCP> paul@vixie.UUCP (Paul Vixie Esq) writes: >>The various standards in place around the net (in RFC form) say: no. > >After the Nth last time this was discussed (*sigh*), I tried to verify >this for a paper I was writing. Various people, including Mark Horton (!), >told me that they couldn't find [it] either. If this has >changed, and someone has found the citation, I'd really appreciate >hearing about it! You can find an RFC that will tell you that @ is the delimiter between the user and the host part of an address, and that same RFC will (possibly) mention ! as an optional, nonstandard thing that some sites do. This is sufficient, in my mind, to justify an operator precedence of @ over ! -- you don't start looking at the non-standard characters if there is a standard one remaining, right? But that's beside your point (sorry, but you didn't remind me what I was talking about when I said "no" :-)... Okay, net-at-large, where in the RFCs pertaining to mail does it say thou-shalt-not-modify-from-and-to-lines ? >And i am rather glad that even the prominent domainists who have >said that they never modify From: lines really do when they send >me mail, out of courtesy (i assume); thus, i can send mail back >more easily. No, prominent domainists write a From: line in the user@domain form; some site between you and the sender rewrote into a form your mail user-agent could deal with. Your transport agent should be able to do this for you; depending on non-standard hosts to rewrite headers for you is chancy at best, and at worst, they will either do the wrong thing, or some standard host "after" them will do the right thing (i.e., very little) and you will have a path a!b!d!e where 'c' isn't listed because they were "correct". Re: smail. It's cheap (free), well documented (uhhhh...) and easily installed (really!). Have your sysadmin mail to me if they are having some specific problem; I'd rather use up some of my own time and effort THAT way than to have my mail bounce because your mail transport agent did the wrong thing when I wasn't looking... Really, I'm serious: I'll help. -- Paul A. Vixie {ptsfa, crash, winfree}!vixie!paul 329 Noe Street dual!ptsfa!vixie!paul@ucbvax.Berkeley.EDU San Francisco CA 94116 paul@vixie.UUCP (415) 864-7013