Object oriented mail server framework mechanism

• US 5,768,505 A
• Filed: 12/19/1995
• Issued: 06/16/1998
• Est. Priority Date: 12/19/1995
• Status: Expired due to Term

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Herness, Eric Nels, Romano, George James, Jenney, Eric H., Ripstra, John Christopher, Gilchrist, Frank William
• Primary Examiner(s): Geckil, Mehmet B.
• Application Number:
  US08/574,820
• Time in Patent Office: 910 Days
• Field of Search: 395/200.33, 395/200.6, 395/200.76, 395/683, 395/285, 370/401
• US Class Current: 709/201
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/48 Message addressing, e.g. address format or anonymous messages, aliases
• CPC Class Codes: H04L 69/32 Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/40 Network security protocols

Abstract

A framework for use with object-oriented programming systems provides a common message processing system structure that can be placed on any OOP platform and be configured to support any e-mail message protocol standard or specific mail server function. The framework defines an e-mail message as a number of distinct objects, each of which contains information that describes some portion of the message. All messages received by a system in which the framework is implemented are defined on this core object structure. Another set of objects and methods define the processing steps required for a mail server to process a message. A message is received as a class of message objects, which are assigned a message type that determines the subsequent processing steps to which the message object is subjected. As a message is processed, the objects of which it is comprised are changed, so that the message processing can be interrupted and then resumed without loss or duplication of processing steps.

Claims

1. A computer system comprising:

a central processing unit;

a user interface; and

a main memory having an operating system that supports an object-oriented programming environment containing a framework that provides an extensible network mail server processing system that receives an e-mail message from an originating network user and transfers the e-mail message to one or more destination addresses of network users who are intended recipients of the e-mail message, wherein the framework defines a message center object that controls message processing, a message class that contains a set of message objects that comprise originator, recipient, and message content information contained in the e-mail message, and a set of object methods that are used by the message center object to place the information of the e-mail message into the message objects according to a message processing protocol of the e-mail message and process it accordingly;

wherein the message objects include objects belonging to classes comprising a message originator list that identifies the network address of the originating network user, a recipient list that identifies intended recipients of the e-mail message, and an envelope list that contains message attribute information for a message protocol, such that the mail server processing system can be configured to support a plurality of e-mail message protocol standards or mail server functions.

2. A computer system as defined in claim 1, wherein the class of message originator list comprises objects that define an originating user network address and a message protocol type.

3. A computer system as defined in claim 2, wherein the message protocol type is defined by an originating user network address object.

4. A computer system as defined in claim 1, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

5. A computer system as defined in claim 4, wherein the recipient list objects of the e-mail message specify a plurality of different message protocol types.

6. A computer system as defined in claim 1, wherein the class of envelope list comprises objects that are defined by a message protocol type.

7. A computer system as defined in claim 6, wherein the envelope list objects of the e-mail message specify a plurality of different message protocol types.

8. A computer system as defined in claim 1, wherein the message objects further include objects belonging to an attachment reference class that identifies information attached to the e-mail message.

9. A computer system as defined in claim 8, wherein the attachment reference class objects specify a plurality of different protocol types of the information attached to the e-mail message.

10. A computer system as defined in claim 1, wherein the object methods include message originator list creator methods that create the originator list objects, recipient list creator methods that create the recipient list objects, and envelope list creator methods that create the envelope objects.

11. A computer system as defined in claim 1, wherein the object methods include envelope list creation methods that determine a message protocol type and create a corresponding envelope object.

12. A computer system as defined in claim 11, wherein the object methods further include an add method that places the e-mail message in a message queue for processing by the message center object.

13. A computer system as defined in claim 11, wherein the object methods further include a retrieve method that retrieves the e-mail message from a message queue for processing by the message center object.

14. A computer system as defined in claim 1, wherein the object methods include an address resolution method that determines a recipient user network address for each member of the recipient list class.

15. A computer system as defined in claim 1, wherein the object methods include a security authorization method that performs message security checking and authorization of an e-mail message.

