Exchange – Error ‘A matching connector cannot be found to route the external recipient’

 

KB ID 0000723 

Problem

You will see this error in one of two scenarios, firstly it’s a new Exchange Installation and you have yet to create a send connector, or your send connector(s) do not cover the DNS name of the recipient the message giving you the error was destined for.

Identity: DC2012Unreachable412316860424
Subject: inter domain
Internet Message ID: <afea4f1a2aa14c2788d872070ae6a5dd@DC2012.PNL.com>
From Address: Administrator@pnl.com
Status: Ready
Size (KB): 4
Message Source Name: SMTP:Default DC2012
Source IP: 192.168.1.0
SCL: -1
Date Received: 11/26/2012 2:04:33 PM
Expiration Time: 11/28/2012 2:04:33 PM
Last Error: A matching connector cannot be found to route the external recipient
Queue ID: DC2012Unreachable
Recipients: name@domain-name.com;2;2;A matching connector cannot be found to route the external recipient;16;<No Matching Connector>

Usually you will have a send connector that covers “*” (that’s everything) so you either need to create that or a connector specifically for this problem domain name.

Solution

1. Launch the Exchange Admin Center https://localhost/ecp > Mail Flow > Send Connector > Click the Add icon.

2. Give it a sensible name and set it’s type to Internet.

3. By default it will select where to send the email based on the DNS name of the recipient, however some people route all their mail via a smart host, (this can be a server or IP address at your ISP or a mail filtering provider). If you use a smart host you will probably already know, in most cases you will want the default option of ‘MX record associated with recipient domain’ > Next.

g

4. Select the Add Icon > To create a ‘Default Send Connector’ that will cover ALL external domains, then set the FQDN to an asterisk, (for a domain specific connector simply enter the FQDN for that domain). > Save > Next.

5. Add > Now select the server(s) that will use the connector > OK > Finish.

Note: This is a great feature, if you have multiple sites, and multiple Exchange servers you can set the Exchange server at your main site as the default sending server. That’s great for solving mail flow problems caused by reverse DNS lookup failures.

6. At this point I’d either restart the Exchange services, or simply reboot the server.

Related Articles, References, Credits, or External Links

NA

Apple Device Stopped Sending Email – “Cannot Send Mail – A copy has been placed in your Outbox. The Recipient {name} was rejected by the server.”

KB ID 0000654 

Problem

Yesterday I got a text message from my wife to say she could not sent me an email. When she tried this happened:

At first I thought it was just me, until I asked her to try sending an email to someone else, then she got the same result. Trying over 3G, and on the wireless at home, the results were the same.

It had been working fine, but had then suddenly stopped working. My own iPhone was happily talking to the same mail server so I was stumped for a while.

Solution

1. Even though it’s my email server, its hosted for me, so I could not guarantee nothing had changed at the other end. She could receive email but not send email.

Note: Most internet email services receive email using POP3 (which uses TCP port 110) and they send email using SMTP (which uses TCP port 25), so the symptoms of the problem (she cant send) are pointing to SMTP/TCP Port 25 not working or being blocked.

2. On your device open Settings > Mail, Contacts, Calendars > Select the email account that has the problem > In the outgoing mail server section select the mail server.

3. Select the mail server again.

4. Make sure authentication is set to password, if not change it, also make sure the server port is set to 25 > Done.

Note: If you could send but not receive then you would do the same, but this time on the Incoming server, but the port number would be 110, (unless you are using SSL then it will be 995).

Related Articles, References, Credits, or External Links

NA