| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Adding methonds to avoid resource leaks issue
of Explicit termination method 'close' not called
Change-Id: Ic66e9c1beb48122e843537c618b32ceaf788c540
CRs-Fixed: 1036339
|
|
|
|
| |
Change-Id: I47f29c16c066eb077c64ef8c89e91df88d15caf0
|
|
|
|
|
|
|
| |
Found this issue when addressing the root problem for this bug and testing
with various mixes of text and html content in emails.
Change-Id: I875fd9fac85b07484c27db383e3ac4a3cb935ee6
|
|
|
|
|
|
|
|
|
|
|
|
| |
THIS DOES NOT CHANGE ANY EXISTING FUNCTIONALITY.
Address.pack() has been removed and all calls replaced with its synonym Address.toHeader().
Address.unpack() has been renamed to Address.fromHeader() to follow the new naming convention.
In days of yore, pack() and toHeader() used to do different things. Now they are identical and
thus one is superfluous. We have standardized on toHeader() and fromHeader().
Change-Id: Iac91c966eb6c1477f8dba0dd2ae01c84b359e539
|
|
|
|
|
|
|
|
|
|
| |
Quoted text pos may be out of bounds of message body.
This may be caused by the pos being calculated in html while the message is being
sent as plain text. A seperate CL will attempt to address the root cause. This
is a last resort so we don't crash.
Bug: 11538910
Change-Id: I326ebe56ee15368983caa2fa76605e7658dab014
|
|
|
|
|
| |
Bug: 9565838
Change-Id: I5e95562bbf463f057cbcc4a9884427a774473b45
|
|
|
|
|
|
|
| |
This CL is mostly just deletion since the new code
is in a new project.
Change-Id: I4aee519187a6ed7514c97d2a7a85ed29ea29d25f
|
|
|
|
| |
Change-Id: Idbfff4ddc8fca4829228d04816d40a4ab9639382
|
|
|
|
|
|
|
|
|
|
| |
The problem was that when the attachment was attempted to be opened
from the Exchange process, it didn't have access to the cached file.
Instead, use a content provider uri to reference the cached file.
Bug: 8400456
Change-Id: I80abd66642e938cf09f73bf0e9bd049aa8d7ba1d
|
|
|
|
|
|
|
|
| |
Cache attachments in a email directory when sending to allow sending
to succeed when the content provider has a permission
Bug: 7381557
Change-Id: Icf9faead2048de237228625f998b42feade48978
|
|
|
|
|
|
|
| |
* Make sure new code works with old Attachment rows
Bug: 7130972
Change-Id: Ia5d258930f39266517eead535a92bb4380fdb594
|
|
|
|
|
|
|
|
|
|
| |
* The default is to send all attachments, of course, but with
smartSend, we need to exclude the original ones or they will
be duplicated
* Another CL in Exchange is required to fix the bug
Bug: 7005505
Change-Id: I0e8bab2fb53dd4d60c82f2ef9a525ff7b015f2eb
|
|
|
|
|
|
| |
* Also, handle MessagingException when doing STAT
Change-Id: I5267b64f18a84fcc97fc2d003e49d4e373ea02c5
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Much, much faster
* Remove message length pass and lots of other useless code
* Create pseudo-attachment for long messages (click to download) that
includes size (so user can determine whether it's worth it)
* Handle download of message via pseudo-attachment; real attachments
are then created as necessary.
TODO: Add real UI with UX input (or modify existing to clean up the
loose ends)
TODO: Optimizations for loading the whole message
TODO: Get server delete working (isn't working currently anyway)
Change-Id: I31f3809fc5a2f9fd490d33cfed70d2930654e71d
|
|
|
|
| |
Change-Id: I06df7e467cd2e0117df8b8db3ddc6ff9da13f1c7
|
|
|
|
|
|
|
| |
* When confirmed fixed, this should be backported to MR2/MR2
Bug: 4490341
Change-Id: Ie99047b465ed7087e6e0100f7d517ac3fb6b803c
|
|
|
|
|
|
|
|
|
|
| |
On exchange servers that support "smart reply", the original message is
actually appended by the server. In this situation, we should not append
the original HTML text on the client.
but 4177192
Change-Id: I6fad74ac761e2abfe7cb0f536df4db30f7d5ca9a
|
|\
| |
| |
| |
| | |
* commit 'b50a766d4acc563beff90d22dc3dac48038ff4f1':
Remove STOPSHIP logging
|
| |
| |
| |
| | |
Change-Id: I73786fb2f4ff10d3c0767a873e5eb1e443f1affc
|
|\|
| |
| |
| |
| | |
* commit '39121c758dcc919b5fde4c893d488916e26d3140':
Fix display of inline images
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Inline images can be specified in two different ways -- explicitly with a
Content-Disposition of "inline" or implicitly with no Content-Disposition.
We correctly handled the former. For the later, we now default to an "inline"
disposition if one was not specified. This is acceptable per RFC 822 which
states:
Content-Disposition is an optional header field. In its absence,
the MUA may use whatever presentation method it deems suitable.
Additionally, if the disposition is not specified by the server, we need to
look at the Content-Type header for the file name.
bug 2824698
Change-Id: I146f7a67197b4e737e5f82a3d570e0f74e23fa35
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When replying or fowarding an HTML message, we now send both plain text and
HTML bodies as a multi-part mime message. We take special care to ensure the
message bodies are in their own multi-part block and do not interfere with
any additional attachments to the message.
bug 3060920
Backport-Of: I2fc3cb4e1f65bcc28486a62731b44b0ee0a99719
Change-Id: I89ec2795b55ceb7472a8ee3db2dc8f50cf537d9c
|
|/
|
|
|
|
|
|
|
|
|
| |
When replying or fowarding an HTML message, we now send both plain text and
HTML bodies as a multi-part mime message. We take special care to ensure the
message bodies are in their own multi-part block and do not interfere with
any additional attachments to the message.
bug 3060920
Change-Id: I2fc3cb4e1f65bcc28486a62731b44b0ee0a99719
|
|
|
|
| |
Change-Id: I846ee2a4b541f4709e647aa537c61549db2bec2e
|
|
|
|
| |
This reverts commit c28bf353190eb576072a8fd2f98821424144876e.
|
|
|
|
|
|
|
|
|
| |
Slight API change to make it more clear what the method parameter is for.
Also add some additonal test conditions to the Rfc822Output tests.
Reapply changes in CL https://android-git.corp.google.com/g/#change,99090
Change-Id: I7a48c9544e48cbdf44b14f4b1f8d92fe01f7861e
|
|
Change-Id: I90653e8601ee3ee6a8719d87ffb93222a11a22c0
|