Sectional E-mail transmission

- IBM

A process of segmenting a single email so that portions of it may be directed to or away from select recipients is disclosed. The sender highlights portions of the email and right clicks (or key command, button, or menu item) and selects an option to select recipients. The operator interface then provides the sender with the option of selecting recipients from their address book or the server's address book. To speed the process along, the sender may select those already on the To, Cc, or Bcc distribution lists. The sender then selects whether those chosen will receive the highlighted portion or if they will be excluded from receiving it. Lastly, the sender will have the option of providing text that is unique to each of the selected groups.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATION

This application is related to co-pending a continuation of U.S. utility patent application entitled “System And Method for Sectional E-Mail Transmission” filed on Aug. 19, 2004 and accorded Ser. No. 10/922,249, which is entirely incorporated herein by reference.

FIELD OF THE INVENTION

This invention is related to the field of electrical computers and digital processing systems to transfer data via one or more communications media in general, and specifically, to a demand-based messaging system for simultaneous transmission of sections of an email to different recipients without the need to send separate emails.

BACKGROUND OF THE INVENTION

A demand-based messaging system is any communication system that enables a person to exchange electronic messages with another person over a communications media. Demand-based messaging systems typically comprise a network of data processing machines and a messaging program operable on at least one machine to transfer electronic messages over the network to one or more of the other machines. Electronic messages typically are composed of a variety of information, including message data and transmission data. As those terms are used here, “message data” generally refers to the substance of the message, such as text or images, while “transmission data” generally refers to the information required to deliver or respond to the message, such as the correspondents' electronic addresses. Electronic messages also may include status information, such as the time and date that the message was composed, sent, or received.

LOTUS NOTES, MOZILLA, and MICROSOFT OUTLOOK are exemplary messaging programs that enable users to exchange electronic mail messages through networked computers. Instant messaging (“IM”) programs such as MSN MESSENGER and YAHOO! MESSENGER, which have gained popularity in recent years, exemplify another embodiment of messaging programs that enable users to exchange electronic messages in real-time through networked computers.

Electronic mail messages are often sent to a group of recipients. Such recipients fall into three categories: the addressee, the copied recipient, and the recipient who receives a blind copy. The addressee receives the message and sees who has been copied. The recipient who has been copied receives the message and knows to whom the message was directed. The recipient who receives a blind copy receives the message, knows to whom the message was directed and who received copies, but the addressee and the copied recipients do not know the identity of the blind copy recipient.

An originator may want to send a bulk message to all recipients, but a small section unique to each individual recipient. For example, a user may send instructions to coordinate an event, with a unique time assignment to each recipient who receives the email. Sometimes a need arises to vary the message sent to one or more recipients. A sender of an email may not want its entire contents to go to all recipients. Normally, the sender would have to break up the email and send it in segments. Having to send multiple emails wastes the sender's time as well as wastes disk space on the server and bandwidth on the network.

An originator may desire to send an email where only a portion is intended for all recipients, another portion only for select recipients, and a final portion that is not to be sent to certain other recipients. Perhaps the material sent to the select recipients is confidential. The material not to be sent to some recipients may be attachments that are already available to them on their server.

An originator may desire to send an email containing a section of text that is of common interest to all the recipients followed by text that is specific to each recipient. Perhaps the specific text is the recipient's new password. The desire is to send the specific text only to the intended recipient. The common text would go to all recipients.

The need to vary the message can arise with a group of recipients in one status grouping or in more than one status grouping. For example, the sender may want to provide additional information for a recipient who is less familiar with the context of the message than other recipients. Likewise, a user may want to send special instructions to a recipient such as a reminder to a blind copy recipient not to reply because the user does not want the other recipients to know he included the blind copy recipient. Presently, varying message text requires sending separate messages.

Sending separate messages requires time to create the separate electronic messages and to copy and paste the content of the separate messages. Since the messages are sent separately, some of the reply messages will not go to all of the recipients. In particular, reply messages will not go to all recipients when the reply comes from a message sent only to a subset of the overall group of recipients. In order to solve this problem, the sender could include the subset of recipients on both emails. In that event, the subset of recipients receives redundant emails. Sending multiple electronic messages consumes more network bandwidth and storage space. Increased consumption of network bandwidth and storage space increases costs. Costs further increase when the email is large or has large attachments. If an originator of an email had an easy way to segment a single email, the originator would save time as well as network disk storage space and bandwidth. Therefore, a need exits for an improved electronic messaging system that allows transmission of e-mail segments to different recipients.

U.S. Pat. No. 6,118,856 discloses receiving an email and automatically forwarding it to a remote device. The forwarding is done by an act of the recipient, not the sender. The forwarding may be limited to a selective portion of the original email. This patent is primarily concerned with forwarding received emails to a cell phone or a text pager. The forwarding is based on the content of the message. For example, the forwarding may be done based on a particular sender.

