System and method for increasing email productivity

Description

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of patent application Ser. No. 09/602,588 filed on Jun. 21, 2000, by the same title and inventor.

This application is a continuation-in-part of U.S. patent application Ser. No. 10/112,230, entitled “System and Method for Determining a Set of Attributes Based on Content of Communications,” filed Mar. 27, 2002. This application is also related to U.S. patent application Ser. No. 09/754,179, entitled “System and Method for Electronic Communication Management,” filed Jan. 3, 2001. The subject matter of the related applications is hereby incorporated by reference. The related applications are commonly assigned.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to electronic mail (email) and relates more particularly to a system and method for increasing email productivity.

2. Description of the Background Art

Electronic mail (email) has become an important tool for both business and personal communication, and its use will likely become even more critical in the future. Many professionals spend a good part of their workday reading and drafting email messages for various purposes. High-volume email users, for example professionals with publicly-available email addresses, may receive hundreds of email messages a day, and can spend several hours each day dealing with them. The sheer volume of received email messages challenges the productivity of any professional.

Email users often receive junkman, also known as unsolicited commercial email or spam. Most users are not interested in such messages and routinely delete them unread. However, some junkman messages are not easily identified as such from the sender or the subject line, and a user may waste time opening and reading a message only to discover that it is unwanted junkman. Email users also often receive personal messages such as jokes, invitations, and notes from friends. Some users may consider these types of messages as junkman, while others enjoy sending and receiving such messages.

For most business users, the bulk of received email messages are work-related, some of which have a higher priority than others. For example, an email message from a key customer is likely to be of a higher priority than a message from a co-worker. Also, a message from a user's supervisor is likely to be of a higher priority than a message that is a reminder of a regularly scheduled meeting. In addition, messages regarding certain topics may be regarded as having a higher priority than messages regarding a different topic. Each user may have a different determination of which messages have a higher priority, and this determination of priority may change over time.

SUMMARY OF THE INVENTION

An email productivity module interacts with an existing email application to perform a variety of functions, such as prioritizing and sorting email messages and filtering junk email messages. The email productivity module performs these functions and others by first analyzing the content of each message using a content analysis engine that implements natural language text classification techniques. Performance of the email productivity module is maintained and/or improves over time by learning from feedback generated by a user's actions taken in connection with email messages. Feedback may be utilized to adapt one or more knowledge bases, which may be stored locally or at another computing device located on a computer network. A knowledge base is a collection of information used by the system to analyze and classify messages. The knowledge base may include any combination of statistical information about messages, domain or language in general, as well as rules, lexicons, thesauri, anthologies and other natural language processing elements known in the art. The knowledge base may additionally include thresholds, likelihood tables, and other information used to classify a message.

The content analysis engine analyzes the content of the message. A prioritization module assigns a priority score and a priority label to the message based on its content. In one embodiment, the priority score is a whole number from 0 to 100, and the priority label is a designation such as high, medium, or low. The user provides feedback to the email productivity module by either accepting the prioritization assigned to the message, changing the priority label (e.g., changing a low priority message to high), or providing feedback by some other means to establish the priority of a selected message. The email productivity module may also infer information about the priority of the message from the actions of the user (implicit feedback).

In connection with the prioritization function, the email productivity module may advantageously provide a mechanism for filtering low-priority (but otherwise legitimate) email messages having content that is relatively unimportant to the recipient and which does not require a response therefrom. These low-priority e-mail messages, which are known colloquially in the art as “occupational spam,” may consist of enterprise-wide announcements, reminders, status reports, and the like, and may constitute a significant portion of the total number of emails received by employees, particularly high-level executives. However, existing junkmail filtering software is not capable of detecting and filtering occupational spam, and so a user may spend a substantial amount of time reading through such messages and taking appropriate action, such as deleting the messages or moving them to a folder for later review. Embodiments of the present invention address this deficiency by generating a priority score for each message, and then executing a predetermined action, such as deleting the message or moving it to a specified folder, if the priority score falls below a predetermined threshold representative of occupational junkmail having little importance and/or urgency to the user.

