<?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 email logging alerts in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635009#M594037</link>
    <description>&lt;P&gt;Nowadays, most mail servers require authentication and many also require encryption. As far as I can tell, the ASA offers no alternative ports and authentication for email logging setup. Does that mean ASA email logging is not possible in modern environments? What workarounds are their for sending email based logging alerts when your site's email server won't let the ASA connect with old insecure protocols and no authentication?&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 19:36:04 GMT</pubDate>
    <dc:creator>lcaruso</dc:creator>
    <dc:date>2019-03-11T19:36:04Z</dc:date>
    <item>
      <title>smtp email logging alerts</title>
      <link>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635009#M594037</link>
      <description>&lt;P&gt;Nowadays, most mail servers require authentication and many also require encryption. As far as I can tell, the ASA offers no alternative ports and authentication for email logging setup. Does that mean ASA email logging is not possible in modern environments? What workarounds are their for sending email based logging alerts when your site's email server won't let the ASA connect with old insecure protocols and no authentication?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:36:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635009#M594037</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2019-03-11T19:36:04Z</dc:date>
    </item>
    <item>
      <title>Re: smtp email logging alerts</title>
      <link>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635010#M594038</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;If the logging information you're after is typically also available via syslog you could send all of your alerts/warnings/etc to your syslog server.&amp;nbsp; You could then employ a script, such as "swatch" for most *nix varieties, that will watch the log file on the server for "interesting messages" and email those to you.&amp;nbsp; This is one of the methods I employ as a more pro-active way to monitor syslog messages coming from our Cisco devices.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;You can find swatch here if you're interested:&amp;nbsp; &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://sourceforge.net/projects/swatch/"&gt;http://sourceforge.net/projects/swatch/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Ben.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jan 2011 06:30:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635010#M594038</guid>
      <dc:creator>ben_johnson</dc:creator>
      <dc:date>2011-01-17T06:30:43Z</dc:date>
    </item>
    <item>
      <title>Re: smtp email logging alerts</title>
      <link>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635011#M594039</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for your reply. That's a good idea for sites that are sending to syslog servers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jan 2011 17:16:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/smtp-email-logging-alerts/m-p/1635011#M594039</guid>
      <dc:creator>lcaruso</dc:creator>
      <dc:date>2011-01-17T17:16:39Z</dc:date>
    </item>
  </channel>
</rss>