16. A computer system as defined in claim 1, wherein the object methods include an attachment reference list method that creates attachment list objects containing information attached to the e-mail message.

17. A computer system as defined in claim 1, wherein the message objects further include objects belonging to classes comprising a message originator list, original recipient list, recipient list, and envelope list.

18. A computer system as defined in claim 17, wherein the class of original recipient list contains one or more entry objects, each of which contains one or more objects that are defined by a recipient user network address and a distribution type.

19. A computer system as defined in claim 18, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

20. A computer system as defined in claim 19, wherein each recipient user network address specifies a message protocol type.

21. A computer system as defined in claim 19, wherein the message objects include multiple recipient list objects of different message protocols.

22. A computer system as defined in claim 19, wherein the object methods include recipient list resolve methods that create the recipient list objects from the original recipient list entry objects.

23. A computer system as defined in claim 22, wherein the recipient list resolve methods repeatedly operate on the original recipient list entry objects until no additional destination addresses are specified by a distribution type, whereby the distribution type specifies a set of destination addresses corresponding to a single original recipient list entry.

24. A computer system comprising:

a central processing unit;

a user interface;

a network interface through which e-mail messages are received; and

a main memory having an operating system that supports an object-oriented programming environment containing a framework that defines a message center object that controls message processing, a message class that contains a set of message objects that define originator, recipient, and message content information contained in a received e-mail message, and a set of object methods that are used by the message center object to place the information contained in the received e-mail message into the message objects according to a message processing protocol of the e-mail message and process it accordingly;

wherein the message objects include objects belonging to classes comprising a message originator list that identifies the network address of the originating network user, a recipient list that identifies intended recipients of the e-mail message, and an envelope list that contains message attribute information for a message protocol such that the mail server processing system can be configured to support a plurality of e-mail message protocol standards or mail server functions.

25. A computer system as defined in claim 24, wherein the class of message originator list comprises objects that define an originating user network address and a message protocol type.

26. A computer system as defined in claim 25, wherein the message protocol type is defined by an originating user network address object.

27. A computer system as defined in claim 24, wherein the class of recipient list comprises objects that arc defined by a recipient user network address and a recipient address message protocol type.

28. A computer system as defined in claim 27, wherein the recipient list objects of the e-mail message specify a plurality of different message protocol types.

29. A computer system as defined in claim 24, wherein the class of envelope list comprises objects that are defined by a message protocol type.

30. A computer system as defined in claim 29, wherein the envelope list objects of the e-mail message specify a plurality of different message protocol types.

31. A computer system as defined in claim 24, wherein the message objects further include objects belonging to an attachment reference class that identifies information attached to the e-mail message.

32. A computer system as defined in claim 31, wherein the attachment reference class objects specify a plurality of different protocol types of the information attached to the e-mail message.

33. A computer system as defined in claim 24, wherein the object methods include message originator list creator methods that create the originator list objects, recipient list creator methods that create the recipient list objects, and envelope list creator methods that create the envelope objects.

34. A computer system as defined in claim 24, wherein the object methods include envelope list creation methods that determine a message protocol type and create a corresponding envelope object.

35. A computer system as defined in claim 34, wherein the object methods further include an add method that places the e-mail message in a message queue for processing by the message center object.

36. A computer system as defined in claim 34, wherein the object methods further include a retrieve method that retrieves the e-mail message from a message queue for processing by the message center object.

37. A computer system as defined in claim 24, wherein the object methods include an address resolution method that determines a recipient user network address for each member of the recipient list class.

38. A computer system as defined in claim 24, wherein the object methods include a security authorization method that performs message security checking and authorization of an e-mail message.

39. A computer system as defined in claim 24, wherein the object methods include an attachment reference list method that creates attachment list objects containing information attached to the e-mail message.

40. A computer system as defined in claim 24, wherein the message objects further include objects belonging to classes comprising a message originator list, original recipient list, recipient list, and envelope list.