The sorting function determines a set of suggested folders for storing incoming messages. For each incoming message, the content analysis engine analyzes the content of the message. A message sorting module determines a confidence score for the message based on content for each available folder and lists the top scoring folders in descending order. The user provides feedback to the email productivity module by moving the message into a folder, or by other means of explicit or implicit feedback. In one embodiment, the user may enable the email productivity module to automatically move a message into a folder, for example if the message score for that folder exceeds a threshold.

The junkman identifying function determines whether a message qualifies as junkmail (also known as unsolicited commercial email or spam). The content analysis engine analyzes the content of each incoming message and a junkmail module determines a junkmail score based on the content of the message. The user provides feedback by moving the message to a junkmail folder, which provides positive feedback, or moving the message to a folder not associated with junkmail, which provides negative feedback. The user may also provide explicit feedback to the email productivity module by manually indicating that the message is junkmail or non-junkmail, for example by a keystroke or by clicking on a button. In one embodiment, the user may enable the email productivity module to automatically move a message into the junkmail folder or delete the message if that message's junkman score exceeds a threshold.

The email productivity module may modify the user interface of the email application. The inbox view includes additional fields to show the prioritization score, prioritization level, and junkmail score. In one embodiment, the user interface also includes a toolbar with buttons related to the functions of the email productivity tool. For example, the toolbar includes a junkman button for identifying a message as junkmail, a number of buttons for assigning a priority level to a message, and a drop down list of suggested folders.

The email productivity module may also provide an intelligent search function that allows a user to select one or more messages and search stored messages in every folder to find messages with similar content (“search by example”).

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one embodiment of an electronic communications network, according to the invention;

FIG. 2 is a block diagram of one embodiment of the email productivity module of FIG. 1, according to the invention;

FIG. 3 is a block diagram of one embodiment of the email productivity server of FIG. 1, according to the invention;

FIG. 4 is a diagram of one embodiment of an explorer window of the email application of FIG. 1, according to the invention;

FIG. 5 is a diagram of one embodiment of the message window of FIG. 4, according to the invention; and

FIG. 6 is a flowchart of method steps for processing a received email message according to one embodiment of the invention.

DETAILED DESCRIPTION OF THE INVENTION

FIG. 1 is a symbolic diagram of an implementation of one embodiment of the invention in a networked computing environment 100. A computing device 120 communicates over a network 110 with other computing devices, such as client computer 114. Network 110 may be any appropriate type of network or combination of networks, for example a local area network (LAN), a wide area network (WAN), a wireless network, a home network, the public switched telephone (PSTN), or the public Internet. Computing device 120 may take the form of any suitable device capable of sending an receiving email message, for example a desktop computer, a laptop computer, a set-top box, a handheld computing device, a handheld messaging device, a mobile telephone, or a dedicated email appliance. In a typical network environment, computing device 120 received and sends email messages via at least one email server 117, which performs a standard set of store-and-forward, addressing and routing functions. Computing device 120 may also communicate with an email productivity server 118 to effect various productivity functions, as is described in further detail below.

Computing device 120 is provided with storage and a processor for storing and executing an email application 122 having an email productivity add-in 124, and an email productivity module 126. Email application 122 may be, for example, a widely utilized commercial application such as Microsoft Outlook®. Email productivity add-in 124 and email productivity module 126 cooperate to process incoming email messages before the messages are displayed by email application 122. More specifically, email productivity module 126 analyzes the content of incoming email messages and accordingly generates a set of scores and other attributes characterizing the content. Email productivity add-in 124 adds fields containing these scores and attributes to the message so that they may be displayed to the user by email application 122, or so that the presentation of incoming email messages in the user interface may be modified in accordance with the associated scores and attributes. Email productivity add-in 124 may also modify the user interface of email application 122 to allow a user to access functions of email productivity module 126. The contents and functionalities of email productivity module 126 are further discussed in conjunction with FIG. 2.

FIG. 2 is a block diagram of one embodiment of the email productivity module 126 of FIG. 1. Email productivity module 126 includes, but is not limited to, a content analysis engine 212, a prioritization module 214, a message sorting module 216, and a junkmail module 218. Prioritization module 214 has an associated prioritization knowledge base 224, message sorting module 216 has an associated sorting knowledge base 226, and junkmail module 218 has an associated junkman knowledge base 228. It should be noted that the architecture depicted by FIG. 2, in which the functions of productivity module 126 are distributed among four separate and distinct component structures, is provided by way of example only, and that the productivity module may instead be implemented having a greater or lesser number of component structures.

