US 7,444,382 B2Grant
Method and apparatus for minimizing storage of common attachment files in an e-mail communications server
Issue Date:2008-10-28
•17 Claims
•7 Drawing Sheets
Abstract
The present invention provides an e-mail communications system that minimizes the number of duplicate copies of common attachment files to e-mail communications that are stored in the mail store of an e-mail server. When the e-mail server receives an e-mail attachment file that is larger than a threshold size, the server performs a database search for another copy of the attachment file in the mail store. If another copy is located, the system creates a pointer in the mail store that associates the located attachment file with the e-mail for the additional recipient(s). Attachment files are deleted only after the recipients of the associated e-mail communications delete each of the respective e-mails.
Metadata
Assignee
- AT&T Intellectual Property I, L.P.
Inventor
- Dale W. Malik
Application Information
Application Number:US 11/303,839
Filing Date:2005-12-16
Priority Date:2000-11-30
Art Unit:2619
Classifications
IPC:
G06F15/16
Patent Drawings (7 sheets)
Description
Cross Reference to Related Application
[0001] This application is a continuation of U.S. utility application Ser. No. 09/725,719, filed Nov. 30, 2000, now U.S. Pat. No. 7,003,551.
Field of the Invention
[0002] The present invention relates to the storage and maintenance of e-mail attachment files in an e-mail communications server, and more particularly, to a method and apparatus for reducing the number of copies of identical attachment files stored in the e-mail communications server.
Description of the Related Art
[0003] During the past decade, electronic mail (“e-mail”) has become an indispensable tool for facilitating business and personal communications. Through computer networking systems such as local-area networks (“LAN”), wide-area networks (“WAN”), and the world-wide web (“WWW”), network users can send and receive notes, messages, letters, etc., to communicate with others who are in the same office or perhaps in remote locations across the world.
[0004] E-mail application programs are typically configured for generating messages in the form of memoranda. An e-mail application user interface guides a user to “compose” an e-mail communication by providing a platform for entering at least one outgoing e-mail address, a “subject” heading, and a “body” for the actual message. The user may also designate a document, file or executable program to be attached to the e-mail message. When the user completes typing the message and presses the “send” key, the message is transmitted over the network and is routed for delivery to an e-mail server corresponding to the provided destination address.
[0005] A known e-mail communications system and a method for transmitting e-mail communications between networks over the Internet are described with reference to FIG. 1 . Computers 10a-10c are connected through a local area network (LAN) 11 to e-mail communications system 12, which can send e-mail communications to any of computers 18a-18c through e-mail communications system 16 and local area network (LAN) 17. E-mail communications systems 12 and 16 include Mail Transport Agent (MTA) servers 12a, 16a, Post Office Protocol (POP or POP3) servers 12b, 16b, and Message Store 12c, 16c. The e-mail communications servers 12 and 16 are also connected to their respective domain name servers (DNS) 13, 15.
[0006] When an e-mail communication is transmitted according to the Simple Mail Transport Protocol (SMTP), it is first divided into three components: the sender's “mail from:” address; the recipient address list; and the data portion of the message. After a user of computer 10c prepares an e-mail communication and sends the e-mail across the LAN 11, it is sent to the MTA 12a, which accepts e-mails for delivery. The MTA then separates the address information from the data portion of the e-mail. The MTA parses the envelope to determine whether to route the message to an external network or store the message in Message Store 12c for access by another computer connected to the LAN 11. The MTA “postmarks” the e-mail by adding routing data to the header before storing the message.
[0007] If the e-mail is to be sent to another user on a different mail system, the MTA 12 next determines the domain for the intended recipient through its DNS 13, which queries the recipient system's DNS 15 through the Internet. Upon receiving the domain information, MTA 12a transmits the e-mail communication to MTA 16b, which is waiting to accept e-mail. MTA 16b then stores the received e-mail in Message Store 16c. Later, a user on computer 18a can log in to the e-mail system and connect to the POP server 16a, which determines if there is new mail to download. POP server 16a can then retrieve the e-mail communication from the Message Store 16c and transmit the e-mail through the LAN 17 to the user.
[0008] It is common for users to send a single e-mail communication to multiple recipients. This typically occurs when the e-mail communication contains a humorous joke or anecdote, a political announcement or notice, an advertisement, or pertains to any other subject matter that is of common interest. Some of the recipients may in turn forward this e-mail communication to other groups of recipients. In some instances, a single e-mail communication ultimately may be transmitted and forwarded to thousands of recipients, and, through different sources, some users may even receive multiple copies of the same e-mail communication. Such e-mail communications may additionally include large attachment files stored along with the e-mail message.
[0009] When an e-mail communication is transmitted to a plurality of recipients who are connected to the same e-mail communications server, only a single copy of the e-mail communication message and attachment is stored in the Mail Storage of the e-mail server. For example, if a prospective vendor sends a solicitation via e-mail to a large group of employees in a single company, the company's e-mail server will store only a single copy of the e-mail solicitation. The e-mail message and attachment will remain in the Mail Storage until it is designated for deletion by each of the recipients. Consolidating storage of e-mail communications in this manner can reduce the amount of memory required in the company's e-mail communications server.
[0010] Although presently available e-mail communications systems consolidate storage when an e-mail communication transmitted by a single sender is received for distribution to a plurality of recipients in a common e-mail server, such e-mail systems do not consolidate storage of the e-mail communication file when it is forwarded to others in the network, resulting in multiple copies of the same file(s). Likewise, if a common e-mail communication is separately transmitted to multiple recipients in a network, or is transmitted multiple times to a single recipient, the e-mail system retains multiple copies of the same file(s) in Mail Storage. This duplication of file storage reduces the efficiency of the e-mail communications server.
Summary of the Invention
[0011] In view of the difficulties described above regarding the duplication of storage of common e-mail communications in an e-mail server, there is a need for a method and apparatus for automatically detecting and consolidating storage of common e-mail attachment files received in an e-mail communications server.
[0012] An object of the present invention is to provide a method of storing an e-mail communication containing an attachment file received in an e-mail server. A database of attachment files previously stored in the e-mail server is searched for a copy of the attachment file from the received e-mail communication. If a copy of the attachment file is located in the e-mail server, the attachment file from the e-mail communication is removed, and a link is created from the e-mail communication to the previously stored attachment file in the database.
[0013] Another object of the present invention is to provide a method of storing attachment files to e-mail communications received in an e-mail server. Header information from the e-mail communications is extracted and stored in a mail store. Header information from the attachment file to be stored is also extracted. The extracted attachment file header information is compared with header information from attachment files previously stored in the mail store to determine whether the attachment files received with the e-mail communications are duplicates of previously stored files. If an attachment file is a duplicate, a link is stored in the mail store between the e-mail header information and the previously stored attachment file.
[0014] Yet another object of the present invention is to provide an e-mail communications server. An MTA server receives e-mail communications from an external network. A mail store stores e-mail communications received by the MTA server. A POP server downloads e-mail communications from the mail store to client computers through an internal network. E-mail attachment file checking software determines whether attachment files in received e-mail communications are duplicates of attachment files in the mail store. The mail store then removes duplicate attachment files from e-mail communications and creates links from received e-mail communications to the corresponding attachment files in the mail store.
Brief Description of the Drawings
[0015] FIG. 1 is a schematic diagram of a known e-mail communications and computer network system.
[0016] FIG. 2 is a schematic diagram of an e-mail communications server according to a preferred embodiment of the present invention.
[0017] FIG. 3 is a flow diagram for storing an attachment file in the e-mail communications server of the preferred embodiment of the present invention of FIG. 2 .
[0018] FIG. 4 is a table of an exemplary header database in the e-mail communications server of FIG. 2 .
[0019] FIG. 5 is a table of an exemplary attachment file database in the e-mail communications server of FIG. 2 .
[0020] FIG. 6 is a flow diagram for deleting e-mail communications and e-mail attachment files from e-mail communications according to the preferred embodiment of the present invention.
Detailed Description of the Preferred Embodiments
[0021] The present invention provides an e-mail communications system that minimizes the number of duplicate copies of common attachment files to e-mail communications that are stored in the mail store of an e-mail server. When the e-mail server receives an e-mail attachment file that is larger than a threshold size, the server performs a database search for another copy of the attachment file in the mail store. If another copy is located, the system creates a pointer in the mail store that associates the located attachment file with the e-mail for the additional recipient(s). An attachment file is deleted only after all e-mail communications that include the attachment file are deleted.
[0022] The present invention will now be described in more detail with reference to the figures. FIG. 2 is a schematic diagram of an e-mail communications server 20 in accordance with a preferred embodiment of the present invention. E-mail server 20 includes an MTA server 22 for transmitting and receiving e-mails, a mail store 23 for storing e-mail communications prior to downloading by a recipient client, and a POP server 21 for forwarding e-mail communications from the mail store 23 to recipient clients. In the present invention, e-mail server 20 additionally includes a duplication checker 24, which intercepts e-mail communication files prior to storage in mail store 23. The duplication checker 24 contains size checker software 25 that determines the size of e-mail attachments to be stored in the mail store 23, and file comparison software 26 for detecting whether large e-mail attachment files that are to be stored are duplicate copies of previously-stored e-mail attachment files.
[0023] Mail store 23 contains an attachment file storage database 28 for storing attachment files from e-mail communications received from the MTA 22. The attachment files are stored separately from the corresponding e-mail header information and message, which are maintained in a header database 27. For each e-mail communication received by the MTA 22 that includes at least one attachment file, the header database 27 stores at least one link to the corresponding attachment file(s) in the attachment file storage database 28. As explained in further detail below, detected attachment files that are referenced by multiple e-mail communications are stored in a common attachment section 29a, separate from the storage of other attachment files 29b. Much like a cache, the common attachment section 29a stores files that are accessed more frequently in the attachment file database 28.
[0024] FIG. 3 shows a method for storing e-mail attachment files in the mail store according to the preferred embodiment. When an e-mail communication is received in the MTA server in step 30, the MTA server processes the e-mail communication in step 31 to separate the header file from the e-mail message data and e-mail attachment file data, if present. If the MTA server determines in step 32 that no attachment file is included in the e-mail communication, the e-mail message is stored in step 33 in the mail store. The e-mail message may be stored in any conventional manner in the mail store. The mail store may be configured such that the e-mail header and message are stored in header database 27, without a link to the attachment file storage database. Alternatively, the header of the e-mail message can be stored in header database 27 with a link to the e-mail message data, which may be stored in another e-mail database in the mail store (not shown in FIG. 2 ). As a further alternative, the e-mail header and message data may be stored together in the e-mail database without any link in the header database 27.
[0025] If the MTA server determines in step 32 that an attachment file is included in the e-mail communication, the size checker software 25 in the duplication checker 24 determines the attachment file size in step 34. If it is determined in step 35 that the attachment file is not greater than a threshold size, the mail store in step 39 stores the header and message information (depending upon configuration) in the header database 27. In step 40, the attachment file is then stored in the main section 29b of the attachments file storage database 28. A link is created in the header database from the header to the stored attachment file. In the e-mail server 20 of the preferred embodiment, all attachment files, regardless of size, are stored in the attachment file storage database, and the header database 27 creates a link from the corresponding e-mail header to the attachment. In the alternative embodiment in which the e-mail message is stored in an e-mail database in the mail store 23, the attachment file may also be stored in the e-mail database together with the e-mail message.
[0026] The duplication checker of the preferred embodiment is configured to reduce the number of duplicate attachment files that are greater than a certain, predetermined threshold size. As will be described, the steps of processing the attachment file prior to storage, searching the attachment file database for duplicates, and moving files from the main section 29b to the cached common attachments portion 29a of the attachment files database are time intensive. Attachment files of a relatively small size, such as those below 50 KB, do not occupy significant space in the attachment file storage database, even if multiple copies have been received and stored therein. Therefore, attachments that are relatively small text files, such as short letters or memoranda, are not searched for duplicates. In contrast, large attachment files, such as those above 1 MB (or any other pre-determined threshold), can require significant resources when multiple copies are stored in the e-mail server. An inordinate number of duplicates of large attachment files stored in the e-mail server may overfill the server, such that the e-mail communications server will cease operating until files are deleted. For this reason, information systems managers who operate conventional e-mail communications systems caution users to promptly delete large e-mails and discourage others from sending e-mails with large attachment files to the e-mail server.
[0027] If, in step 35, size checker 25 in the e-mail server 20 determines that an e-mail attachment in a received e-mail communication is greater than a threshold size, the duplication checker 24 next processes the attachment file in step 36 to generate file identification information. As will be described in further detail below, this can be performed by any of several methods, such as a checksum determination, or extraction of certain attachment file header information. The processing step generates information by which the attachment file comparison section 26 of the duplication checker 24 can search the attachment file storage database 28 for identical attachment files, in step 37.
[0028] If the duplication checker determines, in step 38, that there are no copies of the attachment file previously stored in the mail store 23, then the mail store stores the attachment file in the main section 29b in step 39, and creates a record in the header database and a link in the record from the attachments database to the header database, in step 40.
[0029] If the duplication checker locates another copy of the attachment file, the mail store 23 checks in step 41 if the attachment file is presently stored in the cache portion 29a of the attachment file storage database 28. However, if the duplication checker determines that the attachment file is in the cache portion 29a, then the attachment file is already associated with a plurality of e-mail communications. In that case, the mail store creates a link in the record of the header database to the attachment in the cache portion 29a in step 44.
[0030] If the attachment file is not presently in the cache portion 29a, then the attachment file has thus far been associated with only a single e-mail communication. In step 42, the attachment file is transferred from main section of the database 29b to the cache portion 29a. The links in the record of the other, previously stored e-mail communication associated with the attachment file is modified to reflect the change in storage location in step 43. The mail store then creates a link in the record of the header database to the attachment in the cache portion 29a in step 44.
[0031] In the preferred embodiment, as shown in FIG. 3 , the mail store 38 places an attachment file in the cache portion of the attachment file storage database 28 only when there are a plurality of e-mail communications received that contain an identical attachment file. In some e-mail communications systems, when a sender transmits a single e-mail communication to a plurality of recipients on the same e-mail server, the MTA in the e-mail server receives a single e-mail with a plurality of recipient addresses in the header. For such systems, the mail store 23 can be configured to check, after determining in step 38 that there is not an attachment file already in the database, whether the header of the received e-mail communication contains a plurality of recipients who are on the e-mail server. In such case, the mail store will create a pointer in step 41 and store the attachment file in the cache portion of the database in step 43.
[0032] The process of searching the attachment file storage database 37 for a duplicate of the attachment file to be stored in the mail store indicated by step 37 of FIG. 3 can be performed by a variety of methods, according to the type of information process for file identification in step 36. Although the most accurate method for determining whether a duplicate file exists in the attachment file database is to perform a bit-by-bit comparison of each file stored in the database with the file to be stored, such a test would be unduly time consuming and would adversely affect the operability of the e-mail system. A more efficient method to identify the attachment files is to compare the characteristics concerning the files, rather than the actual file data itself.
[0033] According to the preferred embodiment, the duplication checker 24 first identifies the type of file that is to be stored as an attachment to an e-mail communication. For example, an attachment file may be a text, spreadsheet, graphics, picture, audio, or video file. By searching first according to the type of file, the duplication checker can immediately eliminate the majority of files stored in the mail store from consideration. The duplication checker next identifies the properties associated with the attachment file in the file header, which may include any of: title/name, MS-DOS name, software program, software program version number, author, creation date/time, last modified date/time, size, attributes, last saved by, revision number, and revision time (minutes). In the case of a text document, such as a Microsoft Word™ document, other properties might include the number of sections, pages, paragraphs, lines, words, and characters. A Microsoft PowerPoint™ document may include properties such as the type of fonts used, design template, embedded OLE servers, and slide titles.
[0034] The duplication checker searches the properties of each attachment file in the database that is of the same type as the application file in the received e-mail communication. If another attachment file has the identical properties, the attachment file in the received e-mail is identified as being a duplicate.
[0035] FIGS. 4 and 5 illustrate an example of the method for storing an attachment file in the mail store. The e-mail server 20 of the preferred embodiment, operating an e-mail system for the domain “anycompany.com,” receives an e-mail in the MTA server 22 on Nov. 7, 2000, intended for an employee at the company, Larry Aslad. The MTA server processes the e-mail and identifies the following: the e-mail communication is from [email protected]; it is to be sent to [email protected]; the subject heading is “This will get you laughing”; the size of the file is 2.03 MB; the e-mail was delivered on Nov. 4, 2000, at 10:22 AM; and the e-mail includes an attachment file. The size of the attachment file is 2.03 MB.
[0036] Because the attachment file in the received e-mail communication is greater than the threshold size of 0.5 MB, the duplication checker 24 processes the attachment file in the e-mail communication for file identification. Looking to header of the attachment file, the duplication checker identifies that the attachment is a video file, entitled “Whassup,” playable on Real Audio™, version 2.0, created on Oct. 6, 2000, authored by “Spike.”
[0037] The duplication checker 24 now performs a search of the attachment file database for common attachment files. Searching the cached attachment file of FIG. 5 first, it becomes clear that there is only one video file stored in the cache, link number 3. As indicated by the “header number” field, this file is currently the linked attachment for header numbers 1, 5, and 6.
[0038] Comparing this file to the attachment file in the e-mail, it becomes evident that the title, size, software and version, author, and creation date are the same. Based upon these common properties, it is determined that the attachment file in the e-mail communication for [email protected] is a duplicate. It is worth noting that the subject headings for the e-mails stored as header numbers 1, 5, and 6 are each different, and header number 5 was received on a different date from a different source than headers 1 and 6. The duplicate server and mail store can detect that the attachment files are duplicates by storing the attachment file separately from the corresponding e-mails.
[0039] Because the file is already in the cache portion of the database, there is no need to move the attachment file from the main attachment file storage database 29b to the cache 29a. The mail store 23 creates a new link and header record in the header database of FIG. 4 . The new header record appears as follows: header no. 9; username asla8908; subject “This will get you laughing;” date received Nov. 7, 2000, and from [email protected]. Attachment “3” corresponds to the previously cached storage of the same file in the mail store. In the cached attachment files, header no. 9 is now added to the header number list.
[0040] The steps for retrieving e-mail from the e-mail server by a client computer are now described with reference to FIG. 6 . An e-mail client connects with POP server 21 in step 60, and selects to download received e-mail in step 61. The POP server then accesses the header database 27 in the mail store in step 62 and extracts the header and e-mail message information from the mail store. In step 63, the mail store retrieves the attachment file corresponding to the requested e-mail communication through the link in the header database to the attachment file storage database 28. The client now can view, reply, forward, copy, or delete the received e-mail message and corresponding attachment file.
[0041] If the POP server detects in step 64 that the client requests to delete the e-mail communication, the header in the mail store corresponding to the received e-mail communication is deleted from the header database in step 66. The header reference number is then deleted in step 67 from the corresponding attachment file in the attachment file storage database. The mail store then checks in step 68 if any header reference numbers for the attachment file remain in the attachment database. If all e-mail recipients have deleted the e-mail communication, then the attachment file is deleted from the attachment database, in step 70.
[0042] Accordingly, the duplication checker and mail store header and attachment databases of the present invention can minimize storage of duplicate attachment files in an e-mail communications system. The e-mail server of the present invention is configured such that duplicate copies of attachment files are not unnecessarily stored in the mail store, whether the attachment files are received through separate e-mails or e-mail forwarding by users within the same e-mail server network. Thus, it is readily seen that the method and system of the present invention provides for improved and efficient e-mail communications, and saves valuable memory space in the mail store of an e-mail server.
[0043] The foregoing disclosure of embodiments of the present invention and specific examples illustrating the present invention have been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many variations and modifications of the embodiments described herein will be obvious to one of ordinary skill in the art in light of the above disclosure. The scope of the invention is to be defined only by the claimed appended hereto, and by their equivalents.
Claims
What is claimed is:
1. A method of storing an attachment file of an e-mail communication received in an e-mail server, comprising the steps of:
(a) extracting header information from the e-mail communication and storing the e-mail header information in a mail store;
(b) extracting header information from the received attachment file;
(c) comparing the extracted attachment file header information with header information from attachment files previously stored in the mail store to determine whether the received attachment file is a duplicate of a previously stored attachment file; and
(d) if the received attachment file is a duplicate of a previously stored attachment file, storing a link between the e-mail header information and the previously stored attachment file; and
(e) if the received attachment file is not a duplicate of a previously stored attachment file, storing the attachment file and storing a link between the e-mail header information and the received attachment file.
2. The method of storing an attachment file of an e-mail communication according to claim 1, further comprising the steps of:
(f) deleting the e-mail header information stored in the mail store and the link between the e-mail header information and a corresponding attachment file in response to a delete request; and
(g) deleting the corresponding attachment file if there are no links remaining to the corresponding attachment file.
3. The method of storing an attachment file of an e-mail communication according to claim 1, wherein e-mail messages in the e-mail communications are stored with the corresponding e-mail header information in the mail store.
4. The method of storing an attachment file of an e-mail communication according to claim 1, wherein the header information extracted from the received attachment file includes a designation of file type.
5. The method of storing an attachment file of an e-mail communication according to claim 4, wherein the step of comparing extracted attachment file header information is performed by searching the previously stored attachment files that are designated as the same file type as the received attachment file.
6. The method of storing an attachment file of an e-mail communication according to claim 4, wherein the header information extracted from the received attachment file further includes at least one of: size, creation date, revision date, author, software type, version, and revision number.
7. The method of storing an attachment file of an e-mail communication according to claim 1, wherein the step of comparing extracted attachment file header information is performed only when the size of the received attachment file is greater than a predetermined size.
8. An e-mail communications server comprising:
(a) an MTA server for receiving e-mail communications from an external network;
(b) a mail store for storing e-mail communications received by the MTA server;
(c) a POP server for downloading e-mail communications from the mail store to client computers through an internal network; and
(d) e-mail attachment file checking software for determining whether attachment files in received e-mail communications are duplicates of attachment files in the mail store, wherein the mail store removes duplicate attachment files from e-mail communications and creates links from received e-mail communications to the corresponding attachment files in the mail store.
9. The e-mail communications server according to claim 8, wherein the mail store further comprises a database for storing the links from received e-mail communications to the attachment files.
10. The e-mail communications server according to claim 9, wherein the mail store further comprises a first attachment storage database for storing attachment files that are each associated with a single e-mail communication, and a second attachment storage database for storing attachment files that are each associated with a plurality of e-mail communications.
11. The e-mail communications server according to claim 8, further comprising e-mail file attachment size checker software for detecting the size of attachment files in received e-mail communications, wherein the e-mail attachment file checking software only checks attachment files that are greater than a predetermined size.
12. The e-mail communications server according to claim 8, wherein the e-mail attachment file checking software extracts properties associated with the attachment files in the received e-mail communications, and searches the mail store for attachment files having the same properties.
13. A method of storing an e-mail communication containing an attachment file received in an e-mail server, comprising the steps of:
(a) searching a database of previously stored attachment files for a duplicate of the attachment file from the received e-mail communication;
(b) if a duplicate of the attachment file is located by the search, removing the attachment file from the e-mail communication, and creating a link from the e-mail communication to the duplicate of the attachment file in the database; and
(c) if a duplicate of the attachment file is not located by the search, separating the attachment file from the e-mail communication and storing the attachment file in the database, and creating a link from the e-mail communication to the corresponding attachment file stored in the database.
14. The method of storing an e-mail communication containing an attachment file received in an e-mail server according to claim 13, further comprising the step of detecting the size of the attachment file associated with the received e-mail communication,
wherein the steps of searching the database, removing the attachment file from the e-mail communication; and creating a link from the e-mail communication are performed if the attachment file is greater than a predetermined size.
15. The method of storing an e-mail communication containing an attachment file received in an e-mail server according to claim 13, wherein the database of attachment files is searched by performing a checksum against the attachment file of the received e-mail communication.
16. The method of storing an e-mail communication containing an attachment file received in an e-mail server according to claim 13, wherein the database of attachment files is searched by comparing properties associated with the attachment files with corresponding properties associated with the attachment file of the received e-mail communication.
17. The method of storing an e-mail communication containing an attachment file received in an e-mail server according to claim 13, further comprising the steps of:
(c) deleting the link from e-mail communication to the attachment file in response to a delete request; and
(d) deleting the corresponding attachment file when there are no links remaining to the attachment file.
Patent Citations (58)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US5323394(A) | 1994-06-01 | Perlman | Applicant |
| US5327534(A) | 1994-07-01 | Hutchison et al. | Applicant |
| US5379448(A) | 1995-01-01 | Ames et al. | Applicant |
| US5771355(A) | 1998-06-01 | Kuzma | Applicant |
| US5778395(A) | 1998-07-01 | Whiting et al. | Applicant |
| US5781901(A) | 1998-07-01 | Kuzma | Applicant |
| US5809481(A) | 1998-09-01 | Baron et al. | Applicant |
| US5832208(A) | 1998-11-01 | Chen et al. | Applicant |
| US5892909(A) | 1999-04-01 | Grasso et al. | Applicant |
| US5903723(A) | 1999-05-01 | Beck et al. | Applicant |
| US5905712(A) | 1999-05-01 | Cresswell et al. | Applicant |
| US5937160(A) | 1999-08-01 | Davis et al. | Applicant |
| US6009462(A) | 1999-12-01 | Birrell et al. | Applicant |
| US6021433(A) | 2000-02-01 | Payne et al. | Applicant |
| US6035104(A) | 2000-03-01 | Zahariev | Applicant |
| US6073142(A) | 2000-06-01 | Geiger et al. | Applicant |
| US6092101(A) | 2000-07-01 | Birrell et al. | Applicant |
| US6138149(A) | 2000-10-01 | Ohmura | Applicant |
| US6199061(B1) | 2001-03-01 | Blewett et al. | Applicant |
| US6246669(B1) | 2001-06-01 | Chevalier et al. | Applicant |
| US6256672(B1) | 2001-07-01 | Redpath | Applicant |
| US6275848(B1) | 2001-08-01 | Arnold | Applicant |
| US6275850(B1) | 2001-08-01 | Beyda et al. | Applicant |
| US6278449(B1) | 2001-08-01 | Sugiarto et al. | Applicant |
| US6321242(B1) | 2001-11-01 | Fogg et al. | Applicant |
| US6327594(B1) | 2001-12-01 | VanHuben et al. | Applicant |
| US6366949(B1) | 2002-04-01 | Hubert | Applicant |
| US6405244(B1) | 2002-06-01 | Bando et al. | Applicant |
| US6408040(B2) | 2002-06-01 | Cho | Examiner |
| US6415278(B1) | 2002-07-01 | Sweet et al. | Examiner |
| US6453340(B1) | 2002-09-01 | Emura | Applicant |
| US6457044(B1) | 2002-09-01 | IwaZaki | Applicant |
| US6463430(B1) | 2002-10-01 | Brady et al. | Applicant |
| US6499001(B1) | 2002-12-01 | Meyer | Applicant |
| US6505236(B1) | 2003-01-01 | Pollack | Applicant |
| US6560639(B1) | 2003-05-01 | Dan et al. | Applicant |
| US6606654(B1) | 2003-08-01 | Borman et al. | Applicant |
| US6611830(B2) | 2003-08-01 | Shinoda et al. | Applicant |
| US6662212(B1) | 2003-12-01 | Chandhok et al. | Applicant |
| US6704772(B1) | 2004-03-01 | Ahmed et al. | Examiner |
| US6714968(B1) | 2004-03-01 | Prust | Examiner |
| US6728733(B2) | 2004-04-01 | Tokui | Applicant |
| US6728752(B1) | 2004-04-01 | Chen et al. | Applicant |
| US6732111(B2) | 2004-05-01 | Brodersen et al. | Applicant |
| US6738800(B1) | 2004-05-01 | Aquilon et al. | Applicant |
| US6757712(B1) | 2004-06-01 | Bastian et al. | Applicant |
| US6772139(B1) | 2004-08-01 | Smith, III | Applicant |
| US6785679(B1) | 2004-08-01 | Dane et al. | Examiner |
| US6801962(B2) | 2004-10-01 | Taniguchi et al. | Applicant |
| US6823365(B1) | 2004-11-01 | Mattis et al. | Examiner |
| US6829636(B1) | 2004-12-01 | Kubik et al. | Applicant |
| US6920608(B1) | 2005-07-01 | Davis | Examiner |
| US7003551(B2) | 2006-02-01 | Malik | Applicant |
| US7039678(B1) | 2006-05-01 | Halahmi et al. | Examiner |
| US7051085(B1) | 2006-05-01 | Lee | Examiner |
| US7054905(B1) | 2006-05-01 | Hanna et al. | Examiner |
| US7117246(B2) | 2006-10-01 | Christenson et al. | Examiner |
| US2002/0016818(A1) | 2002-02-01 | Kirani et al. | Examiner |
Non-Patent Literature (24)
- McCann; “Modeling Mobile IP in Mobile Unity”, www.cs.wustl.edu/cs/techreports1998/wucs-98-03.ps.Z, 1998, pp. 1-22.Applicant
- Manola; “Initial Use of COTS Tools in the OBJS Virtual Office”, www.bojs.com/survey/Scenario-1.html, 1997, pp. 1-20.Applicant
- Fortiner; “Small-Speedy Email”, Design Specification, cs.wwc.edu/˜fortsa/se/designspec/html, Aug. 28, 2005, pp. 1-5.Applicant
- White; “How To Use Automatic Formatiing to Turn File Names into Hyperlinks”, www.wellesley.edu/Computing/Word/hyperlinks.html, May 19, 2005, pp. 1-2.Applicant
- Internet Adventurer; “Adventure Software-Internet Adventurer- File Attachments”, www.ietadv.net.hel-p/newsatt.htm, 2005, pp. 1-2.Applicant
- Microsoft; “Microsoft Office Developer Forum Microsoft Access Objects”, Office 97 Programmer's Guide, www.microsoft.com/officedev/articles/Opg/003/003.htm, last updated Feb. 3, 1997, pp. 1-31.Applicant
- Meyers; “Standardization of the Complement Adjunct Distinction”, nlp.cs.nyu.edu/publication/papers/adj-compl-old. ps, 1994, pp. 1-11.Applicant
- Finger; “On the Semantics of ‘Current Time’ in Temporal Databases”, ftp.ime.usp.br/pub/mfinger/SBBD96.ps.gz, 1996, 14 pages.Applicant
- Miller; “Kerberos Authentication and Authorization System”, krasse.ce.chalmers.se/Security/techplan.PS.gz, Oct. 27, 1988, pp. 1-36.Applicant
- Sitescape; “SiteScape for IU Faculty”, www.indiana.edu/˜ssf/b155/htm; Sep. 1999, pp. 1-24.Applicant
- JMS; “Email Protocols: SMTP, MIME, POP, & IMAP”, www.opus1.com/www/presentation/emailproto; Nov. 13, 1997, pp. 1-4.Applicant
- WPL MAC; “Woburn Public Library and the World Wide Web”, WPL MAC Tutorial, users.rc.com/woblib/mactut.htm, pp. 1-7.Applicant
- Kowalchuk; “VNEWS: A Multicast, Multimedia New Service with Virtual Messages”, Computers and Communications, Conference Proceedings of the 1996 IEEE Fifteenth Annual International Phoenix Conference Mar. 27-29, 1996, pp. 44-50.Applicant
- Thomas; “Controlling Interests”, Digital Toolbox, IEEE Internet Computing May-Jun. 1997, pp. 97-99.Applicant
- Jaeger; “Flexible Control of Downloaded Executable Content”, citeceer.nj.nec.com/jaeger97flexibile.html, pp. 1-47.Applicant
- Malik; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Non- Final Rejection mailed Mar. 2, 2004; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Non- Final Rejection mailed Aug. 10, 2004; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Examiner Interview Summary Record mailed Sep. 16, 2004; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Non-Final Rejection mailed Jan. 31, 2005; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Examiner Interview Summary Record mailed Mar. 3, 2005;U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Non- Final Rejection mailed May 23, 2005; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Examiner Interview Summary Record mailed Jun. 8, 2005; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant
- Malik; Notice of Allowance and Fees Due mailed Nov. 2, 2005; U.S. Appl. No. 09/725,719, filed Nov. 30, 2000.Applicant