On 03/06/2016 05:35 PM, Stephen J. Turnbull wrote: > > But note that as a practical matter some receiving sites demand (or > use to demand) that a sender's PTR roundtrip (ie, A -> PTR -> same A). > > Is that not a problem any more?
Thanks for bringing this up. It is definitely still a problem and it is a problem here too, but these are two separate issues. The issue I raised and which is now fixed is regarding mail to x...@mailman3.org. That's where the MX for mailman3.org should point to a name with an A and not a CNAME record. I neglected to even think about the full circle DNS which is for outgoing mail. The issue here is that the server's IP address has no rDNS PTR record at all. The authority for this is rackspace, so they would need to install a PTR from 201.228.239.104.in-addr.arpa. (i.e.rDNS for 104.239.228.201) to mail.mailman3.org. Probably infrastruct...@python.org can help with this. -- Mark Sapiro <m...@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailman-Developers mailing list Mailman-Developers@python.org https://mail.python.org/mailman/listinfo/mailman-developers Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-developers%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-developers/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
