Ah remember the heady days of the Y2K bug? Well, as if 2021 didn’t have enough to answer for, it bit again…20 years later, with the transition to 2022. This time it was a flaw in the programming which led to some customers' Exchange servers not processing emails – just as we were putting down the Twiglets and settling into our annual rendition of Auld Langs Syne.
Microsoft explains “The problem relates to a date check failure with the change of the new year. The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues.”
Microsoft worked quickly to fix the issue – and the reports are looking good. It was a close one…and a reminder to future-proof everything, including your file naming conventions!
Think ahead, folks.