Problem lies with customer.com, or at least with Customer's mail client configuration.
customer.com has a list in DNS of where emails purporting to be from customer.com are supposed to come from (this is called SPF). $server.my.work goes and looks at this as a means of identifying potential spam. The mail came to $server.my.work from 194.1.166.183, which appears not to be in the customer.com SPF record.
So either customer.com need to update their SFP record to reflect the SMTP server they're actually using, or Customer has tried to be clever and configured their mail client to relay via some random convenient SMTP server (eg. perhaps they're sending emails via gmail or their home ISP) that isn't in the list.