<?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 Mail loopback in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/mail-loopback/m-p/2004810#M435219</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I hate to bump a thread but I'm hoping someone has some idea of the "right way" to route mail between my vlans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 06 Jun 2012 01:55:09 GMT</pubDate>
    <dc:creator>mikeschietinger</dc:creator>
    <dc:date>2012-06-06T01:55:09Z</dc:date>
    <item>
      <title>Mail loopback</title>
      <link>https://community.cisco.com/t5/network-security/mail-loopback/m-p/2004809#M435215</link>
      <description>&lt;P&gt;Ok so, I have an ASA acting as a firewall for a bunch of hosted servers, includig a bunch of Small Business servers. Each customer server is on its own vlan and are trunked into the asa. My office mail server is on the inside interface. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside&amp;nbsp;&amp;nbsp; xxx.xxx.xxx.162&amp;nbsp;&amp;nbsp; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Inside 192.168.1.0 =vlan1 my mail server at 192.168.1.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;trunk10 192.168.10.0 =vlan10 pat/nat to xxx.xxx.xxx.163&lt;/P&gt;&lt;P&gt;trunk20 192.168.20.0 =vlan20 pat/nat to xxx.xxx.xxx.164&lt;/P&gt;&lt;P&gt;trunk30 192.168.30.0 =vlan30 pat/nat to xxx.xxx.xxx.165&lt;/P&gt;&lt;P&gt;etc&lt;/P&gt;&lt;P&gt;pat/nat rules are set up so that each customer has their own public ip for services they are running (https/mail mostly)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've got some other stuff going on but thats the key config.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Everything works great except that hosted customers cant send me emails and viseversa as well as inter-customer. I understand why thats not allowed but I need to get it to work in a scaleable way with out something crazy. Best I can tell I either need to route inter-customer mail internally and do a bunch on the exchange/dns side, ot get the asa to allow traffic on port 25 between the outside interface IPs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also if something above is totally jacked up let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks in advance&lt;/P&gt;&lt;P&gt;Mike Schietinger&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 23:14:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mail-loopback/m-p/2004809#M435215</guid>
      <dc:creator>mikeschietinger</dc:creator>
      <dc:date>2019-03-11T23:14:19Z</dc:date>
    </item>
    <item>
      <title>Mail loopback</title>
      <link>https://community.cisco.com/t5/network-security/mail-loopback/m-p/2004810#M435219</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; I hate to bump a thread but I'm hoping someone has some idea of the "right way" to route mail between my vlans&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jun 2012 01:55:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/mail-loopback/m-p/2004810#M435219</guid>
      <dc:creator>mikeschietinger</dc:creator>
      <dc:date>2012-06-06T01:55:09Z</dc:date>
    </item>
  </channel>
</rss>

