Add Reverse DNS Entries for AmeriCommerce's Email-Originating IP Addresses (4)

Completed

Jason

• February 15, 2013 11:24

Many email spam filters are known to block emails originating from an IP address not able to provide Reverse DNS lookup details. As of right now, we have transactional emails originating from AmeriCommerce IP 174.143.73.233 This ip address can be verified by viewing the email header from a store-sent email. Look for the first "Received" line near the bottom of header. Received: from 234507-web4 (unknown [174.143.73.233]) by mi23 (SG) with ESMTP id 5114026e.651d.5acf3f Thu, 07 Feb 2013 13:37:18 -0600 (CST) The message's originating server IP address, 174.143.73.233, has a reverse DNS record of UNKNOWN and was received by SendGrid. Performing a reverse DNS lookup results in a FAILURE. Without being able to verify the originating server, many spam filters simply dump the email.

0

• Official comment

  

  Ryan

  • February 15, 2013 11:24

  The Reverse DNS entries have been added.
• 

  Jason

  • February 15, 2013 13:28

  Testing our transactional emails sent from AmeriCommerce against SpamAssassin rules, every email is being tagged with points for a host with no reverse DNS. http://spamscorechecker.com

  0
• 

  David Blount

  • February 18, 2013 09:41

  I would like to thank everyone for their input. AmeriCommerce has created the Reverse DNS Records for our Web Servers to point to americommerce.com. Thank you, David Blount

  0
• 

  Jason

  • February 19, 2013 14:09

  The subsequent forward lookup verifying the PTR entry is still not working. 174.143.73.233 --- PTR Record ---> americommerce.com americommerce.com --- A Record ---> DOES NOT MATCH (174.143.73.233) Feel free to test it here: http://ipadmin.junkemailfilter.com/rdns.php

  0
• 

  David Blount

  • February 20, 2013 06:10

  This has been corrected. http://www.debouncer.com/reverse-dns-check FCrDNS test result: 174.143.73.233 resolved to smtp4.americommerce.com. smtp4.americommerce.com resolved to 174.143.73.233; rDNS if forward confirmed.

  0
• 

  David Blount

  • February 20, 2013 06:25

  I made one more change for cleanliness on our side. 174.143.73.233 is still showing as failing on http://ipadmin.junkemailfilter.com/rdns.php but it looks like it is cached. Currently every IP address that was not hit by this service is working. Just to double check i tested it in another FCrDNS validation site which can be found in my previous comment, and it passes.

  0

Please sign in to leave a comment.