Per Hosted Organization Journaling - Exchange 2010 SP1 /hosting

Posted on 2011-03-02
Last Modified: 2012-05-11
Good day to everybody!

I am currently setting up an Exchange 2010 Standard SP1 /hosting environment and have kept pretty much the standard configuration coming out of the box for the hosting plans and features. I am attempting to set up journaling rules at a per hosted organization level and am running into some issues when attempting to create the journaling rules themselves.

Steps I have taken:

Created an Organization:
new-organization -name "Constoso" -DomainName "" -ProgramID HostingSample -OfferID 2 -Location en-US -AdministratorPassword $c.password

Open in new window

Created a User Mailbox:
new-mailbox "John Doe" -UserPrincipalName -Organization "Contoso"

Open in new window

Created Journaling Mailbox:
new-mailbox "Journaling" -UserPrincipalName -Organization "Contoso"

Open in new window

Turned off Quota's, etc for Journaling Mailbox:
get-mailbox "Journaling" -Organization "Contoso" | set-mailbox -UseDatabaseQuotaDefaults $false -IssueWarningQuota unlimited -ProhibitSendQuota unlimited -ProhibitSendReceiveQuota unlimited

Open in new window

Attempted to create Journal Rule via Shell:
new-journalrule -Name "Contoso Journaling" -Organization "Contoso" -JournalEmailAddress "Journaling" -Scope Global -Enabled $true

Open in new window

Generates Error: No recipient matched the speicfied parameter value.
new-journalrule -Name "Contoso Journaling" -Organization "Contoso" -JournalEmailAddress -Scope Global -Enabled $true

Open in new window

Generates Error: The specified recipient is invalid.

Created Distribution Group to house mailboxes to be journaled thinking maybe it was because I didn't specify what to journal:
new-journalrule -Name "Contoso Journaling" -Organization "Contoso" -Recipient -JournalEmailAddress "Journaling" -Scope Global -Enabled $true

Open in new window

Generates Error: No recipient matched the speicfied parameter value.

new-journalrule -Name "Contoso Journaling" -Organization "Contoso" -Recipient -JournalEmailAddress -Scope Global -Enabled $true

Open in new window

Generates Error: The specified recipient is invalid.

Attempted to create Journal Rule through OWA -> Options -> Manage My Organization -> Mail Control -> Journaling -> Journal Rules -> New...:
If the message is sent to or from: Apply to all messages
Journal the following messages... All Messages
Send journal Reports to:
Name of Rule: Contoso Journaling
Clicked Save, Error: The specified recipient is invalid. Same thing happens if I specify the distribution list for the message to or from.
I am at a bit of a loss as to why this isn't working. My theory is that the new-journalrule cmdlet is ignoring the -Organization parameter since the mailboxes I'm trying to send journal reports to obviously exist. I've tried piping in the identity of those mailboxes various ways, but the new-journalrule cmdlet doesn't take direct piping from get-mailbox commands, and any formatting of data from the get-mailbox commands returns the same errors stated before. Any suggestions are definitely welcome. We are trying to avoid doing something at a global level due to the nature of the hosting environment.

Thanks and have a great day!
Question by:AutomatedIT
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
  • 3
  • 2
LVL 13

Expert Comment

ID: 35020998
It seems to me, that the JournalEmailAddress should belong to a recipient outside the organization journalled. Please try that.

Author Comment

ID: 35021852

Thanks for responding. That is not really what we are aiming for, as we would like for everything to be in the same organization space for each customer we are looking at hosting. In a non-hosted exchange environment, the journaling mailbox would be set up in the same organization as the mailboxes it would be receiving journal messages from, so I'm not sure how the hosted environment would require any difference in respect to that.

I did do what you suggested, however, and created a mailbox outside the organization.

Due to the Organizational divide being the sole idea behind Exchange 2010 with the /hosting switch, I could not create a mailbox for the domain in the base of the hosted solution (exchlab2010.local is the test domain I set up for this). So, that being said...

New-Mailbox "Contoso Journaling" -UserPrincipalName contosojournal@exchlab2010.local

creates a mailbox in the base exchange organization.

New-JournalRule -Organization "Contoso" -JournalEmailAddress contosojournal@exchlab2010.local -Recipient -Scope Global -Enabled $true

creates the journal rule and it is scoped out per organization.

Testing the rule by sending a message from to does NOT record the email header in the specified journal mailbox.

Amusingly enough, an attempt to create that same journal rule at the base organization level (same level as the journal mailbox) brings back the same problem of the recipient being invalid.

We made progress there for a moment :)
LVL 13

Accepted Solution

soostibi earned 500 total points
ID: 35021936
You have to solve the cross organization routing outside your exchange system. Set up an external SMTP relay host to relay back you e-mails. Create a Send Connector with a smart host to this external relay host.
If you want to host the journal mailbox inside the organization you may be able to set up a forwarding of the journal messages from the journal mailbox back to the originating org...
Comprehensive Backup Solutions for Microsoft

Acronis protects the complete Microsoft technology stack: Windows Server, Windows PC, laptop and Surface data; Microsoft business applications; Microsoft Hyper-V; Azure VMs; Microsoft Windows Server 2016; Microsoft Exchange 2016 and SQL Server 2016.


Author Comment

ID: 35026646

We will give it another shot with the external connector. I suspect to have something set up and testing sometime today. In the mean time, any other suggestions are welcome :)


Author Comment

ID: 35031741
Setting up the mailbox in the other organization works to the extent that the journal headers can be shown being delivered to that mailbox in the transactional logs, but the actual messages are not appearing in the box when I log into it. I think there is a different issue at play here, which brings a whole new line of troubleshooting into view. We'll move on past this point, though.

Expert Comment

ID: 36890764
I have the exact same issue. Hosted organisations can only have their Journaling enabled to mailboxes outside of the hosted environment.

Another strange issue that is also related, when Journaling is enabled to an external email address, Out of Office stops working to external senders for that organisation. I can confirm this as when you disable the journal rule, the OOF messages reach the external senders, but when enabled they do not.

Any help with this would be appreciated.

Featured Post

PeopleSoft Has Never Been Easier

PeopleSoft Adoption Made Smooth & Simple!

On-The-Job Training Is made Intuitive & Easy With WalkMe's On-Screen Guidance Tool.  Claim Your Free WalkMe Account Now

Question has a verified solution.

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

A list of top three free exchange EDB viewers that helps the user to extract a mailbox from an unmounted .edb file and get a clear preview of all emails & other items with just a single click on mailboxes.
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
In this video we show how to create a Resource Mailbox in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: Navigate to the Recipients >> Resources tab.: "Recipients" is our default selection …
The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager

728 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