Xink experienced a notice incident on January 10, 2024 affecting Outlook Add-in, lasting 5d 1h. The incident has been resolved; the full update timeline is below.
Affected components
Update timeline
- identified Jan 10, 2024, 11:25 AM UTC
Microsoft launched Outlook 2312 on 4 Jan, which changes the encoding from UFT-8 to CP-1252. Learn more on GitHub: https://github.com/OfficeDev/office-js/issues/3892 We recommend returning to 2311 until Microsoft fixes the Outlook ‘classic’ desktop. WORKAROUNDS You can switch to the New Outlook. You can use Outlook on the web. You can click the email signature in the Xink add-in. You can update email signatures using the Xink client. You can move to a server-side email signature. RESOLUTION (pending while we wait for the Microsoft fix) Our add-in developer team are investigating if they can fix the encoding via the add-in (not likely). Our template team is investigating if we can change the built-in designer source (likely). Sorry about the inconvenience. Jesper Frier
- monitoring Jan 12, 2024, 08:21 AM UTC
We have pushed the add-in 4.1.0, which addresses the special characters issue with Outlook's 'classic' desktop version 2312.
- monitoring Jan 12, 2024, 09:01 AM UTC
We are getting reports that v.4.1.0 adds a strange character to some email signatures. We are looking into it as a priority.
- resolved Jan 15, 2024, 12:39 PM UTC
This incident has been resolved.