IP Library Granted Patent US 9,633,336
Granted Patent B2
US 9,633,336 · App. 12/156,537 · Granted Apr 25, 2017

Method, system, and apparatus for truncating markup language email messages

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,633,336
App. No.
12/156,537
Granted
Apr 25, 2017
Kind
B2
Abstract

Truncating markup language email messages involves receiving a markup-language-formatted, source email having a message size that exceeds a predetermined size limit. The source email is truncated to conform to the predetermined size limit. The existence of unclosed tags in the truncated email is determined, and a suffix is appended to the truncated email. The suffix includes closing tags that correspond to the unclosed tags to the truncated email. A truncation index indicating where the truncation occurred is added to the message, as is a unique identifier usable to uniquely identify the source email stored on an email server. The truncated email is then sent to a recipient email client.

Claims (78)

1. A method comprising:

receiving a markup-language-formatted source email having a message size that exceeds a predetermined size limit;

truncating the source email to conform to the predetermined size limit;

determining unclosed markup-language tags in the truncated email;

appending a suffix to the truncated email that includes closing markup-language tags that correspond to the unclosed markup-language tags, the predetermined size limit including the suffix;

adding to the truncated email: a) a truncation index indicating where the truncation occurred, and b) a unique identifier uniquely identifying the source email stored on an email server;

sending the truncated email to a recipient email client at a recipient device;

receiving a markup-language-formatted response email formed at the email client based on the truncated email, wherein the response email includes the truncation identifier, the unique identifier, and the suffix of the source email;

retrieving the source email based on the unique identifier;

replacing the suffix of the response email with data from the source email that was removed from the truncated email;

sending the response email as replaced to the recipient device;

determining a second truncated message by repeating the truncation of the source email to conform to the predetermined size limit, based, at least in part, on the data from the source email that was removed from the truncated email,

wherein the truncated email is further added with attributes related to automatic truncation, the attributes include a source email identification and a point of truncation, and the truncated email includes a leading portion copied verbatim from the source email.

2. The method of claim 1 , further comprising:

retrieving the source email based on the unique identifier;

determining a second truncated message by repeating the truncation of the source email to conform to the predetermined size limit determining a second suffix of the second truncated message that includes closing markup-language tags that correspond to unclosed markup-language tags of the second truncated email, wherein data from the source email that was removed from the truncated email is determined based on determining the second truncated message; and

sending the response email with a message content portion unaltered based on a mismatch between a suffix of the response email and the second suffix.

3. The method of claim 2 , further comprising including the source email as an attachment to the unaltered response email based on the mismatch between the suffix of the response email and the second suffix.

4. The method of claim 1 , further comprising adding to the truncated email a selectable object that allows the entirety of the source email to be accessed.

5. The method of claim 1 , wherein at least one of the truncation index and unique identifiers are added as an email attribute that is separate from content of the truncated email.

6. An apparatus comprising:

a network interface capable being coupled to a recipient email client via a network;

a processor coupled to the network interface; and

at least one memory coupled to the processor and including computer programs code for one or more programs, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to perform at least the following:

receive a markup language formatted, source email having a message size that exceeds a predetermined size limit;

truncate the source email message to conform to the predetermined size limit;

determine unclosed markup-language tags in the truncated email;

append a suffix to the truncated email that includes closing markup-language tags that correspond to the unclosed markup-language tags, the predetermined size limit including the suffix;

add to the truncated email: a) a truncation index indicating where the truncation occurred, and b) a unique identifier uniquely identifying the source email stored on an email server;

send the truncated email to a recipient email client at a recipient device;

receive a markup-language-formatted response email formed at the email client based on the truncated email, wherein the response email includes the truncation identifier, the unique identifier, and the suffix of the source email;

retrieve the source email based on the unique identifier;

replace the suffix of the response email with data from the source email that was removed from the truncated email;

send the response email as replaced to the recipient device;

determine a second truncated message by repeating the truncation of the source email to conform to the predetermined size limit, based, at least in part, on the data from the source email that was removed from the truncated email,

wherein the truncated email is further added with attributes related to automatic truncation, the attributes include a source email identification and a point of truncation, and the truncated email includes a leading portion copied verbatim from the source email.

7. The apparatus of claim 6 , wherein the apparatus is further caused to:

retrieve the source email based on the unique identifier;

determine a second suffix of the second truncated message that includes closing markup-language tags that correspond to unclosed markup-language tags of the second truncated email, wherein data from the source email that was removed from the truncated email is determined based on determining the second truncated message; and

send the response email with a message content portion unaltered based on a mismatch between the suffix of the response email and the second suffix.

8. The apparatus of claim 7 , wherein the apparatus is further caused to include the source email as an attachment to the unaltered response email based on the mismatch between the suffix of the response email and the second suffix.

9. The apparatus of claim 6 , wherein the apparatus is further caused to add to the truncated email a selectable object that allows the entirety of the source email to be accessed.

10. The apparatus of claim 6 , wherein the apparatus is further caused to verify that the truncated message is well-formed according to rules of the markup language before sending the truncated message to the recipient email client.

11. A non-transitory computer readable storage medium carrying one or more sequences of one or more instructions which, when executed by one or more processors, cause an apparatus to at least perform the following steps:

