<?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 SMTP IPS block problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/smtp-ips-block-problem/m-p/606189#M100418</link>
    <description>&lt;P&gt;I setup ID 3110 (suspicious mail attachment)to deny attacker inline thinking that nobody needs to send those type of attachments and it would cut down on virus's. Worked fine until today when someone internal tried to send one and the IPS blocked my internal smtp server from going to the internet. Is there a way of setting up execptions in the IPS so that my internal IP range is allways allowed access? Or is there a better way of doing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Sun, 10 Mar 2019 10:03:09 GMT</pubDate>
    <dc:creator>dstjames123</dc:creator>
    <dc:date>2019-03-10T10:03:09Z</dc:date>
    <item>
      <title>SMTP IPS block problem</title>
      <link>https://community.cisco.com/t5/network-security/smtp-ips-block-problem/m-p/606189#M100418</link>
      <description>&lt;P&gt;I setup ID 3110 (suspicious mail attachment)to deny attacker inline thinking that nobody needs to send those type of attachments and it would cut down on virus's. Worked fine until today when someone internal tried to send one and the IPS blocked my internal smtp server from going to the internet. Is there a way of setting up execptions in the IPS so that my internal IP range is allways allowed access? Or is there a better way of doing this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:03:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/smtp-ips-block-problem/m-p/606189#M100418</guid>
      <dc:creator>dstjames123</dc:creator>
      <dc:date>2019-03-10T10:03:09Z</dc:date>
    </item>
    <item>
      <title>Re: SMTP IPS block problem</title>
      <link>https://community.cisco.com/t5/network-security/smtp-ips-block-problem/m-p/606190#M100434</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;We've seen false positives with that signature, but YMMV...they've modified it recently so maybe it's fixed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;anyway, to answer your question...there are two ways to handle this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Use an event filter to subtract the action from the alarm. The mail server source ip would part of the criteria in the filter.  You might want to consider creating an event variable for your entire DMZ and creating an event filter that subtracts any of the "deny" actions if DMZ=source. See Event Action Rules-&amp;gt;Even Action Filters in the IDM.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) add the source ip or network to the "never block addresses".  See Blocking-&amp;gt;Blocking Properties in the IDM. I don't believe this works for actions that are "deny"...you'll need an event filter for those.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 08 Jun 2006 17:46:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/smtp-ips-block-problem/m-p/606190#M100434</guid>
      <dc:creator>mhellman</dc:creator>
      <dc:date>2006-06-08T17:46:13Z</dc:date>
    </item>
  </channel>
</rss>

