No, their MX is correct. Was just posting it so you could compare what I got to what you get. If they match, they are blocking you, imnsho. Lets try a copy paste from Notepad to clean it up.
Non-authoritative answer: animikisee.ca MX preference = 10, mail exchanger = mail.animikisee.ca mail.animikisee.ca internet address = 184.70.35.78 ________________________________ From: [email protected] [[email protected]] on behalf of Steve Ens [[email protected]] Sent: Tuesday, October 07, 2014 4:36 PM To: [email protected] Subject: Re: [Exchange] 421 4.2.1 Unable to connect errors Sorry Jim, I don't get your answer. The animikisee.ca<http://animikisee.ca> domain is the one that won't accept the messages. Is there something awry with the mx record? On Tue, Oct 7, 2014 at 3:24 PM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: Good from here. As long as your MX lookup on your exchange server looks as below they don’t want to talk to you. Non-authoritative answer: animikisee.ca<http://animikisee.ca> MX preference = 10, mail exchanger = mail.animikisee.ca<http://mail.animikisee.ca> mail.animikisee.ca<http://mail.animikisee.ca> internet address = 184.70.35.78 From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Ens Sent: Tuesday, October 7, 2014 4:12 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] 421 4.2.1 Unable to connect errors one of the domains is animikisee.ca<http://animikisee.ca> but I can send to it from gmail no problem. Test the email address [email protected]<mailto:[email protected]> On Tue, Oct 7, 2014 at 3:06 PM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: Toss us a domain so we can try from ours. Go off list if need be. From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Ens Sent: Tuesday, October 7, 2014 4:02 PM To: [email protected]<mailto:[email protected]> Subject: Re: [Exchange] 421 4.2.1 Unable to connect errors Yes, already tried that. I can do a MX lookup, but cannot telnet to the server. Also getting this in the logs Error Code: 10061, Error Message: No connection could be made because the target machine actively refused it That seems to point to us being blacklisted, but I come up clean on the mxtoolbox tests. On Tue, Oct 7, 2014 at 2:48 PM, Kennedy, Jim <[email protected]<mailto:[email protected]>> wrote: What are the domains? Could be bad bounces from spam to non-existent domains Your server can not contact them, so it tried alternates either in dns or per the RFC’s (for example A record of domain.com<http://domain.com>) and that failed. So it is still trying. Do an MX lookup from your transport server to verify your DNS is working. Then try telnet port 25 from the transport server to that IP to verify connectivity. What do you get? From: [email protected]<mailto:[email protected]> [mailto:[email protected]<mailto:[email protected]>] On Behalf Of Steve Ens Sent: Tuesday, October 7, 2014 3:42 PM To: [email protected]<mailto:[email protected]> Subject: [Exchange] 421 4.2.1 Unable to connect errors Odd errors in my mail queue. Just started appearing yesterday. Most mail gets sent, but from certain domains I get these errors. "Attempted failover to alternate host, but that did not suceed." Anyone see this before? Exchange 2010 on Windows 2008 R2.
