• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 264
  • Last Modified:

How do I block all traffic from a foreign country using SBS2003 with ISA 2004

Hello all,

I would like to setup a rule to block remote smtp connections from China and Latin America by IP address or range of IP's. I followed the steps outlined in the last post here: http://forums.isaserver.org/m_250018400/mpage_1/key_block%2cchina/tm.htm#250018416 , but now I am getting a ton of event: 15108 warnings in the Application log. What is the proper way to configure ISA to accomplish this task?

Thanks,

Todd  
0
MasPreguntas
Asked:
MasPreguntas
  • 3
1 Solution
 
Keith AlabasterCommented:
I assume you have published your mail server through a publishing rule? By default the listener that gets configured shows Anywhere as the FROM entry. In the bottom half of the FROM box, you will see an exceptions section.

make subnet entries that cover the IP addresses you want to block port 25 traffic for ( highlight the firewall policy then use the toolbox on the right to create subnets etc) then add these entries to the exceptions box. Save the policy.



0
 
Keith AlabasterCommented:
Alternatively of course you could add the exclusions within the SMTP service itself but ISA is probably the best place.
0
 
MasPreguntasAuthor Commented:
I ended up creating a new address range and creating a new firewall access rule. I called the rule 'Spam-killer' with action set to deny all outbound traffic from the freshly created address range to localhost appied to all users. I chose this method over using the SMTP publishing rule, because I decided to just block all access instead of just SMTP. Your method would have worked, so I'll give you the points.

Thanks.
0
 
Keith AlabasterCommented:
Thank you :)
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now