<?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 Email Logging Source Interface in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829626#M488831</link>
    <description>&lt;P&gt;I've got email logging for a few specific syslog messages working and sending to an email server on the inside network.&amp;nbsp; However, the source IP ends up being the DMZ interface.&amp;nbsp; Is there a way to force it to use the inside IP instead?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Code Version 7.22&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside Interface IP:&amp;nbsp; 10.104.36.4&amp;nbsp; Mask:255.255.255.0&lt;/P&gt;&lt;P&gt;DMZ IP: 10.100.20.1&amp;nbsp; Mask:255.255.255.0&lt;/P&gt;&lt;P&gt;SMTP Server IP: 10.100.10.100&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logging commands in config:&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging list email-alerts message 106100&lt;/P&gt;&lt;P&gt;logging mail email-alerts&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;logging from-address &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:ASA@xyz.com" target="_blank"&gt;ASA@xyz.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;logging recipient-address &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:tgw@xyz.com" target="_blank"&gt;tgw@xyz.com&lt;/A&gt;&lt;SPAN&gt; level debugging&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 22:12:49 GMT</pubDate>
    <dc:creator>terrygwazdosky</dc:creator>
    <dc:date>2019-03-11T22:12:49Z</dc:date>
    <item>
      <title>ASA Email Logging Source Interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829626#M488831</link>
      <description>&lt;P&gt;I've got email logging for a few specific syslog messages working and sending to an email server on the inside network.&amp;nbsp; However, the source IP ends up being the DMZ interface.&amp;nbsp; Is there a way to force it to use the inside IP instead?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ASA Code Version 7.22&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside Interface IP:&amp;nbsp; 10.104.36.4&amp;nbsp; Mask:255.255.255.0&lt;/P&gt;&lt;P&gt;DMZ IP: 10.100.20.1&amp;nbsp; Mask:255.255.255.0&lt;/P&gt;&lt;P&gt;SMTP Server IP: 10.100.10.100&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Logging commands in config:&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging list email-alerts message 106100&lt;/P&gt;&lt;P&gt;logging mail email-alerts&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;logging from-address &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:ASA@xyz.com" target="_blank"&gt;ASA@xyz.com&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;logging recipient-address &lt;/SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:tgw@xyz.com" target="_blank"&gt;tgw@xyz.com&lt;/A&gt;&lt;SPAN&gt; level debugging&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 22:12:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829626#M488831</guid>
      <dc:creator>terrygwazdosky</dc:creator>
      <dc:date>2019-03-11T22:12:49Z</dc:date>
    </item>
    <item>
      <title>ASA Email Logging Source Interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829627#M488832</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Terry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The ASA will automatically select the source interface based on the routing table, which is not a configurable option. This is by design as the ASA will only allow communication to an interface from hosts behind that same interface. In other words, the server won't be able to reach the inside interface if it is behind the DMZ interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 14 Jan 2012 16:58:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829627#M488832</guid>
      <dc:creator>mirober2</dc:creator>
      <dc:date>2012-01-14T16:58:18Z</dc:date>
    </item>
    <item>
      <title>ASA Email Logging Source Interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829628#M488833</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I should have secified in my original post - the mail server is behind the inside interface not the DMZ.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2012 13:17:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829628#M488833</guid>
      <dc:creator>terrygwazdosky</dc:creator>
      <dc:date>2012-01-16T13:17:58Z</dc:date>
    </item>
    <item>
      <title>ASA Email Logging Source Interface</title>
      <link>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829629#M488834</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Terry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So is the SMTP server on the inside??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you provide a show route from your asa?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Julio&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 16 Jan 2012 18:50:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-email-logging-source-interface/m-p/1829629#M488834</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-01-16T18:50:53Z</dc:date>
    </item>
  </channel>
</rss>

