

![]() | Start a set with this search |
![]() | Include this search in one of my sets |
![]() | Exclude this search from one of my sets |
![]() | Permalink to these results Paste this link in email or IM: |
| Atom feed for tracking future search results Paste this URL into your reader: |
29 messages in net.sourceforge.lists.courier-usersRe: [courier-users] MX randomizing: t...| From | Sent On | Attachments |
|---|---|---|
| Rodrigo Severo | Jun 22, 2005 1:28 pm | |
| Sam Varshavchik | Jun 22, 2005 2:05 pm | |
| Rodrigo Severo | Jun 23, 2005 2:32 am | |
| Arno | Jun 23, 2005 4:06 am | |
| Rodrigo Severo | Jun 23, 2005 5:12 am | |
| Sam Varshavchik | Jun 23, 2005 6:06 am | |
| Rodrigo Severo | Jun 23, 2005 6:24 am | |
| Sam Varshavchik | Jun 23, 2005 6:58 am | |
| Ben Kennedy | Jun 23, 2005 7:07 am | |
| Sam Varshavchik | Jun 23, 2005 7:26 am | |
| Gordon Messmer | Jun 23, 2005 8:39 am | |
| Rodrigo Severo | Jun 23, 2005 1:06 pm | |
| Alessandro Vesely | Jun 24, 2005 12:04 am | |
| Rodrigo Severo | Jun 24, 2005 4:32 am | |
| Scott Morizot | Jun 24, 2005 5:31 am | |
| Sam Varshavchik | Jun 24, 2005 6:00 am | |
| Rodrigo Severo | Jun 24, 2005 6:43 am | |
| Sam Varshavchik | Jun 24, 2005 7:06 am | |
| Scott Morizot | Jun 24, 2005 7:13 am | |
| Rodrigo Severo | Jun 24, 2005 8:02 am | |
| Gordon Messmer | Jun 24, 2005 8:21 am | |
| Gordon Messmer | Jun 24, 2005 8:26 am | |
| Rodrigo Severo | Jun 24, 2005 8:50 am | |
| Scott Morizot | Jun 24, 2005 9:48 am | |
| Sam Varshavchik | Jun 24, 2005 10:33 am | |
| Rodrigo Severo | Jun 24, 2005 10:41 am | |
| Alessandro Vesely | Jun 25, 2005 9:29 am | |
| Rodrigo Severo | Jun 26, 2005 7:35 am | |
| Rodrigo Severo | Jun 26, 2005 9:08 am |

![]() | Permalink for this message Paste this link in email or IM: |
![]() | Permalink for this thread Paste this link in email or IM: |
| Atom feed for this thread Paste this URL into your reader: |
| Subject: | Re: [courier-users] MX randomizing: trying to understand thesources. | Actions... |
|---|---|---|
| From: | Rodrigo Severo (rodr...@fabricadeideias.com) | |
| Date: | Jun 24, 2005 8:02:50 am | |
| List: | net.sourceforge.lists.courier-users | |
Sam Varshavchik wrote:
Rodrigo Severo writes:
Let's see this example:
10 brsmtp02.br.abnamro.com 10 brsmtp04.br.abnamro.com 15 naxpf001.abnamro.com 15 naxpf002.abnamro.com 15 naxpf003.abnamro.com 15 naxpf011.abnamro.com 15 naxpf012.abnamro.com 15 naxpf013.abnamro.com 30 plum03ap.abnamro.com 30 walnut001ap.abnamro.com
In this case brsmtp02.br.abnamro.com has 9 out of 10 chances of being contacted and brsmtp04.br.abnamro.com have the remaining 1 out of 10
No.
The MX records are always sorted according to their priority.
Ok.
brsmtp02 will be contacted 50% of the time, with brsmtp04 taking the other 50%.
Being dependent on the way bind randomizes it's answers the distribution won't have anything near a 50/50 distribution, I'm afraid.
Let me explain why. The way bind randomizes it's answers, only 10 different answers are possible:
Answer 1) 10 brsmtp02.br.abnamro.com 10 brsmtp04.br.abnamro.com 15 naxpf001.abnamro.com 15 naxpf002.abnamro.com 15 naxpf003.abnamro.com 15 naxpf011.abnamro.com 15 naxpf012.abnamro.com 15 naxpf013.abnamro.com 30 plum03ap.abnamro.com 30 walnut001ap.abnamro.com
Answer 2) 10 brsmtp04.br.abnamro.com 15 naxpf001.abnamro.com 15 naxpf002.abnamro.com 15 naxpf003.abnamro.com 15 naxpf011.abnamro.com 15 naxpf012.abnamro.com 15 naxpf013.abnamro.com 30 plum03ap.abnamro.com 30 walnut001ap.abnamro.com 10 brsmtp02.br.abnamro.com
Answer 3) 15 naxpf001.abnamro.com 15 naxpf002.abnamro.com 15 naxpf003.abnamro.com 15 naxpf011.abnamro.com 15 naxpf012.abnamro.com 15 naxpf013.abnamro.com 30 plum03ap.abnamro.com 30 walnut001ap.abnamro.com 10 brsmtp02.br.abnamro.com 10 brsmtp04.br.abnamro.com
Answer 4) 15 naxpf002.abnamro.com 15 naxpf003.abnamro.com 15 naxpf011.abnamro.com 15 naxpf012.abnamro.com 15 naxpf013.abnamro.com 30 plum03ap.abnamro.com 30 walnut001ap.abnamro.com 10 brsmtp02.br.abnamro.com 10 brsmtp04.br.abnamro.com 15 naxpf001.abnamro.com
and so on.
Please notice that only answer 2 will make Courier contact brsmtp04.br.abnamro.com. All other 9 will make Courier contact brsmtp02.br.abnamro.com. Obviously I'm referring to temporary delivery failures situations, not to failed connections.
This is why I'm saying Courier won't get a 50/50 distribution as expected but 1/9. I hope this is clearer now.
This is why I believe something else should be done to, in this situation for example, get nearer a 50/50 distribution of the MX Courier tries to contact.
Which one will be tried for a given connection attempts depends on the response from the DNS server.
This is already understood.
Rodrigo







