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 ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
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-20188-1119358926-0002 Content-Type: text/plain; format=flowed; charset="US-ASCII" Content-Disposition: inline Content-Transfer-Encoding: 7bit Rodrigo Severo writes: > Sam Varshavchik wrote: > > >> There's nothing that Courier can do here. Courier will not disconnect >> and reconnect to some other MX. Courier will only try to contact the >> next MX if it didn't connect at all to the first MX. > > Why? If Courier contacted a MX and the connection times out at the > middle of the smtp conversation, why can't Courier wait the same amount > of time is already does and then try to connect to another MX server? > Where is the abuse here? Because there can be many reasons why the connection stalled. Courier can't assume that it's because the recipient's mail server is intentionally broken. It could be, for example, that the server lost power in the middle of the transaction. The only thing that can be concluded if the delivery failed for some reason, is that the delivery has failed. Modern technology hasn't yet advanced to the point where you can install some AI engine that will algorithmically determine for you the root cause for the failure, and what is the theoretically best way to recover from this failure. 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. --=_mimegpg-commodore.email-scan.com-20188-1119358926-0002 Content-Type: application/pgp-signature Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBCuA/Ox9p3GYHlUOIRAlF2AJ49er3AlOtDaxEige/sbHZZwjn5YACfWuem RZw+rBjMjw1ZrnqyX+QPGCk= =L1rF -----END PGP SIGNATURE----- --=_mimegpg-commodore.email-scan.com-20188-1119358926-0002-- ------------------------------------------------------- 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 |