Questions on semi-overlapping criteria for imexpire rules
(Doc ID 2685092.1)
Last updated on MAY 18, 2021
Applies to:Oracle Communications Messaging Server - Version 8.1.0 and later
Information in this document applies to any platform.
This document provides answers to questions on semi-overlapping criteria for imexpire rules.
1. We currently have a rule like this, specified via msconfig:
ie, for any folder other than Archive, delete anything older than 2 years.
But, the above would need "join: and" which requires "exclusive: 1".
which means that the first rule above would only be applied to the Archive folder.
We need to do both:
* expunge deleted mail, in any folder, after 7 days
* delete mail older than 2 years, from any folder except under Archive
a) How can I achieve that result?
b) Is folderpattern always treated as "AND"?
c) We look at the documentation around "join" and cannot understand when you would ever want the default behavior (OR).
If we put multiple criteria together in a single rule, why is the default behavior to OR those together instead of AND?
d) If rules that contain folderpattern and one other criteria always AND those two criteria, then it makes sense that "join" is not necessary. Correct?
e) What happens when a rule has folderpattern and multiple other conditions?
f) If a rule has multiple conditions but does NOT have folderpattern, then those are all treated as OR, unless you use join and, and therefore exclusive. Correct?
g) Why was this coded for default OR condition? If you want to have separate conditions tested separately and have actions performed if any one of them is true (ie OR them), you could do that with separate rules.
h) Need the documentation to clearly explain when you will get AND vs OR behavior.
2. How do I exclude certain users from the 2-year retention policy rule, but not other rules?
3. a) Does imsbackup | imsrestore run by rehostuser also move per-user/folder store.expirerule files? When does that happen in the process of imsrestore?
b) If imexpire happened to be run while a migration was in progress, is there protection to make sure the user's store.expirerule file is restored before the messages so that imexpire cannot accidentally run without the per-user/folder store.expirerule files?
The point of this question is that if a per-user file with an exclusive rule is the answer to question 2, then can we be sure that it can't accidentally be avoided during moving users between backends?
4. How to have imexpire rule "fileinto" action file into a folder structure or a variable folder name?
If we wanted to test our 2-year retention policy by moving the mail instead of deleting it, we would need to move it into a similar hierarchy as where it is being moved from.
If a message in user/userA/INBOX is older than 2 years, move it to user/userA/tooOld/INBOX .
If a message in user/userA/some/random/folder is older than 2 years, move it to user/userA/tooOld/some/random/folder .
Don't just move them all to user/userA/tooOld.
5. What is the maximum value I could specify for messagedays?
How is this coded? Is the internal-date on the messages a 64bit int? Is it signed or unsigned?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document