We have addressed the issue causing messages to be stuck in transport queues of on-premises Exchange Server 2016 and Exchange Server 2019. The problem relates to a date check failure with the change ...
Updated Jan 11, 2022
Version 36.0
Blog Post
Well, while this is not working; I still wonder why Microsoft's solution is a security rollback. "Just use our old engine." That is a solution. But on a very short term.
Microsoft is working around the clock to fix this! Microsoft apologizes for the inconvenience that issue caused. In 1999, we had meetings and symposiums all about a so-called Millennium Bug. The world was afraid that engineers could have used strings that can't hold a 4 digit value for the year. Now 22 years later, Microsoft has done it. Companies, where the IT Department is not on duty because New Year's Day and the following Sunday, will have a problem on Monday. Lost E-Mails. Microsoft will tell them, they should have used Exchange online instead.
This is no open-source software maintained by a community. We paid for the software licence. But most valued information you find to this issue is in the community forums instead of Microsoft official platforms.