receive a markup language formatted, source email having a message size that exceeds a predetermined size limit;

truncate the source email to conform to the predetermined size limit;

determine unclosed markup-language tags in the truncated email;

append a suffix to the truncated email that includes closing markup-language tags that correspond to the unclosed markup-language tags, the predetermined size limit including the suffix;

add to the truncated email: a) a truncation index indicating where the truncation occurred, and b) a unique identifier uniquely identifying the source email stored on an email server;

send the truncated email to a recipient email client at a recipient device;

receive a markup-language-formatted response email formed at the email client based on the truncated email, wherein the response email includes the truncation identifier, the unique identifier, and the suffix of the source email;

retrieve the source email based on the unique identifier;

replace the suffix of the response email with data from the source email that was removed from the truncated email;

send the response email as replaced to the recipient device;

determine a second truncated message by repeating the truncation of the source email to conform to the predetermined size limit, based, at least in part, on the data from the source email that was removed from the truncated email,

wherein the truncated email is further added with attributes related to automatic truncation, the attributes include a source email identification and a point of truncation, and the truncated email includes a leading portion copied verbatim from the source email.

12. An apparatus comprising:

a network interface capable being coupled to a recipient email client via a network;

at least one processor coupled to the network interface; and

at least one memory coupled to the processor and including computer program code for one or more programs, wherein the at least one memory and the computer program code are configured to, with the at least one processor, cause the apparatus to perform at least the following:

determine, via the email client, a markup language formatted, source email targeted for the email client and having a message size that exceeds a predetermined size limit;

download a portion of the source email that is used to form a truncated email conforming to the predetermined size limit;

determine unclosed markup-language tags in the truncated email;

append to the truncated email a suffix that includes closing markup-language tags that correspond to the unclosed markup-language tags to the truncated email, the predetermined size limit including the suffix;

add to the truncated email: a) a truncation index indicating where the truncation occurred, and b) a unique identifier uniquely identifying the source email stored on an email server;

send the truncated email to a recipient email client at a recipient device;

receive a markup-language-formatted response email formed at the email client based on the truncated email, wherein the response email includes the truncation identifier, the unique identifier, and the suffix of the source email;

retrieve the source email based on the unique identifier;

replace the suffix of the response email with data from the source email that was removed from the truncated email;

send the response email as replaced to the recipient device;

determine a second truncated message by repeating the truncation of the source email to conform to the predetermined size limit, based, at least in part, on the data from the source email that was removed from the truncated email,

wherein the truncated email is further added with attributes related to automatic truncation, the attributes include a source email identification and a point of truncation, and the truncated email includes a leading portion copied verbatim from the source email.

13. The apparatus of claim 12 , wherein forming the response email comprises:

including in the response email the suffix of the source email; and

preventing user editing of a suffix of the response email.

14. The apparatus of claim 12 , wherein the apparatus is further caused to:

add to the truncated email a selectable object that allows the entirety of the source email to be accessed; and

facilitate accessing the entirety of the source email based on user selection of the selectable object.

Assignments (12)
PATENT SECURITY AGREEMENT Recorded Aug 6, 2024
From: RPX CORPORATION; RPX CLEARINGHOUSE LLC
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 068328/0674 →
RELEASE OF LIEN ON PATENTS Recorded Aug 5, 2024
From: BARINGS FINANCE LLC
To: RPX CORPORATION
Reel/Frame 068328/0278 →
PATENT SECURITY AGREEMENT Recorded Apr 22, 2023
From: RPX CORPORATION
To: BARINGS FINANCE LLC, AS COLLATERAL AGENT
Reel/Frame 063429/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 28, 2021
From: PROVENANCE ASSET GROUP LLC
To: RPX CORPORATION
Reel/Frame 059352/0001 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: NOKIA US HOLDINGS INC.
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058363/0723 →
RELEASE OF SECURITY INTEREST Recorded Nov 30, 2021
From: CORTLAND CAPITAL MARKETS SERVICES LLC
To: PROVENANCE ASSET GROUP HOLDINGS LLC; PROVENANCE ASSET GROUP LLC
Reel/Frame 058983/0104 →
ASSIGNMENT AND ASSUMPTION AGREEMENT Recorded Feb 14, 2019
From: NOKIA USA INC.
To: NOKIA US HOLDINGS INC.
Reel/Frame 048370/0682 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 13, 2017
From: NOKIA TECHNOLOGIES OY; NOKIA SOLUTIONS AND NETWORKS BV; ALCATEL LUCENT SAS
To: PROVENANCE ASSET GROUP LLC
Reel/Frame 043877/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP LLC
To: NOKIA USA INC.
Reel/Frame 043879/0001 →
SECURITY INTEREST Recorded Sep 13, 2017
From: PROVENANCE ASSET GROUP HOLDINGS, LLC; PROVENANCE ASSET GROUP, LLC
To: CORTLAND CAPITAL MARKET SERVICES, LLC
Reel/Frame 043967/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 24, 2015
From: NOKIA CORPORATION
To: NOKIA TECHNOLOGIES OY
Reel/Frame 035496/0653 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2008
From: BARTLETT, TROY LEE
To: NOKIA CORPORATION
Reel/Frame 021146/0867 →