Re: [mailop] Outlook strange behavior from Outlook.com (not a surprise... but...)
>> 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
Re: [mailop] Outlook strange behavior from Outlook.com (not a surprise... but...)
On 2021/06/16 09:04, Xavier Beaudouin via mailop wrote: > Hello there, > > I have a setup with 2 MX : > > domain.tld mx 10 mx1.domain.tld > domain.tld mx 30 mx3.domain.tld > > For some operational reason mx3 replys all mail with a 454 which is TEMPORALY > error... : > Jun 14 23:22:55 mx3 postfix/smtpd[83891]: NOQUEUE: reject: RCPT from > mail-eopbgr50127.outbound.protection.outlook.com[40.107.5.127]: 454 4.7.1 > : Relay access denied; from= > to= proto=ESMTP > helo= > > 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. 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. 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. ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
Re: [mailop] Outlook strange behavior from Outlook.com (not a surprise... but...)
Hi Xavier, If your secondary MX will refuse email with a relaying error, it's not a valid MX and should be removed from DNS... This doesn't explain outlook.com favouring it but also, they've pulled you up on poor configuration. :-) No point in having an advertised MX that isn't ready for action yet. DNS is easily changed when you are good to go. Mark. On 16/06/2021 7:04 pm, Xavier Beaudouin via mailop wrote: Hello there, I have a setup with 2 MX : domain.tld mx 10 mx1.domain.tld domain.tld mx 30 mx3.domain.tld For some operational reason mx3 replys all mail with a 454 which is TEMPORALY error... : Jun 14 23:22:55 mx3 postfix/smtpd[83891]: NOQUEUE: reject: RCPT from mail-eopbgr50127.outbound.protection.outlook.com[40.107.5.127]: 454 4.7.1 : Relay access denied; from= to= proto=ESMTP helo= It trys about 31 times But they didn't had the idea to check the mx1... which is ready for relay. Is there any good reason that outlook.com works like a spammer trying to send mail ONLY to lowest MX server Really guys fix your stuff... Regards, Xavier ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
[mailop] Outlook strange behavior from Outlook.com (not a surprise... but...)
Hello there, I have a setup with 2 MX : domain.tld mx 10 mx1.domain.tld domain.tld mx 30 mx3.domain.tld For some operational reason mx3 replys all mail with a 454 which is TEMPORALY error... : Jun 14 23:22:55 mx3 postfix/smtpd[83891]: NOQUEUE: reject: RCPT from mail-eopbgr50127.outbound.protection.outlook.com[40.107.5.127]: 454 4.7.1 : Relay access denied; from= to= proto=ESMTP helo= It trys about 31 times But they didn't had the idea to check the mx1... which is ready for relay. Is there any good reason that outlook.com works like a spammer trying to send mail ONLY to lowest MX server Really guys fix your stuff... Regards, Xavier ___ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
