Displaying list of file attachments associated with message thread. RU patent 2510525.

FIELD: information technology.

SUBSTANCE: method involves identifying one or more messages associated with a message thread; identifying one or more file attachments attached to the one or more messages; after identifying said one or more file attachments, identifying respective root files related to the one or more file attachments by comparing content of said one or more file attachments with content of said respective root files; generating an aggregated attachment list to include respective list entries for the one or more file attachments and identified root files; wherein the list entries respectively comprise a file-type icon, one or more file names, a file size and identification data of an author related to the root files of the file attachment, having the highest version level, and indication of the file attachment, having the highest version level; displaying the aggregated attachment list in a window of an email application.

EFFECT: shorter time for accessing email file attachments.

16 cl, 6 dwg

Background of the invention

When designing reports, presentations and other documents often involves collaboration between multiple remote individuals within the organization or group. However, even in corporate environments, where you have access to software ensuring collaboration and other technologies to share files, individuals collaboration often use e-mail, using file attachments for sharing documents with each other or to distribute versions of documents for viewing and edit.

For example, one person can send the original e-mail message containing an attached document, several individuals in the organization. Each of these individuals can, in turn, edit these documents, often renaming a document in such a way as to reflect the changes that were made. The revised document should then be returned to the sender in the response message or sent to other individuals in the organization. Messages sent back and forth in response to the original message that together make up the flow of the message or communication session. Message flow can eventually to include multiple file attachments that represent different versions of the original document, referred to here as the root file.

Users who access their e-mail through the e-mail application can be provided with a mechanism to review all messages associated with the flow of messages, or sorted by date, or in a hierarchical display, showing the passage of messages among individuals, affecting the flow of the messages. Display messages associated with the flow of messages can also provide an indication of the messages that include a file attachment.

However, currently there is no easy way to gather together all of the different file attachments that were added or modified by individuals Sodeistviye in the flow of the message or communication session. The user e-mail in a typical case, manually makes the access to each message with an attachment, to identify the root of files associated with the flow of messages. In addition, users typically manually define the most recent version of each root file by viewing varying names and date of last change for every file attachments that are related to the root file.

We present here the disclosure addressed above and related considerations.

Disclosure of the invention

In this application are disclosed technology to display a list of file attachments associated with the flow of messages in an email application. The messages that are associated with the flow of messages that are identified along with file attachments to these messages. Formed mixed list of attachments containing an entry for each file attachments associated with the flow of messages. Mixed list of attachments associated with the stream of messages is then displayed in the application e-mail.

It should be understood that the present invention, the essence of which is briefly described above may be implemented as a computer-controlled devices, computer process, computer system, or industrial products, such as machine-readable medium. These and other signs clearly follow from reading the following is a detailed description of the invention and review the attached drawings.

This is a brief description of the invention provided for the presentation of the compilation of concepts in a simplified form, which are further outlined below, detailed description of the invention. This summary of the invention is not implied neither determining key characteristics or essential features of the claimed invention, nor used to limit the scope of the claimed invention. Moreover, the claimed invention is not limited to the implementations, which eliminates any or all of the weaknesses observed in any part of this disclosure.

List of figures

Figure 1 - block diagram showing the illustrative aspects of working environment and of some software provided here, options implementation;

Figure 2-3 - screen graph that shows illustrative user interfaces to display a list of file attachments associated with the flow of messages, as described here variants of implementation;

Figure 4 - logic diagram showing how to display the list of file attachments associated with the flow of messages, as provided for in the options described here realization;

5 is a logical diagram showing the ways of identification of root files related to the file attachments associated with the flow of messages, as provided for in the options described here realization;

6 is a block diagram showing illustrative computer architecture hardware and software for computer systems, made with the possibility of realization of the aspects presented here variants of implementation.

Detailed description of the invention

