We are running Exchange 2003 and are implementing a Mailbox Management Policy to Delete email from Inbox, Sent Items, and Deleted Items. This also processes sub-folders of these folders. We have found the Mailbox Management process skips folders with the PR_Container_Class property set to IPF.Note. We have successfully used PFDAVAdmin to clear this attribute from selected folders however, we are seeing if users create additional sub folders of the Inbox, they are being set to IPF.Note by default. This is causing us to have to re-run PFDAVAdmin on a regular basis. I read somwhere this attribute is not set on these folders by default. However, I found another article from the TechNet forums stating the default folder type in Exchange is IPF.Note. My question is, it appears the default folder type in Exchange is IPF.Note but the mailbox management process skips folders with this property. This seems counter intuitive. Is there a way around this? Can we either change the default folder type such that new folders are not given this attribute value or modify the Mailbox Managment process to not skip these folders?

IPF.Note is the usual container class for all folders that contain what you would call 'normal' emails. I don't know the answer to your problem, but the direction you should be heading is finding out why the mailbox management process is skipping IPF.Note folders, rather than trying to change the folder type.Outlook Web Access For PDA , OWA For WAP www.owa-pda.com email a@t leederbyshire d.0.t c.0.m

Thank you for the response. This issue is very elusive and thre isn't as much documentation on it as I would like. Suffice it to say, all articles I have found state the skipping of IPF.Note folders this is the default action for Exchange Mailbox Management.

1. Are you using any archiving/journaling like EV. This has known to cause issues. Sukh

We do have eVault in our environment however it is no longer being actively used, meaning it isn't doing any new archiving. Most of the users who are having this property set, and thus for all new folders, were never a part of the eVault user group.