Reply to Re: MHS-DS at the next IETF

Michael.R.Storz@lrz.lrz-muenchen.d400.de Wed, 23 February 1994 15:47 UTC

X400-Received: by /c=us/admd=attmail/prmd=cdc/ ; Relayed ; 23 Feb 94 03:15:33 -0600
X400-Received: by /c=US/admd=/prmd=XNREN/ ; Relayed ; 23 Feb 94 09:16:01 Z
X400-Received: by /c=de/admd=d400/prmd=dfnrelay/ ; Relayed ; 23 Feb 94 09:16:43 Z
X400-Received: by /c=de/admd=d400/prmd=lrz-muenchen/ ; Relayed ; 23 Feb 94 09:12:47 Z
X400-Received: by mta MTAwally in /c=us/admd=attmail/prmd=cdc/ ; Relayed ; 23 Feb 94 03:08:36 +0600
X400-Received: by mta cdc.us in /c=us/admd=attmail/prmd=cdc/ ; Relayed ; 23 Feb 94 03:15:33 -0600
X400-MTS-Identifier: /c=de/admd=d400/prmd=lrz-muenchen/ ; 940223100127711-MTALRZVEE
Content-Identifier: 940223100127711
Content-Return: Allowed
X400-Content-Type: P2-1984 ( 2 )
Conversion: Allowed
Original-Encoded-Information-Types: IA5-Text
Priority: normal
Disclose-Recipients: Prohibited
Alternate-Recipient: Prohibited
X400-Originator: Michael.R.Storz@lrz.lrz-muenchen.d400.de
X400-Recipients: non-disclosure: ;
Message-Id: <940223100127711-MTALRZVEE*/c=de/admd=d400/prmd=lrz-muenchen/o=/ou=LRZ/s=Storz/g=Michael/i=R/@MHS>
In-Reply-To: <Pine.3.89.9402222238.A115 */c=dk/admd=dk400/prmd=minerva/o=uni-c/ou=danpost4/s=Pine.3.89.9402222238.A1155-0100000/@MHS>
Date: 23 Feb 94 09:12:47 Z
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Michael.R.Storz@lrz.lrz-muenchen.d400.de
To: Receipt notification requested </c=dk/admd=dk400/prmd=minerva/o=uni-c/s=Lawaetz/g=Erik/@wally-gw.udev.cdc.com>, Receipt notification requested <mhs-ds@mercury.udev.cdc.com>
Return-Receipt-To: Michael.R.Storz@lrz.lrz-muenchen.d400.de
Subject: Reply to Re: MHS-DS at the next IETF

> Some entries may be found under C=dk, ADMD=dk400. They're in whatever
> format PP 6.4/6.5 used/uses, and no updates have been performed recently.
> PP6.5 proved too unstable (well actually the quipu process became runnable
> all the time) when using X.500 for routing so we switched it off.
> No further work is planned due to lack of manpower.
>
> --Erik
>

This seems to be the major problem for Long Bud, the availability of a stable
MTA + X.500, which can be used in a production like manner and not only for
test purposes.

Steve: Which version of PP is the one you recommend to use for Long Bud?

Others: Who is running a PP version in production, which uses routing trees,
either internally or connected to the international pilot X.500 directory and
therefore to Long Bud?

The only other X.400 software of which I know has implemented the MHS-DS drafts
is Mail*Hub Version 2.1. My experience are only with internal usage and we
encountered no problems with the MHS-DS part of the product (we cannot connect
to Long Bud at the moment because of some internal reasons).

Others: Who is running Mail*Hub together with Long Bud?

--

Michael Storz
================================================================================
                                      !   X.400 : G=michael;S=storz;OU1=lrz;
   Leibniz-Rechenzentrum              !           P=lrz-muenchen;A=d400;C=de
   Barer Str. 21                      !   RFC822: michael.storz@lrz-muenchen.de
   80333 Muenchen                     !   Fax   : ++ 49 89 2809460
   Germany                            !   Tel   : ++ 49 89 2105 8720
================================================================================

Reply to Re: MHS-DS at the next IETF Michael.R.Storz
Re: Reply to Re: MHS-DS at the next IETF Steve Kille
Re: Reply to Re: MHS-DS at the next IETF Harald T. Alvestrand