Share via

Rule Exception of Sender IP not working

Patrick 1 Reputation point
2022-04-14T13:38:22.073+00:00

We are in a hybrid setup. We have not MS365 as our main MX but a local one because we do separate filtering.

So to protect us from Spammers still delievering directly to MIcrosoft, we made a Rule, which forwards all external emails from the internet to the MX entry first. Everything is described in here:

https://practical365.com/how-to-ensure-your-third-party-filtering-gateway-is-secure/

We also added our local Exchange Server as en exception to the forwarding Rule, so we don't get a loop.

But this exception is not working. It still forwards all emails back to our MX again and creates a loop.

When I check the transport log, I see that the rule still was taken, even when the email came from the excepted IP.
So why does it still forward it again?

193152-error.jpg

193068-ip-exeption.jpg

Exchange | Exchange Server | Management
Exchange | Exchange Server | Management
The administration and maintenance of Microsoft Exchange Server to ensure secure, reliable, and efficient email and collaboration services across an organization.

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Patrick 1 Reputation point
    2022-04-15T06:09:27.027+00:00

    Hi joyceshen

    Thanks for the reply. Yes I also tried the other IP formats but it still ignores them.

    The whole rule looks exactly like in the example from the link, just without it being restricted just to the test User.

    193361-e6f8ac6c-6979-4d02-96e1-f73a49237aa0.png

    Really weird that it does not ignore this IP.

  2. Patrick 1 Reputation point
    2022-04-18T09:19:51.277+00:00

    So you think the from IP from the screenshot above is not the real IP MS365 is working with?

    I will check it in ExO with: "Get-MessageTrackingLog -MessageSubject "xxx" | fl"

    But what if it is the same IP ? If it is it seems there is a bug in the excluding via IP function.

    Best regards

  3. Patrick 1 Reputation point
    2022-04-21T07:45:21.8+00:00

    Hi Joce

    It does not find the command mentioned in the article:

    Get-MessageTrackingLog -MessageSubject "xxx" | fl
    Get-MessageTrackingLog: The term 'Get-MessageTrackingLog' is not recognized as a name of a cmdlet, function, script file, or executable program.
    Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

  4. Patrick 1 Reputation point
    2022-04-22T05:35:03.7+00:00

    I firstly connected to the ExO online PowerShell and ran the command. Could it have been changed to a new one?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.