A customer has requested an email signature that I’ve coded up, that should theoretically be compatible with all email clients, and especially with Outlook 2013 and OWA within Office 365, which are the primary clients that the customer users.
The signatures are to be deployed through mail flow rules within Office 365.
I’ve tested them and tested them again and they work in pretty much everything according to my own testing and the EoA testing process, but when received by the customer’s client, which is running Outlook 2013 on Windows, it squashes all the tables.
Can anyone suggest any fixes that I’ve forgotten? This is driving me mad as I’ve run out of solutions and fixes.