Matthias Wimmer writes:
Without the patch "testmxlookup tthias.eu" shows the addresses in the incorrect order:# testmxlookup tthias.eu Domain tthias.eu: Relay: mailin.amessage.eu, Priority: 10, Address: ::ffff:212.112.238.55 [ LOCAL ] Relay: mailin.amessage.eu, Priority: 10, Address: 2001:6f8:900:10d::2 [ LOCAL ] After fixing the bug textmxlookup returns the addresses in the correct order: # testmxlookup tthias.eu Domain tthias.eu: Relay: mailin.amessage.eu, Priority: 10, Address: 2001:6f8:900:10d::2 [ LOCAL ] Relay: mailin.amessage.eu, Priority: 10, Address: ::ffff:212.112.238.55 [ LOCAL ]
You will find that DNS servers will themselves randomize the order of IP address and MX records of the same priority, so the order of records that have the same priority is completely irrelevant here.
A series of queries using dig for aol.com or cnn.com shows that each occurence returns MX and A records in a different order.
pgpSI3WvWbnF0.pgp
Description: PGP signature
------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