U.S. Pat. No. 6,446,118 discloses a system for receiving email while away from your computer without having to subscribe to a “commercial, public network” such as SkyTel. A portion of the email, such as the header, may be all that is transmitted to an email notification device. Other, limited information, like message size and when the message was originally received, may also be transmitted.

SUMMARY OF THE INVENTION

The invention that meets the needs described above is a process of segmenting a single email so that portions of it may be directed to or away from select recipients. The sender highlights portions of the email and right clicks (or key command, button, or menu item) and selects an option to select recipients. The operator interface then provides the sender with the option of selecting recipients from their address book or the server's address book. To speed the process along, the sender may select those already on the To, Cc, or Bcc distribution lists. The sender then selects whether those chosen will receive the highlighted portion or if they will be excluded from receiving it. Lastly, the sender will have the option of providing text that is unique to each of the selected groups.

These and other objects of the invention will be apparent to those skilled in the art from the following detailed description of a preferred embodiment of the invention.

BRIEF DESCRIPTION OF DRAWINGS

The novel features believed characteristic of the invention are set forth in the appended claims. The invention itself, however, as well as a preferred mode of use, further objectives and advantages thereof, will best be understood by reference to the following detailed description of an illustrative embodiment when read in conjunction with the accompanying drawings, wherein:

FIG. 1 depicts a computer network in which the invention may be employed;

FIG. 2 depicts a representative computer memory in which the invention may reside;

FIG. 3 depicts an example e-mail applying the invention;

FIG. 4 depicts a dialog box with a select recipients option;

FIG. 5 depicts a window for the select recipients option;

FIG. 6 depicts a window for entering a recipient address;

FIG. 7 depicts recipient display;

FIG. 8 depicts a copy recipient display;

FIG. 9 depicts a flow chart of the Client Sectional E-Mail Program;

FIG. 10 depicts a flow chart of the Server Sectional E-Mail Program;

FIG. 11 depicts a flow chart of the Client E-mail Clearance Program;

FIG. 12 depicts a flow chart of the Server E-Mail Clearance Program; and

FIG. 13 depicts a flow chart of the Cursor Display Program.

 DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT

A person of ordinary skill in the art will appreciate that the present invention may be implemented in a variety of software and hardware configurations. It is believed, however, that the invention is described best as a computer program that configures and enables one or more general-purpose computers to implement the novel aspects of the invention.

As used herein, “attachment” means a file that is transmitted with an email that is not part of any messages in the email itself.

As used herein, “blind copy recipient” means a recipient whose identity is not to be disclosed to other recipients of the same message.

As used herein, “computer” means a machine having a processor, a memory, and an operating system, capable of interaction with a user or other computer, and shall include without limitation desktop computers, notebook computers, tablet computers, personal digital assistants (PDAs), servers, handheld computers, and similar devices.

As used herein, “copy recipient” means a recipient for whom a message is not primarily intended but who is included in the distribution list to be kept informed, and may be synonymous with secondary recipient.

As used herein, “electronic mail” or “email” means direct user-to-user transmission of messages between user computers over a network.

As used herein, “electronic messaging” means the creation, transfer, storage, and retrieval of text, graphics, images, or voice data by electronic means.

As used herein, “header” means the portion of a message that contains control information for the message.

As used herein, “recipient” means anyone or any location that receives data, and a user of a demand-based messaging system to whom a message is addressed.

As used herein, “section” means a message or a portion of a message.

As used herein, “message” means an electronic mail message transmitted over a network.

FIG. 1 illustrates a common prior art architecture for connecting various hardware devices to create a network for transferring data. Computer network 100 comprises local workstation 101 electrically coupled to network connection 102. In FIG. 1, local workstation 101 is coupled electrically to remote workstation 103 via network connection 102. Local workstation 101 also is coupled electrically to server 104 and persistent storage 106 via network connection 102. Network connection 102 may be a simple local area network (LAN) or may be a larger wide area network (WAN), such as the Internet. While computer network 100 depicted in FIG. 1 is intended to represent a possible network architecture, it is not intended to represent an architectural limitation.

The internal configuration of a computer, including connection and orientation of the processor, memory, and input/output devices, is well known in the art. FIG. 2 represents the internal configuration of a computer having the computer program of the present invention loaded into memory 200. The computer program of the present invention is depicted as SEP 210. As will be discussed further below, SEP 210 includes without limitation Client Sectional E-Mail Program (CSEP) 220, Client E-mail Clearance Program (CECP) 230, Server Sectional E-Mail Program (SSEP) 240, Server E-Mail Clearance Program (SECP) 250, and Cursor Display Program (CDP) 270. Memory 200 also has messaging program 270. Memory 200 is only illustrative of memory within a computer and is not meant as a limitation. Memory 200 may reside in a client computer such as local workstation 101 or in a server computer such as server 104.

