<?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: Routing email to different servers based on domain name. in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217907#M860816</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Roshan,&lt;/P&gt;&lt;P&gt;Will this work if both the mail domains are received from the the same source? i.e. the mx records for both companya.co.uk and companyb.com are set to Messagelabs for spam and virus filtering, Messagelabs then deliver the mail directly to the public interface of the ASA and so will appear to have come from the same place, and is delivered to the same interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;John.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 16 Apr 2009 16:55:06 GMT</pubDate>
    <dc:creator>johnverdon</dc:creator>
    <dc:date>2009-04-16T16:55:06Z</dc:date>
    <item>
      <title>Routing email to different servers based on domain name.</title>
      <link>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217905#M860813</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;Is it possible to deliver email for 2 different domain names to 2 different internal servers? &lt;/P&gt;&lt;P&gt;For example, the emails for companya.co.uk and companyb.com are both delivered from the same mail filtering company and are received on the same external interface of the ASA but need to be delivered to different mail servers internally.&lt;/P&gt;&lt;P&gt;I susspect that I need to do some type of SMTP inspection but have no idea how to achieve this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;John.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:19:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217905#M860813</guid>
      <dc:creator>johnverdon</dc:creator>
      <dc:date>2019-03-11T15:19:14Z</dc:date>
    </item>
    <item>
      <title>Re: Routing email to different servers based on domain name.</title>
      <link>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217906#M860814</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is possible to deliver two different domain emails to two different internal servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For example, the Public IP address for companya.co.uk=A.A.A.A and for companyb.com=B.B.B.B, the respective private address of the servers be P.P.P.A and P.P.P.B.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In ASA do the static nat for the servers&lt;/P&gt;&lt;P&gt;static (inside,outside) A.A.A.A P.P.P.A&lt;/P&gt;&lt;P&gt;static (inside,outside) B.B.B.B P.P.P.B&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, whenever email for companya.co.uk arrives it will be sent to inside P.P.P.A&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Note: This configuration is made on assumption that you have internal Email Server for companya.co.uk and companyb.com&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2009 00:50:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217906#M860814</guid>
      <dc:creator>roshan.maskey</dc:creator>
      <dc:date>2009-04-16T00:50:38Z</dc:date>
    </item>
    <item>
      <title>Re: Routing email to different servers based on domain name.</title>
      <link>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217907#M860816</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Roshan,&lt;/P&gt;&lt;P&gt;Will this work if both the mail domains are received from the the same source? i.e. the mx records for both companya.co.uk and companyb.com are set to Messagelabs for spam and virus filtering, Messagelabs then deliver the mail directly to the public interface of the ASA and so will appear to have come from the same place, and is delivered to the same interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;John.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2009 16:55:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217907#M860816</guid>
      <dc:creator>johnverdon</dc:creator>
      <dc:date>2009-04-16T16:55:06Z</dc:date>
    </item>
    <item>
      <title>Re: Routing email to different servers based on domain name.</title>
      <link>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217908#M860817</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've run something similar in the past. &lt;/P&gt;&lt;P&gt;As long at the static NATs are in place and Messagelabs know which public IP to forward to, (per domain) then you're good to go.  &lt;/P&gt;&lt;P&gt;As an extra (and you may have already done this) but it may be worth while locking down your ACLs to allow only MessageLabs to communicate with your email servers on port 25.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 16 Apr 2009 18:43:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/routing-email-to-different-servers-based-on-domain-name/m-p/1217908#M860817</guid>
      <dc:creator>AxiomConsulting</dc:creator>
      <dc:date>2009-04-16T18:43:03Z</dc:date>
    </item>
  </channel>
</rss>

