Object oriented mail server framework mechanism

• US 6,081,832 A
• Filed: 05/20/1998
• Issued: 06/27/2000
• 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:
  US09/082,284
• Time in Patent Office: 769 Days
• Field of Search: 709/206, 709/203, 709/207, 709/220, 709/227, 709/228, 709/229, 379/93.01, 379/93.24
• US Class Current: 709/206
• 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 method for distributing a program product, the method comprising the steps of:

establishing a connection between a first computer system and a second computer system over a network; and

transmitting the program product from the first computer system to the second computer system, wherein the program product comprises an object oriented framework that provides an extensible network mail server processing system when executed in an object oriented programming environment of the second computer system, such that the extensible network mail server processing system 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.

2. A method for distributing a program product as defined in claim 1, wherein the framework of the transmitted program product defines a message center object that controls message processing in the second computer system, 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.

3. A method for distributing a program product as defined in claim 2, wherein the message class objects include objects belonging to classes comprising a message originator list that identifies network address of the originating network user, a recipient list that identifies the intended recipients of the e-mail message, and an envelope list that contains message attribute information for a message protocol.

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

5. A method for distributing a program product as defined in claim 4, wherein the message protocol type is defined by an originating user network address object.

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

7. A method for distributing a program product as defined in claim 6, wherein the recipient list objects of the e-mail message specify a plurality of different message protocol types.

8. A method for distributing a program product as defined in claim 3, wherein the class of envelope list comprises objects that are defined by a message protocol type.

9. A method for distributing a program product as defined in claim 8, wherein the envelope list objects of the e-mail message specify a plurality of different message protocol types.

10. A method for distributing a program product as defined in claim 3, wherein the message objects further include objects belonging to an attachment reference class that identifies information attached to the e-mail message.

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

12. A method for distributing a program product as defined in claim 3, wherein the object methods of the program product 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.

13. A method for distributing a program product as defined in claim 3, wherein the object methods of the program product include envelope list creation methods that determine a message protocol type and create a corresponding envelope object.

14. A method for distributing a program product as defined in claim 13, 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.

15. A method for distributing a program product as defined in claim 13, 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.

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

17. A method for distributing a program product as defined in claim 3, wherein the object methods include a security authorization method that performs message security checking and authorization of a message.

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

19. A method for distributing a program product as defined in claim 3, wherein the message objects further include objects belonging to classes comprising a message originator list, original recipient list, recipient list, and envelope list.

20. A method for distributing a program product as defined in claim 19, 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.

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

22. A method for distributing a program product as defined in claim 21, wherein each recipient user network address specifies a message protocol type.

23. A method for distributing a program product as defined in claim 21, wherein the message objects include multiple recipient list objects of different message protocols.

24. A method for distributing a program product as defined in claim 21, wherein the object methods include recipient list resolve methods that create the recipient list objects from the original recipient list entry objects.

25. A method for distributing a program product as defined in claim 24, 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.

26. A method for distributing a program product as defined in claim 1, wherein the framework defines at least one core function that cannot be modified by a user of the framework.