The following detailed description focused on technology to display precast list of attachments in the e-mail application, which contains the list of file attachments associated with the flow of the message or communication session. Mixed list of attachments allows the user to view and interact with all file attachments or root files associated with the flow of messages in one place. Providing modular attachment list eliminates the need to manually access by a user to each message in the message flow for the identification of root files associated with the flow of messages. Also the user is no longer required to manually define the most recent version of each root file by viewing varying names and date of last change for every file attachments that are related to the root file.

Although the described invention presented in the General the context of software modules, which are executed in conjunction with the execution of the operating system and application programs in a computer system, specialists will be clear that other implementations may be implemented in combination with other types of software modules. In General, software modules include procedures, programs, components, data structures and other types of structures that perform specific tasks or implement specific abstract data types. Moreover, specialists must be clear that the described invention can be implemented with different configurations of computer systems, including handheld devices, microprocessor systems based on microprocessors, or programmable consumer electronics, minicomputers, universal computers (mainframes), etc.

The following detailed description, refer to accompanying drawings, which form part of it, and by illustrations show the specific ways of implementation or examples. Further, with reference to the drawings, in which the same reference numbers indicate similar elements on several drawings will be presented aspects of the method to display a list of file attachments associated with the flow of messages.

Now, referring to Figure 1, will be provided details regarding illustrative working environment and of some software provided here, options implementation. Figure 1 shows illustrative system 100 to display precast list of attachments in the e-mail application. System 100 includes a workstation 102, which is connected to the display 104, which allows the workstation to display a user interface (UI) for the user 106. It should be understood that the user can interact with a workstation through any number of input and output, such as a computer monitor, printer, keyboard, mouse, trackball, index Playground, pen or touch screen that can be directly connected to a workstation 102 or connected remotely via the network. You should also understand that the workstation 102, shown in figure 1, can represent any computing device with which the user 106 can interact, including desktop computer portable computer, the laptop, pocket PC, ultra-mobile personal computer (PC) or a handheld device.

On the workstation executed 102 Appendix 108 e-mail, allowing the user to access and manage messages and other information. For example, an application 108 e-mail can be a personal information management tool (PIM), which provides access to email, voice mail, personal contact, contacts, organization, calendar events, and other personal or business data and processes. In one embodiment, the application 108 e-mail is a client messaging and collaboration Microsoft Office Outlook from Microsoft Corporation, Redmond, Washington. You should understand that here presented options for implementation can be used with e-mail applications from other vendors, including, but not in a restrictive sense, software IBM Lotus Notes® IBM Corp., Armonk, new York, software, Novell Groupwiseū from Novell, Inc., Waltham, Massachusetts or GMAILTM from Google INC., Mountain View, California.

Appendix 108 e-mail are connected through a network of 110 server 112 messaging running on a remote server platform 114. The server 112 messaging enables exchange of messages and other information services for the application 108 e-mail. According to one version of the exercise of the server 112 messaging is a messaging server Microsoft Exchange Server® from Microsoft Corporation. As should be clear specialist, server, 112 exchanging messages can be anything known in the art messaging server, made with the possibility of providing the described messaging services for the application 108 e-mail, such as software IBM Lotus Domino® IBM Corp or software Novell Groupwiseū from Novell, Inc.

According illustrative options for implementation, a network of 110 is the Internet. At the same time, it should be understood that the network of 110 can be a local area network (LAN), wide area network (WAN) or other network, suitable to provide placed on the workstation 102 Annex 108 e-mail capabilities to exchange data with the server 112 messaging running on the server platform 114. You should also understand that it can be used much more compared to depicted in figure 1 the number of networks and network connections.