Content analysis engine 212 analyzes the content of the message using language processing techniques to produce content information representative of the content of the email message. The content information may include, without limitation, scoring vectors or matrices indicative of the presence, absence, or incidence of concepts or terms in the message, or of the source and/or recipients of the email message. As used herein, the “content” of the message is intended to include without limitation all lexical and syntactical information in the body of the message, any attachments, and in all message headers such as sender, recipient, reply-to address, carbon copy (cc), subject, date, and time.

Prioritization module 214 is configured to generate priority information for email messages received or stored by computing device 120. More specifically, prioritization module 214 operates in conjunction with content analysis engine 212 to assign a priority score and a priority level to email messages. Content analysis engine 212 and prioritization module 214 apply the content information to prioritization knowledge base 224 to determine a priority score for the message. Prioritization module 214 then assigns a priority level to the email message based on the priority score. In an illustrative implementation, priority scores are whole numbers in a range of 0-100, and available priority levels are low, medium, and high. Scores 0-29 correspond to the low level, scores 30-70 correspond to the medium level, and scores 71-100 correspond to the high level. Other ranges of priority scores and other priority levels are within the scope of the invention. Additionally and/or alternatively, priority scores generated by the prioritization module may take the form of vectors, matrices, sets, or other data structures, wherein the universe of possible priority scores includes at least three different values or states.

Prioritization knowledge base 224 is a collection of information used by email productivity module 126 to make determinations regarding the priority of email messages. Prioritization knowledge base 224 may include any combination of statistical information about messages, domain or language in general, as well as rules, lexicons, thesauri, anthologies, and other natural language processing elements well known in the art. Prioritization knowledge base 224 may also include thresholds, likelihood tables, and any other information used to classify a message. Thresholds may be designated by the user, predetermined by the designers of email productivity module 126, or automatically adjusted by email productivity module 126. In one embodiment, prioritization knowledge base 224 stores prioritization information as models arranged in a branch structure, wherein each branch is a model corresponding to a priority level, e.g. the knowledge base may include a first model for high priority messages, a second model for medium priority messages, and a third model for low-priority messages. Prioritization module 214 applies the content information of a received message to each of the models in prioritization knowledge base 224 to determine the priority score, which reflects the relative priority of the message. Each model in prioritization module 214 may have the same threshold or each model may have a uniquely assigned threshold.

It should be noted that the inclusion in the present invention of the prioritization module and its attendant functionality advantageously enables users to identify legitimate but low-priority email messages (which would not be filtered or otherwise flagged by conventional spam filtering software), and to take appropriate action with respect to the low-priority messages, such as deleting them or storing them in a folder for subsequent review at a convenient time. These legitimate but low-priority email messages, which have been referred to as “occupational spam”, may take the form of enterprise-wide announcements, reminders, status reports, and the like, and may constitute a significant portion of the total number of emails received by employees, particularly high-level executives.

Message sorting module 216 operates in conjunction with content analysis engine 212 to determine a set of suggested folders for a message. The set of suggested folders represent one or more folders in which are stored other emails having similar content, and in which the user would be most likely store the message. Content analysis engine 212 applies the content information of the message to sorting knowledge base 226 to determine the set of suggested folders for the message. Sorting knowledge base 226 is a collection of information used by email productivity module 126 to analyze and classify messages. Sorting knowledge base 226 may include any combination of statistical information about messages, domain or language in general, as well as rules, lexicons, thesauri, anthologies, and other natural language processing elements well known in the art. Sorting knowledge base 226 may also include thresholds, likelihood tables, and any other information used to classify a message. Thresholds may be designated by the user, predetermined by the designers of email productivity module 126, or automatically adjusted by email productivity module 126. In one embodiment, sorting knowledge base 226 is organized in a branched structure and includes on each branch a model corresponding to a folder in email application 122 or other class characterizing the content of email messages. Message sorting module 216 generates a score in connection with each model in sorting knowledge base 226, the score being representative of the likelihood that the email should be classified in the folder to which the model corresponds. Message sorting module 216 then identifies a set of suggested folders. In one embodiment, the set of suggested folders includes the top ten highest scoring folders. Each model in sorting knowledge base 226 may have the same threshold or each model may have a uniquely assigned threshold.

