Exchange issue: Remote Server returned '500 5.3.3 Unrecognized command'

Hello, I have been having this issue for some time now and cant seem to narrow it down. We have one vendor we cant email. Everytime I lookup the error it states their server does not have sufficient disk space. I have redacted our server info. I cant seem to figure out where the error is coming from because they keep telling me their server has sufficient space. I also performed a couple of MX tests and their server seems to fail the TLS tests.

remote.TFSJax.com rejected your message to the following email addresses:
'rreyes@tfsjax.com' (rreyes@tfsjax.com)
The recipient's email system can't process this message. Please try resending the message later.
remote.TFSJax.com gave this error:
Unrecognized command

Diagnostic information for administrators:
Generating server: "my mail server"
rreyes@tfsjax.com
remote.TFSJax.com
Remote Server returned '500 5.3.3 Unrecognized command'
Original message headers:
Received: from "my mail server" by
 "my mail server" with Microsoft SMTP Server
 (TLS) id 15.0.1263.5; Fri, 29 Dec 2017 10:12:40 -0500
Received: from "my mail server" by
 "my mail server" with Microsoft SMTP Server
 (TLS) id 15.0.1263.5; Fri, 29 Dec 2017 10:12:39 -0500
Received: from "my mail server" ([fe80::b8bb:d61a:d661:452]) by
 "my mail server"([fe80::b8bb:d61a:d661:452%12]) with mapi id
 15.00.1263.000; Fri, 29 Dec 2017 10:12:39 -0500
From: "me:
To: "'rreyes@tfsjax.com'" <rreyes@tfsjax.com>
Subject: Test
Thread-Topic: Test
Thread-Index: AdOAt3TkYICXtvZZRzORQP6KJ/1sFQ==
Date: Fri, 29 Dec 2017 15:12:39 +0000
Message-ID: <cb403fd5fab544589c51c3e9e587e522@"my email server">
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [xxx.xxx.xxx.xxx]
Content-Type: multipart/alternative;
      boundary="_000_cb403fd5fab544589c51c3e9e587e522S"myemailserver_"
MIME-Version: 1.0
Return-Path: "my email"


DNS RESULTS:
Reply from 96.94.55.86: bytes=32 time=21ms TTL=58
Reply from 96.94.55.86: bytes=32 time=15ms TTL=58
Reply from 96.94.55.86: bytes=32 time=14ms TTL=58
Reply from 96.94.55.86: bytes=32 time=14ms TTL=58

Ping statistics for 96.94.55.86:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 21ms, Average = 16ms

C:\Users\administrator.CO>nslookup remote.TFSJax.com
Server:  "my dns server"
Address:  xxx.xxx.xxx.xxx

Non-authoritative answer:
Name:    remote.TFSJax.com
Address:  96.94.55.86


C:\Users\administrator.CO>nslookup tfsjax.com
Server:  "my dns server"
Address:  xxx.xxx.xxx.xxx

Non-authoritative answer:
Name:    tfsjax.com
Address:  96.94.55.86


C:\Users\administrator.CO>nslookup 96.94.5.86
Server:  "my dns server"
Address:  xxx.xxx.xxx.xxx

Name:    96-94-5-86-static.hfc.comcastbusiness.net
Address:  96.94.5.86
2017-12-29-11_01_54-Network-Tools_-D.png
Brandon MillerSystems AdministratorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

RoninCommented:
Send them this link:
https://mxtoolbox.com/domain/tfsjax.com/
They might want to correct some errors.

They need to enable logging on the receive connector to troubleshoot the problem.
If they won't do it - there's no much you can do on your side.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Jason CrawfordTransport NinjaCommented:
Well it does certainly sound like a recipient issue but SMTPSend Protocol Logs from your Exchange server would help in proving it.  Is verbose logging enabled on the Send Connector associated with this recipient?
0
Jason CrawfordTransport NinjaCommented:
Either that or they have a firewall that is inspecting SMTP and fouling up the handoff.  I've seen this many times with Cisco ASAs and it's a tough issue to spot.  Ask the recipient if their firewall is performing SMTP Fixup.
0
Brandon MillerSystems AdministratorAuthor Commented:
Thank you for confirming, I have been thinking the same thing but they don't have any IT support. So when I talk to them they don't understand how to troubleshoot from their end.
0
Jason CrawfordTransport NinjaCommented:
Just think of it as job security for those of us who take this seriously :)
1
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.