Link to home
Start Free TrialLog in
Avatar of fredimac
fredimacFlag for United States of America

asked on

Exchange Journaling mailbox filling up with messages, how to create management policy for single user.

We have a server that is jusing Exchange 2007 recipient journaling to send messages to MS Hosted archive, however the mailbox has filled up with thousands of messages.

Is there a way to create a managed folder policy and apply it to a single mailbox?

Avatar of Member_2_4436132

Managed folders are applied to all mailboxes.  You could try to setup your journaling rules to be more particular about which mailboxes you collect messages from.  

Avatar of fredimac


The idea is that MS is only keeping 30 days of mail, but something is filling up the Journaling box.  I'm considering deleting it, and having a small window of no archive, but I need to find a way to keep the folder from filling with old mail.  It's so large presently I have no way of viewing it.
Did you create the journaling rule on the mailbox stores (old school) or on the hub servers (new)?  The downside to using the Hub agent is that anything which hits the hubs (including bounced messages, etc.) is likely to be considered for archiving.

We use Symantec Enterprise Vault for our archiving / journaling along with E2K7's hub agent journaling and I've had to put numerous exceptions into Symantec to ignore certain message types / addresses.  Particularly nasty if you have a large ListServ environment like we do where messages sent to ListServ lists can often be viewed as individual messages to all recipients.
It's new school (HUB) and the scope is Global.  Since MS is only archiving 30 days, I need to purge just that mailbox of mail older than 30 days. Is this possible?  Managed Content rules seem to apply to all users, and I'm not sure, even after reading the docs, how the Managed Folder Policies link to Managed Content Settings.
Avatar of Michael B. Smith
If you create a managed folder mailbox policy, that policy will only apply to the users to which you assign the policy.

So, don't modify the default policy. Create a new one just for the Journaling mailbox. If you need specific instructions on how to do that, let us/me know.

Yes, if could point me in the right direction, that would be appreciated!
Avatar of Michael B. Smith
Michael B. Smith
Flag of United States of America image

Link to home
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
OK, so far so good... now, how do I go about monitoring / troubleshooting the process that actually does the work?  It's been 24 hours and the mailbox is still huge.
So...every run of the maintenance window (by default - 1am - 5am) should generate a fair number of event log messages.

You should also be able to look at the "Deleted Item Recovery" for the mailbox (from Outlook or OWA) to see how many messages were deleted.
I think the issue is with the maintenance schedule.  I'm getting an event that indicates an overlap, but I cant' figure out with what!

og Name:      Application
Source:        MSExchangeIS Mailbox Store
Date:          9/15/2010 7:00:00 PM
Event ID:      9871
Task Category: Background Cleanup
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      server
There is an online maintenance overlap for database "First Storage Group\Mailbox Database". Please revise the online maintenance schedule.
Event Xml:
<Event xmlns="">
    <Provider Name="MSExchangeIS Mailbox Store" />
    <EventID Qualifiers="32783">9871</EventID>
    <TimeCreated SystemTime="2010-09-16T02:00:00.000Z" />
    <Security />
    <Data>First Storage Group\Mailbox Database</Data>
I was able to get past the above error, but now the mailbox process runs but the size of the mailbox hasn't changed.  Thoughts?
I'm still stumped, the policy doesn't appear to be doing anything.  Backups have run.  Mailbox mangement has run and indicates no issues.   Is it possilbe the mailbox is just too big?  it's 30GB with 90K messages!
good answer