The server 112 exchanging messages can be connected with storage 116 messages. Store 116 messages can store messages and other items of data for access by applications 108 e-mail. Message 118 may constitute an e-mail, text message, a Fax message, the voice message or any other message. Message 118 may contain a theme 120 messages. According illustrative options for implementation, the message 118 may also contain an identifier (ID) 122 session of communication that is used to group messages by thread messages or communications, which are discussed in more detail below, with reference to Figure 4. According to the described variants of implementation, the message 118 may also include a number of file attachments 124. File attachment 124 is a document or file attached to the message 118. File attachment 124 may be 126 name of the file, date 128 changes, showing the date when the file was last modified, size 130 file showing the file size in bytes, and ID 132 of the author, showing the author of the document or file. As should be clear to experts, store 116 messages can be located on the server platform 114 or on a remote storage device to which the server 112 exchanging messages can access. Store 116 messages may contain other data elements, such as calendar events, contacts, tasks, notes and other personal or business data beyond those shown in figure 1.

Additional options exercise of the application 108 e-mail can include local store 134 in which the application 108 e-mail caches the data pertaining to the message 118, and other data elements. Message 118 can be cached in the local store 134 when you first access the message 118-side applications 108 e-mail, or all available messages 118 can be moved or copied from the repository 116 messages in a local store 134 on a scheduled basis. For example, an application 108 e-mail can access the server 112 messaging under version 3 of the post office Protocol (POP3) every hour available for download messages from the store 116 messages and store them in a local repository 134. It should be understood that the application 108 e-mail can be used in many other ways and protocols to retrieve messages from the messaging server and the local conservation of these messages.

