We are currently having issues with one of our Xeams servers not sending emails externally. All internal emails are working fine, but external ones have stopped working for some reason despite having the same settings/configs as on 2 of our other Xeams instances. I stumbled onto this article talking about configuring custom SMTP routing:
https://xeams.com/custom-smtp-routing.htm

Currently, our Xeams relay to our O365 and then send out, but we would like to have Xeams send out anything going to "@specific.com" directly and bypass our O365. I came up with this CustomSMTPRouting.xml, but it didn't work. Could I have some assistance in setting this up? Anything going to @specific.com goes straight there, and all others go to our O365.

Apologies for the formatting.

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<CustomRouting>
<Routes>
<Route>
<sender>ANY</sender>
<recipient>@specific.com</recipient>
<recipientExceptions></recipientExceptions>
<ip></ip>
</Route>

<Route>
<sender>ANY</sender>
<recipient>ANY</recipient>
<recipientExceptions>@specific.com</recipientExceptions>
<ip>OUR-O365.outlook.com</ip>
</Route>
</Routes>
</CustomRouting>

Chris,

The following recommendation assumes you only have a handful of "specific.com" domains.

Don't use the Custom SMTP Routing. Instead, use the following steps:

• Log in to your Xeams web interface as the administrator
• Click Server Configuration/Manage Local Host File
• Add the word ALLDOMAINS for the domain name and put our-O365.outlook.com for the IP Address field. This will send every out-bound emails through O365
• Now, for the handful of specific domains, find the value for their MX records. For example, you want to send emails directly to gmail.com. Type nslookup -q=mx gmail.com in a Command Prompt to find the hostname for their MX. This command should yield gmail-smtp-in.l.google.com as the highest priority A record. Use that value for the IP and put the "specific.com" for the Domain name.

The only problem with this approach is that if the MX value changes for the "specific.com" domain, you may have to reconfigure your settings in Xeams. One way to avoid this reconfiguration is to use another Xeams instance. The first Xeams will always point the specific domains to the second Xeams instance, which will use MX record to send out.

I am trying to send to a cisco.com email, I have things stuck in the queue. I tried the above mentioned and still cannot send a message from in the queue. I received the below message. The IP address for the cisco.com domain is "alln-mx-01.cisco.com" in the Local Host file.

Please go to Server Configuration/Manage Local Host File and post a screenshot of that page.

Upon running this again, nslookup -q=mx cicso.com, i got a different answer from lastnight and have put it in here. Seeing the same issue when trying to send an email that is stuck in the queue. I have also tried the IP address for that address. 
cicso.com       MX preference = 10, mail exchanger = park-mx.above.com

Chris,

When I do an MX lookup on cisco.com, I get the following results.

I don't know why you're getting a hostname ending with above.com.

In any case, try sending one of the stuck messages manually from the queue. Then, copy/paste the last part of the logs from SMTPOutboundConversation.log here. You should see Xeams' communication with the receiving server at the end.

It is cisco.com, NOT cicso.com!

I see you put cisco.com in the Local Host file (screenshot above). Change that to cicso.com.