METHOD AND APPARATUS FOR STORING AND DISTRIBUTING ELECTRONIC MAIL

• US 20090132490A1
• Filed: 11/29/2006
• Published: 05/21/2009
• Est. Priority Date: 11/29/2005
• Status: Abandoned Application

• Current Assignee: Coolrock Software Pty Limited
• Original Assignee: Coolrock Software Pty Limited
• Inventors: Okraglik, Henry
• Application Number:
  US12/095,117
• Publication Number:
  US 20090132490A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/42 Mailbox-related aspects, e.g. synchronisation of mailboxes

Abstract

The present invention relates to a method and apparatus for storing and distributing emails. Instead of using the conventional “Inbox” paradigm, all email processed in an organisation is stored in a database. User access to the emails in the database is carried out by utilising search queries based on a high level language, to search the database.

Claims

1. A method of storing and distributing emails in an organisation having a plurality of email users, comprising the steps of storing received emails in a database and distributing emails to users in response to a step of querying of the database, by search queries associated with the users.

2. A method in accordance with claim 1, wherein the step of querying the database is carried out by utilising a database query language.

3. A method in accordance with claim 2, comprising the further step of saving queries expressed in the query language so that the queries may be re-used.

4. A method in accordance with claim 3, comprising the further step of sharing queries between users.

5. A method in accordance with claim 2, comprising the step of providing one or more predefined queries for use by a user.

6. A method in accordance with claim 2, comprising the step of enabling email users to formulate their own queries.

7. A method in accordance with claim 2, wherein queries are able to be combined.

8. A method in accordance with claim 7, wherein queries may be combined in AND/OR/NOT style relationships.

9. A method in accordance with claim 2, wherein the database query language is a high level language that is database agnostic.

10. A method in accordance with claim 2, wherein the database query language has been particularly designed for email searching and retrieval.

11. A method in accordance with claim 2, comprising the step of implementing security by combining a security query with the queries.

12. A method in accordance with claim 2, wherein a query is able to access on behalf of a user all emails available in the database, regardless of the identity of the sender or identity of intended recipient.

13. A method in accordance with claim 2, wherein the step of storing comprises the step of storing emails received by the organisation directed to the organisations users.

14. A method in accordance with claim 13, wherein the step of storing comprises the step of storing emails sent by users within the organisation.

15. A method in accordance with claim 1, wherein emails are stored substantially in real time, when received or sent.

16. A method in accordance with claim 1, wherein the step of storing comprises storing the emails in a location separate from a standard email server processor of the organisation.

17. A method in accordance with claim 1, wherein the step of storing comprises the step of processing the emails to produce query index information.

18. A method in accordance with claim 16, wherein the step of storing comprises the step of storing the query index information in a first sub-database accessible to respond to queries.

19. A method in accordance with claim 18, wherein the step of storing comprises storing email content in a second sub-database.

20. A method in accordance with claim 18, wherein the step of querying is able to request that only query index information may be returned.

21. A method in accordance with claim 1, wherein the database comprises a relational database.

22. A method in accordance with claim 1, wherein the step of storing comprises identifying identical emails and storing only one version of the identical emails.

23. A method in accordance with claim 1, wherein the step of storing comprises identifying identical email attachments and storing only one version of the attachment.

57. A computer program comprising instructions to control a computing system to implement a method in accordance with claim 1.

58. A computer readable medium providing a computer program in accordance with claim 57.

24. A method of storing email received by an organisation, comprising the step of storing the email in relational form.

25. A method in accordance with claim 24, comprising the further step of storing the email substantially in real time as it is received by the organisation.

26. A method in accordance with claim 24, wherein the step of storing the email in relational form comprises the step of processing the emails to provide an index, the index being stored in relational form.

27. A method in accordance with claim 26, wherein the step of storing comprises the step of storing the index separately from email content.

28. A method in accordance with claim 24, wherein the step of storing comprises interfacing with an underlying database architecture via a plug-in type interface which enables different types of database architectures to be used for storage of emails.

59. A computer program comprising instructions for controlling a computer system to implement a method in accordance with claim 24.

60. A computer readable medium providing a computer program in accordance with claim 59.

29. An apparatus for storing and distributing email in an organisation having a plurality of email users, the apparatus comprising a database arranged to receive emails and a distribution means arranged to distribute emails to the email users in response to search queries to the database, the search queries being associated with the email users.

30. An apparatus in accordance with claim 29, further comprising a query means arranged to query the database, the query means utilising a database query language.

31. An apparatus in accordance with claim 30, wherein the query means is arranged to enable queries to be saved so that they may be re-used.

32. An apparatus in accordance with claim 31, wherein the query means is arranged to enable sharing of queries between users.

33. An apparatus in accordance with claim 30, the query means being arranged to enable preparation of pre-defined queries for use by the users.

34. An apparatus in accordance with claim 30, the query means being arranged to enable email users to formulate their own queries.

35. An apparatus in accordance with claim 30, the query means being arranged to enable queries to be combined.

36. An apparatus in accordance with claim 35, wherein the queries are combinable in AND/OR/NOT style relationships.

37. An apparatus in accordance with claim 30, wherein the database query language is a high level language that is database agnostic.

38. An apparatus in accordance with claim 37, wherein the database query language is specifically designed for email searching and retrieval.

39. An apparatus in accordance with claim 30, further comprising a security means, comprising a security query which is arranged to be combined with the search queries to implement security.

40. An apparatus in accordance with claim 29, wherein the query means is able to access all emails available in the database, regardless of the identity of the sender or identity of intended recipient.

41. An apparatus in accordance with claim 29, further comprising storing means, arranged to store in the database any emails received by the organisation directed to the organisation'"'"'s users.

42. An apparatus in accordance with claim 41, wherein the storing means is arranged to store emails sent by users within the organisation.

43. An apparatus in accordance with claim 41, the storing means operating substantially in real time to store emails in the database.

44. An apparatus in accordance with claim 29, wherein the database is in a location separate from a standard email server of the organisation.

45. An apparatus in accordance with claim 29, comprising processing means for processing the email to produce query index information.

46. An apparatus in accordance with claim 45, wherein the database comprises a first sub-database storing the query index information.

47. An apparatus in accordance with claim 46, wherein the database comprises a second sub-database for storing email content.

48. An apparatus in accordance with claim 29, arranged so that only query index information may be returned in response to a query.

49. An apparatus in accordance with claim 29, the database comprising a relational database.

50. An apparatus in accordance with claim 29, the storing means comprising means for comparing emails and determining whether emails are identical, and in response for determination of emails are identical ensuring only one version of the email is stored.

51. An apparatus in accordance with claim 29, wherein the storing means is arranged to determine whether email attachments are identical and ensure that only a single attachment is stored where there are identical attachments.

52. An apparatus for storing email received by an organisation, comprising a relational database arranged to store the emails in relational form.

53. An apparatus in accordance with claim 52, further comprising storing means arranged to store email in the database in real time as it is received by the organisation.

54. An apparatus in accordance with claim 53, further comprising processing means arranged to process the emails to provide an index, the index being stored in the database in relational form.

55. An apparatus in accordance with claim 54, the index being stored separately from the email content in the database.

56. An apparatus in accordance with claim 52, the storing means comprising storage management engine comprising a front-end interface and an architecture which enables the implementation of plug-ins to interface with difference underlying database architectures.