In alternative embodiments, SEP 210 can be stored in the memory of other computers. Storing SEP 210, in the memory of other computers allows the processor workload to be distributed across a plurality of processors instead of a single processor. Further configurations of SEP 210 across various multiple memories and processors are known by persons skilled in the art.

FIG. 3 depicts an example e-mail 300. E-mail 300 has originator section 310, addressee section 320, message section 330, first tab 340 and second tab 350. Addressee section 320 has recipient address section 322, copy recipient address section 324, blind copy recipient address section 326 and subject section 328. Message Section 330 has first message section 332, second message section 334, and attachment 336. Recipient address section 322 has first recipient address 322A shown as customer1@customer.com and second recipient address 322B shown as “customer2@customer.com.” Copy recipient address section 324 has first copy recipient address 324A shown as SalesRep1@ibm.com and second copy recipient address 324B shown as SalesRep2@ibm.com. Blind copy recipient address section 326 is empty. Subject section 328 shows “Product Demonstration.” First message section 332 shows an example message intended for internal use only, “Below is the email I am sending to the customer.” First message section 332 also contains information only for the copy recipient addressees explaining to them that they are not receiving the attachment sent to the recipients, “The attachment is hidden from your view since you already have it on your hard drives.” Second message section 334 contains information for the recipient addresses regarding an invitation to a product demonstration.

Originator 310 normally would create one email to the customers shown in recipient addressee section 322 and create another email to the copy recipient addressees shown in copy recipient address section 324. However, SEP 210 allows originator 310 to create one email and to sectionalize that one email in the following manner.

In order to sectionalize the email, originator 310 highlights first message section 332 and, using a mouse, right clicks (or such other means known to person skilled in the art such as a key command button or menu item) to receive a display of options from which the originator selects “select recipients.” Upon selecting “select recipients” a dialog box appears asking the originator to identify who will receive the section. Referring to FIG. 4, dialog box 400 has a number of prior art options for selection and a new option appearing in dialog box 400, select participants 410. Upon activating select recipients 410 a further selection window, window 500 appears providing selection options.

Referring to FIG. 5, window 500 has Select all To 510, Select all Cc 520, Select all Bcc 530, Select from address book 540, and Select User defined 550. Activation of Select All To 510 means that the highlighted portion of the e-mail will only be received by those recipients identified in recipient address section 322. Activation of Select All Cc 520 means that the highlighted portion of the e-mail will only be received by those recipients identified in copy recipient address section 324. Activation of Select All Bcc 530 means that the highlighted portion of the e-mail will only be received by those recipients identified in blind copy recipient section 326.

Alternatively, upon selection of select recipients window 410 from dialog box 400, a list of all recipients in the recipient address section 322, copy recipient address section 324, and blind copy recipient address section 326 may be presented so that the user can select recipients using drag and drop, highlighting, checkboxes, add/remove buttons, and other means known to persons skilled in the art.

Activation of Select from Address Book 540 means that originator 310's address book will be displayed so that originator 310 can select addressees to receive the highlighted portion of the e-mail, and those selected will be the only ones that will receive the highlighted portion. SEP 210 may be configured to display the user's local or server address book. In addition, originator 310 may add recipients from the address book to names selected from other options in window 500. Activation of Select User Defined 550 means that an entry field window, such as Enter recipient window 600 will appear. Referring to FIG. 6, enter recipient window 600 has entry field 620 for originator 310 to enter a recipient email address. Persons skilled in the art will be aware of multiple ways in which information may be presented, and multiple ways in which selections may be made by originator 310.

Once originator 310 makes selections, the email appears in its entirety to originator 310, but the recipients will only receive and be able to read those portions designated for them to receive and read. Originator 310 may review the e-mail by passing the cursor over the various portions of the email. For example, passing the cursor over second section 334, causes second recipient window 700 (see FIG. 7) to appear displaying the recipients designated to receive second section 334. Likewise, passing the cursor over first section 332 causes a window to appear, such as copy recipient window 800 (see FIG. 8), displaying the recipients designated for first section 332.

FIG. 9 depicts a flow chart for the CSEP 220. CSEP 220 begins and determines whether originator 310 has made a selection (910). If not, CSEP 220 goes to step 928. If originator 310 made a selection, then a determination is made whether originator 310 chose a field (912). If originator 310 chose a field, then the selected field is saved (914) and CSEP 220 goes to step 918. If not, CSEP 220 determines whether originator 310 wants to choose an address from an address book (918). If so, CSEP 220 saves the address selected by the user (920) and goes to step 926. If not, CSEP 220 determines whether the user wants to enter an address (922). If so, CSEP 220 enters the address (924) and goes to step 926. If not, an error message is displayed (923) and CSEP 220 goes to step 928. At step 926, CSEP 220 inserts section information into the email header (926). The section information embedded in the email header designates the section by starting and ending character. By designating starting and ending characters, the originator can specify sections by word, phrase, sentence or paragraph. In other words, the originator can specify sections with total granularity. The originator may have the option to prefix the selected sections with explanatory text to inform the recipients that the section is being transmitted only to them. Moreover, standard explanatory text may be automatically inserted with a section that has been designated for specific recipients. The preferred implementation of such optional text would be hypertext markup language (HTML) formatting with indenting and coloring capability. A determination is made whether there is another segment (928). If so, CSEP 220 goes to step 910. If not, CSEP 220 sends the email to the server (930) and stops (940).

