Solved

Exchange 2007: Managed Content Settings not deleting messages

Posted on 2013-01-04
5
747 Views
Last Modified: 2013-01-21
I'm trying to delete emails that are in the Junk E-Mail default folder on Exchange 2007.  I've created Managed Content Settings to delete them after 180 days.

I've set the MRM schedule to run, plus I've run the mailbox folder assistant manually using "Start-ManagedFolderAssistant".  

Nothing seems to be deleting.  If I log into OWA, I can still see Junk Email in my folder older than 180 days.

What am I missing?
0
Comment
Question by:BMFC
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
5 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 38743888
If you have only just set the policy, then it will come in to effect in 180 days time.
That is because Exchange doesn't know how old those messages are, and it needs to stamp them for the policy to apply.

Simon.
0
 

Author Comment

by:BMFC
ID: 38744674
So it's from the day I created the Managed Content Settings?  Now anything coming into the Junk Email folder will be marked?

Is there a way to delete old messages?  I want to apply this same rule to "Deleted Items" to delete old emails.
0
 

Author Comment

by:BMFC
ID: 38745135
If what you're telling me is correct, then there would be no way to delete old emails.
0
 
LVL 58

Accepted Solution

by:
tigermatt earned 500 total points
ID: 38745857
BMFC,

It is possible to delete old email, but not immediately after messaging records management (MRM) is first enabled. If you are using the option "Retention period starts: When message is moved to folder" option in your managed content settings, then this is a classic case of the system appearing to misfunction, but actually working as designed.

As Simon has already stated, Exchange does not, by default, internally track the date at which a message was moved to a folder. Thus, the first time MRM is enabled, a process is initiated to stamp all messages in the managed folders with the date and time they were first seen by Exchange - specifically by the "Managed Folder Assistant", a process which enforces MRM content settings.

On each pass of a mailbox to apply tags and enforce Content policies on managed folders, the folder assistant then makes comparisons between the number of days defined on the content setting you created (180 days) and the date it stamped on the item when it first saw it in that folder. Only when the difference between today's date and that initially stamped date is greater than the policy (180 days) will the action be applied - in this case, the message will be deleted.

This is not a problem in normal operation. The folder assistant task runs on a schedule, and should complete a full scan over all mailboxes periodically to keep the timestamps in check and purge messages which are now deemed expired. After 180 days of continuous operation, the messages stamped today will be deleted. On the 181th day, all the messages moved to Junk/Deleted Items tomorrow will be removed. On the 182nd day, the messages moved there on Sunday will be removed, and so on. There will just be a lag period up front of 180 days, as the tags were only just applied with today's date when the content policy was first created.

The technicalities are explained here, along with the instructions you can follow to download MFCMAPI to interrogate the MAPI properties of messages in the managed folders of your mailbox to determine whether the ElcMoveDate stamp has actually been applied.

For reference, I just checked this with an Exchange 2010 instance. The MAPI property is different (it now tracks the date the message expires, rather than the date it was first seen). This is because MRM has moved on slightly and the architecture is different (it is now known as "retention", in line with the legalese which normally accompanies it). But, the principle is pretty much the same with some minor changes.

-Matt
0

Featured Post

Salesforce Has Never Been Easier

Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
exchange 2007 5 20
exchange 7 23
powershell to notify users for password setting 2 25
EXCH2013 Standard and Enterprise CALs 5 18
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
Read this checklist to learn more about the 15 things you should never include in an email signature.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

730 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question