Host smtp...refused to talk to me: 554 5.7.1 You are not allowed to connect

Hi, recently upgraded to v0.19b from earlier version but I think we were already running like v0.18. Since upgrade we are now getting undeliverable mail to several of our routine business partners, like Fedex and Future Electronics. ’

Below is the error message from trying to send an email to our @fedex.com contact and same issue with emails to our @futureelectronics.com contacts. Any input on what may be happening? It is greatly appreciated!

This is the mail system at host box.mydomain.com.

####################################################################

THIS IS A WARNING ONLY. YOU DO NOT NEED TO RESEND YOUR MESSAGE.

####################################################################

Your message could not be delivered for more than 3 hour(s).
It will be retried until it is 2 day(s) old.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can
delete your own text from the attached returned message.

               The mail system

fxm@fedex.com: host smtp.dmz.fedex.com[204.135.8.98] refused to talk to
me: 554 5.7.1 You are not allowed to connect.

Reporting-MTA: dns; box.mydomain.com
X-Postfix-Queue-ID: E3A8F2145D
X-Postfix-Sender: rfc822; smewp@mydomain.com
Arrival-Date: Tue, 6 Sep 2016 03:48:28 -0400 (EDT)

Final-Recipient: rfc822; fxm@fedex.com
Original-Recipient: rfc822;fxm@fedex.com
Action: delayed
Status: 4.7.1
Remote-MTA: dns; smtp.dmz.fedex.com
Diagnostic-Code: smtp; 554 5.7.1 You are not allowed to connect.
Will-Retry-Until: Thu, 8 Sep 2016 03:48:28 -0400 (EDT)

Return-Path: smewp@mydomain.com
Received: from authenticated-user (box.mydomain.com [192.99.14.66])
(using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by box.mydomain.com (Postfix) with ESMTPSA id E3A8F2145D;
Tue, 6 Sep 2016 03:48:28 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=mydomain.com; s=mail;
t=1473148110; bh=rISw1Zi7uQ0ZB6uDTsDfDVETwFjyd9ss6lSnVq7JR7I=;
h=Date:From:To:Subject:From;
b=jnfkDXj/jkoFVNneUOm1g41KOexgLVNIWE63aSrg09XKJPnbS4KeaRPVerD6Bx2qW
b+dBHs3VjmLGtpPL1vrMKpftNMPVKnmY6D+Q8pyWQinoOLe7d17s+TQ//onEIKl17G
O6/CNU9DvHJb+gjqdoW7p3ivx7WG01naU/spxJrSYqWV1u5OqASlfJBwBRa9opfCZv
b3jURtwj3uhAj4JrBthGrgRcO7ozquA/4aauIjgX3ZGI+1yr3PvGrVUVRagaQ6rXTj
cCX9DSUZkIJPlW/uUmbVax4/xsUapVj6YOdoK9Mobf9wA4kkvo8Fd51ugW64GFR9LJ
jOt4BQljK4+Mg==
Message-ID: 57CE74C7.60200@mydomain.com
Date: Tue, 06 Sep 2016 15:48:23 +0800
From: smewp smewp@mydomain.com
MIME-Version: 1.0
To: fxm@fedex.com
Subject: Check if you can receive my email now
Content-Type: multipart/alternative;
boundary="------------000501070507050202070401"

Getting the same error from Shutterfly’s MTA. Have you chased this down?

Cheerio, Harry.