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? Wouldn't it be a good approach to try other MXs after any kind of error: failed connection, 4xx error, 5xx error etc? 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 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. 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. These alternative behaviours could be made optional if they represent a problem to anyone. Any chance this being implemented? TIA, Rodrigo Severo ------------------------------------------------------------- People who bite the hand that feeds them usually lick the boot that kicks them. ------------------------------------------------------------- Rodrigo Severo Fábrica de Idéias [EMAIL PROTECTED] SBS - Ed. Empire Center - Sala 1301 - Cobertura CEP: 70070-904 Fone: (61) 321 1357 Fax: (61) 223 1712 ------------------------------------------------------------- ------------------------------------------------------- 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_idt77&alloc_id492&op=click _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
