Microsoft has actually started 2022 by releasing a spot for Exchange Server 2016 and 2019, which both had a “hidden date problem” that saw e-mails marked time rather of being dispatched to inboxes.
” The issue associates with a date check failure with the modification of the brand-new year,” specifies a January 1st post to the Exchange Blog.
Exchange’s malware scanning engine is the source of the issue, as Exchange checks the variation of that software application and after that attempts to compose the date into a variable. That variable’s optimum worth is 2,147,483,647 and the worth Exchange attempts to compose – 2,201,010,001, to show the date of January 1st, 2022, at midnight– goes beyond the variable’s optimum limit.
The malware engine for that reason crashes when it checks out the variable.
Deprived of its malware-scanner– a crucial component of a mail server – Exchange lines mail rather of sending it.
- Let us appreciate that this November, Microsoft has actually provided us simply 55 security repairs, 2 of which are for actively made use of defects
- Story of the creds-leaking Exchange Autodiscover defect– the one Microsoft would not repair even after 5 years
- Microsoft Exchange Autodiscover procedure discovered dripping numerous countless qualifications
A wag on Reddit called the mess “The Y2K22 bug”, a referral to the notorious Y2K bug triggered by early developers embracing a date format of DD/MM/YY to utilize less memory than would be needed by a format of DD/MM/YYYY. That choice indicated that numerous systems would presume that the 1st of January 2000 was the very first day of the year 1900, which would have made for some merry messes.
The Y2K bug was remediated after years of costly effort.
Fixing the Exchange mess requires some work, too. While Microsoft has actually launched a script to fix the scenario, the business’s Exchange group has actually alerted “it will take a while to make the needed modifications, download the upgraded files, and clear the transportation lines.”
Microsoft’s post about the bug and how to resolve it was upgraded 7 times in between publication on January 1st and the time this story was published. Chatter in Microsoft online forums and somewhere else recommends that the repair can be difficult to use, and in some cases stops working.
All of which suggests Exchange Admins have an exceptionally enjoyable start to 2022 – who does not like a deluge of courteous questions from users miffed that they can’t access e-mail? Thanks, Microsoft. ®