Browse Prior Art Database

Defining of Auto Actions into Separate Classes

IP.com Disclosure Number: IPCOM000109522D
Original Publication Date: 1992-Sep-01
Included in the Prior Art Database: 2005-Mar-24
Document File: 2 page(s) / 63K

Publishing Venue

IBM

Related People

Bower, RA: AUTHOR [+3]

Abstract

This article describes a method for allowing a user to define X.400 auto-actions into separate classes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 55% of the total text.

Defining of Auto Actions into Separate Classes

       This article describes a method for allowing a user to
define X.400 auto-actions into separate classes.

      X.400 is the international standard for electronic mail.  This
defines a Message Store (MS) and User Agent (UA).  Auto-actions are
defined by the UA and registered with the MS.  They define the
actions that a user wants performed on mail items when they are
stored in the MS.

      When creating X.400 auto-actions, there is no way to assign an
auto-action to a class (e.g., at class, on vacation, out ill) that
can be used by a user to register or de-register a whole set of
auto-actions in a class.

      When an auto-action is stored, the user will be given a chance
to assign it to a class.  This will enable a user to look at a
class and see the auto-actions that have been assigned to it.  The
user can then select an entire class of auto-actions that will be in
effect until they are changed.

      For example, a user has the following auto-actions defined:
  Class            Filter               Action
  Normal work      From=Kim             Print
                   Subject=Prototype    File to prototype folder
                   From=Manager         Print
                   From=BBOARD          Print
  Illness          From=Kim             File to...