35.14 KB, text/plain
hotmail.com/outlook.com supports IMAP now. Switching to IMAP will allow us to avoid a number of ActiveSync protocol-related things that are a problem for us: - arbitrary time restrictions, all-or-nothing-ish syncs - no mime types for attachments - no ability to APPEND drafts/etc. to the server - HTML upconversion due to body type ambiguity (although I think our decision here was mainly because of gmail's wacky ActiveSync implementation) - can't see bcc recipients of a message And then there are some things that are somewhat more our fault: - We always report the same device id (bug 825538) We do want to do a little bit of testing before throwing the switch on this, of course. Relevant bugs are the ISP DB bugs: bug 916121 and bug 917035.
Oh, and another biggie: - Threading. Threading is absolutely broken on ActiveSync for us because of the inability to fetch headers.
should also CC this to Thunderbird. Config new is: Incoming IMAP Server: imap-mail.outlook.com Server port: 993 Encryption: SSL Outgoing SMTP Server: smtp-mail.outlook.com Server port: 587 Encryption: TLS source: http://blogs.office.com/2013/09/12/outlook-com-now-has-imap/
Bug 917035 is fixed now. Thanks for the reminder, Andrew. I hope this helps you.
Created attachment 8417210 [details] notes/logcat-ish output from distubring outlook.com IMAP sync Ugh, so I just tried with my hotmail account and it looks like the outlook.com IMAP has major issues from our perspective. Its SINCE/BEFORE logic will actually skip over messages somehow, we fail to parse out a bodystructure for some messages, etc. I'm attaching the logs here. I also have super-verbose json logs locally but I hate changing my hotmail credentials without a good reason and I suspect these types of problems are easy to repro.
> Its SINCE/BEFORE logic will actually skip over messages somehow, > we fail to parse out a bodystructure for some messages, etc. Can you more concretely describe what the problems are? Symptoms and - if you know - background and concrete reasons. Does Thunderbird have the same issues? If not, can you adapt your logic to do what TB does?
(In reply to Ben Bucksch (:BenB) from comment #5) > Can you more concretely describe what the problems are? Symptoms and - if > you know - background and concrete reasons. > > Does Thunderbird have the same issues? If not, can you adapt your logic to > do what TB does? I would expect Thunderbird to be fine. The SINCE/BEFORE stuff matters since the Gaia email app does date-based partial syncs (see https://wiki.mozilla.org/Gaia/Email/Implementation/MailSynchronization#Partial_Folder_Sync_Basics). Thunderbird just synchronizes the whole folder using UIDs and does not depend on the server's search implementation to be correct unless you search-on-server. The bodystructure failure is likely a problem with the imap.js we use which is forked enough that we have not been tracking upstream and has had some bodystructure issues before. We need to switch to the email.js implementations. This is bug 885110, marking dependency.
[priority] --> tracking-b2g:+ conversion