41. A computer system as defined in claim 40, wherein the class of original recipient list contains one or more entry objects, each of which contains one or more objects that are defined by a recipient user network address and a distribution type.

42. A computer system as defined in claim 41, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

43. A computer system as defined in claim 42, wherein each recipient user network address specifies a message protocol type.

44. A computer system as defined in claim 42, wherein the message objects include multiple recipient list objects of different message protocols.

45. A computer system as defined in claim 42, wherein the object methods include recipient list resolve methods that create the recipient list objects from the original recipient list entry objects.

46. A computer system as defined in claim 45, wherein the recipient list resolve methods repeatedly operate on the original recipient list entry objects until no additional destination addresses are specified by a distribution type, whereby the distribution type specifies a set of destination addresses corresponding to a single original recipient list entry.

47. An object oriented framework for use in a computer system connected to a network, the computer system receiving e-mail messages from originating network users and having an operating system that supports an object oriented programming environment that maintains a message center object that controls e-mail message processing, a message class comprising a set of message objects that comprise originator, recipient, and message content information contained in a received e-mail message, and a set of object methods that are used by the message center object to place the information of the received e-mail message into the message objects according to a message processing protocol of the received e-mail message and process it accordingly;

wherein the message class objects include objects belonging to classes comprising a message originator list that identifies the network address of the originating network user, a recipient list that identifies intended recipients of the e-mail message, and an envelope list that contains message attribute information for a message protocol, such that the mail server processing system can be configured to support a plurality of e-mail message protocol standards or mail server functions.

48. A framework as defined in claim 47, wherein the class of message originator list comprises objects that define an originating user network address and a message protocol type.

49. A framework as defined in claim 48, wherein the message protocol type is defined by an originating user network address object.

50. A framework as defined in claim 47, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

51. A framework as defined in claim 50, wherein the recipient list objects of the e-mail message specify a plurality of different message protocol types.

52. A framework as defined in claim 47, wherein the class of envelope list comprises objects that are defined by a message protocol type.

53. A framework as defined in claim 52, wherein the envelope list objects of the e-mail message specify a plurality of different message protocol types.

54. A framework as defined in claim 47, wherein the message objects further include objects belonging to an attachment reference class that identifies information attached to the e-mail message.

55. A framework as defined in claim 54, wherein the attachment reference class objects specify a plurality of different protocol types of the information attached to the e-mail message.

56. A framework as defined in claim 47, wherein the object methods include message originator list creator methods that create the originator list objects, recipient list creator methods that create the recipient list objects, and envelope list creator methods that create the envelope objects.

57. A framework as defined in claim 47, wherein the object methods include envelope list creation methods that determine a message protocol type and create a corresponding envelope object.

58. A framework as defined in claim 57, wherein the object methods further include an add method that places the e-mail message in a message queue for processing by the message center object.

59. A framework as defined in claim 57, wherein the object methods further include a retrieve method that retrieves the e-mail message from a message queue for processing by the message center object.

60. A framework as defined in claim 47, wherein the object methods include an address resolution method that determines a recipient user network address for each member of the recipient list class.

61. A framework as defined in claim 47, wherein the object methods include a security authorization method that performs message security checking and authorization of the e-mail message.

62. A framework as defined in claim 47, wherein the object methods include an attachment reference list method that creates attachment list objects containing information attached to the e-mail message.

63. A framework as defined in claim 47, wherein the message objects further include objects belonging to classes comprising a message originator list, original recipient list, recipient list, and envelope list.

64. A framework as defined in claim 63, wherein the class of original recipient list contains one or more entry objects, each of which contains one or more objects that are defined by a recipient user network address and a distribution type.

65. A framework as defined in claim 64, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

66. A framework as defined in claim 65, wherein each recipient user network address specifies a message protocol type.

67. A framework as defined in claim 65, wherein the message objects include multiple recipient list objects of different message protocols.

68. A framework as defined in claim 65, wherein the object methods include recipient list resolve methods that create the recipient list objects from the original recipient list entry objects.

