Y2K22 - Why 2022 Broke Email

Using signed integers to represent values which never go negative is a pet peeve of mine.

I wasn't expecting to see issues with dates until 2038 but I suppose I never considered that a programmer would be crazy enough to still use 2 digit years (even after Y2K), 32 bit numbers, and string formatted dates converted and stored in integers (instead of either strings as strings or integers as integers).

And nobody saw it coming? That also mean who ever programmed it years ago wasn't expecting to pass 2021.

This was a great one Colin. Its so funny that once again types bit us.

“Why 2022 broke some piece of terrible Microsoft software.” FTFY

What Up Colin it's the dreaded two again

Yikes. Seems like a pretty obvious test case, to catch the signed long? Convert dates to anything else is just asking for trouble.

Thought at that time my mail was being consumed by China and they had a backlog on resending. Great video!

The more you know

long could be 32bits or 64bits. i386 4 alpha 8 armv4 4 ia64 8 m68k 4 mips 4 ppc 4 sparc 4 sparc64 4 x86_64 8

But how did they fix it?!

Sorry to say that but that title is total clickbait. Only Microsoft Exchange was affected by this whereas the title suggests that it affected E-Mail in general. No other mail server software apart from Microsoft Exchange was affected by this. I've been a mail server admin for over a decade even working for major ISPs and titles like this just rub me the wrong way. MS Exchange isn't even remotely the most common MTA around... thus saying that 2022 "broke email" just because some toy MTA like Exchange had a severe bug (yeah... no shit sherlock its Microsoft Exchange... the only thing coming close in terms of bugs is Exim) is simply wrong and clickbait af!