<?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: PTR RECORDS and static translations in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768104#M1036856</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes sir.&lt;/P&gt;&lt;P&gt;The solution was to have the firm we were speaking to point to a 2nd IP as a 2nd PTR and then we xlated the spam filter to IT, and we were OK.  A band-aid, but it worked! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;  I hope this helps you!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 19 Apr 2008 01:16:25 GMT</pubDate>
    <dc:creator>netsec123</dc:creator>
    <dc:date>2008-04-19T01:16:25Z</dc:date>
    <item>
      <title>PTR RECORDS and static translations</title>
      <link>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768102#M1036828</link>
      <description>&lt;P&gt;Hi.  I am certain the issue we are experiencing is one that is very common.  We have an internal spam filter [10.1.1.5] that receives all smtp traffic by being translated to 1.1.1.1 [obviously an example IP] on the Internet.  Therefore, our public mail.acme.com is 1.1.1.1.  Now, our mail server [10.1.1.10] send OUT mail on 1.1.1.2 [public].  The PROBLEM is that today, many firms are using reverse lookups when they receive an email.  Thus, an email received from us has a source address 1.1.1.2 yet our 'SPF' record returns 1.1.1.1 for the lookup.  The mail is droppeed.  We need to have all smtp outbound mail 'look like' its source address is 1.1.1.2 EVEN THOUGH incoming traffic for 1.1.1.2 goes to the spam filter at 10.1.1.1.  I hope that makes sense.... I've tried reversing the parameters in static translations to now avail... Please help.&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:50:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768102#M1036828</guid>
      <dc:creator>netsec123</dc:creator>
      <dc:date>2019-03-11T10:50:19Z</dc:date>
    </item>
    <item>
      <title>Re: PTR RECORDS and static translations</title>
      <link>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768103#M1036845</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Did you ever get this resolved?  If so can you share the fix?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 18 Apr 2008 16:04:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768103#M1036845</guid>
      <dc:creator>Matt Boeckner</dc:creator>
      <dc:date>2008-04-18T16:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: PTR RECORDS and static translations</title>
      <link>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768104#M1036856</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes sir.&lt;/P&gt;&lt;P&gt;The solution was to have the firm we were speaking to point to a 2nd IP as a 2nd PTR and then we xlated the spam filter to IT, and we were OK.  A band-aid, but it worked! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;  I hope this helps you!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 19 Apr 2008 01:16:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ptr-records-and-static-translations/m-p/768104#M1036856</guid>
      <dc:creator>netsec123</dc:creator>
      <dc:date>2008-04-19T01:16:25Z</dc:date>
    </item>
  </channel>
</rss>

