On 4/11/20 4:41 PM, Grant Taylor wrote: > On 4/11/20 2:17 PM, Michael Orlitzky wrote: >> Exchange used to do all manner of stupid things, but now that Microsoft >> is running it themselves and making money from O365, they seem to have >> figured out how to make it send mail correctly. > > I've found that Exchange / IIS SMTP is fairly standards compliant since > the early-mid 2000s. > > Microsoft has always been making money off of Exchange. (Presuming > people are being legal about it.) Be it CALs, upgrade licensing, etc.
Right, but back then, they already had your money by the time you realized Exchange was a turd. Now people can cancel their subscription, and Microsoft has to field support calls when things don't work, so they have a bit more incentive to do things right. >> Nowadays they prefer to cripple Outlook with non-Exchange protocols, >> so that our users complain about not having shared calendars when >> we've had CalDAV integrated with IMAP for 10+ years. > > CalDAV is decidedly not an email protocol; POP3, IMAP, SMTP. > > ... > > So, IMHO, complaining that Outlook doesn't support CalDAV is sort of > like complaining that Firefox doesn't support SIP telephony. Could it > if it wanted to, sure. Should it, maybe. Does it, no. Outlook has (shared) calendars and contacts built-in for 20+ years. What's missing is the support for the standard CalDAV and CardDAV protocols in addition to the proprietary MS ones. I agree that an email client shouldn't do calendars and contacts to begin with, but that battle was lost when I was in high school.