FIG. 10 depicts a flow chart of Server Sectional Email Program (SSEP) 240. SSEP 240 begins, and receives an email (1010). SSEP 240 parses the header of the email (1020) and determines whether recipient is designated (1030). If not, SSEP 240 stops (1090). If so, SSEP 240 determines whether there is a section header for the recipient (1040). If so, SSEP 240 goes to step 1080. If not, SSEP 240 removes the section (1050), removes the header (1060) and sends the email to the messaging program (1070). In other words, SSEP 240 sends to the recipient only the text and/or attachments of the section that have been specified for that recipient. Correspondingly, SSEP 240 strips from the email the text and attachments of the section for those who are not specified to receive the section. When stripping text and attachments for those message recipients that are not to receive the section, SSEP 240 also removes the header information so that the recipient cannot see that there were sections the recipient did not receive. However, for sections the recipient does receive, the email retains the header which provides additional functionality as described in FIG. 13. SSEP 240 determines whether there is another recipient (1080). If so, SSEP 240 goes to step 1040. If not, SSEP 240 stops (1090).

Since CSEP 220 sends the email to the server with instructions on segmenting the email, and SSEP 240 then segments the email according to the instructions in the header and sends the separate emails to the respective recipients, network bandwidth and storage are conserved.

FIG. 11 depicts a flow chart of Client E-mail Clearance Program (CECP) 230. CECP 230 starts (1102) and parses the header of an email (1110). CECP 230 determines whether approval is required (1120). If not, CECP 230 stops (1150). If so, CECP 230 holds the email (1130), sends the email to an approver (1140) and stops (1150). Persons skilled in the art are aware that CECP 230 may be enabled or disabled. Furthermore, CECP 230 may be configured so that a criteria is established for determining which emails require approval. Approval criteria may include emails to a certain domain, such as a customer's domain, time, location, keywords, recipients, or any other criteria that would support management functions.

FIG. 12 depicts a flow chart of Server E-mail Clearance Program (SECP)250. SECP 250 starts (1202) and receives a reply from the approver (1210). SECP 250 determines whether the reply is correct (1220). If the reply is not correct, an error message is displayed, and SECP 250 goes to step 1280. If the reply is correct, SECP 250 determines whether approval has been granted (1230). If not, SECP 250 cancels the email (1240), sends a status to the approver (1250), sends a status to the originator (1260), and stops (1290). If so, SECP 250 sends the email to the messaging program (1270). SECP 250 then determines whether there is another reply (1280). If so, SECP 250 goes to step 1220. If not, SECP 250 stops (1290). Persons skilled in the art are aware of multiple methods by which the approver may reply. For example, approval may consist of a reply from the approver, or an action such as changing the subject to “Approve” or “Yes.” Likewise, denial can be controlled by changing the subject to “Deny” or “No” along with optional comments in the body of the email.

Once section information has been inserted into the header of the email, a user may hover the mouse over a given section of email and obtain information regarding who received or did not receive that section. FIG. 13 depicts a flow chart of the Cursor Display Program CDP 270. CEP 270 starts (1302) and determines whether SEP is running (1310). If not, CDP 270 stops. If so, CDP 270 determines whether the user has placed a cursor over the email (1320). If not, CDP 270 goes to step 1350. If so, CDP 270 determines whether the cursor is over a selected section (1330). If not CDP 270 goes to step 1350. If so, CDP 270 displays the recipients for the selected section (1340). At step 1350, CDP 270 determines whether the cursor has moved (1350). If so, CDP 270 goes to step 1320. If not, CDP goes to step 1310.

In an additional embodiment, SEP 210 may he configured to block a recipient from replying or forwarding an email that was sent only to that recipient. Such an embodiment may prevent accidental disclosure of information intended only for specified recipients.

In an alternate embodiment, SEP 210 may be employed only in the client computer. In such an embodiment, the client computer segments the email and sends separate emails as provided by the originator. Such an embodiment does not save bandwidth and disk storage space, but it does save the originator's time by automatically preparing the separate messages. In addition, such an embodiment allows for a pure client implementation, at reduced functionality, without requiring a server implementation.

A preferred form of the invention has been shown in the drawings and described above, but variations in the preferred form will be apparent to those skilled in the art. The preceding description is for illustration purposes only, and the invention should not be construed as limited to the specific form shown and described. The scope of the invention should be limited only by the language of the following claims.

Claims

1. A computer program product for segmenting an email addressed to a plurality of original email recipients without the need to send separate emails, the computer program product comprising:

