the-microsoft-exchange-mail-server-experiences-an-'effect-2022':-the-turn-of-the-year-has-paralyzed-the-…-!

The Microsoft Exchange mail server experiences an 'Effect 2022': the turn of the year has paralyzed the … -!

The Microsoft Exchange mail server experiences an ‘Effect 2022’: the change of year has paralyzed the … -!: All the details about The server of Microsoft Exchange mail experiences an ‘Effect 2022’: the turn of the year has paralyzed the … -! are on topwhich.com. I am happy to present you all the developments about The Microsoft Exchange mail server experiences an ‘Effect 2022’: the change of year has paralyzed the … -!. Here’s what you need to know about The Microsoft Exchange mail server experiences an ‘Effect 2022’: the change of year has paralyzed the … -!, here are the details … It is possible that you have attributed the lack of emails in your Inbox to the holiday dates in which we are, but if your e-mail server works with Microsoft Exchange (as will be the case with many corporate email accounts), probably the explanation is that you are being the victim of a strange bug due to the change of year .

As recognized by Microsoft, the MS Exchange antispam and antimalware engine (FIP-FS, activated by default in the installations of said platform since its version 2013) suffers an error processing the date since midnight yesterday , so millions of emails are being being paralyzed on the servers, without referring their recipients.

Joseph Roosen, cybersecurity researcher – in addition to MS Exchange administrator – stated that this problem is due to the fact that Microsoft developers decided store in due course the val or of the date in a variable int 32 whose maximum value is 2. 147. 375. 647 …

… and yet they did it in such a way that the smallest of the dates corresponding to this year had to occupy a minimum value of ‘2. 201. 010. 001 ‘ (that is, using the last three digits to store the day and the previous three for the month).

A strange decision that now causes the FIP-FS engine to not be able to understand the date of the emails .

Possible solutions to the problem

Microsoft has confirmed that it is already working on a patch that fixes this problem in versions 2016 and 2019 of Microsoft Exchange, which has not set a release date for now. As explained by Microsoft,

“Our engineers were working day and night on a solution that would eliminate the need for action by part of the customer, but we determined that any patch that did not involve such would require several days to develop and deploy. So we are working on another update, the validation of which is now in its final testing phase. ”

However, companies that return to work tomorrow and need to be able to send and receive their emails must resort to the temporary deactivation of the FIP-FS engine . Fortunately, this solution (not to be taken lightly due to the danger of malicious emails reaching users) is easy to implement.

Enough with running the following PowerShell commands on Exchange Server:

Set-MalwareFilteringServer -Identity -BypassFiltering $ true

Restart-Service MSExchangeTransport

And, after restarting the MSExchangeTransport service, mail will be forwarded back to users. Hopefully there will be no new New Year scares in the short term … at least not before it’s time to face the Effect 2038.