My Oracle Support Banner

Imexpire Is Ignoring Errors (Doc ID 2753545.1)

Last updated on FEBRUARY 18, 2021

Applies to:

Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.

Symptoms


Typing errors in a store.expire rule file (and/or not understanding that rule names are case-sensitive), can lead to unexpected results from imexpire.

For example (assume the below snippet is from a file called "testfile"):


For "rule1.folderpattern: user/user1/Inbox archives", there is no corresponding messagedays, messagesize, messagecount/etc. other rule criterion...
At least one of the associated attributes must be present, else it gets ignored.


For "Rule1" similar to the above case, it got ignored because there is no other criteria to perform this action.

The fact that it ignores the error is the problem.

A rule was specified with no action, so it was ignored.

A rule with no action is an error.  If there are any types of typing/syntax/etc. errors in a store.expirerule file, an error message should be generated.

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.