Appendix 108 e-mail can also include module 136 collection of investments, which performs operations on display precast list of attachments that will be described in detail below. According illustrative options for implementation, the functionality of the module, 136 collection of attachments provided by the application 108 e-mail. It should, however, understand that the module 136 collection attachments can be provided as add (add-in module for the application 108 e-mail. Add the module can use an application programming interface (API)provided by the application 108 e-mail to access data from the server 112 messaging or from local storage 134 and to display precast attachment list as part of the application interface 108 e-mail.

Messages 118A-118I assosiated with specific thread 204 messages that can be identified on the basis of shared ID 122 session of communication, identical or similar to those 120 message or some other way of determining relationships among the messages will be described in more detail below, with reference to Figure 4. For example, a thread 204 messages, illustrated in figure 2, contains several associated messages 118A-118I, grouped under the heading 206 “Document plan a new project ...”. The presence of one or more file attachments 124 for a particular message 118A can specify an image or icon 208 attachments. Another indicator of 208 attachments can be displayed next to the title 206 flow 204 message to indicate that the thread 204 message includes at least one message 118A with a file attachment 124. When a particular message 118F user selectable 106 from a stream 204 messages, as specified frame 210 choice in figure 2, the information related to the selected message 118F, is displayed in the app 108 e-mail panel 214 details window messages 202.

According to the present here variants of implementation, when the panel 214 details of the message is shown to associate with the flow 204 message 118F, which includes at least one file attachment 124, 136 module collection attachments modular displays a list of 216 investments in the window near 202 panel 214 detail message. According illustrative options for implementation, collecting a list of 216 attachments may contain entries 218a Centralnaya street-Z list for file attachments 124 attached to messages 118A-118I associated with the stream 204 message, part of which is selected message 118F. Write 218a Centralnaya street-Z list can contain an icon 220 file type that indicates the file type of the corresponding file attachment, the name 222 of the file, the author 224 file and the size 226 of the file in bytes.

As described above, file attachments 124 associated with the flow of messages that can be a number of different versions of several root files. Additional options exercise of precast list 216 attachments may contain entries 218a Centralnaya street-Z list for any root of the file identified by the file attachments 124 associated with the stream 204 messages that will be described in more detail below, with reference to Figure 5. Icon 220 file type, name, 222, author 224 and size 226 file displayed for entries 218a Centralnaya street-Z list, represent the most recent version of the relevant root of the file. In addition, write-218a Centralnaya street-Z list for corresponding with many versions of root files identified in file attachments 124 may also include an indication of the number of versions 228 root file in the file attachments 124.

The latest version of the root of the file and the number of available versions can be defined by a module 136 collection of investments, as will be described below, with reference to Figure 5. The number of versions 228 can be displayed as a hyperlink, which provides the user with 106 access to different versions of the root file when the user 106 chooses this hyperlink using the mouse, for example. It should be understood that although we present here the examples describes how to use a mouse, you can use any appropriate user input devices to provide users with the ability to choose or interact with the UI controls, including, but not in a restrictive sense, keyboard, trackball, index, site, pen or touch screen which can be connected to a workstation 102.

According illustrative options for the implementation of the module, 136 collection of investments can provide the same functionality UI for various records 218A-218C of the list displayed in the combined list 216 attachment, as provided for any other view file in the application 108 e-mail. For example, 218B of the list may be selected by the user 106 mouse dragged from precast list 216 attachments and put in a file folder or another location for the files presented in the UI. If the entry 218B list dragged from precast list 216 investment and put in place for the files that the latest version of the root file corresponding entry 218B of the list can be copied to that location for the files.

Module 136 collection of attachments provided that the files are dragged and placed in prefabricated list 216 investments through the UI. If the file is dragged into a collecting a list of 216 investments from some other place, the module 136 collection attachments can create a new message 118 associated with the stream 204 messages, attach this file as a file attachment 124 and save the message 118 store 116 messages or local store 134. In addition, the module 136 collection of investments can forward the message 118 some or all of the individual senders and recipients of messages 118A-118I associated with the stream 204 messages.

In another embodiment, the module 136 collection attachments can provide additional functionality for managing the root file or file attachments, 124, relevant records 218F-218C of the list displayed in the combined list 216 investments. As illustrated shown in figure 3 UI 300, access to these additional functionality can be implemented from the context menu 302, display module, 136 collection of investment, when the user places the mouse cursor over a collective list 216 investments and makes you right click, for example. The context menu 302 can contain menu items that provide user 106 the ability to perform actions in relation to all groups of attachments, such as:

“Save all attachments, in which case all file attachments or to the root files assosiated with thread 204 messages would be stored in one place;

“Forward all the attachments that result would give the user 106 the opportunity to create a new message with 118 attached to all of the root file;

Remove previous versions than from storage 116 messages or local storage 134 deletes all versions of the boot files except the most recent version of each of them; and

“To filter by sender”, which allows the user to only view the file attachment from a specific sender.

You should understand that the context menu 302 may contain other menu items that provide user 106 the ability to perform actions in respect of all file attachments 124 or a separate file attachments 124, or the root of the file associated with stream 204 messages.

Although mixed list 216 attachments are shown in figure 2-3 as shown in combination with data specific to the message 118F, selected from the stream 204 messages, it should be understood that the module 136 collection attachments can form a combined list 216 investments in conjunction with the display of any message in store 116 messages that are associated with the stream 204 messages, regardless of the context of his choice. Moreover, numerous variations in the location of precast list 216 investments in the box 202 and placing icons 220 file type, name, 222, author 224, size 226 file and the number of versions 228 displayed in the combined list 216 investments will be obvious to specialists, this variant of application of means covering any such variations beyond those shown in figure 2-3.

Let us turn now to Figure 4-5, which provides additional details regarding represent variants of implementation. In particular, figure 4 illustrates how, collectively denoted 400, to display precast attachment list associated with the message flow. Should to understand what is described here logical operations are implemented (1) as a sequence of computer-implemented actions or software modules running in the computer system, and/or (2) interconnected schemes machine logic or circuit modules within the computer system. Implementation is a matter of choice depending on performance and other requirements for the computer system. Accordingly, described here logical operations variously referred to as operation conditions, structural devices, steps or modules. These transactions are structured, actions, and modules can be implemented in software, firmware (firmware), specialized in digital logic and any combination of them. It should be understood that may be more or fewer operations compared with what is shown on the drawings and described here. These operations can also be performed in a different order to those described here.

Procedure 400 begins with operations 402, where module 136 collection attachments identifies messages 118A-118I associated with the current thread messages 204. As described above, this can be done by identifying all messages 118 store 116 messages or local store 134, which is shared ID 122 session of communication, according illustrative options for implementation. ID 122 session of communication can be globally unique identifier (GUID) or a string that identifies the session of communication or message flow, with whom the message 118 associated with. ID 122 session of communication may be formed for the first message 118A mail stream. Subsequent messages 118B-118I in the stream 204 messages, such as answers or forwarded messages, can have the same ID 122 session of communication, and that the original message 118A. This allows subsequent messages 118B-118I save them a thread binding 204 messages, even if other data related messages 118, such as subject 120 messages has changed.

From operations 402 procedure moves to the operation 404, where module 136 collection attachments identifies any file attachments 124 messages 118A-118I associated with the stream 204 messages. Module 136 collection of investments can access the messages 118A-118I identified in the operation 402 to determine file attachments 124 assosiated with flow 204 messages. After file attachments 124 assosiated with flow 204 messages identified, the procedure 400 can go from operations 404 for surgery 406, where module 136 collection attachments identifies the root files for file attachments 124, which will be described in more detail below, with reference to Figure 5.

Procedure 400 then passes from operations 406 operation 408, where module 136 collection attachments modular displays a list of 216 investments in the box 202 applications 108 e-mail. Record 218A-218C list can be created in the combined list 216 investments for root file associated with stream 204 messages that are identified by the module, 136 collection of investments in operations 406. Module 136 collection attachments uses the name 126 file, size 130 file and ID 132 of the author learned from file attachments 124, which is defined as being the most recent version of the relevant root file to display the icon 220 file type, name, 222, author 224 and size 226 file for entries 218A-218C list in the combined list 216 investments. In addition, the number of versions 228 each root of the file, specified in the operation 406, is shown in the corresponding entry 218A-218C list.

Figure 5 illustrates the procedure generally marked 500, which provides additional aspects of the above operations 406 to identify the root of files associated with the stream 204 messages from file attachments 124. Procedure 500 begins operation 502, where module 136 collection attachment provides access to the file attachments 124 identified in the previous operations 404 as assosiated with flow 204 messages. For a given file attachments procedure 500 goes to the operation 504, where module 136 collection attachments determines if it is a file attachment to the root file already identified for the thread 204 messages.

According illustrative options for the implementation of the module, 136 collection attachments can use the name of 126 file file attachments 124 to determine whether the two file attachments 124 to the same root file or document. If the names 126 files two file attachments 124 same, the module 136 collection attachments can determine what file attachments 124 belong to one and the same root file.

However, when the user 106 replies to or forwards the message 118 containing the modified file attachment, 106 user can rename a file attachment to indicate that the document or file was edited. For example, a user can receive the message 118A with a file attachment named as “the Project Plan Project X.xls”. Next, the user later changes the document attached to the message 118A, and meet new message 118G to which the revised document is attached as a file attachment named “Project Plan Project X (version 9-15 from Bill J).xls”. To determine what file attachments 124, attached to the two messages 118A, 118G are versions of the same root file module, 136 collection attachments can analyze the 126 name of the file, each file attachments 124 by applying the General syntax rules or methods for such rename files. You should understand that many methods syntax of logic can be applied to determine file attachments that are related to the same root file, and distribution versions root files based on filenames.

Additional options exercise of the module 136 collection attachments can use other attributes file attachments 124 to determine whether they refer to the same root document, such as title of a document or description, extracted from the contents of a file attachments 124. It should be understood that the module 136 collection attachments can use many different methods to compare file attachments, including a comparison of the contents of file attachments.

In operation 506 136 module collection attachments determines that a file attachment 124 refers to already identified the root of the file, and then the procedure is 500 can go for surgery 508. In operation 508 module 136 collection attachments can determine the level version of file attachments 124 on the basis of comparison with the identified root file. By determining the level of versions of each file attachments 124 relating to the same root file module, 136 collection attachments can define a file attachment 124, which is the latest version of the root of the file and the number of versions of the root file available for display in the combined list 216 investments. According illustrative options for the implementation of the module, 136 collection of investments can define levels versions of file attachments that are related to the same root file by comparing data 128 last modified file attachments 124.

If the transaction 506 module 136 collection of investments is determined that a file attachment does not apply to already identified the root file, the procedure 500 can go for surgery 510, where the new root file is identified for a thread 204 messages from file attachments 124. Then, in the operation 512, if there is another file attachments to be processed, the procedure 500 can return to operation 504, where module 136 collection attachments repeats the process 500 for the next file attachments 124. If no more file attachments 124 for processing, the procedure 500 can go from operations 512 for surgery 514, where the procedure is 500 ends.

Fig.6 shows illustrative computer architecture for computers 600, made with the possibility of performance described here software components to display a list of file attachments associated with the flow of messages above. Computer architecture, shown in 6 illustrates the well-known desktop, laptop or server computer and can be used to perform any of the aspects presented here are software components that are described as running on the workstation 102 or server platform 114.

Shown in Fig.6 computer the architecture includes a Central processing unit (CPU) 602, system memory 608, which includes random access memory (RAM, RAM) 614 and permanent memory (ROM, ROM) 616, and system bus 604, which connects the memory with the CPU 602. The system basic input/output containing basic procedures that facilitate the transfer of information between elements in a computer 600, for example, at the time of its launch, is stored in ROM 616. Computer 600 also includes mass storage device 610 to store the operating system 618, applications and other software modules that are described here in detail.

Mass storage device 610 connected to CPU 602 through the controller mass storage devices (not shown)connected to the bus 604. Mass storage device 610 and associated readable media provide non-volatile storage for computer 600. Although included here is a description of a machine-readable media refers to mass storage such as a hard disk or CD-ROM, you should understand that machine-readable form can be any available computer data media, to which the computer may 600 to access.

As an example, but not limitation, machine-readable form may include non-volatile and volatile, removable and non-removable drives, implemented by any method or technology to store information, such as machine-readable instructions, data structures, software modules or other data. For example, readable media include but are not in a restrictive sense, ROM, RAM, erasable programmable read-only memory (EPROM), electrically erasable programmable ROM (EEPROM), flash memory or other solid-state technology, CD-ROM, digital versatile discs (DVD), HD-DVD, Blu-Ray, or other optical storage, magnetic tape, magnetic tape, magnetic disk drives or other magnetic storage devices or any other media that can be used for storage of information required, and to which computer 600 can access.

According to various variants of implementation, the computer 600 can work in a networked environment using logical connections to remote computers over the network, such as the network of 110. Computer 600 can connect to the network through 110 unit 606 network interface connected to the bus 604. It should be understood that the unit 606 network interface can also be used for connection with other types of networks and remote computer systems. Computer 600 can also include a controller 612 I/o for the reception and processing of input from other devices like a keyboard, mouse or stylus (not shown in Fig.6). Similarly, the controller's I/o can submit display 104, printer, or other type of output device.

As briefly mentioned earlier, in the mass storage device 610 and RAM 614 from the computer 600 can store a number of software modules and the data files, including the operating system 618, the right to control the use of network-connected desktop computer, laptop or server computer. Mass storage device 610 and RAM 614 can store one or more software modules. In particular, mass storage device 610 and RAM 614 can store application 108 e-mail or server 112 exchanging messages, each of which is discussed in detail above in relation to the Figure 1. Mass storage device 610 and RAM 614 can also store other types of software modules or data.

Based on the above, it should be understood that in this application presents technology to display a list of file attachments associated with the flow of messages in an email application. Although the open here invention was described in a language-specific computational structural characteristics of methodological actions and machine-readable media, it should be clear that the invention defined by the appended claims, not necessarily limited to these specific characteristics, actions or media that are described here. Such specific characteristics, actions and media revealed rather as illustrations of forms of realization of the claims.

The above description is presented only as an illustration and should not be interpreted restrictively. Various modifications and changes can be made in respect of these inventions, not following it is shown and described illustrative options implementation and enforcement, and is not straying from the true nature and scope of the present invention, as defined supplied by the claims.

1. How to display precast list investments associated with the flow of messages in an email application that contains the time that: identify one or more messages associated with the flow of messages; identify one or more file attachments that one or more messages; after identification referred to one or more file attachments, identify appropriate root files related to this, one or more file attachments, by comparing the contents referred to one or more file attachments with the contents of the corresponding root files; form mixed list of attachments to include the appropriate entry in the list referred to one or more file attachments and identified root files, and list entries contain, respectively, the icon file type, one or more of the file name, file size and identification the author of the data related to the root file file attachments that have the highest level version, and specifying file attachments that have the highest level of release; and display mixed attachment list in the application window e-mail.

2. The method according to claim 1, wherein when identifying one or more messages associated with the flow of messages, identify one or more messages with the same session ID communication.

3. The method according to claim 1, wherein when identifying one or more messages associated with the flow of messages, identify one or more messages that have the same or similar subject.

4. The method according to claim 1, further comprising stages, which are: determine appropriate levels versions for the mentioned one or more file attachments based on the root file specific to the file attachment; and form a combined list of attachments to include the appropriate entry in the list referred to one or more file attachments with the associated version levels, and the identified root files.

5. The method according to claim 1 in which the mentioned list entries respectively optionally specify the number of file attachments that are related to the root files.

6. The method according to claim 1, wherein when identifying the appropriate root file relating to one or more file attachments, identify a file attachments that have the same or similar file name, as referring to the same root file.

7. The method according to claim 1, wherein when determining appropriate levels versions for one or more file attachments based on the root file associated with a file attachment, compare appropriate date change for one or more file attachments that are related to the root file.

11. Machine-readable medium of claim 8, when identifying the relevant root file relating to one or more file attachments are identified file attachments that have the same or similar file name, as referring to the same root file.

12. Machine-readable medium of claim 8, when determining appropriate levels versions for one or more file attachments based on the root file associated with a file attachment, compared to the corresponding date of change for one or more file attachments that are related to the root file.

13. System to display precast list of attachments containing: the message store that contains many messages associated with the flow of messages; mail application is configured to run on a workstation and implemented with the possibility to access the message store and display a window containing information about this set of messages; and the collection engine attachments configured to execute within the e-mail application and implemented with the possibility to identify mentioned many messages associated with the stream messages by identifying in the message store the messages that have the same session ID communication; to identify one or more file attachments to this set of messages; to identify appropriate root files related to this one or more file attachments, by comparing the contents referred to one or more file attachments with the contents of the corresponding root file, in this case, the identification of root files related to the mentioned one or more file attachments: determine, for each of referred to one or more file attachments, whether this file attachment to an identified the root file associated with the flow of messages in determining that a file attachment refers to the identified root file associated with the flow of messages determine the level version of this file attachments based on identified the root of the file, and you determine that a file attachment does not apply to the identified root file associated with the flow of messages, identify new root file to thread messages; to form a combined list of attachments to include the appropriate entry in the list referred to one or more file attachments with the associated version levels, and identified root files; display mixed attachment list in the application window e-mail moreover list entries contain, respectively, the icon file type, one or more of the file name, file size, and the identity of the author referred to one or more file attachments; and display the control of the user interface in combination with the cumulative list of attachments which, when selected, deletes all versions of all the root files except file attachments that have the highest level version of the corresponding root of the file.

14. The system indicated in paragraph 13, in which identification of the respective root file relating to one or more file attachments are identified file attachments that have the same or similar file name, as referring to the same root file.

15. The system indicated in paragraph 13, in which the message store is stored locally on the workstation.

16. The system indicated in paragraph 13, in which the message store is stored on the server computer remote relative to the workstation.