Preparing the Command File

The RULEEDIT command file must contain several sections.

Initialization Section

The initialization section must appear first in the file and start with the [Initialization] header. The initialization section specifies general parameters used for the RULEEDIT session. These may include:

FOLDER=<folder name> Name of the folder in which the rules will be created. The syntax of this line is the same as the syntax of the /FOLDER command-line flag.
PROVIDER=<provider name> Name of the rule provider to use. If this value is not present in either the .INI file or the command line, the default MSFT:RuleEdit name will be used when inserting or deleting rules
PROFILE=<profile name> The MAPI profile used for logging to a store

Parameters specified in this section may be overwritten by setting the corresponding command-line flags.

Command Sections

These sections specify the individual rule creation, deletion, or listing commands that are to be executed during the RULEEDIT session. Each command section must start with a [Command#] header, where # is a unique number assigned to the command.

Note At this time individual command numbers specified in the .INI file are not used by the program and need not be unique. Commands are executed in the order they are listed in the file, not in the order of their numbers. It is recommended, however, that each command be assigned a unique number in the [Command#] header to maintain compatibility with future versions of RULEEDIT.

Valid Command Section Entries

Entry	Description
COMMAND=	Specifies a valid rule command, one of the following: DELETE\|INSERT\|LIST. For example, COMMAND=DELETE
POSITION=	Gives the rule position, a number designating a rule's position in the rule table. The rule command specified will be attempted at this position. This parameter is required only for INSERT or DELETE. For example, POSITION=0
aCTION=	Describes a rule action for a new rule. This parameter is needed only when COMMAND=INSERT. A list of possible actions is included in the following section. For example: ACTION=BOUNCE BOUNCE_MESSAGE_SIZE_TOO_LARGE
RESTRICTION=	Describes a rule restriction for the new rule. The restriction syntax used by RULEEDIT corresponds to the syntax used by the Rules interface. Only one restriction is allowed per command.