Junkmail module 218 operates in conjunction with content analysis engine 212 to determine a junkmail score for each message. Content analysis engine 212 applies the content information of the message to junkmail knowledge base 228. Junkman knowledge base 228 is a collection of information used by email productivity module 126 to analyze and classify messages. Junkmail knowledge base 228 may include any combination of statistical information about messages, domain or language in general, as well as rules, lexicons, thesauri, anthologies, and other natural language processing elements well known in the art. Junkman knowledge base 228 may also include thresholds, likelihood tables, and any other information used to classify a message. Thresholds may be designated by the user, predetermined by the designers of email productivity module 126, or automatically adjusted by email productivity module 126. In one embodiment, junkman knowledge base 228 is organized into a branched structure and includes on one branch a junk model and at the other a not junk model. The score generated when the content information is applied to the junk model is the junkmail score for the message. In one embodiment, the junkmail score is a whole number in a range of 0-100. The higher the junkman score, the higher the probability that the message is junkmail according to the criteria in junkmail knowledge base 228. Each model in junkmail knowledge base 228 may have the same threshold or each model may have a uniquely assigned threshold.

Prioritization module 214, message sorting module 216, and junkmail module 218 supply the priority score and priority level, the set of suggested folders, and the junkmail score, respectively, to email productivity add-in 124. Email productivity add-in 124 attaches fields for the priority score, priority level, set of suggested folders, and junkmail score to the message for display by email application 122. The user interface of email application 122 modified by email productivity add-in 124 is discussed below in conjunction with FIGS. 4 & 5.

Prioritization knowledge base 224, sorting knowledge base 226, and junkmail knowledge base 228 are updated by feedback from user input to email application 122. Email productivity add-in 124 monitors user inputs to email application 122 and reports these inputs as feedback to email productivity module 126. Prioritization module 214 may update prioritization knowledge base 224 using both explicit and implicit feedback. In other words, the terms “feedback” and “user action” are not limited to affirmative actions taken by the user, but rather extend to actions wherein the user accepts the result produced by the productivity module and/or refrains from modifying the result. The user may provide explicit feedback, for example, by changing a priority level that has been assigned to a message. For example, if a message has been assigned a priority level of low and the user feels that the message has a higher priority, then the user can assign a new priority level to the message, such as high. When the user assigns a new priority level to a message, prioritization module 214 assigns the message a priority score in the range of scores for that priority level. In one embodiment, prioritization module 214 assigns a score in the middle of the range of possible scores for the priority level assigned by the user. If the user does not provide explicit priority feedback for a message and does not delete the message but instead takes another action with respect to the email, implicit feedback may be provided to prioritization knowledge base 224. If the user reads or otherwise deals with messages in order of the relative priority scores, this action provides positive feedback to prioritization knowledge base 224. If the user reads messages in an order other than in descending order of priority score, this user action may provide negative feedback to prioritization knowledge base 224. Thus, prioritization knowledge base 224 is updated with feedback for every message received by email application 122. Updating of the prioritization knowledge base may be effected, for example, by adapting the models corresponding to each priority level in accordance with the feedback generated by user action. The feedback is preferably supplied to the prioritization module immediately after the relevant user action is taken to allow real-time adaptation of the models, thereby improving the accuracy and reliability of the prioritization function.

Message sorting module 216 updates sorting knowledge base 226 using feedback generated by user action, for example moving the received message to a selected folder for storage. When the user moves a message to a folder, email productivity add-in 124 provides explicit feedback to message sorting module 216. The user can move the message to one of the set of suggested folders or to any other folder, or create a new folder. When the user creates a new folder in email application 122, message sorting module 216 creates a new model in sorting knowledge base 226. Email productivity module 126 preferably learns in real time how the user prefers to store messages by updating sorting knowledge base 226 with feedback for each message moved into a folder.