a computer readable storage device;
first program instructions for selecting a section of the email;
second program instructions for selecting a recipient for the section from the plurality of recipients;
third program instructions for inserting, responsive to selecting the recipient for the section, a section information that identifies the recipient for the section and a starting and an ending character of the section into a header of the email;
fourth program instructions for sending the email to an email server, the email server comprising a processor and a memory;
fifth program instructions for receiving the email at the email server;
sixth program instructions for parsing, at the email server, the header for the section information;
seventh program instructions for sending, at the email server, the email to the recipient for the section; and
eighth program instructions for sending, at the email server, the email without the section and the section information to the plurality of original recipients that have not been selected for receiving the section so that the plurality of original recipients cannot see that the section was removed;
wherein the first through the eighth program instructions are stored in the computer readable storage device; and
wherein the section information is adapted to automatically prefix the section with an explanatory text to inform the section recipient that the section is being transmitted only to the section recipient, and wherein the explanatory text is adapted to be indented and colored.

2. The computer program product of claim 1 further comprising:

ninth program instructions for displaying, responsive to passing a cursor over the selected section of the email, a window showing a recipient of the selected section;
wherein the ninth program instructions are stored in the computer readable storage device.

3. The computer program product of claim 1, wherein selecting a section of the email is responsive to a user highlighting a portion of the email and right clicking on the highlighted portion.

4. The computer program product of claim 1 further comprising:

tenth program instructions for displaying, responsive to selecting the section of the email, a window having the plurality of recipients for identifying the section recipient of the section;
wherein the tenth program instructions are stored in the computer readable storage device.

5. The computer program product of claim 1, wherein the starting character and the ending character are adapted to designate a word, a phrase, a sentence, or a paragraph.

6. A computer implemented method for segmenting an email addressed to a plurality of original email recipients without the need to send separate emails comprising:

selecting a section of the email;
selecting a recipient for the section from the plurality of recipients;
responsive to selecting the recipient for the section, inserting a section information that identifies the recipient for the section and a starting and an ending character of the section into a header of the email;
sending the email to an email server, the email server comprising a processor and a memory;
at the email server, performing steps including: receiving the email; parsing the header for the section information; sending the email to the recipient for the section; sending the email without the section and the section information to the plurality of original recipients that have not been selected for receiving the section so that the plurality of original recipients cannot see that the section was removed;
wherein the section information is adapted to automatically prefix the section with an explanatory text to inform the section recipient that the section is being transmitted only to the section recipient, and wherein the explanatory text is adapted to be indented and colored.

7. The computer implemented method of claim 6 further including responsive to passing a cursor over the selected section of the email, displaying a window showing a recipient of the selected section.

8. The computer implemented method of claim 6, wherein selecting a section of the email is responsive to a user highlighting a portion of the email and right clicking on the highlighted portion.

9. The computer implemented method of claim 6 further including responsive to selecting the section of the email, displaying a window having the plurality of recipients for identifying the section recipient of the section.

10. The computer implemented method of claim 6, wherein the starting character and the ending character are adapted to designate a word, a phrase, a sentence, or a paragraph.

11. A data processing system comprising:

a bus;
a communications unit connected to the bus;
a computer readable storage device connected to the bus;
a processor unit connected to the bus and to a computer readable memory;
first program instructions for selecting a section of the email;
second program instructions for selecting a recipient for the section from the plurality of recipients;
third program instructions for responsive to selecting the recipient for the section, inserting a section information that identifies the recipient for the section and a starting and an ending character of the section into a header of the email;
fourth program instructions for sending the email to an email server, the email server comprising a processor and a memory;
fifth program instructions for receiving the email at the email server;
sixth program instructions for parsing, at the email server, the header for the section information;
seventh program instructions for sending, at the email server, the email to the recipient for the section; and
eighth program instructions for sending, at the email server, the email without the section and the section information to the plurality of original recipients that have not been selected for receiving the section so that the plurality of original recipients cannot see that the section was removed;
wherein the first through the eighth program instructions are stored in the computer readable storage device for running via the computer readable memory; and
wherein the section information is adapted to automatically prefix the section with an explanatory text to inform the section recipient that the section is being transmitted only to the section recipient, and wherein the explanatory text is adapted to be indented and colored.

12. The data processing system of claim 11 further comprising:

ninth program instructions for displaying, responsive to passing a cursor over the selected section of the email, a window showing a recipient of the selected section;
wherein the ninth program instructions are stored in the computer readable storage device for running via the computer readable memory.

13. The data processing system of claim 11, wherein selecting a section of the email is responsive to a user highlighting a portion of the email and right clicking on the highlighted portion.

14. The data processing system of claim 11 further comprising:

tenth program instructions for displaying, responsive to selecting the section of the email, a window having the plurality of recipients for identifying the section recipient of the section wherein the tenth program instructions are stored in the computer readable storage device for running via the computer readable memory.

