Expire Rule Fileinto A Hierarchy Instead Of Specific Folder (Doc ID 2694283.1)

Last updated on JULY 27, 2020

Applies to:

Goal

An implementation of a new email retention policy would behave whereby instead of just deleting older mail, either move it to another folder or in some way hide it from the user.

The imexpire rules have a "fileinto" feature, but it only takes a single folder name as the destination.
In many deployments, users have hundreds of folders.
If all the old mail from all those folders was suddenly moved into a single folder, it would be a mess. If the need to move the mail back from that folder to its original folder arose, it would be very difficult to determine where it came from.

Is there some variation of "fileinto" that would allow the base of a hierarchy to be specified and move the message to a similar position?

For example, for a message in user/user1/some/random/folder --> move it to user/user1/toberemoved/some/random/folder ?

Or, is there any other suggestion for how to go about tentatively implementing such a retention policy to make it easier to recover if something goes wrong?

Another option would be to get either an additional optional argument to fileinto or a new command (perhaps "archive"? or "fileintoarchive"?) where the path specifies the base rather than the folder and the action would be to move the message from its current location to the same position but relative to the specified folder.

For example:  if the the rule action was: archive tobedeleted

• user/user1/some/folder/1.msg would be moved to user/user1/tobedeleted/some/folder/nn.msg
• user/user1/INBOX/2.msg would be move to user/user1/tobedeleted/INBOX/nn.msg
   

Solution

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