<?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 Re: Outlook access problem for Inside hosts in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726652#M557083</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As a quick test you could try disabling esmtp inspection to see if that makes any difference.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 Apr 2011 08:35:11 GMT</pubDate>
    <dc:creator>sean_evershed</dc:creator>
    <dc:date>2011-04-27T08:35:11Z</dc:date>
    <item>
      <title>Outlook access problem for Inside hosts</title>
      <link>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726650#M557081</link>
      <description>&lt;P&gt;Dear Gurus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using ASA 5505 firewall with base-license. I connected my firewall to one cisco 3750 switch where i created 5 vlans. I done NATing for all vlans and they able to get internet and working fine. They able to&amp;nbsp; browse all internet sites like gmail and yahoo mail.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;All internal users are configured to use Outlook for their webmail. Here the problem is with outlook they are unable to send and receive the mails.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If they directly connected their system using public ip( Directly from ISP) they able to send and receive mails from outlook.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please help me to solve the issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For your reference i am attaching the sh run configuration below.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Janardhan&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 20:25:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726650#M557081</guid>
      <dc:creator>Janardhan Meesala</dc:creator>
      <dc:date>2019-03-11T20:25:53Z</dc:date>
    </item>
    <item>
      <title>Re: Outlook access problem for Inside hosts</title>
      <link>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726651#M557082</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Janardhan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What syslogs do you see on the ASA when you attempt to send mail traffic through it? To enable logging:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;logging buffered 7&lt;/P&gt;&lt;P&gt;logging on&lt;/P&gt;&lt;P&gt;sh log&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Anu.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2011 08:12:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726651#M557082</guid>
      <dc:creator>Anu M Chacko</dc:creator>
      <dc:date>2011-04-27T08:12:53Z</dc:date>
    </item>
    <item>
      <title>Re: Outlook access problem for Inside hosts</title>
      <link>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726652#M557083</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;As a quick test you could try disabling esmtp inspection to see if that makes any difference.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 Apr 2011 08:35:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/outlook-access-problem-for-inside-hosts/m-p/1726652#M557083</guid>
      <dc:creator>sean_evershed</dc:creator>
      <dc:date>2011-04-27T08:35:11Z</dc:date>
    </item>
  </channel>
</rss>

