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.
pgpmNUW56DAKF.pgp
Description: PGP signature
