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

This is a discussion on [courier-users] Re: Automatically use secondary MX host if primary fails within the Courier-Imap forums, part of the Mail Servers and Related category; This is a MIME GnuPG-signed message. If you see this text, it means that your E-mail or Usenet ...


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-20-2005
Sam Varshavchik
 
Posts: n/a
Default [courier-users] Re: Automatically use secondary MX host if primary fails

This is a MIME GnuPG-signed message. If you see this text, it means that
your E-mail or Usenet software does not support MIME signed messages.

--=_mimegpg-commodore.email-scan.com-13041-1119296332-0001
Content-Type: text/plain; format=flowed; charset="US-ASCII"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Rodrigo Severo writes:

> Sam Varshavchik says:
>
>> If Courier cannot contact the primary MX it will automatically contact the
>> secondary MX.

>
> Is there any reason for Courier only try to contact a secondary MX if it
> can't contact the primary at all?


Why should Courier contact a secondary MX if it was perfectly able to reach
the primary?

> Wouldn't it be a good approach to try other MXs after any kind of error:
> failed connection, 4xx error, 5xx error etc?


When I see a sender repeatedly try to contact other MXs, even after being
told in no uncertain terms to 5xx-off, due to them being blacklisted, my
only response is typically a hardware firewall to such abusive and obnoxious
behavior.

> I'm recently having problems sending messages to several of my clients
> because they have MXs with one problem or the other: two top priority


So? Their MX is the one with the problem, not yours'.

> MXs and one of them is too busy, two top priority MXs and one of them is
> turned off (my client says it will only be turned on in case of
> emergency!!!) etc.


If it's turned off, and does not accept connection, Courier will go to the
backup MX. What's the problem?

> I know that some of these problems should be solved on the other end but
> I believe my suggestion is a more productive approach from Courier.


Accomodating technical incompetence is never productive in the long run.



--=_mimegpg-commodore.email-scan.com-13041-1119296332-0001
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQBCtxtMx9p3GYHlUOIRAkMIAJ493586pteBZMDIXHfHxt M1GXJevwCfR2g4
bP08uaM7mVgXu3mrDr0uuvM=
=7O61
-----END PGP SIGNATURE-----

--=_mimegpg-commodore.email-scan.com-13041-1119296332-0001--


-------------------------------------------------------
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 10:24 PM.


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