<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic ASA - Inspect ESMTP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479971#M689170</link>
    <description>&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;I am working with an ASA 5520 with a SPAM appliance located within the DMZ.&amp;nbsp; Not all smtp connections are being corrupted by the inspect esmtp setting, just a few.&amp;nbsp; It was discovered that those few sites that are connecting to the SPAM appliance traverse 2 additional firewalls (1 ASA and 1 PIX), *before* their smtp traffic hits the Internet to continue on to our DMZ.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Why would this be the case?&amp;nbsp; Is it due to passing through two additional firewalls that may be adjusting the headers (static NAT, etc.)?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;If we are not comfortable turning off the inspect esmtp setting, is it possible to write a specific policy that would include these few sites MX records?&amp;nbsp; If so, how might that be done?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 17:51:58 GMT</pubDate>
    <dc:creator>cdcjim2877</dc:creator>
    <dc:date>2019-03-11T17:51:58Z</dc:date>
    <item>
      <title>ASA - Inspect ESMTP</title>
      <link>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479971#M689170</link>
      <description>&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;I am working with an ASA 5520 with a SPAM appliance located within the DMZ.&amp;nbsp; Not all smtp connections are being corrupted by the inspect esmtp setting, just a few.&amp;nbsp; It was discovered that those few sites that are connecting to the SPAM appliance traverse 2 additional firewalls (1 ASA and 1 PIX), *before* their smtp traffic hits the Internet to continue on to our DMZ.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;Why would this be the case?&amp;nbsp; Is it due to passing through two additional firewalls that may be adjusting the headers (static NAT, etc.)?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="background-color: #f8fafd;"&gt;If we are not comfortable turning off the inspect esmtp setting, is it possible to write a specific policy that would include these few sites MX records?&amp;nbsp; If so, how might that be done?&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 17:51:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479971#M689170</guid>
      <dc:creator>cdcjim2877</dc:creator>
      <dc:date>2019-03-11T17:51:58Z</dc:date>
    </item>
    <item>
      <title>Re: ASA - Inspect ESMTP</title>
      <link>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479972#M689198</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You could create an access list&lt;/P&gt;&lt;P&gt; that matches specific server ip addresses and put it under the policy map and inspect esmtp on it&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;------------&lt;/P&gt;&lt;P&gt;access-l esmtp-acl deny tcp &lt;IP not="" to="" inspect=""&gt; any eq 25&lt;/IP&gt;&lt;/P&gt;&lt;P&gt;access-l esmtp-acl perm tcp any any eq 25&lt;/P&gt;&lt;P&gt;class-m esmtp-cm&lt;/P&gt;&lt;P&gt;&amp;nbsp; match access-l esmtp-acl&lt;/P&gt;&lt;P&gt;policy-map globasl_policy&lt;/P&gt;&lt;P&gt;&amp;nbsp; class espmtp-cm&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; inspect esmtp&lt;/P&gt;&lt;P&gt;------------&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PK&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 May 2010 00:48:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479972#M689198</guid>
      <dc:creator>Panos Kampanakis</dc:creator>
      <dc:date>2010-05-29T00:48:13Z</dc:date>
    </item>
    <item>
      <title>Re: ASA - Inspect ESMTP</title>
      <link>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479973#M689216</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, this is what I needed.&amp;nbsp; Thank you PK,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jim&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 29 May 2010 14:09:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-inspect-esmtp/m-p/1479973#M689216</guid>
      <dc:creator>cdcjim2877</dc:creator>
      <dc:date>2010-05-29T14:09:55Z</dc:date>
    </item>
  </channel>
</rss>

