Danstr1
asked on
Exchange 2010 - IP Allow List Not Working
I have two Exchange 2010 servers I manage at different clients where I'm experiencing the same problem. The Exchange anti-spam is enabled on both servers in question. What's occurring is, email sent from specific domains is being rejected regardless of the fact that I have the IP Allow List enabled on each with the sending IP of the problem email domain listed. Despite the IP's appearing in IP Allow List, the server continues to block the messages. I have double verified that both the IP Allow List is enabled and that I have the correct IP addresses listed. I know it's Exchange blocking the messages after reviewing the transport logs where the reason for rejection states, "550 5.7.1 Sender ID (PRA) Domain Does Not Exist." I do have Sender ID enabled and verified that the email domain of this specific sender does not have a SPF record created so it makes perfect sense that the Sender ID test would fail and reject the message aside from the fact that I have it on the IP Allow List. I'm not sure if something is possibly taken precedence over the IP Allow List? I could disable the Sender ID but I'd prefer to know what's causing the issue.
Thanks in advance!
Thanks in advance!
Michael Machie
An email can come from multiple different IPs from the same Domain. For instance, a remote User would not have the same IP when working remotely (unless using a Proxy on that IP), but will have the same Domain info. I would attempt to add the entire Domain name to your Safe Sender's List and see how that goes. This will allow anything from that @Domain to pass through regardless of the IP Allow used.
ASKER
The sending IP has remained consistent when I reviewed the transport logs. However, I did add the domain itself to the whitelist in Exchange by performing the steps below. After doing so, email messages are still being blocked. Error message in transport logs states Sender ID as the reason for the failure. I don't understand why Exchange continues to block the emails in questions!?
Set-ContentFilterConfig –BypassedSenderDomain (“domain.com, domain.com”)
Set-ContentFilterConfig –BypassedSenderDomain (“domain.com, domain.com”)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Sounds like you found the fix. You should close this question as solved by yourself.
ASKER
The is really more of a workaround than a solution.