Are Journal Messages recorded like regular messages when using Message Journaling to a custom recipient?
With a store enabled for Journaling, incoming messages for delivery will be Journaled at the point where the message is being delivered to the original recipient. At that point, a copy of the message is created with the recipient of the journal address. The journal message has an originator of <> (at least that it what is logged in the tracking log).
The effect on MessageStats reports are The Server Activity values will be increased as the journal messages will be sent off the server. For the affected mailboxes, they will not see the additional activity due to the Journaling. However, the additional traffic to the custom recipient defined as the destination address for the journal destination is not captured (even when using it with a mailbox enabled object). The reason is that since the originating address is <>, MessageStats ignores it as it cannot resolve that address. We may want to consider doing something with this <> originator, but we have yet to. The main reason is that it is really not an address and is something put in by Exchange to the tracking log.
Custom install with 4 consoles on W2K Servers Sp4 with Outlook 2003 Sp2 and the Database is on a SQL 2000 Sp3a Farm on a W2K Server Sp4
Message Journaling going to a custom recipient that passes the messages onto a UNIX System for storage.