This is a discussion on Re: [courier-users] MX randomizing: trying to understand thesources. within the Courier-Imap forums, part of the Mail Servers and Related category; On 24 Jun 2005 at 12:48, Rodrigo Severo wrote: > I agree completely. It isn't bind randomness strategy ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
On 24 Jun 2005 at 12:48, Rodrigo Severo wrote:
> I agree completely. It isn't bind randomness strategy per si that > creates the distortion. Nor is Courier's MX choosing strategy either. > It's the *interaction* of bind randomness strategy and Courier MX > choosing strategy that produces the distortion. Which reinforces my point, I think. If the administrator of the mail servers behind the MX records wants to ensure that all of their same priority MX'ed mail systems are attempted, they should put together their MX lists appropriately. Personally, I wouldn't mix a lot of same *and* different priority MX records in the MX list. I would either use all the same priority or establish different priorities to create essentially a backup system and overload the A record for the first MX'ed system. I've done both and been satisfied with the results. But the more you describe the issue, the less it looks like something that should be resolved at the point of the sending system. Scott ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/.../courier-users |