4 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Found small bug i...
FromSent OnAttachments
Matthias WimmerNov 27, 2007 6:14 pm 
Sam VarshavchikNov 27, 2007 6:48 pm 
Arturo 'Buanzo' BusleimanNov 28, 2007 2:33 am 
Matthias WimmerNov 28, 2007 3:02 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Found small bug in rfc1035/rfc1035mxlist.cActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Nov 27, 2007 6:48:27 pm
List:net.sourceforge.lists.courier-users

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.