Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ukma!xanth!lll-winken!ncis.llnl.gov!BARILVM.BITNET!HANK
From: HANK@BARILVM.BITNET
Newsgroups: comp.protocols.iso.x400
Subject: Suggestions for inlog/outlog in Message Store
Message-ID: <8902121306.AA19554@runix>
Date: 12 Feb 89 15:11:00 GMT
Sender: daemon@ncis.llnl.gov
Distribution: inet
Organization: The Internet
Lines: 35
Approved: post-x400@tis.llnl.gov

>X-Originator: Hank Nussbacher <HANK@BARILVM>

I'd like to add a few comments for discussion on the inlog/outlog
item.  It might be too late and some of the items raised may already
appear in the inlog/outlog proposal but maybe there is still time
to get them included:

- the ability for a user to specify different inlog and outlog (M/S)
  depending on the incoming or outgoing O/R name.  This way a user
  could store, for example, all items relating to X.400 in one outlog.

- if the above point is acceptable, then the ability of moving items
  between different inlogs and outlogs, along with the ability to add
  replace or delete items from the inlog or outlog.

- a flag on each item in the inlog to specify whether the user has
  read it or not.

- a flag on each item in the inlog to specify whether the user has
  replied to it or not.

- the ability for the user to turn off logging to outlog, at his/her
  request.

- the ability for a system administrator to specify a maximum size
  for an item to be allowed to be added to either the inlog or outlog.

- if multiple inlogs and outlogs are allowed then the user should have
  the ability to decide whether an item that has multiple recipients
  should be logged in one inlog/outlog or whether multiple copies of
  the item should be saved in separate inlog/outlogs based on the O/R
  name.

Hank Nussbacher
Israel