Categories may be used to search for or locate messages, whether or not used in conjunction with a keyword search engine. In one embodiment, message sorting module 216 operates in conjunction with a category function native to email application 122. If the category function is enabled, a category is created for each folder of email application 122 and the user designates a category threshold. If a message receives one or more folder scores that exceeds the category threshold, then message sorting module 216 assigns the categories for these folders to the message. Although a message is stored in only one folder, the message may be assigned a plurality of categories. The user is then able to locate messages by category. Other implementations of a category function are within the scope of the invention, for example a category function in which the category names do not correspond to a folder of email application 122.

In one embodiment, message sorting module 216 includes an automove function that, when enabled by the user, will automatically move a received message to the highest scoring folder when the score for that folder exceeds a user-designated threshold value. For example, if message sorting module 216 determines a highest scoring folder with a score that exceeds the threshold for a received message, message sorting module 216 will notify email productivity add-in 124 to cause email application 122 to move the received message directly to the highest scoring folder instead of the inbox. When a message has been automoved to a folder, email productivity add-in 124 may provide implicit feedback to message sorting module 216 if the user reads the message and does not move it to another folder. If the user does move the message to a different folder, email productivity add-in 124 provides explicit feedback to message sorting module 216.

Junkmail module 218 updates junkmail knowledge base 228 using explicit and implicit feedback generated by user actions. The user provides explicit feedback to junkman module 218, for example, by taking an action indicating that a message is junkmail, for example by moving it to a junkmail folder. If the user reads a message and does not delete it or indicate that it is junkmail, junkmail module 218 receives implicit feedback that the message is not junkmail. If the user moves a message out of the junkman folder, junkman module 218 receives implicit feedback that the message is not junkmail. If the user deletes a message from the junkmail folder, junkman module 218 receives implicit feedback that the message is junkmail. In one embodiment, junkmail module 218 has an automove function that, when enabled by the user, will automatically move a received message to a junkman folder if the junkmail score for that message exceeds a user-designated threshold. Email productivity module 126 learns in real-time the user's criteria for junkmail by updating junkmail knowledge base 228 with feedback for each received message.

In one embodiment, junkmail knowledge base 228 may be updated using information provided from an external source. For example, an email service provider could implement a service whereby it generates rules and other information for filtering junkmail messages. Junkmail module 218 may, upon receipt of such rules and other information (which may supplied, for example, through network 110), update junkmail knowledge base 228 in accordance with the received information.

In one embodiment, email productivity module 126 includes an intelligent search function. The user may select a message, and instruct email productivity module 126 to find other similar messages. Content analysis engine 212 analyzes the selected message to identify concepts of the message, and then analyzes stored messages in all folders to identify similar messages.

In one embodiment, email productivity module 126 includes a folder management function. When enabled by the user, email productivity module 126 will analyze the content of previously stored messages in each folder and identify messages that may not belong in a particular folder according to the information in sorting knowledge base 226. The user may then decide to move such an identified message to a folder suggested by email productivity module 126, move the message to some other folder, or not move the message. Each of these actions provides feedback to message sorting module 216 and sorting knowledge base 226. The folder management function may also suggest to the user that certain folders be combined into a single folder, or a single folder be split up into multiple folders.

In one embodiment, email application 122 may forward copies of email messages to a wireless device. Email productivity module 126 can enhance this function by selectively forwarding copies of messages to a wireless device based on analysis of content. For example, the user may designate that messages that have a priority level of high should be forwarded to a wireless device. In another example, the user may designate that only messages that are automoved to a certain folder are to be copied to a wireless device. Email productivity module 126 can also enhance other functions of email application 122, for example a text-to-voice function that only converts messages having a high priority level to voice.

Email productivity module 126 may perform other automatic operations based on results generated by content analysis engine 212 and other components of the email productivity module. Such other automatic operations may include auto-forward to another email address, notification to the user that a message from a particular address has been received, automatically using a web browser to open an embedded hyperlink, or automatically opening an attachment.

