Method and apparatus for minimizing storage of common attachment files in an e-mail communications server

• US 7,444,382 B2
• Filed: 12/16/2005
• Issued: 10/28/2008
• Est. Priority Date: 11/30/2000
• Status: Expired due to Term

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: AT&T Intellectual Property I LP (AT&T, Inc.)
• Inventors: Malik, Dale W.
• Primary Examiner(s): Vu; Thong H
• Application Number:
  US11/303,839
• Publication Number:
  US 20060095527A1
• Time in Patent Office: 1,047 Days
• Field of Search: 709/203, 709/206, 709/219, 709/207, 707/10, 707/2
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments

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.

Claims

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.