Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!orion.oac.uci.edu!ucivax!gateway From: agda001@mailserv.zdv.uni-tuebingen.de ("R. Daeschler") Newsgroups: comp.protocols.iso.x400 Subject: Smtp <---> X400 Message-ID: <9105251734.AA28968@mailserv.zdv.uni-tuebingen.de> Date: 25 May 91 18:09:40 GMT Lines: 106 Approved: usenet@ics.uci.edu Hi everybody, I followed the ungoing discussion about Addressing problems between domain addressing and X400 addressing style. an addressing like /c=us/adamd......./@X400net, Ch. Huitema suggested, already exists in form of the Spintmail/Telemail gateway: /pn=rainer.daeschler/o=testorg.ati/ADMD=ati/c=jp/@sprint.com ATI is a commercial X400 Mailservice belonging to Telemail/Sprintmail. This works fine with my smpt-mailer here, but some local mailers refuse to handle it. It is impossible for any smtp-Mailer to handle for example "/ADMD=British Telecom". The British PTT was clever enough to accept also adresses like uk.british-telecom and uk.bt if they are addressed from outside. My X400 address here is: c=de;a=dbp;p=uni-tuebingen;ou=kulturwissenschaften;s=daeschler while our Smtp-Mail gateway uses "/c=", in DFN (German Research Network) we have to use "c=XX;a=" As you see, the way X400 addresses are written are not the same everywhere. It much easier to address a German DFN-site with its's domain-address rather than using X400 Style. It is more secure to leave the convertion to the gateway, than doing it by yourself. Why? Look at the address above. One has to know, that German Universities don't use o=organization, other institutions do. But if you address it with daeschler@kulturwissenschaften.uni-tuebingen.dbp.de you don't have to care about this problem. How should an inocent novice know, that he has to leave the ADMD empty it he addresses c=no;a= ;p=uninett;o=uninett@s=mhsnews ? His collegues in the internet would never notice, that there might be a problem. As you see, each X400 network should have an gateway, where domain-style addresses are converted to X400. This keeps the X400 nets free from bouncing mails. Unless on doesn't stop this incomaptible variety of addressing shemes in the X400 world, there is little chance that it will substitute the smtp-mail and UUCP-mail in future. The way German DFN accepts domain addresses ist a solution, but addressing shemes are still very unrational if it is done in it's own X400 system. If one sends mail *within X400* using domain-style, it is only supported by the software EAN for VAX/VMS. The Ositel for UNIX adopted for DFN is still buggy. While EAN is able to change an domain-address to X400 style using the "compose" command, Ositel forces the input of X400 style. Further ist doesn't accept any /=DD.XX style address. This means, that existing forms of addresse can't be adressed, if someone has the wrong software. The software available is machine depended. Please don't forget, one major argument for OSI is not to be dependent from manufacturers from certain brands. Now I would be dependent on Digital Equipment here, because there is no reasonable software offered for other machines and supported by the DFN. I think in the development of X400 networks we should not start to create a science, only dealing with the problem how to address whom. A novice user should be able to use addresses as easy as using a phonenumber. Further we should more empahasis the transperancy of the system to contact other networks. Most people we contact are not in the network we are ourself. Now, either I spend all my time in learing the secrets of mailing into other networks myself, or I have to invite the system-manager to a beer (probably more) to encourage him to spend half an hour to figure out what I all have to keep in mind if I address this and this address. Regards Rainer -------------------------+------------------------------------- Rainer Daeschler | Telex.: 7-262867 utzv d Tuebingen University | Fax: +49 7071 293989 Dep. of Japanese Studies | Tel.: +49 7071 296985 Wilhelmstr.90 | 7400 Tuebingen /Germany | agda001@convex.zdv.uni-tuebingen.de | daeschler@mailserv.zdv..... -------------------------+-------------------------------------