Original email header does not appear after exchange transport rule

Question

Hello,

I have an email account that has several forwardings applied to it through a server transport rule and when the email arrives in the mailbox, the original sender's data does not appear in the header. This causes the antiphishing filters not to be applied. For example, if that account receives an email from Gmail, after applying the forwarding rules, the Gmail data does not appear in the header and if it is spam/phishing, it is not detected by the filters. I have read that this can be solved by configuring the Enhanced Filtering for Connectors. The problem i have is that this option is applied to the inbound connectors and my email account does not go through any inbound connector. Does any to know if there is a solution to be able to keep the data of the original email in the header?

I have an hybrid exchange enviroment.

Thanks.

Answer 1

Hello, @Jose TB,

Welcome to the Microsoft Q&A platform!

Based on your description, I understand that you encountered a situation where the original sender's data was not in the header after the email was forwarded through the server transport rules, affecting the proper functioning of the phishing filter.

To solve your problem, I have performed the following test.

1. User A sends an email directly to user B. User B receives the email successfully, and the sender in the header is user A.

2. Set up automatic forwarding for user C's mailbox, with the destination set to user B. User A sends an email to user C. User B receives the email successfully and the sender in the header is still user A.

I am using an Outlook mailbox for this test and the data shown in the header is always the original sender's data, regardless of whether automatic forwarding is enabled or not. It doesn't reproduce what you're describing. Regarding your reference to “Gmail data”, is that where I circled in the screenshot? This issue may be related to the Gmail mailbox you are using, do emails from Outlook have the same problem? I hope you will take the time to reply to me, it will help me to resolve your issue faster.

If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

Thank you for your support and understanding.

Best Wishes,

Alex Zhang

Answer 2

Hello Alex,

Thanks for your answer. You have understood it perfectly. I already thought about the solution you indicated, but I would like to continue using transport server rules. If there is no other option, i will apply these solutions

Regarding my reference to “Gmail data”, yes, is that you circled in the screenshot. Gmail is only an example, the problem happens from any sender (User A in your example), any sender's data was not in the header after forwarded through transport server rules, affecting the proper functioning of the phishing filter.

BR,

Jose