69. A framework as defined in claim 68, wherein the recipient list resolve methods repeatedly operate on the original recipient list entry objects until no additional destination addresses are specified by a distribution type, whereby the distribution type specifies a set of destination addresses corresponding to a single original recipient list entry.

70. A program product for use in a computer system having an operating system that supports an object-oriented programming environment, the program product comprising:

a recordable media; and

a framework recorded on the recordable media the framework providing an extensible network mail server processing system that receives an e-mail message from an originating network user and transfers the e-mail message to one or more destination addresses of network users who are intended recipients of the e-mail message;

wherein the framework defines a message center object that controls message processing, a message class that contains a set of message objects that comprise originator, recipient, and message content information contained in the e-mail message, and a set of object methods that are used by the message center object to place the information of the e-mail message into the message objects according to a message processing protocol of the e-mail message and process it accordingly; and

wherein the message class objects include objects belonging to classes comprising a message originator list that identifies the network address of the originating network user, a recipient list that identifies intended recipients of the e-mail message, and an envelope list that contains message attribute information for a message protocol, such that the mail server processing system can be configured to support a plurality of e-mail message protocol standards or mail server functions.

71. A program product as defined in claim 70, wherein the class of message originator list comprises objects that define an originating user network address and a message protocol type.

72. A program product as defined in claim 71, wherein the message protocol type is defined by an originating user network address object.

73. A program product as defined in claim 70, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

74. A program product as defined in claim 73, wherein the recipient list objects of the e-mail message specify a plurality of different message protocol types.

75. A program product as defined in claim 70, wherein the class of envelope list comprises objects that are defined by a message protocol type.

76. A program product as defined in claim 75, wherein the envelope list objects of the e-mail message specify a plurality of different message protocol types.

77. A program product as defined in claim 70, wherein the message objects include objects belonging to an attachment reference class that identifies information attached to the e-mail message.

78. A program product as defined in claim 77, wherein the attachment reference class objects specify a plurality of different protocol types of the information attached to the e-mail message.

79. A program product as defined in claim 70, wherein the object methods include message originator list creator methods that create the originator list objects, recipient list creator methods that create the recipient list objects, and envelope list creator methods that create the envelope objects.

80. A program product as defined in claim 70, wherein the object methods include envelope list creation methods that determine a message protocol type and create a corresponding envelope object.

81. A program product as defined in claim 80, wherein the object methods further include an add method that places the e-mail message in a message queue for processing by the message center object.

82. A program product as defined in claim 80, wherein the object methods further include a retrieve method that retrieves the e-mail message from a message queue for processing by the message center object.

83. A program product as defined in claim 70, wherein the object methods include an address resolution method that determines a recipient user network address for each member of the recipient list class.

84. A program product as defined in claim 70, wherein the object methods include a security authorization method that performs message security checking and authorization of the e-mail message.

85. A program product as defined in claim 70, wherein the object methods include an attachment reference list method that creates attachment list objects containing information attached to the e-mail message.

86. A program product as defined in claim 70, wherein the message objects further include objects belonging to classes comprising a message originator list, original recipient list, recipient list, and envelope list.

87. A program product as defined in claim 86, wherein the class of original recipient list contains one or more entry objects, each of which contains one or more objects that are defined by a recipient user network address and a distribution type.

88. A program product as defined in claim 87, wherein the class of recipient list comprises objects that are defined by a recipient user network address and a recipient address message protocol type.

89. A program product as defined in claim 88, wherein each recipient user network address specifies a message protocol type.

90. A program product as defined in claim 88, wherein the message objects include multiple recipient list objects of different message protocols.

91. A program product as defined in claim 88, wherein the object methods include recipient list resolve methods that create the recipient list objects from the original recipient list entry objects.

92. A program product as defined in claim 91, wherein the recipient list resolve methods repeatedly operate on the original recipient list entry objects until no additional destination addresses are specified by a distribution type, whereby the distribution type specifies a set of destination addresses corresponding to a single original recipient list entry.