Do you remember the 2000 effect? With the evolution of the numbers and the year, many had problems that could be generated in the computer hardware. In the end, it was not as bad as it was thought and now Microsoft Exchange is the platform that was affected by an outage related to the beginning of the year. A failure that we could relive in 2038
Users see how empty the Microsoft Exchange Inbox is and no, this is not a problem with the corresponding mail server. Microsoft Exchange in versions 2016 and 2019 is the victim of a bug related to the change of year which is generated when processing the new date.
The 2022 effect
An error that the company itself has already recognized. The MS Exchange antispam and antimalware engine (FIP-FS, enabled by default in installations of this platform since its 2013 version) generates a failure when updating to the new date, a bug that causes many emails missing. recipients.
Apparently, this problem is caused by Microsoft developers choosing to store the date value in an int32 variable whose maximum value is 2,147,483,647. This is the opinion of Joseph Roosen, a cybersecurity researcher, who asserts that the failure is that they did it in such a way that the smallest of the dates corresponding to that year had to occupy a minimum value of ‘2.201.010.001’ (i.e., using the three last digits to memorize the day and the three preceding ones for the month).
In this way, the MS Exchange antispam and antimalware engine is not able to understand the date of the emails and they do not reach users’ computers.
Microsoft has acknowledged the failure and the company advises that it is already working on a fix to correct the issue that affects the 2016 and 2019 versions of Microsoft Exchange:
“Our engineers were working tirelessly on a solution that would eliminate the need for customer intervention, but we determined that any fix that did not involve such action would take several days to develop and deploy. We are therefore working on another update, the validation of which is now in its final testing phase. “
This failure mainly affects corporate emails and to correct the failure during the release of the corrective patch, the people concerned have no other choice but to temporarily deactivate the FIP-FS engine, a solution which nevertheless leaves the teams without protection. , that they are exposed to the arrival of malicious programs. emails. To temporarily disable the FIP-FS engine, type the following PowerShell commands in Exchange Server:
With these steps, users will get their emails again and this is the only solution at least until Microsoft releases the final fix.