[Last Call] Learn how to a build a cloud-first strategyRegister Now


Exchange 2010 - IP Allow List Not Working

Posted on 2014-07-11
Medium Priority
Last Modified: 2014-10-18
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!
Question by:Danstr1
  • 3
  • 2
LVL 13

Expert Comment

by:Michael Machie
ID: 40191405
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.

Author Comment

ID: 40194762
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”)

Accepted Solution

Danstr1 earned 0 total points
ID: 40211796
I ended resolving the issue by disabling the Sender ID filtering in the built-in Exchange anti-spam.  I was hesitant to do so but I do have additional spam mechanisms in place. I still confused as to why the messages in question were continuing to be filtered despite the fact that I had included them in the safe sender's list as well as their domain in the bypassed sender domain. The issue really was on their end since they didn't have SPF records created which is why the messages were being blocked in the first place. We just need a means from time to time to allow specific email domains through since a fair amount of the companies we interact with have limited if any IT support.
LVL 13

Expert Comment

by:Michael Machie
ID: 40217230
Sounds like you found the fix. You should close this question as solved by yourself.

Author Closing Comment

ID: 40388244
The is really more of a workaround than a solution.

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

If something goes wrong with Exchange, your IT resources are in trouble.All Exchange server migration processes are not designed to be identical and though migrating email from on-premises Exchange mailbox to Cloud’s Office 365 is relatively simple…
This month, Experts Exchange sat down with resident SQL expert, Jim Horn, for an in-depth look into the makings of a successful career in SQL.
how to add IIS SMTP to handle application/Scanner relays into office 365.
Whether it be Exchange Server Crash Issues, Dirty Shutdown Errors or Failed to mount error, Stellar Phoenix Mailbox Exchange Recovery has always got your back. With the help of its easy to understand user interface and 3 simple steps recovery proced…
Suggested Courses
Course of the Month17 days, 18 hours left to enroll

830 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question