It is noted that although the embodiment of the invention described and depicted herein includes prioritization, sorting, and junkmail filtering functions, this embodiment is intended as illustrative rather than limiting, and other embodiments within the scope of the invention may include a subset or superset of these functions.

FIG. 3 is a block diagram of one embodiment of the email productivity server 118 of FIG. 1, according to the invention. Email productivity server 118 includes, but is not limited to, a content analysis engine 312, client knowledge bases 314, and a backup and synchronization module 316. In the FIG. 3 embodiment of email productivity server 118, content analysis engine 312 performs the functions of content analysis engine 212 (FIG. 2) for clients that do not have content analysis engine 212 (i.e., for “thin clients” having limited storage and/or data processing capabilities). Client knowledge bases 314 include a prioritization knowledge base, a sorting knowledge base, and a junkmail knowledge base for each client in network 100 that does not have resident knowledge bases. It will be appreciated that two or more clients may share a common set of knowledge bases, or alternatively the productivity server 118 may store a separate knowledge base for each client. In another embodiment, client knowledge bases 314 includes a global junkman knowledge base that includes information adapted in accordance with the information in the clients' junkmail knowledge bases 228. This architecture allows feedback regarding junkmail to be utilized by each client in network 100, thereby improving filtering accuracy for all clients.

Backup and synchronization module 316 is configured to copy the clients' knowledge bases as a backup in case of failure at one of the clients in network 100. Backup and synchronization module 316 is also configured to synchronize the information in the clients' junkmail knowledge bases 228. Backup and synchronization module 316 may also manage licensing of email productivity module 216 and email productivity add-in 214 on clients 120. Backup and synchronization module 316 may also synchronize the knowledge bases for users that use multiple instances of email application 122.

FIG. 4 is a diagram of one embodiment of an explorer window 400 of the user interface of email application 122 of FIG. 1, according to an embodiment of the invention. Window 400 includes, but is not limited to, a window toolbar 410, an email toolbar 420, a productivity toolbar 430, a folder list 450, and a message window 460. Window toolbar 410 includes a file menu button 412, an edit menu button 414, and a view menu button 416. Window toolbar 410 may include any other appropriate menu buttons. Email toolbar 420 includes a new button 422 configured to open a new blank message, a reply button 424 configured to open a reply message, and a forward button 426 configured to open a forward message window. Email toolbar 420 may include any other appropriate buttons.

