Forum Discussion
Solved
O365 Exchange not journaling incoming emails, only outgoing
Funky situation that I just came upon. I use an outside company to archive all inbound/outbound emails. To do so, journaling is is set up to share those emails with them. I checked the archi...
- Figured out the issue on this one.
It turns out that the SPF record on the domain was misconfigured. If was invalid and resulted in journaled emails Exchange was sending out not being accepted by the third party archive company.
After the revision to the SPF record, it all worked perfectly.
Of additional note, it seems as if the "Undeliverable Reports" email should not be an Exchange email address. I would have figured this out earlier but the reports were being "sent" (never received) to an Exchange user. When I switched that to a Yahoo account, I received the report, and was able to determine next steps. Suggest a non-Exchange email for these reports (which is mentioned on that same admin page, but we all read that stuff 😉 all the time).
Dan_Snape Using Exchange online (365), not on premise.
Simply have a journal rule to send all emails for all users to an email address.
If you do a message trace on an incoming message you should see the journal message trail as well. if the connector is configured correctly to capture and forward messages for the mailbox specified in the journal rule to the 3rd party journal service, and your journal rule is configured for all messages (not just external!) then all should be good and I'd say it's a problem with the 3rd party. You can always log a ticket with Microsoft to investigate as well.
- Hi Dan. Journal rule is configured appropriately. I set up a ticket with Microsoft last week and we'll see what they find out. When I do a message trace on the email that the journaled messages are supposed to be sent to, it only shows the "incoming" emails, none of the outgoing ones I'm sending. I know that they are passing through Microsoft because otherwise I would not be receiving them in my inbox. And, further to that point, they show up in the third party provider's log as being "forwarded" to Microsoft. It definitely seems to be a problem on Microsoft's side.