Confirm
360
edits
Changes
update for v1.2
* Maximum file size
** The maximum file size of sent attachments is 5 megabytes on v1.1 , v1.2 and master. This is done because we are likely to crash if we try and send larger files. {{bug|871897}} is about us switching to streaming for sending which would allow us to remove our send-side limitations. Receiving servers may still enforce a size limit. v1.0.1 has no size limit, but is likely to crash if files larger than 5 megabytes are sent.
* Attachment types supported
** We only support sharing images right nowImages: '''YES'', All versions** Audio: '''YES''', but thatv1.2 onwards (landed in {{bug|838008}})** Video: '''YES's an artificial limit '', v1.2 onwards (landed in {{bug|838008}})** PDF: No, although it is just a question of modifying our webapp.manifest.** Other type: No, although it is just a question of modifying our webapp that can and should be removed.manifest
=== Received Attachments ===
* Caveats
** ActiveSync does not provide the MIME-type for attachments, just the file name. So we need to infer the file type from the file extension.
=== Sharing ===
Sharing URLs from the browser app is supported.
=== Sent Mail Metadata ===
* Return Receipt / Delivery Status Notification
** '''NO'''.
=== Periodic Mail Synchronization / Push Notification ===
From version 1.2 onwards you can have the e-mail app automatically wake up and synchronize your e-mail message at various intervals, the lowest of which is every 5 minutes. Currently, we will not turn on wi-fi if it is not already on, so we will use a phone's data-plan if we have it. {{bug|907028}} is about improving this situation. If the device is charging/on wall power, it will not power off wi-fi when the screen goes off, and so wi-fi will be used for periodic sync.
There is currently no support for push notification. What is commonly referred to for ActiveSync purposes for 'push' is effectively the same as what IMAP IDLE/NOTIFY does; they require you to keep a connection alive for a long time, which is not something our devices are capable of doing in their current markets (and with the logic they use about turning off wi-fi when the screen comes off.) In the post-v1.3 time-frame we are going to try and work to establish a standard for allowing IMAP servers to use the simple push notification API by providing plugin implementations, etc.
=== ActiveSync ===
ActiveSync is supported since v1.0. Our primary test targets are hotmail.com/outlook.com and Microsoft-hosted Exchange servers. If you are using a third-party ActiveSync implementation. Specific third-party server implemenations we know about:
* Specific Third-party server support:
** 163.com: Yes, v1.1 onwards.
** m.gmail.com: It works, but do not use it! gmail's ActiveSync implementation has various issues and we do not support using it. See {{bug|810031}} for more information.
* Mail Sync Process
* Mail Sync Process
** IDLE-based push notifications: '''NO'''. We do use IDLE, but only as a means of keeping the connection alive. We want to support properly handling IDLE events. (asuth, 2013/05/15).
=== POP3 ===
POP3 support is planned for version 1.3. It is not yet landed.
=== Security ===
