[comp.protocols.iso.x400] X.400 Product for PCs. Forwarding IPM logic.

rothstein@nutmeg.enet.dec.COM ("Lee Rothstein, 603-884-0039") (09/23/90)

several have asked about PC clients

and

jlowry@bbn.COM (John Lowry), 28 Aug 90 18:00:50 GMT,
Bolt Beranek and Newman Inc., Cambridge MA:

>The implementation of '84 X400 I have does not support Forwarded
>IPM's. I would like to know if any implementations that support
>FIPM's and in anticipation of positive responses, have some
>questions:

ALL-IN-1 (tm) MAIL supports FIPM.

ALL-IN-1 MAIL is a 1988 P2 conformant UA developed and marketed
by Digital. It is composed of two components, a Server which
"serves" (what else?) all copies of all classes of clients and
and a client which "runs on or for a desktop device." Clients
are currently available for character cell DOS, terminals, and
DECwindows workstations or anything capable of "running" an X
Server". A Macintopsh client should ship about the end of the
year, followed thereafter by an MS-Windows and OS/2 Presentation
Manager clients.

ALL-IN-1 MAIL Server currently runs only on VMS.

>1) Is there a limit (standard or practical) on the level of nesting
>   that can appear within FIPM's ?

I don't know. There does not seem to be a practical limit on the
nesting allowed. I will check further.

>2) Is there a common or accepted solution as to how a user indicates
>   to the UA that "X" is to be forwarded, or that "Y" is to be a FIPM
>   within "X" which is to be a FIPM in the message I am preparing for
>   submission ? Is there an assumption that "X" and "Y" are already
>   encoded ? How does one specify (or save) the delivery Time and
>   the DeliveryInformation to the UA ?

There are two ways that an ALL-IN-1 MAIL user can indicate that
s/he want to forward a message. The first is to invoke the
forward command. The second is to do an attachment. In either
case, all headers of nested messages are preserved. If the
sending user does an attachment, s/he can attach any level of a
hierarchy of messages. However, all messages attached "below"
the requested attachment are also attached with their
sub-heirachy preserved.

>3) Upon delivery, is there a common or accepted solution for the UA to
>   notify the reader that "Y" is a FIPM of "X" which is a FIPM of the
>   message just received ? How does the UA inform the reader of the
>   delivery Time and DeliveryInformation of each FIPM ?

Attachments, as already implied, are arranged heirarchically, and
are displayed in a manner consistent with the UI of the desktop
device for illustrating hierarchy.

>Does anyone have an example of 2) or 3) which they would be so kind
>as to describe to me ?

>John Lowry

Lee

+---------------------------------------------------------+
| Lee Rothstein * UUCP: {purdue,ucbvax,hplabs,labrea,sun, |
|  pyramid,gryphon,angelo}!decwrl!nutmeg.dec.com!rothstein|
|   * Arpa/Domain Address: rothstein@nutmeg.enet.dec.com  |
+---------------------------------------------------------+