This issue is still occurring. We believe that it is being caused by a feature called Mailguard on their firewall. Currently waiting for a good time for them to turn it off and run some tests, but thought I'd throw an update on here since its been a week and a half...