 | 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: | Alessandro Vesely (ves...@tana.it) | |
| Date: | Jun 25, 2005 9:29:56 am | |
| List: | net.sourceforge.lists.courier-users | |
Rodrigo Severo wrote:
[...] I'm wondering if it might be better to:
a) not to deal with it at all because there might be so few cases
Appealing as this option can be, to make an informed decision we still need a sharp view of what we don't want to deal with. Your clear analysis of the abnamro.com DNS setup proves that Courier has a problem with broken hosts with badly configured DNS records. Thanks for that.
b) try to detect the specific situation when this problem occurs with simple non-obstrusive code and use a more convoluted strategy to choose MXs only then;
That apparently implies saving host status information. Accompanying questions are where and how to store it, when to delete it, etcetera. I would opt for a global db rather than each single control file.
That is not extraneous to an MTA business. Sendmail, for one, does so: " [HostStatus] allows mail to be queued immediately or skipped during a queue " run if there has been a recent failure in connecting to a remote machine " <http://www.sendmail.org/~ca/email/doc8.12/op-sh-2.html>
instead of changing the way Courier chooses MXs for every situation as it's current implementation is quite appropriate most of the times.
Storing host status only when the MTA detects a problem makes sense. Additionally, it can be further restricted to the case when the target MX is not the only one with its weight. To reduce the amount of new problems introduced by the new strategy, the host status can be deleted when the set of MXes changes, when the target MX changes address, when a timeout expires, and similar euristic criteria. In such environment, connection timeout failures can be distributed evenly among sibling MXes.
Is that the kind of solution we're talking about?