Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!orion.oac.uci.edu!ucivax!gateway From: MAILER-DAEMON@nac.no (Mail Delivery Subsystem) Newsgroups: comp.protocols.iso.x400 Subject: Returned mail: Unable to deliver mail Message-ID: <655512440.5349.0@nac.no> Date: 10 Oct 90 05:56:54 GMT Lines: 103 Approved: usenet@ICS.UCI.EDU Autoforwarded: true ----- Transcript of session follows ----- 554 xfAAnac01824: line 10: ... Host taurus not known within the bitnet domain 554 xfAAnac01824: line 12: ... Domain earn not known--please try to route manually 554 xfAAnac01824: line 13: ... Domain earn not known--please try to route manually 554 xfAAnac01824: line 15: ... Host haseoc not known within the bitnet domain 554 xfAAnac01824: line 23: ... Host dd0rud81 not known within the bitnet domain ----- Unsent message follows ----- Received: from localhost by nac.no (5.64+IDA/Babel-1.6/6.0) with SMTP id AAnac01824; Tue, 9 Oct 1990 23:05:44 +0100 Received: from /PRMD=uninett/ADMD=/C=no/ by nac.no with X.400 id ; Tue, 9 Oct 1990 23:01:10 +0100 Date: Tue, 9 Oct 1990 23:01:10 +0100 From: Mail Delivery Subsystem To: Subject: Returned mail: Unable to deliver mail Message-Id: <655509666.1511.0@nac.no> Autoforwarded: true ----- Transcript of session follows ----- 554 xfAAnac25525: line 10: ... Host taurus not known within the bitnet domain 554 xfAAnac25525: line 12: ... Domain earn not known--please try to route manually 554 xfAAnac25525: line 13: ... Domain earn not known--please try to route manually 554 xfAAnac25525: line 15: ... Host haseoc not known within the bitnet domain 554 xfAAnac25525: line 23: ... Host dd0rud81 not known within the bitnet domain ----- Unsent message follows ----- Received: from localhost by nac.no (5.64+IDA/Babel-1.6/6.0) with SMTP id AAnac25525; Tue, 9 Oct 1990 21:56:53 +0100 Received: from /PRMD=uninett/ADMD=/C=no/ by nac.no with X.400 id ; Tue, 9 Oct 1990 21:39:16 +0100 Date: Tue, 9 Oct 1990 21:39:16 +0100 From: Mail Delivery Subsystem Subject: Returned mail: unknown mailer error 1 Reply-To: Message-Id: <9010090330.AA05096@gshegering1.informatik.tu-muenchen.de> To: Autoforwarded: true ----- Transcript of session follows ----- mail: cannot append to /usr/spool/mail/kaiser Mail saved in dead.letter 554 ... unknown mailer error 1 ----- Unsent message follows ----- Received: by gshegering1.informatik.tu-muenchen.de (5.61++L/TUMinfo2.6Ni/SMTP) from tuminfo2.informatik.tu-muenchen.de id AA05084; Tue, 9 Oct 90 04:30:21 +0100 Received: by tuminfo2.informatik.tu-muenchen.de (5.61++L/TUMinfo2.6R/SMTP) from tuminfo2.informatik.tu-muenchen.de id AA04488; Tue, 9 Oct 90 04:33:34 +0100 Reply-To: Received: by uninett with X.400; 08 Oct 90 23:16:08+0100 Date: 08 Oct 90 23:16:08+0100 From: Steve Kille To: Alf Hansen Cc: , , , , Subject: Re: The NSF X.400 Pilot Project. References: , <900927170926*@MHSk> Message-Id: <802.655381297@UK.AC.UCL.CS> Autoforwarded: True Phone: +44-71-380-7294 Alf, Thanks for this message. I hope that your piloting activities and PP will have a useful symbiosis. A few thoughts: 1) I find the Internet X.400 piloting discussions difficult, as they seem to occur in a policy vacuum (this statement is meant to be provocative). Your description is of laying out a pilot service, with transition to full service. However, I don't see this reflected in overall strategy for the Internet (e.g., as RFCs on overall plan or IETF minutes). 2) Your service model is very oriented to the "external view". This facilitates connection of other WEPs and external commercial services using X.400. There needs to be more focus on an "internal" view. I'd like to see: - Information as to benefits of joining the pilot (short term, strategic) - Model for an organisation to transition / join the pilot. This is non-trivial for any organisation with a serious commitment to local messaging services - managing links within the PRMD (X.400 is oriented to bilaterally agreed links), and intra-PRMD routing. I don't see how the external aspects can be tackled as any sort of service, until there is a coherent internal view. This needs to be considered in terms of overall message service for the organisation, and not just X.400. 3) On managing 987 /1148 mapping tables for PP. UCl provides PP format mapping tables derived from the international tables, which PP sites can pull on a regular basis. US PP sites should submit any mappings they need through you. This will ensure that the mapping is a genuinely global one. Steve