Download of current portions of email messages

• US 9,935,908 B2
• Filed: 03/23/2015
• Issued: 04/03/2018
• Est. Priority Date: 04/01/2008
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Inventors: Sawhney, Ishdeep
• Primary Examiner(s): Joo, Joshua
• Application Number:
  US14/666,209
• Publication Number:
  US 20150195238A1
• Time in Patent Office: 1,107 Days
• Field of Search: None
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/063 Content adaptation, e.g. replacement of unsuitable content
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes

Abstract

In general, this disclosure describes techniques of enabling devices to download only current portions of email messages without downloading historical portions of the email messages. For instance, when an email client generates a reply email message to an original email message, the reply email message includes a current portion and a historical portion. The current portion of the reply email message includes new information and the historical portion of the reply email message includes the original email message. The techniques of this disclosure enable devices to download the current portions of email messages without downloading the historical portions of the email messages.

Claims

1. A computing device comprising:

a data storage medium that stores instructions; and

a processor to execute the instructions, which causes the computing device to;

receive a truncated message, the truncated message including a current portion;

determine, by the computing device, whether the truncated message includes a message identifier that identifies a historical portion associated the truncated message;

when the truncated message does not include any message identifier that identifies the historical portion, send a request for an untruncated message to a message server;

when the truncated message includes a message identifier that identifies the historical portion;

determine, by the computing device, whether the historical portion is stored;

generate a combined message by appending the historical portion to the truncated message; and

replace the truncated message with the combined message.

2. The computing device of claim 1, further comprising:

when there is no historical portion, sending a request for the untruncated message to a message server.

3. The computing device of claim 1, further comprising:

when there is no historical portion, sending a request for the untruncated message to a message server.

4. The computing device of claim 1, wherein the truncated message includes a plurality of header fields.

5. The computing device of claim 4, wherein a portion partition header field of the plurality of header fields identifies the historical portion.

6. The computing device of claim 4, wherein a message identifier header field of the plurality of header fields identifies the historical portion.

7. The computing device of claim 4, wherein an in-reply-to header field of the plurality of header fields identifies the historical portion.

8. The computing device of claim 4, wherein a references header field of the plurality of header fields identifies the historical portion.

9. A method comprising:

receiving a truncated message, the truncated message including a current portion;

determining, by a computing device, whether the truncated message includes a message identifier that identifies a historical portion;

when the computing device determines that the truncated message does not include any message identifier that identifies the historical portion, sending a request for an untruncated message to a message server;

when the computing device determines that the truncated message includes a message identifier that identifies the historical portion;

determining, by the computing device, whether the historical portion is stored;

generating a combined message by appending the historical portion to the truncated message; and

replacing the truncated message with the combined message.

10. The method of claim 9, further comprising:

when there is no historical portion, sending a request for the untruncated message to a message server.

11. The method of claim 9, further comprising:

when there is no historical portion, sending a request for the untruncated message to a message server.

12. The method of claim 9, wherein the header includes a portion partition header field that identifies the historical portion.

13. A computing device comprising:

a data storage medium that stores instructions;

a processor; and

a client application including;

an incoming message module operable to receive a message, determine whether message is a truncated message, and to determine whether the truncated message includes a message identifier that identifies a historical portion associated with the truncated message; and

a message recovery module operable to send a request for an untruncated message when the truncated message does not include any message identifier that identifies the historical portion; and

when the truncated message includes a message identifier that identifies the historical portion;

the message recovery module operable to determine whether the historical portion associated with the truncated message is stored as a cached message, and generate a combined message by appending the historical portion to the truncated message when the historical portion associated with the truncated message is stored as the cached message.

14. The computing device of claim 13, wherein the message recovery module is further operable to send a request for an original message to a message server when there is no historical portion.

15. The computing device of claim 13, wherein the message recovery module is further operable to send a request for the untruncated message to a message server when there is no historical portion.

16. The computing device of claim 13, wherein the historical portion associated with the truncated message is identified in a header field associated with the truncated message.

17. The computing device of claim 13, wherein the historical portion is excluded from the truncated message.