Weekly Reading: Remember the Y2K bug? Microsoft confirms new Y2K22 issue
Microsoft encountered the same programming bug, naming after Y2K22, as in Y2K before.
It has made a negative impact on their enterprise clients, causing nearing 10,000 messages being queued in less than 24 hours and potentially taking their clients’ business offline.
Microsoft says it is aware of a programming flaw which saw some customers’ Exchange servers stop processing emails just as the clock struck midnight on New Year’s Eve.
The version checking performed against the signature file is causing the malware engine to crash, resulting in messages being stuck in transport queues.
Due to the crash of system, the messages of Microsoft enterprise clients which should be queued up and checked are simply being queued.
If you have an existing malware scanner for email other than the engine in Exchange Server, then you can use the workaround which involves disabling the malware filtering feature.
A way of dealing with a problem or making something work despite the problem, without completely solving it.
Computer software that is designed to damage the way a computer works.
A line of people, usually standing or in cars, waiting for something.
Happening or done all day and all night.
“Microsoft said its engineers had been “working around the clock on a fix” that…”
To make something officially acceptable or approved, especially after examining it.
To give something or someone a particular name, especially describing what you think of it, him, or her.
這是我給自己在 2022 年訂的一個目標，希望每周都能至少閱讀一篇英文文章，不限類別，並且整理出摘要與重點。
透過分享到 Medium 上，也算是給自己立個 flag，同時也藉由外部壓力/資源來鞭策自己，希望可以堅持下去 :)