>> | Check your MTA logs, I am sure they reject your mail for policy >> >> outlook (etc) don't actually reject the e-mail, they just don't answer >> DNS requests for the address for the MX record. The MX exists, so it >> is known the addr (domain name part) is valid, but after that it is just >> wait forever. > >This is really strange. I have never seen something like this (except >when the DNS is broken). > >Do you have any logs that demonstrate this? Do you have DNSSEC >validating resolver enabled or something like this?
I wanted to address this particular point as well. I use a DNSSEC validating resolver and I can _not_ reproduce this. Specifically: % host -t mx outlook.com outlook.com mail is handled by 5 outlook-com.olc.protection.outlook.com. % host -t a outlook-com.olc.protection.outlook.com outlook-com.olc.protection.outlook.com has address 52.101.42.5 outlook-com.olc.protection.outlook.com has address 52.101.41.23 outlook-com.olc.protection.outlook.com has address 52.101.73.3 outlook-com.olc.protection.outlook.com has address 52.101.41.25 % host -t aaaa outlook-com.olc.protection.outlook.com outlook-com.olc.protection.outlook.com has no AAAA record --Ken
