Microsoft rang in the new year with a cutesy tweet in C#. Just one problem: The code sucked

Microsoft has kicked off 2022 by issuing a patch for Exchange Server 2016 and 2019, which both possessed a “latent date issue” that saw emails queued up instead of being dispatched to inboxes.

“The problem relates to a date check failure with the change of the new year,” states a January 1st post to the Exchange Blog.

Exchange’s malware scanning engine is the source of the problem, as Exchange checks the version of that software and then tries to write the date into a variable. But that variable’s maximum value is 2,147,483,647 and the value Exchange tries to write – 2,201,010,001, to reflect the date of January 1st, 2022, at midnight – exceeds the variable’s maximum threshold.

Microsoft rang in the new year with a cutesy tweet in C#. Just one problem: The code sucked
Source: Expert Gwapo Pinoys