Productivity toolbar 430 includes buttons that allow the user to provide input to email productivity module 126. Productivity toolbar 430 includes, but is not limited to, a folder pull-down menu 432, a move button 436, a productivity module (PM) button 438, a junkmail button 440, a high button 442, a medium (med) button 444, a low button 446, and a score button 448. A window of folder pull-down menu 432 displays a highest scoring folder for a selected message in message window 460. The user can actuate an arrow button 434 to view the rest of the set of suggested folders and a “select a folder” choice (to select a folder that doesn't appear in the set of suggested folders). Folder pull-down menu 432 shows the folder name and score for each suggested folder. Actuating move button 426 moves the selected message to the folder currently selected in folder pull-down menu 432.

Actuating junkmail button 440 provides explicit feedback to junkman module 218 that the selected message in message window 460 is junkman. In one embodiment, actuating junkmail button 440 also moves the selected message to the junkmail folder or deletes the selected message. Actuating high button 442, medium button 444, or low button 446 provides explicit feedback to prioritization module 212 regarding the priority of the selected message in message window 460. Actuating score button 448 causes email productivity module 126 to score (or re-score) a selected message or messages in message window 460. In response to input from score button 448, the selected message or messages will be scored by prioritization module 214, message sorting module 216, and junkmail module 218.

Actuating productivity module 438 button opens a productivity module window (not shown) that allows the user to modify certain aspects of email productivity module 126. A message sorting tab allows the user to enable or disable an automove function for message sorting module 216, designate a sorting score threshold, enable or disable categories, designate a category threshold, and select a base folder. A junkmail tab allows the user to enable or disable an automove function for junkmail module 218 and designate a junkmail score threshold. The productivity module window may also include a help button that provides access to help regarding the functions of email productivity module 126.

Folder list 450 includes, but is not limited to, an inbox folder 452, a plurality of folders 454, a junkmail folder 456, and a deleted items folder 458. The user can select any of these folders to view the messages in that folder in message window 460. The user can move a message to a folder in folder list 450 by dragging and dropping the message from message window 460 to the folder in folder list 450. As discussed above, moving a message into a folder in folder list 450 provides feedback to message sorting module 216, and moving a message into junkmail folder 456 provides feedback to junkmail module 218.

FIG. 5 is a diagram of one embodiment of message window 460 of FIG. 4. Message window 460 displays messages for a selected folder. In the FIG. 5 example, message window 460 displays messages in the inbox of email application 122. Message window 460 includes four messages 532, 534, 536, and 538. Message window 460 further includes a junkmail column 512, a priority score column 514, a priority level column 516, “a from” column 518, a subject column 520, and a received column 522. Other embodiments of message window 460 may contain additional columns.

Junkmail column 512 shows a junkmail score for each message as determined by junkman module 218. Priority score column 514 shows a priority score for each message and priority level column 516 shows a priority level for each message as determined by prioritization module 214. Message 532 is the currently selected message. The set of suggested folders for message 532 determined by message sorting module 216 is shown in folder pull-down menu 432 (FIG. 4).

It is noted that different and/or additional visual indications be employed to represent the junkmail score, priority score, and priority levels of listed email messages. For example, messages having a high priority score and level may be presented in a brightly colored font or other manner that draws the user's attention, whereas messages assigned a low priority score can be presented in a duller font. In addition, the message window may be configured to sort the messages in order of priority score or other user-selected field such that messages having relatively greater importance to the user are grouped together above and apart from messages having relatively lesser importance.

FIG. 6 is a flowchart of method steps for processing a received email message according to one embodiment of the invention. Although the steps of FIG. 6 are discussed in the context of email productivity module 126 and email productivity add-in 124, any other means configured to perform the steps are within the scope of the invention. In step 610, email productivity module 126 receives an email message. In step 612, content analysis engine 212 analyzes the content of the message using language processing techniques. Then, in step 614, prioritization module 214 applies the content information to prioritization knowledge base 224, producing a priority score and a priority level. At about the same time, in step 616, message sorting module 216 applies the content information to sorting knowledge base 226, producing a set of suggested folders. At about the same time, in step 618, junkman module 218 applies the content information to junkman knowledge base 228, producing a junkman score for the message.

Then, in step 620, email productivity module 126 determines whether a folder automove function is currently enabled. If the folder automove function is not enabled, the method continues with step 622. If the folder automove function is enabled, then in step 626 email productivity module 126 determines whether the score of the highest scoring folder of the set of suggested folders exceeds the designated threshold. If the score of the highest scoring folder does not exceed the designated threshold, then the method continues with step 622. If the score of the highest scoring folder exceeds the designated threshold, then in step 632, email productivity add-in 124 adds the priority score, priority level, set of suggested folders, and junkmail score fields to the message. Then, in step 638, email productivity add-in 124 sends the message to the highest scoring folder of email application 122.

In step 622, email productivity module 126 determines whether a junkmail automove function is enabled. If the junkman automove function is enabled, the method continues with step 624. If the junkmail automove function is not enabled, then in step 628 email productivity add-in 124 adds the priority score, priority level, set of suggested folders, and junkmail score fields to the message. In step 634, email productivity add-in 124 sends the message to the base folder, such as the inbox, of email application 122.

In step 624, email productivity module 126 determines whether the junkmail score for the message exceeds the designated threshold. If the junkmail score does not exceed the designated threshold, then the method continues with step 628, discussed above. If the junkman score exceeds the designated threshold, then in step 630 email productivity add-in 124 adds the priority score, priority level, set of suggested folders, and junkmail score fields to the message. In step 636 email productivity add-in 124 sends the message to the junkmail folder of email application 122.

It is noted that the steps set forth above are preferably performed automatically upon receipt of each incoming email. However, in other embodiments and implementations, the foregoing steps or portions thereof may be performed only on selected messages, at specified intervals, or responsively to a user request.

The invention has been described above with reference to specific embodiments. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The foregoing description and drawings are, accordingly, to be regarded in an illustrative rather than a restrictive sense.