Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!orion.oac.uci.edu!ucivax!gateway
From: SXKAC%ALASKA.BITNET@cornellc.cit.cornell.edu (Kurt Carlson)
Newsgroups: comp.protocols.iso.x400
Subject: Re: Was: X.400 version 88? Correction on previous post!
Message-ID: <9010082019.aa00336@ICS.UCI.EDU>
Date: 9 Oct 90 03:25:25 GMT
Lines: 28
Approved: usenet@ICS.UCI.EDU

> Date: Mon, 08 Oct 90 15:26:18 -0700
> From: Einar Stefferud <stef@ics.uci.edu>

> So what is this all about.  How is A-1 conformant with any version of
> X.400?

Dec's message router with the MRX gateway is conformant to x.400 1984.
A1Mail *is* indeed a User Agent (actually, a Message Store + UA). I can't
comment on how compatable old All-In-1 Mail is with x.400, we've hung our
own UA off of the Message Router... their programmer's kit is quite
functional.  The 'free' VMSMail has a crude gateway to MR and hence
MRX/x.400... crude may be a kind description.  The newer A1Mail services
appear to be well integrated with Message Router which does seem to be
evolving from the old NBS standards to x.400.

The word I heard from Dec (a year ago, have not attended any conferences
or seminars since) was that the Message Router will be natively x.400
in a future release.  They expect the MRX product to remain as a tool
for filtering / securing an x.400 network from others.  I did not see
any definitive description on this or any time table.

They also have statement of direction for their directory service component
of message router / mailbus (DDS) to become x.500 compliant.  We continue
to use our own (non-x.500) directory services until theirs is closer to
x.500 and until they provide a programmer's kit for dds.

regards,
kurt carlson   university of alaska computer network <sxkac@alaska.bitnet>