15. The data processing system of claim 11, wherein the starting character and the ending character are adapted to designate a word, a phrase, a sentence, or a paragraph.

Referenced Cited
U.S. Patent Documents
5694616 December 2, 1997 Johnson et al.
5754778 May 19, 1998 Shoujima
5805830 September 8, 1998 Reese et al.
5864684 January 26, 1999 Nielsen
5878230 March 2, 1999 Weber et al.
5893914 April 13, 1999 Clapp
5995597 November 30, 1999 Woltz et al.
6044395 March 28, 2000 Costales et al.
6052709 April 18, 2000 Paul
6061698 May 9, 2000 Chadha et al.
6074772 June 13, 2000 Hofer et al.
6101532 August 8, 2000 Horibe et al.
6118856 September 12, 2000 Paarsmarkt et al.
6122632 September 19, 2000 Botts et al.
6163809 December 19, 2000 Buckley
6182059 January 30, 2001 Angotti et al.
6192396 February 20, 2001 Kohler
6205471 March 20, 2001 Gilchrist et al.
6246992 June 12, 2001 Brown
6247045 June 12, 2001 Shaw et al.
6275848 August 14, 2001 Arnold
6275850 August 14, 2001 Beyda et al.
6289372 September 11, 2001 Vyaznikov
6308179 October 23, 2001 Petersen et al.
6324569 November 27, 2001 Ogilvie et al.
6332156 December 18, 2001 Cho et al.
6370567 April 9, 2002 Ouchi
6389475 May 14, 2002 Speakman et al.
6393423 May 21, 2002 Goedken
6405243 June 11, 2002 Nielsen
6415290 July 2, 2002 Botts et al.
6424828 July 23, 2002 Collins et al.
6424996 July 23, 2002 Killcommons et al.
6427076 July 30, 2002 Skog
6446118 September 3, 2002 Gottlieb
6449635 September 10, 2002 Tilden, Jr. et al.
6453337 September 17, 2002 Miller et al.
6457045 September 24, 2002 Hanson et al.
6476930 November 5, 2002 Roberts et al.
6480711 November 12, 2002 Guedalia
6480885 November 12, 2002 Olivier
6484196 November 19, 2002 Maurille
6496849 December 17, 2002 Hanson et al.
6496853 December 17, 2002 Klein
6505233 January 7, 2003 Hanson et al.
6507865 January 14, 2003 Hanson et al.
6529942 March 4, 2003 Gilbert
6549957 April 15, 2003 Hanson et al.
6553425 April 22, 2003 Shah et al.
6563912 May 13, 2003 Dorfman et al.
6563913 May 13, 2003 Kaghazian
6574671 June 3, 2003 Haynes
6578025 June 10, 2003 Pollack et al.
6584564 June 24, 2003 Olkin et al.
6615241 September 2, 2003 Miller et al.
6643684 November 4, 2003 Malkin et al.
6668325 December 23, 2003 Collberg et al.
6687741 February 3, 2004 Ramaley et al.
6704772 March 9, 2004 Ahmed et al.
6705381 March 16, 2004 Huang
6721785 April 13, 2004 Raghunandan
6735741 May 11, 2004 Pannu
6745197 June 1, 2004 McDonald
6751453 June 15, 2004 Schemers et al.
6775689 August 10, 2004 Raghunandan
6789107 September 7, 2004 Bates et al.
6802067 October 5, 2004 Camp et al.
6816868 November 9, 2004 Shimizu
6820081 November 16, 2004 Kawai et al.
6823368 November 23, 2004 Ullmann et al.
6826596 November 30, 2004 Suzuki
6886030 April 26, 2005 Easterbrook et al.
6925605 August 2, 2005 Bates et al.
6970907 November 29, 2005 Ullmann et al.
6972861 December 6, 2005 van Zee et al.
6993573 January 31, 2006 Hunter
7039678 May 2, 2006 Halahmi et al.
7062536 June 13, 2006 Fellenstein et al.
7103634 September 5, 2006 Ullmann et al.
7107518 September 12, 2006 Ramaley et al.
7111046 September 19, 2006 Watanabe et al.
7130885 October 31, 2006 Chandra et al.
7130887 October 31, 2006 Goldberg
7136180 November 14, 2006 Utsunomiya
7136897 November 14, 2006 Raghunandan
7155481 December 26, 2006 Prahlad et al.
7219129 May 15, 2007 Weissman
7222156 May 22, 2007 Gupta et al.
7243125 July 10, 2007 Newman et al.
7257610 August 14, 2007 Lai et al.
7275214 September 25, 2007 Itoh
7305381 December 4, 2007 Poppink et al.
7305430 December 4, 2007 Choubey et al.
7305436 December 4, 2007 Willis
7328241 February 5, 2008 Ribak et al.
7363490 April 22, 2008 Paulsen et al.
7375835 May 20, 2008 Hull et al.
7383305 June 3, 2008 Kelley et al.
7596603 September 29, 2009 Chen et al.
7801960 September 21, 2010 Hockey
7844676 November 30, 2010 Prahlad et al.
7890593 February 15, 2011 Chen et al.
8131806 March 6, 2012 Chen et al.
8214444 July 3, 2012 Prahlad et al.
8631077 January 14, 2014 Chen et al.
20010047389 November 29, 2001 Prahlad et al.
20020019827 February 14, 2002 Shiman et al.
20020029247 March 7, 2002 Kawamoto
20020046250 April 18, 2002 Nassiri
20020052923 May 2, 2002 Anderson
20020097414 July 25, 2002 Utsunomiya
20020097850 July 25, 2002 Schemers et al.
20020099777 July 25, 2002 Gupta et al.
20020107930 August 8, 2002 Itoh
20020120702 August 29, 2002 Schiavone et al.
20020122411 September 5, 2002 Zimmerman et al.
20020138582 September 26, 2002 Chandra et al.
20020138586 September 26, 2002 Paleiov et al.
20020188683 December 12, 2002 Lyttle et al.
20020193986 December 19, 2002 Schirris
20030014490 January 16, 2003 Bates et al.
20030018731 January 23, 2003 Watanabe et al.
20030061111 March 27, 2003 Dutta et al.
20030070077 April 10, 2003 Redlich et al.
20030088704 May 8, 2003 Mertama et al.
20030093483 May 15, 2003 Allen et al.
20030097414 May 22, 2003 Cabello
20030101412 May 29, 2003 Eid
20030115271 June 19, 2003 Weissman
20030195933 October 16, 2003 Curren et al.
20030200272 October 23, 2003 Campise et al.
20030223554 December 4, 2003 Zhang
20030229900 December 11, 2003 Reisman
20040006599 January 8, 2004 Bates et al.
20040024810 February 5, 2004 Choubey et al.
20040034688 February 19, 2004 Dunn
20040064515 April 1, 2004 Hockey
20040068544 April 8, 2004 Malik et al.
20040073616 April 15, 2004 Fellenstein et al.
20040078452 April 22, 2004 Jamieson
20040139480 July 15, 2004 Delpuch et al.
20040141004 July 22, 2004 Cabezas et al.
20040221295 November 4, 2004 Kawai et al.
20040260756 December 23, 2004 Forstall et al.
20050021637 January 27, 2005 Cox
20050038804 February 17, 2005 Shimizu
20050039048 February 17, 2005 Tosey
20050060372 March 17, 2005 DeBettencourt et al.
20050080853 April 14, 2005 Kelley et al.
20050108351 May 19, 2005 Naick et al.
20050138109 June 23, 2005 Redlich et al.
20050138133 June 23, 2005 Voticky et al.
20050165740 July 28, 2005 Kerr et al.
20050223061 October 6, 2005 Auerbach et al.
20050267944 December 1, 2005 Little
20050278426 December 15, 2005 Blagg
20050289113 December 29, 2005 Bookstaff
20060020668 January 26, 2006 Chen et al.
20060031324 February 9, 2006 Chen et al.
20060041624 February 23, 2006 Lyle et al.
20060041625 February 23, 2006 Chen et al.
20060168044 July 27, 2006 Chen et al.
20070036301 February 15, 2007 Voticky et al.
20070110103 May 17, 2007 Zimmerman et al.
20070143431 June 21, 2007 Prahlad et al.
20070214216 September 13, 2007 Carrer et al.
20070300153 December 27, 2007 Newman et al.
20080281823 November 13, 2008 Chen et al.
20090012984 January 8, 2009 Ravid et al.
20090276732 November 5, 2009 Dervan
20090319506 December 24, 2009 Ngan
20100017408 January 21, 2010 Chen et al.
20100017481 January 21, 2010 Chen et al.
20100070584 March 18, 2010 Chen et al.
20100077323 March 25, 2010 Hunter
20100106788 April 29, 2010 Lynn et al.
20110072097 March 24, 2011 Prahlad et al.
Other references
  • “Selective Receipt of Document Elements in an Electronic Mail System”, International Business Machines Corporation, Kenneth Mason Publications Ltd., Jan. 2000, p. 1.
  • USPTO Final Office Action for U.S. Appl. No. 10/897,230 dated Jul. 9, 2009.
  • USPTO Office Action for U.S. Appl. No. 10/897,230 dated Dec. 8, 2008.
  • USPTO Final Office Action for U.S. Appl. No. 10/897,230 dated Jul. 2, 2008.
  • USPTO Final Office Action for U.S. Appl. No. 11/032,850 dated Dec. 1, 2008.
  • USPTO Office Action for U.S. Appl. No. 11/032,850 dated May 13, 2008.
  • USPTO office action for U.S. Appl. No. 10/922,249 dated Apr. 17, 2008.
  • USPTO final office action for U.S. Appl. No. 10/922,249 dated Sep. 17, 2008.
  • USPTO final office action for U.S. Appl. 10/922,249 dated Dec. 11, 2008.
  • USPTO notice of allowance for U.S. Appl. No. 10/922,249 dated Jun. 2, 2009.
  • USPTO notice of allowance for U.S. Appl. 11/032,850 dated Apr. 17, 2009.
  • “How to sort addresses by last name in Outlook Express,” Microsoft Outlook 2003, dated Jan. 29, 2007, 1 page. Accessed Jun. 20, 2007, http://support.microsoft.com/kb/282253/en-us.
  • “Sort a Range,” Microsoft Excel 2003, copyright 2007, 3 pages. Accessed Jun. 20, 2007, http://office.microsoft.com/en-us/excel/HP052029541033.aspx?pid=CH062527971033&mode=print.
  • “Sort your Inbox by using multiple columns”, Microsoft Outlook 2003, copyright 2007, 1 page. Accessed Jun. 20, 2007 from office.microsoft.com.
  • Notice of Allowance, dated Dec. 15, 2003, regarding U.S. Appl. No. 09/589,140 6 pages.
  • Office Action, dated Aug. 13, 2003, regarding U.S. Appl. No. 09/589,140 11 pages.
  • Notice of Allowance regarding U.S. Appl. No. 10/897,230, dated Sep. 5, 2013, 19 pages.
  • Notice of Allowance regarding U.S. Appl. No. 10/897,230, dated Oct. 2, 2012, 22 pages.
  • Office Action regarding U.S. Appl. No. 10/897,230, dated Feb. 1, 2008, 12 pages.
  • Office Action regarding U.S. Appl. No. 10/897,230, dated Dec. 18, 2008, 9 pages.
  • Notice of Allowance regarding U.S. Appl. No. 12/175,280, dated Oct. 4, 2010, 19 pages.
  • Office Action regarding U.S. Appl. No. 12/175,280, dated May 4, 2010, 8 pages
  • Final Office Action regarding U.S. Appl. No. 12/177,283, dated Oct. 4, 2011, 32 pages.
  • Office Action regarding U.S. Appl. No. 12/177,283, dated Apr. 12, 2011, 37 pages.
  • Final Office Action regarding U.S. Appl. No. 12/175,300, dated Dec. 28, 2010, 34 pages.
  • Notice of Allowance regarding U.S. Appl. No. 12/175,300, dated May 3, 2011, 11 pages.
  • Notice of Allowance regarding U.S. Appl. No. 12/175,300, dated Oct. 28, 2011, 12 pages.
  • Office Action regarding U.S. Appl. No. 12/175,300, dated Jul. 2, 2010, 20 pages.
  • Final Office Action, dated Oct. 1, 2010, regarding U.S. Appl. No. 12/209,573, 14 pages.
  • Final Office Action, dated Nov. 25, 2011, regarding U.S. Appl. No. 12/209,573, 13 pages.
  • Office Action, dated Jun. 15, 2010, regarding U.S. Appl. No. 12/209,573, 12 pages.
  • Office Action, dated Jun. 22, 2011, regarding U.S. Appl. No. 12/209,573, 14 pages.
  • Final Office Action regarding U.S. Appl. No. 10/880,729, dated Dec. 10, 2008, 16 pages.
  • Notice of Allowance regarding U.S. Appl. No. 10/880,729, dated May 21, 2009, 16 pages.
  • Office Action regarding U.S. Appl. No. 10/880,729, dated Jul. 18, 2008, 14 pages.
  • Notice of Allowance, dated Feb. 9, 2004, regarding U.S. Appl. No. 09/588,951, 9 pages.
  • Office Action, dated Aug. 21, 2003, regarding U.S. Appl. No. 09/588,951, 13 pages.
  • Jackman, “Use These Five Tips to Control How Outlook 2003 Displays E-Mail”, Sep. 22, 2004, 6 pages. http://www.techrepublic.com/article/use-these-five-tips-to-help-control-how-outlook-2003-displays-e-mail/5287013.
  • Courter et al., “Getting the Most Out of Outlook: Rules, Calendars, Views,” TRIAD Consulting, 2003 IAAP International Convention, Jul. 2003, 9 pages. http://www.triadconsulting.com/events/IAAP/2003—Convention/.
Patent History
Patent number: RE45184
Type: Grant
Filed: Feb 14, 2013
Date of Patent: Oct 7, 2014
Assignee: International Business Machines Corporation (Armonk, NY)
Inventors: Yen-Fu Chen (Austin, TX), John Hans Handy-Bosma (Cedar Park, TX), Mei Yang Selvage (Austin, TX), Keith Raymond Walker (Austin, TX)
Primary Examiner: Wing F Chan
Assistant Examiner: Benjamin M Thieu
Application Number: 13/767,476
Classifications
Current U.S. Class: Demand Based Messaging (709/206); Priority Based Messaging (709/207); Computer-to-computer Data Modifying (709/246)
International Classification: G06F 15/16 (20060101);