 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Cisco ASA 5505 Limit IP that can send mail to the Internal network</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/asa-5505-limit-ip-that-can-send-mail-to-the-internal-network/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/asa-5505-limit-ip-that-can-send-mail-to-the-internal-network/</link>
	<description></description>
	<lastBuildDate>Sat, 25 May 2013 13:28:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: blankreg</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/asa-5505-limit-ip-that-can-send-mail-to-the-internal-network/#comment-63413</link>
		<dc:creator>blankreg</dc:creator>
		<pubDate>Mon, 11 May 2009 18:12:09 +0000</pubDate>
		<guid isPermaLink="false">#comment-63413</guid>
		<description><![CDATA[Thanks Guys - I appreciate the feedback :-)]]></description>
		<content:encoded><![CDATA[<p>Thanks Guys &#8211; I appreciate the feedback <img src='http://itknowledgeexchange.techtarget.com/itanswers/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vnoome</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/asa-5505-limit-ip-that-can-send-mail-to-the-internal-network/#comment-63404</link>
		<dc:creator>vnoome</dc:creator>
		<pubDate>Mon, 11 May 2009 17:02:01 +0000</pubDate>
		<guid isPermaLink="false">#comment-63404</guid>
		<description><![CDATA[Good posting BLankReq!!!]]></description>
		<content:encoded><![CDATA[<p>Good posting BLankReq!!!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: edctech</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/asa-5505-limit-ip-that-can-send-mail-to-the-internal-network/#comment-63372</link>
		<dc:creator>edctech</dc:creator>
		<pubDate>Sat, 09 May 2009 01:36:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-63372</guid>
		<description><![CDATA[Thanks for the information and it worked perfectly. I knew it had to be a rule, but I was looking at the static routes and not the access list. Thanks again, and by the way it did stop the spam instantly.]]></description>
		<content:encoded><![CDATA[<p>Thanks for the information and it worked perfectly. I knew it had to be a rule, but I was looking at the static routes and not the access list. Thanks again, and by the way it did stop the spam instantly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: blankreg</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/asa-5505-limit-ip-that-can-send-mail-to-the-internal-network/#comment-63363</link>
		<dc:creator>blankreg</dc:creator>
		<pubDate>Fri, 08 May 2009 21:27:57 +0000</pubDate>
		<guid isPermaLink="false">#comment-63363</guid>
		<description><![CDATA[KevinBeaver is basically right. You need to create an access list that allows mail from the spam blocker, but not from anywhere else. It will also need to allow any other traffic to any hosted systems, such as a web server. It will also block anything else that is not implicitly allowed, as there is an implied deny everything at the end of any access list.

It should look sometihng like this

access-list Internet-In permit tcp host {IP of spam blocker} host {public IP of your Mailhost} eq 25
access-list Internet-In deny ip any host {public IP of your Mailhost}
access-list Internet-In permit [other services you want to allow in]

Then apply this to the inbound traffic on the &#039;outside&#039; interface with the command

access-group Internet-In in interface outside

Then the only mail traffic that will hit your mail server will be from the spam blocker.

PM me if you need something more detailed for your particular network.]]></description>
		<content:encoded><![CDATA[<p>KevinBeaver is basically right. You need to create an access list that allows mail from the spam blocker, but not from anywhere else. It will also need to allow any other traffic to any hosted systems, such as a web server. It will also block anything else that is not implicitly allowed, as there is an implied deny everything at the end of any access list.</p>
<p>It should look sometihng like this</p>
<p>access-list Internet-In permit tcp host {IP of spam blocker} host {public IP of your Mailhost} eq 25<br />
access-list Internet-In deny ip any host {public IP of your Mailhost}<br />
access-list Internet-In permit [other services you want to allow in]</p>
<p>Then apply this to the inbound traffic on the &#8216;outside&#8217; interface with the command</p>
<p>access-group Internet-In in interface outside</p>
<p>Then the only mail traffic that will hit your mail server will be from the spam blocker.</p>
<p>PM me if you need something more detailed for your particular network.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.012 seconds using memcached
Object Caching 314/317 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-05-25 15:00:26 -->