Rodrigo Severo wrote at 7:12 pm (-0300) on 20 6 2005: >> Why should Courier contact a secondary MX if it was perfectly able to >> reach the primary? > >Two possible reasons that came to my mind right now are: a 4xx error and >a "Connection time out" => "deferred" situation.
There is a fault in your logic here. If there is a "connection time out", then clearly it was not "perfectly able to reach the primary". Therefore, in this case, the secondary MX would be tested (presumably). >You couldn't be more right. My problem is that I have, by contract, to >send several emails to this client and my messages aren't getting >through because of the problems on their MX. So set up esmtproutes. If the first MX is unreliable, hard-code the second MX instead. >As I said, I believe that trying subsequent MXs on 4xx errors and >"Connection time out" would be more constructive. I can't see a problem >here. Do you? What is this "connection time out" you keep alluding to; are we talking about the same thing? -b -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca ------------------------------------------------------- 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/listinfo/courier-users
