Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.1 6/24/83 (MC840302); site diku.UUCP Path: utzoo!linus!philabs!cmcl2!seismo!mcvax!diku!kimcm From: kimcm@diku.UUCP (Kim Christian Madsen) Newsgroups: net.mail Subject: Re: Mail routing -- problems showing up - (nf) Message-ID: <1084@diku.UUCP> Date: Sat, 27-Jul-85 07:29:59 EDT Article-I.D.: diku.1084 Posted: Sat Jul 27 07:29:59 1985 Date-Received: Tue, 30-Jul-85 06:33:57 EDT References: <3018@nsc.UUCP> <11500001@unido.UUCP> Reply-To: kimcm@diku.UUCP (Kim Christian Madsen) Organization: DIKU, U of Copenhagen, DK Lines: 39 In article <11500001@unido.UUCP> dfk@unido.UUCP (Daniel Karrenberg) writes: >I admit this was rather lengthy, so let me repeat the morale: > > 1) don't mix ! and @ > 2) If you get a mixed address decide about precedence > based on the network by which the message ARRIVES > >Comments welcome. One of the pleasant news I've got earlier this year was that many, backbone sites are doing a rerouting of the paths to a given site. This means that I don't have to write mcvax!seismo!decvax!ihnp4...etc...!site!user Now I can relax and say mcvax!user@site.domain which saves me a lot of typing and reduces the chance of typos. I agree that the syntax of adresses can be horrible. But to give absolute paths would be ridiculous -- Let the routing databases with their optimized paths give the absolute path. You don't tell the postman which way he shall walk to deliver your ordinary mail, as long as it is delivered - do you ? (-; Maybe what we need is an net-addressing like: [] at nettype example: mcvax joe at foo nettype bar Which should be obvious for anyone to understand, and it's more like the address you write on an envelope... -- Kim Chr. Madsen Datalogisk Institut (Institute of CS) University of Copenhagen {decvax,philabs,seismo}!mcvax!kimcm@diku.UUCP