[07:58] *** mkb_ has joined #arpnetworks [08:25] *** mkb_ has quit IRC (Quit: leaving) [11:14] *** Lucifer333 has joined #arpnetworks [11:19] *** nesta_ has joined #arpnetworks [11:23] *** mjp__ has joined #arpnetworks [11:28] *** mjp_ has quit IRC (*.net *.split) [11:28] *** nesta has quit IRC (*.net *.split) [11:28] *** dne has quit IRC (*.net *.split) [11:34] *** dne has joined #arpnetworks [13:09] *** mkb_ has joined #arpnetworks [15:31] *** mkb_ has quit IRC (Remote host closed the connection) [15:36] *** Lucifer333 has quit IRC (Quit: Leaving) [15:49] anyone know if Amazon WorkMail is run on Windows Servers + Exchange or *NIX / Outlook Compatible Servers ? [15:50] in WINE on ArchLinux [15:51] lol [15:54] i imagine it would be too much pain for anyone to try and keep a *nix compatible service up to date with the latest Microsoft protocols [15:54] this is Amazon though - so if anyone can do it its them [15:54] Microsoft can't even get theit Skype/Outlook clients working properly on MacOS [15:54] *their own [15:55] You reckon Amazon would risk causing an outage to their customers every time Microsoft releases and updated client etc? [15:55] https://www.youtube.com/watch?v=ViGdElGV6nk [15:55] I dunno maybe they have reverse engineered it properly, seems like a waste of time though [15:55] YouTube video: "AWS re:Invent 2016: Stop Managing Email Infrastructure: Move to Amazon WorkMail (BAP205)" by Amazon Web Services [15:56] watching that now maybe they reveal the infrastructure design [15:57] looks like they use the EWS protocol not MAPI [15:58] does EWS require Windows? [15:58] on the server end [16:02] dont think so, i think its HTTP based? [19:32] *** andol has quit IRC (Quit: leaving)