Bluehost.com Web Hosting $6.95

Re: [courier-users] Re: Automatically use secondary MX host if primary

This is a discussion on Re: [courier-users] Re: Automatically use secondary MX host if primary within the Courier-Imap forums, part of the Mail Servers and Related category; Malcolm Weir wrote: >>-----Original Message----- >>From: Sam Varshavchik >>Sent: Tuesday, June 21, 2005 12:...


Go Back   Usenet Forums > Mail Servers and Related > Courier-Imap

FAQ Members List Calendar Search Today's Posts Mark Forums Read
  #1 (permalink)  
Old 06-21-2005
Rodrigo Severo
 
Posts: n/a
Default Re: [courier-users] Re: Automatically use secondary MX host if primary

Malcolm Weir wrote:

>>-----Original Message-----
>>From: Sam Varshavchik
>>Sent: Tuesday, June 21, 2005 12:11 PM
>>
>>

>
>
>
>>>>So, until modern technology advances to such a point, the
>>>>only logical
>>>>thing to do is attempt to deliver E-mail repeatedly, and follow the
>>>>preferred logic for making each delivery attempt: pick a
>>>>primary MX at
>>>>random, if you can't connect it to it, pick a secondary MX
>>>>at random, and so on.
>>>>
>>>>

>
>
>
>>>I have to admit I am starting to come around to understanding
>>>Rodrigo's viewpoint on this, however. What is the *downside* of
>>>having Courier retry a different (same-priority if exists, or next
>>>lowest, as usual) MX rather than the same
>>>*potentially*-broken one, after the usual interval?
>>>
>>>

>
>
>
>>If there are multiple primary MXs set, Courier should already
>>pick one at random with each delivery attempt.
>>
>>

>
>And, contrary to the implication, it would be a BAD idea to include logic
>that selects lower priority ("secondary") MXs for the subsequent attempts
>unless (all) the higher priority ones cannot be contacted.
>
>Why?
>
>Well, how do you know that the _list_ of MXs hasn't been changed between
>attempts?
>

If this is a concern, Courier can fetch a new list at every delivery
attempt. Discard the ones it already tried and pick the remaining top
priority one.

> And if it has, presumably the recipient had a reason for so
>doing.
>
>

I agree.

>Multiple MXs with priorities are largely an artifact of unreliable
>multi-path networks (i.e. dial-ups).
>

I'm really in no position as to speak about the reasons other sys admins
might setup multiple MXs with priorities. The real fact is that they
still do. I'm just trying to make the best use of it.

> In this day and age, the chances of
>usefully using secondary MXs seems to me to be slight, except in a few
>specialized cases.
>

Well, maybe I'm just a lucky guy but I have to regulary send messages to
two different domains with different misconfigurations for which such a
feature would be very helpfull.


Rodrigo



-------------------------------------------------------
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
Reply With Quote
Reply
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are Off
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




All times are GMT +1. The time now is 04:55 PM.


Powered by vBulletin® Version 3.7.3
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.0.0