[prev in list] [next in list] [prev in thread] [next in thread] 

List:       inet-access
Subject:    Re: conditional secondary MX ???
From:       "Patrick W.Gilmore" <patrick () ianai ! net>
Date:       2004-06-04 20:15:21
Message-ID: E7D2811A-B663-11D8-B80C-000A9578BB58 () ianai ! net
[Download RAW message or body]

On Jun 4, 2004, at 11:49 AM, Chuck Mead wrote:

> Patrick W.Gilmore said:
>> On Jun 3, 2004, at 2:34 PM, csm@moongroup.com wrote:
>>
>>> As some of you may know I am actually teaching for Red Hat these
>>> days...
>>> in addition to owning a piece of anirononline.com. As a part of my
>>> duties for Red Hat I regularly teach lessons on SMTP and mail
>>> acrchitecture and I tell my students not to bother with secondary 
>>> MX's
>>> anymore specifically because of the aformentioned problems.
>>
>> I am not at all certain that is a good idea.  For "business critical"
>> communication, and e-mail definitely qualifies, delaying things for 30
>> minutes because of a transient error (e.g. routing loop) is probably
>> unacceptable.
>
> Even if you have a secondary the mail is going to be delayed until the
> primary returns to service so what's the difference? How long do people
> leave their corporate/business mail servers down when they fail?

But the primary might have been up the whole time.  Network 
connectivity on the Internet is not guaranteed to be the same from all 
vantage points.

Also, I do not know a company which leaves its primary down any longer 
than absolutely necessary.


> I think I'll keep doing it the way I'm doing it. :-)

Your computers, your choice.  Or, I guess in this case, your students.

Doesn't mean I can't do it differently. :)

-- 
TTFN,
patrick

_______________________________________________
"Eat sushi frequently". - Avi
inet@inet-access.net is the human contact address.
list@inet-access.net is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]