hi,
many people enabled more spamfilter options in the last weeks, i saw.
locky could be a reason why ;-)
did you enable "dns-validation" on the scanner's?
are the mx records in the public DNS of the companyx.net correct?
i enabled dns-validation on our scanners last week, some senders got this message, too.
the reason was that the sending server had an other ip as in MX-record's fieds in the public-dns of the company.
dns-validations checks this and they got a 554 error.
and senders can't be whitlisted against dns-validating. there is no option to bybass this.
regards,
eurass