>> It trys about 31 times.... But they didn't had the idea to check the mx1... >> which is ready for relay. > > You can't tell for certain that they didn't check the mx1.
Well absolutly NO connection for this domain on mx1... according to the logs. And I had some reports about some similars problems from other people from outlook mail hosting. > Perhaps there was a network error. Sometimes route announcements > don't make it to the whole world, sometimes packets to some hosts > but not others end up on a broken member of a load-balanced port > group. I am sure there is no network error, all of the MX are (unfortunatly) on same AS, and dual stacked. > Related, note that some SMTP software doesn't fall to a lower > priority MX if the higher priority one connects but rejects with > temporary failure. Things work best if all listed MX that accept > connections are prepared to accept mail. Well, if the DNS rules has not changed, the highest priority should be the MX which has the lower weight, not the biggest. But I don't know how MS has written their software but they don't follow the rules and obviously the RFC... but this is not the first time and the people who like to push the mail in all GAFAM because this is not their jobs make them more and more powerfull and painfull for mail admin who doesn't want that. Regards, Xavier _______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
