<p>As people around the world welcomed the new year 2022 over the weekend, several Microsoft communication service users were in for a little disappointment as they could not send any emails on January 1, 2021.</p>.<p>It has come to light that a glitch in the malware detection system caused date check failure and emails got stuck at exchange servers and couldn't get redirected to the recipients.</p>.<p>Apparently, the FIP-FS antivirus scanning engine of the Microsoft Exchange server, while attempting to store the new date in a signed int32 variable, was less and couldn't process it.</p>.<p>The aforementioned variable had 2,147,483,647 values, which is less than the new date value of 2,201,010,001 for January 1st, 2022, at midnight.</p>.<p>"The problem relates to a date check failure with the change of the new year and it not a failure of the AV engine itself. This is not an issue with malware scanning or the malware engine, and it is not a security-related issue. The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues," Microsoft <a href="https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-exchange-on-premises-transport-queues/ba-p/3049447" target="_blank">said</a>.</p>.<p>Now, the company has addressed the problem of messages stuck in transport queues on Exchange Server 2016 and Exchange Server 2019.</p>.<p>Microsoft has asked system admins in companies and other business establishments to update their systems to fix the glitch.</p>.<p><em>Get the latest news on new launches, gadget reviews, apps, cybersecurity, and more on personal technology only on <a href="https://www.deccanherald.com/tag/dh-tech?_ga=2.210580691.73733284.1595225125-1706599323.1592232366" target="_blank">DH Tech.</a></em></p>
<p>As people around the world welcomed the new year 2022 over the weekend, several Microsoft communication service users were in for a little disappointment as they could not send any emails on January 1, 2021.</p>.<p>It has come to light that a glitch in the malware detection system caused date check failure and emails got stuck at exchange servers and couldn't get redirected to the recipients.</p>.<p>Apparently, the FIP-FS antivirus scanning engine of the Microsoft Exchange server, while attempting to store the new date in a signed int32 variable, was less and couldn't process it.</p>.<p>The aforementioned variable had 2,147,483,647 values, which is less than the new date value of 2,201,010,001 for January 1st, 2022, at midnight.</p>.<p>"The problem relates to a date check failure with the change of the new year and it not a failure of the AV engine itself. This is not an issue with malware scanning or the malware engine, and it is not a security-related issue. The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues," Microsoft <a href="https://techcommunity.microsoft.com/t5/exchange-team-blog/email-stuck-in-exchange-on-premises-transport-queues/ba-p/3049447" target="_blank">said</a>.</p>.<p>Now, the company has addressed the problem of messages stuck in transport queues on Exchange Server 2016 and Exchange Server 2019.</p>.<p>Microsoft has asked system admins in companies and other business establishments to update their systems to fix the glitch.</p>.<p><em>Get the latest news on new launches, gadget reviews, apps, cybersecurity, and more on personal technology only on <a href="https://www.deccanherald.com/tag/dh-tech?_ga=2.210580691.73733284.1595225125-1706599323.1592232366" target="_blank">DH Tech.</a></em></p>