Regressions that should never happen, episode 42: Outlook 2016
-
Apparently, Outlook 2016 doesn't allow Unicode characters in IMAP passwords:
How the fuck can a regression like that happen in 2016? Unicode has been around for ages and if they would have any sensible regression test for IMAP support, they should have caught that before the release.
-
@asdf said in Regressions that should never happen, episode 42: Outlook 2016:
How the fuck can a regression like that happen in 2016?
MS have a very uneasy relationship with UTF-8 (and always seem to have done) which is the only sensible way to handle this sort of thing. Hence this sort of thing sneaks through, and there's probably some customers who are demanding that nothing change in this area because that would break their existing (indefensible) practices.
-
@dkf said in Regressions that should never happen, episode 42: Outlook 2016:
there's probably some customers who are demanding that nothing change
That's exactly what I expected as well. ;)
(Not that I ever use Outlook, but I own it as part of Office and would not be able to use it anymore.)
-
@asdf said in Regressions that should never happen, episode 42: Outlook 2016:
Not that I ever use Outlook, but I own it as part of Office and would not be able to use it anymore.
Because you always use umlauts in your passwords?
-
@boomzilla said in Regressions that should never happen, episode 42: Outlook 2016:
Because you always use umlauts in your passwords?
All my passwords are auto-generated and may or may not contain characters outside the ASCII range. (I adjust the settings of my password generator if the site doesn't accept random characters.)
Das ist empörend: Microsoft slams umlaut for email depth charge
