gplan@sun9.aer.com (George A. Planansky) (04/26/91)
We received an "Unrecognized address" report, regarding an X.400 domain in France, which suggests we get in touch with the manager of that domain. I don't know how to do this, however. The 3 messages involved are below. If you know how we should address our message, to get through, we'd greatly appreciate the information. 1) Original email from user in France to user in USA: || >From gaspar@argos2.cnes.fr Wed Apr 24 10:14:03 1991 || Received: from pamir.inria.fr by sol.aer.com id <AA23159@sol.aer.com>; Wed, 24 Apr 91 10:13:57 EDT || X400-Received: by /PRMD=inria/ADMD=atlas/C=FR/; || Relayed; 24 Apr 91 16:15:08+0100 || X400-Received: by /PRMD=cnes/ADMD=atlas/C=fr/; || Relayed; 24 Apr 91 16:15:25+0200 || Date: 24 Apr 91 16:15:25+0200 || From: " \]" <gaspar@argos2.cnes.fr> || Message-Id: <9104241415.AA00897@eliot.cnes.fr> || Subject: 1st test message from Philippe Gaspar || To: ponte <ponte@aer.com> || Status: OR || || {{ body of message }} 2) Reply from user in USA to user in France: || From: Rui Ponte <ponte@aer.com> || Message-ID: <9104251444.AA06645@sol.aer.com> || To: gaspar@argos2.cnes.fr || Subject: test || || {{ body of message }} 3) The unrecognized address report from France: || >From postmaster@pamir.inria.fr Thu Apr 25 10:45:01 1991 || Received: from pamir.inria.fr by sol.aer.com id <AA06649@sol.aer.com>; Thu, 25 Apr 91 10:44:56 EDT || Message-Id: <9104251444.AA06649@sol.aer.com> || X400-Received: by /PRMD=inria/ADMD=atlas/C=FR/; || Relayed; 25 Apr 91 16:46:14+0100 || X400-Received: by /PRMD=CNES/ADMD=ATLAS/C=FR/; || Relayed; 25 Apr 91 16:45:46 GMT || Date: 25 Apr 91 16:45:46 GMT || From: Postmaster@pamir.inria.fr || Apparently-To: <ponte@aer.com> || Status: OR || || Your message had been relayed through an X.400 network, which has issued || a "delivery report". The syntax of these reports had been devised to || fit the needs of X.400 user software; it is a terse binary structure. || Our gateway is making its best effort to present this information in an || understandable manner; we apology for its esoteric structure. || || The report contains information on the following recipients: || || <gaspar@argos2.cnes.fr>: Unable to transfer. || Unrecognized address (Please check the address of your correspondant). || On X.400, the address was: /C=FR/ADMD=atlas/PRMD=cnes/O=cnes/OU=argos2/S=gaspar/ || || This message is issued by <postmaster@pamir.inria.fr>. || In fact, it has been automatically generated by an X.400 message || switch, an MTA as it is called. We dont know exactly which one, but || it is located in the following X.400 domain: || /PRMD=CNES/ADMD=ATLAS/C=FR/ || If you need more info, try to figure out who the manager of that || X.400 domain is. || || By chance, we have been able to extract from the X.400 network a copy || of your original message. Some fields may look strange, as they have || been converted back and forth, but we hope that the information will || be useful. Here is your original message: || || From: Rui Ponte <ponte@aer.com> || Message-ID: <9104251444.AA06645@sol.aer.com> || To: gaspar@argos2.cnes.fr || Subject: test || || {{ body of message }} -- George Planansky Atmospheric & Environmental Research 840 Memorial Drive, Cambridge, MA 02139 gplanansky@aer.com (617) 547-6207 fax: 661-6479
huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence) (04/27/91)
George, Tough question. The only network I've seen connected to Internet that uses x.400 addressing is SprintMail. Can't say for certain this will work, but it's worth a try. SprintMail's addresses follow a very similar format: in%"I=M/G=D/S=USERNAME/O=US.SPRINT/ADMD=TELEMAIL/C=US/@sprint.com" Try substituting your /N= parts and send it to sprint.com. Good luck! Thanks. Steve ----- Steve Huff, student, University of Kansas "Still love that KU basketball!" Microcomputer Consultant, Hill's Pet Products, Topeka, Kansas Internet: HUFF@kuhub.cc.ukans.edu Bitnet: HUFF@UKANVAX GEIS: HUFF@HILLCORP#
smd@lsuc.on.ca (Sean Doran) (04/28/91)
In an article (Message-Id: <1991Apr27.083359.30117@kuhub.cc.ukans.edu>), (huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence)) wrote: | Tough question. The only network I've seen connected to Internet that | uses x.400 addressing is SprintMail. Can't say for certain this will work, | but it's worth a try. Just FYI, that won't work. SprintMail (aka Telemail) is a comercial mail system run by GTE Sprint, and partly administered by alan.roszkiewicz@sprint.com. The gateway is fully bidirectional ONLY for ADMD=TELEMAIL. Sending to any other MTAs costs Sprint money which they are not willing to pay, so they have taken them out of thier RFC-987 routing tables. For instance, while ADMD=TELECOM.CANADA and ADMD=TELEMAIL talk directly to each other, sprint.com will not gateway to ADMD=TELECOM.CANADA because it costs $$$. However, the gateway is fully unidirectional in that users on other MTAs which talk to TELEMAIL can send through their RFC-987 gateway to the Internet. So, you could not send to ADMD=ATLAS via sprint.com. Nasamail and the Commercial Mail Relay people at ISI.EDU run two fully bidirectional gateways to TELEMAIL and MTAs which talk with it. The gateways are mostly publically funded, and are for "acceptable use" purposes only. There are several other X.400 networks which are even more closely connected to the Internet: XNREN, the U.S. pilot X.500 project; CDNNet, the Canadian X.400 research network; and RARE, the European Research Community Network (using X.400/X.500). All of these have several peer-level gateways which don't rely upon the spooling done at e.g. sprint.com or nasamail.nasa.gov or intermail.isi.edu. Some of them are nac.no and mhs-relay.ac.uk, and probably still mirsa.inria.fr. In this case, gplanansky would probably want to send to: /C=FR/ADMD=ATLAS/PRMD=CNES/O=CNES/OU=ARGOS2/S=gaspar/@nac.no Which will work, if the X.400 address is valid. | Steve | ----- | Steve Huff, student, University of Kansas "Still love that KU basketball!" | Microcomputer Consultant, Hill's Pet Products, Topeka, Kansas | Internet: HUFF@kuhub.cc.ukans.edu Bitnet: HUFF@UKANVAX GEIS: HUFF@HILLCORP# -- Sean Doran <smd@lsuc.ON.CA> The Law Society of Upper Canada also seand@ziebmef.mef.org Young Liberals of Canada/Parti Liberal du Canada and /C=CANADA/ADMD=TELECOM.CANADA/ID=ICS.TEST/S=TESTGROUP/@nasamail.nasa.gov
heiko@methan.chemie.fu-berlin.de (Heiko Schlichting) (04/29/91)
smd@lsuc.on.ca (Sean Doran) writes: >In an article (Message-Id: <1991Apr27.083359.30117@kuhub.cc.ukans.edu>), >(huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence)) wrote: >| The only network I've seen connected to Internet that >| uses x.400 addressing is SprintMail. Can't say for certain this will work, >| but it's worth a try. >[...] gplanansky would probably want to send to: > >/C=FR/ADMD=ATLAS/PRMD=CNES/O=CNES/OU=ARGOS2/S=gaspar/@nac.no > >Which will work, if the X.400 address is valid. I have problems with this because this might be a valid X.400 address but this is NOT a valid RFC822 address. You are not allowed to use the character "/" in a RFC822 address (I know there are differences in the various RFCs but the newest say that "/" is forbidden). Our MTA (smail 3.1.20) says that this address has an invalid character and refuses such an address. The most MTAs of the European backbones refuses such an address too. Any idea to mail to a X.400-address over sprint.com without using "/" or "#"? Bye, Heiko. -- |~| Heiko Schlichting | Freie Universitaet Berlin / \ heiko@fub.uucp | Institut fuer Organische Chemie /FUB\ heiko@methan.chemie.fu-berlin.de | Takustrasse 3 `---' phone +49 30 838-2677; fax ...-5163 | D-1000 Berlin 33 Germany
ralphs@seattleu.edu (Ralph Sims) (04/29/91)
heiko@methan.chemie.fu-berlin.de (Heiko Schlichting) writes: > >/C=FR/ADMD=ATLAS/PRMD=CNES/O=CNES/OU=ARGOS2/S=gaspar/@nac.nok > I have problems with this because this might be a valid X.400 address but > this is NOT a valid RFC822 address. You are not allowed to use the > character "/" in a RFC822 address (I know there are differences in > the various RFCs but the newest say that "/" is forbidden). Isn't ">/C=FR/ADMD=ATLAS/PRMD=CNES/O=CNES/OU=ARGOS2/S=gaspar/@nac.nok" or some permutation suggested as the way to avoid the dreaded '/' creature? -- halcyon!ralphs@seattleu.edu The 23:00 News and Mail Service - +1 206 292 9048 - Seattle, WA USA +++ A Waffle Iron, Model 1.64 +++
tron@Veritas.COM (Ronald S. Karr) (04/29/91)
In article <7FFQ3IC@methan.chemie.fu-berlin.de> admin@methan.chemie.fu-berlin.de writes: >smd@lsuc.on.ca (Sean Doran) writes: >>In an article (Message-Id: <1991Apr27.083359.30117@kuhub.cc.ukans.edu>), >> >>/C=FR/ADMD=ATLAS/PRMD=CNES/O=CNES/OU=ARGOS2/S=gaspar/@nac.no >> >>Which will work, if the X.400 address is valid. > >I have problems with this because this might be a valid X.400 address but >this is NOT a valid RFC822 address. You are not allowed to use the >character "/" in a RFC822 address (I know there are differences in >the various RFCs but the newest say that "/" is forbidden). >Our MTA (smail 3.1.20) says that this address has an invalid character >and refuses such an address. The most MTAs of the European backbones >refuses such an address too. To clarify things, smail will deliver the specified address to nac.no, though it does not have the X.400 support necessary to do anything with this address on the machine nac.no. Note that smail does NOT accept "/" as part of a hostname, which is in accordance with RFC standards. -- tron |-<=>-| ARPAnet: veritas!tron@apple.com tron@veritas.com UUCPnet: {amdahl,apple,pyramid}!veritas!tron
rickert@mp.cs.niu.edu (Neil Rickert) (04/29/91)
In article <7FFQ3IC@methan.chemie.fu-berlin.de> admin@methan.chemie.fu-berlin.de writes: > >I have problems with this because this might be a valid X.400 address but >this is NOT a valid RFC822 address. You are not allowed to use the >character "/" in a RFC822 address (I know there are differences in >the various RFCs but the newest say that "/" is forbidden). There is nothing in RFC822, nor RFC1123 (which updates 822) that bans the use of '/'. It is a perfectly valid character in the local part of an address. >Our MTA (smail 3.1.20) says that this address has an invalid character >and refuses such an address. The most MTAs of the European backbones >refuses such an address too. Sounds like your MTA is broken. To clarify. The '/' character is permitted in the local part. Your MTA does not have to permit it in the local part of mail addressed to your domain. But it should permit it in the local part of mail addressed to other domains. The difference here is that your MTA interprets the contents of the local part only when the message is addressed to your own domain. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science <rickert@cs.niu.edu> Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940
les@chinet.chi.il.us (Leslie Mikesell) (04/30/91)
In article <1991Apr29.013708.26439@Veritas.COM> tron@Veritas.COM (Ronald S. Karr) writes: >>the various RFCs but the newest say that "/" is forbidden). >>Our MTA (smail 3.1.20) says that this address has an invalid character >>and refuses such an address. The most MTAs of the European backbones >>refuses such an address too. >To clarify things, smail will deliver the specified address to nac.no, >though it does not have the X.400 support necessary to do anything with >this address on the machine nac.no. Note that smail does NOT accept >"/" as part of a hostname, which is in accordance with RFC standards. Note that you may have problems with addresses that start with the "/" character when using uucp delivery. At least some versions of uuxqt scan all of each remote command's arguments looking for filenames, checking to see if the path is allowed. To get addresses starting with a "/" passed to rmail, you will probably need to have READ=/ WRITE=/ in the Permissions file for the sending site. The common use of spaces in X.400 addresses will be equally problematic for uux/uuxqt. Les Mikesell les@chinet.chi.il.us
dweissman@amarna.gsfc.nasa.gov (WiseGuy) (04/30/91)
In article <GPLAN.91Apr25180206@sun9.aer.com>, gplan@sun9.aer.com (George A. Planansky) writes...
^We received an "Unrecognized address" report, regarding an X.400
^domain in France, which suggests we get in touch with the manager
^of that domain. I don't know how to do this, however.
^
^The 3 messages involved are below. If you know how we should address
^our message, to get through, we'd greatly appreciate the information.
^
^1) Original email from user in France to user in USA:
^
^|| >From gaspar@argos2.cnes.fr Wed Apr 24 10:14:03 1991
^|| Received: from pamir.inria.fr by sol.aer.com id <AA23159@sol.aer.com>; Wed, 24 Apr 91 10:13:57 EDT
^|| X400-Received: by /PRMD=inria/ADMD=atlas/C=FR/;
^|| Relayed; 24 Apr 91 16:15:08+0100
^|| X400-Received: by /PRMD=cnes/ADMD=atlas/C=fr/;
^|| Relayed; 24 Apr 91 16:15:25+0200
^|| Date: 24 Apr 91 16:15:25+0200
^|| From: " \]" <gaspar@argos2.cnes.fr>
^|| Message-Id: <9104241415.AA00897@eliot.cnes.fr>
^|| Subject: 1st test message from Philippe Gaspar
^|| To: ponte <ponte@aer.com>
^|| Status: OR
^||
^|| {{ body of message }}
^
^ 2) Reply from user in USA to user in France:
^
^|| From: Rui Ponte <ponte@aer.com>
^|| Message-ID: <9104251444.AA06645@sol.aer.com>
^|| To: gaspar@argos2.cnes.fr
^|| Subject: test
^||
^|| {{ body of message }}
^
^
^3) The unrecognized address report from France:
^
^|| >From postmaster@pamir.inria.fr Thu Apr 25 10:45:01 1991
^|| Received: from pamir.inria.fr by sol.aer.com id <AA06649@sol.aer.com>; Thu, 25 Apr 91 10:44:56 EDT
^|| Message-Id: <9104251444.AA06649@sol.aer.com>
^|| X400-Received: by /PRMD=inria/ADMD=atlas/C=FR/;
^|| Relayed; 25 Apr 91 16:46:14+0100
^|| X400-Received: by /PRMD=CNES/ADMD=ATLAS/C=FR/;
^|| Relayed; 25 Apr 91 16:45:46 GMT
^|| Date: 25 Apr 91 16:45:46 GMT
^|| From: Postmaster@pamir.inria.fr
^|| Apparently-To: <ponte@aer.com>
^|| Status: OR
^||
^|| Your message had been relayed through an X.400 network, which has issued
^|| a "delivery report". The syntax of these reports had been devised to
^|| fit the needs of X.400 user software; it is a terse binary structure.
^|| Our gateway is making its best effort to present this information in an
^|| understandable manner; we apology for its esoteric structure.
^||
^|| The report contains information on the following recipients:
^||
^|| <gaspar@argos2.cnes.fr>: Unable to transfer.
^|| Unrecognized address (Please check the address of your correspondant).
^|| On X.400, the address was: /C=FR/ADMD=atlas/PRMD=cnes/O=cnes/OU=argos2/S=gaspar/
^||
^|| This message is issued by <postmaster@pamir.inria.fr>.
^|| In fact, it has been automatically generated by an X.400 message
^|| switch, an MTA as it is called. We dont know exactly which one, but
^|| it is located in the following X.400 domain:
^|| /PRMD=CNES/ADMD=ATLAS/C=FR/
^|| If you need more info, try to figure out who the manager of that
^|| X.400 domain is.
^||
^|| By chance, we have been able to extract from the X.400 network a copy
^|| of your original message. Some fields may look strange, as they have
^|| been converted back and forth, but we hope that the information will
^|| be useful. Here is your original message:
^||
^|| From: Rui Ponte <ponte@aer.com>
^|| Message-ID: <9104251444.AA06645@sol.aer.com>
^|| To: gaspar@argos2.cnes.fr
^|| Subject: test
^||
^|| {{ body of message }}
George, look like a machine at INRIA is being used as an X.400 gateway. I
suggest you talk to the admin for domain FR first to get an idea of the setup
over there. Maybe have some docs thrown your way.
Alain Bensoussan - fr-domain-admin@inria.fr
telephone - +33 1 39635405
================================================================================
Dave Weissman - Broadband and FDDI LAN Operations Group
Snail mail: NSI DECNET (SPAN) - 6153::DWEISSMAN
Code 543.8 NSI TCP/IP - dweissman@128.183.112.2
Goddard Space Flight Center SPRINTnet's X.400 -
Greenbelt, Maryland 20771 (C:USA,A:TELEMAIL,P:GSFC,FN:DAVID,SN:WEISSMAN)
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*
I don't speak for nor represent the views of NASA or my company although
they would both be happy if I just shut up for once.........
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*dweissman@amarna.gsfc.nasa.gov (WiseGuy) (04/30/91)
In article <1991Apr27.083359.30117@kuhub.cc.ukans.edu>, huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence) writes...
^George,
^
^Tough question. The only network I've seen connected to Internet that
^uses x.400 addressing is SprintMail. Can't say for certain this will work,
^but it's worth a try.
^
^SprintMail's addresses follow a very similar format:
^ in%"I=M/G=D/S=USERNAME/O=US.SPRINT/ADMD=TELEMAIL/C=US/@sprint.com"
^
^Try substituting your /N= parts and send it to sprint.com. Good luck!
^
Sprintmail's X.400 gateway at MERIT (sprint.com) is one of many, though not
all commercial. The Sprint ADMD must recognize the ADMD of 'atlas' and at
this time it doesn't (according to Sprint Cust. Serv.).
================================================================================
Dave Weissman - Broadband and FDDI LAN Operations Group
Snail mail: NSI DECNET (SPAN) - 6153::DWEISSMAN
Code 543.8 NSI TCP/IP - dweissman@128.183.112.2
Goddard Space Flight Center SPRINTnet's X.400 -
Greenbelt, Maryland 20771 (C:USA,A:TELEMAIL,P:GSFC,FN:DAVID,SN:WEISSMAN)
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*
I don't speak for nor represent the views of NASA or my company although
they would both be happy if I just shut up for once.........
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*dweissman@amarna.gsfc.nasa.gov (WiseGuy) (04/30/91)
In article <m0jX6Rd-0000gZC@lsuc.lsuc.on.ca>, smd@lsuc.on.ca (Sean Doran) writes...
^In an article (Message-Id: <1991Apr27.083359.30117@kuhub.cc.ukans.edu>),
^(huff@kuhub.cc.ukans.edu (Steve Huff, University of Kansas, Lawrence)) wrote:
^
^| Tough question. The only network I've seen connected to Internet that
^| uses x.400 addressing is SprintMail. Can't say for certain this will work,
^| but it's worth a try.
^
^Just FYI, that won't work. SprintMail (aka Telemail) is a comercial mail
^system run by GTE Sprint, and partly administered by
^alan.roszkiewicz@sprint.com.
FYI right back at you...Alan was a customer service rep for Sprintmail and
last I heard he left in 1990. The Sprintmail X.400 gateway (sprint.com)
is a SUN box at MERIT.
^Nasamail and the Commercial Mail Relay people at ISI.EDU run two fully
^bidirectional gateways to TELEMAIL and MTAs which talk with it. The
^gateways are mostly publically funded, and are for "acceptable use" purposes
^only.
The NASAmail gateway 'acceptable use' being NASA related business...
================================================================================
Dave Weissman - Broadband and FDDI LAN Operations Group
Snail mail: NSI DECNET (SPAN) - 6153::DWEISSMAN
Code 543.8 NSI TCP/IP - dweissman@128.183.112.2
Goddard Space Flight Center SPRINTnet's X.400 -
Greenbelt, Maryland 20771 (C:USA,A:TELEMAIL,P:GSFC,FN:DAVID,SN:WEISSMAN)
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*
I don't speak for nor represent the views of NASA or my company although
they would both be happy if I just shut up for once.........
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*dweissman@amarna.gsfc.nasa.gov (WiseGuy) (04/30/91)
In article <7FFQ3IC@methan.chemie.fu-berlin.de>, heiko@methan.chemie.fu-berlin.de (Heiko Schlichting) writes...
^
^I have problems with this because this might be a valid X.400 address but
^this is NOT a valid RFC822 address. You are not allowed to use the
^character "/" in a RFC822 address (I know there are differences in
^the various RFCs but the newest say that "/" is forbidden).
^Our MTA (smail 3.1.20) says that this address has an invalid character
^and refuses such an address. The most MTAs of the European backbones
^refuses such an address too.
^
^Any idea to mail to a X.400-address over sprint.com without using "/"
^or "#"?
The gateway at sprint.com needs the /c,/admd,/prmd, etc. to parse out the
X.400 address for the Sprintmail side. Internet (SMTP) mail could care less
about anything before the @ sign in "/...../@sprint.com". The format isn't
straight X.400 (everyone has a different implementation of X.400 addressing
for their UA/MTA) but it's what that particular gateway needs.
================================================================================
Dave Weissman - Broadband and FDDI LAN Operations Group
Snail mail: NSI DECNET (SPAN) - 6153::DWEISSMAN
Code 543.8 NSI TCP/IP - dweissman@128.183.112.2
Goddard Space Flight Center SPRINTnet's X.400 -
Greenbelt, Maryland 20771 (C:USA,A:TELEMAIL,P:GSFC,FN:DAVID,SN:WEISSMAN)
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*
I don't speak for nor represent the views of NASA or my company although
they would both be happy if I just shut up for once.........
*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*DISCLAIMER*