WO2000030009A2

WO2000030009A2 - System and method of augmented messaging toolkit

Info

Publication number: WO2000030009A2
Application number: PCT/US1999/027068
Authority: WO
Inventors: Tyler Peppel; Lowell D. Kaufman
Original assignee: Xoom.Com
Priority date: 1998-11-13
Filing date: 1999-11-12
Publication date: 2000-05-25
Also published as: WO2000030009A3; AU1726500A

Abstract

The invention provides an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user. The toolkit includes a client e-mail interface, a content creation wizard and a content entity.

Description

SYSTEM AND METHOD OF AUGMENTED MESSAGING

TOOLKIT

Technical field

This invention relates to e-mail and other messaging user tools.

Background Art

E-mail and messaging systems have been in use for many years. E-mail specifically, and messaging in general, has proven to be a remarkably useful communication mechanism for a wide diversity of users facing various communication needs.

E-mail began as the ability to transfer plain text from a user to one or more other users. It has evolved to typically include the ability to embed html (Hyper Text Markup Language) commands and the ability to attach files. It is now possible to apply encryption algorithms in a fairly seamless fashion to the contents of e-mail messages. It is further possible to include signature files providing a uniform "signature" which can include stating the user's name, position, company information, contact information etc.. Contemporary e-mail services support maintaining address lists within an "address book", so that specific groups of users may be targeted by a single e-mail broadcast to every user in the address list.

Figure 1 depicts a typical prior art e-mail tool 30 interacting 34 with standard mail services 10 and interacting 32 with a user 20. Standard mail services 10 provide the transfer of messages 34 between e-mail tool 30 operated 32 by users 20. These messages are created, viewed and their storage managed by e-mail tools 30 under the control 32 of users 20.

E-mail tool 30 performs the generation of the message provided 34 as a message to the standard mail service 10. The embedding of text, html, signature files and attachments are all performed by standard e-mail tools 30 to create raw messages. Once created, these raw messages may be further encrypted by e-mail tool 30 before being sent 34 to standard mail services 10.

E-mail tool 30 can often perform a number of tasks to process a received message 34 from standard mail services 10. The received message may be encrypted and e-mail tool 30 may need to decrypt the received message to create a viewable message. The viewable message may further contain html code, which the e-mail tool 30 will interpret to present the hypertext in a viewable manner. The viewable message attachments are presented in some fashion by the e-mail tool 30. Upon user 20 stimulus, e-mail tool 30 may detach the attachments as files in the local file management of the computer running the e-mail tool 30.

These innovations have been significant, but there remain several problems and needs which are not addressed in the prior art. Many users belong to multiple affinity groups and would like to share embedded information regarding those affinity groups. One engineer may be a devoted science fiction fan, specifically an X-files fan. Hyper text links to web-sites for fans would be something such an individual might well wish to include in e-mail to other fans. This same engineer may be an active participant in a professional organization such as the Institute for Electrical and Electronic Engineers (IEEE) and a member of local chapters of several professional societies within the IEEE, say the Communications Society and the Antenna Society. Hypertext to favorite web-sites for local chapter information, or a schedule of upcoming events is desirable to keep other members up to date. This same individual may be a sports fan, seriously dedicated to specific teams or players. Inclusion of sports related information, recent scores or photos of teams or players is desirable.

Contemporary messaging services support this individual being able to target these distinct interests using difference address lists. However contemporary messaging services provide no help in tailoring the content of messages aimed at these distinct interest groups. The user must laboriously develop html code to then be embedded into the text of the message to achieve anything other than an attached file or embedded link. Getting the graphical information to fit is a time-consuming job of matching the pixel sizing of a frame with the html code. What is needed is a tool or toolkit providing messaging users with the ability to customize content layouts, which could be used for a variety of messages.

Many companies expend significant revenue and effort to provide messaging services to their employees and affiliates. This effort does not help a company's marketing and sales effort, as the messages contain little, if anything, related to what the company deems its marketing and/or sales message. What is needed is a mechanism whereby a collection of targeted content templates could be uniformly made available to employees and affiliates to embed not only the personal e-mail message but also the overall corporate message at the same time.

Many advertisers are discovering electronic commerce to be an effective way to market products. Utilizing entertainment fan clubs, sporting team, social, institutional, and professional affiliations in personal e-mails to disseminate an advertising message in a coherent, measurable manner is not possible with the prior art. What is needed is a coherent, measurable manner to disseminate an advertising message using personal e-mail based upon using entertainment, sporting, social, institutional and professional affiliations.

Many advertisers desire to form a mutual branding of trademarked or copyrighted products, images, logos and the like to create a co-branded image. The prior art provides no way for this to be carried out in an efficient manner for advertising embedding content with e-mail. Further, there is no way to monitor licensing fees based upon usage of such agreed upon content. What is needed is a mechanism supporting co-branded advertising embedded content in personal e-mails. Disclosure of the invention

Aspects of this invention solve all the disclosed problems and unanswered needs of the prior art.

One aspect of the invention provides an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from the client user. The toolkit includes a client e-mail interface, a content creation wizard and a content entity.

The client e-mail interface couples the client user to the standard mail service. The client e-mail interface supports client user selectable entities. The content creation wizard couples to the client e-mail interface as one of the client user selectable entities. The content library couples to the client e-mail interface as one of the client user selectable entities. The content library contains at least one content entity coupled to the client e-mail interface as one of the client user selectable entities.

The client user selects the content creation wizard coupled to the client e-mail interface to create a content e-mail template containing at least one client user selectable content site within the content e-mail template. The client user selects a first selectable content entity and a first content site within the content e-mail template to create the content e-mail template with the first content entity at the first content site. The client user uses the content e-mail template to create a first e-mail message sent by the standard mail service from the client user.

This aspect of the invention advantageously provides for the simplified creation of e-mail templates using the content creation wizards with inserted selectable content for messages to be sent to a standard mail service.

Certain embodiments include user created selectable content entities. A further embodiment includes only user created selectable content entities. These embodiments are advantageous for individuals placing classified ads and posting announcements, such as baby pictures, invitations and surveys. A further embodiment incorporates content libraries including selectable content entities. These provide a user-friendly way to organize and make available many content entities.

A further embodiment incorporates customizable content libraries customized by the client user. Embodiments offer the client user increased flexibility and control of their content.

A further embodiment incorporates an administrator, which is sent a subscription message by a client user wishing to subscribe to the augmented mail service. The administrator receives the subscription message and responds to the message. The administrator response includes creating the content creation wizard, content library and client e-mail interface with content creation wizard and content library. The administrator provides a mechanism by which multiple user may be accommodated in terms of setting up accounts, initializing content creation wizards, content libraries and client e- mail interfaces.

A further embodiment incorporates a database under the control of the administrator and from which the content creation wizard, content libraries and client e-mail interface are created upon a client user subscribing. This is advantageous in ordering the initializing of a user subscription.

A further embodiment incorporates a tracking module coupled to the database and responding to commands from the administrator. The client e-mail interface further records with the database every instance of using a content creation wizard template and/or selectable content entity to create a message sent to the standard mail services. The tracking module, responding to administrator requests, queries the database regarding database records of usage and generates a report message to the administrator. This is advantageous in providing exact usage information to content providers such as advertisers. Another aspect of the invention includes a client-server system for a network supporting an augmented messaging toolkit. The augmented messaging toolkit includes a client interface with a selectable content creation wizard a selectable content entity. The client interface uses a standard mail service module. The user operates a client computer communicating via the network to a server system.

The client computer executes program code segments. These program code segments implement the client interface, selection of the selectable content creation wizard, and selection of the selectable content entity.

The server system executes program code segments. These program code segments implement the standard mail service module, the selectable content creation wizard, and the selectable content entity.

This system advantageously provides content creation wizards and selectable content entity capabilities in an augmented messaging toolkit to clients distributed throughout a network. Such capabilities are distributed without any physical delivery, no boxes, CD's, etc. need be received to effect operation.

An embodiment includes use of a web browser on the client computer to execute the client interface. This is advantageous in that many people are already familiar with the basic user interface aspects of such an interface.

A further embodiment includes using a web page to subscribe. Another further embodiment includes using a web page in the client interface. A further embodiment includes the client interface web page originating from the server system. Another further embodiment includes access to the client interface web page being enabled from the server system. Another further embodiment includes the program code segments for the client interface being enabled by the web browser accessing the client interface web page. These embodiments are advantageous in providing consistent, readily accessible, high bandwidth capable avenues for client server interaction in these activities. Another embodiment includes the server system containing a database, which records client subscriptions. A further embodiment includes the client interface recording all sent e-mail in the database. A further embodiment records the click-through from the client interface to the database. These embodiments are advantageous in providing marketing data on which advertisements are being used by which clients, where are they being sent, and the nature of the follow-up activities (or click-through) to these advertisements.

Another further embodiment includes an administrator commanding a tracking module which in turn accesses the database in response to administrator commands to build reports. This embodiment is advantageous in providing the collected marketing data in an organized fashion and also providing a specific point of access to this valuable source of marketing and confidential information. A further embodiment includes the database containing a database engine controlling a mass storage system. This embodiment provides optimal database throughput to handle large numbers of client generated database accesses.

Another further embodiment includes an application server engine executing at least one of the program code segments of the invention of the server system. A further embodiment includes an application server engine executing all of the application program code segments except possibly the standard mail services in the server system. This is advantageous in providing a platform for the program code segments to execute in response to potentially large numbers of tasks large numbers of client would need for support. An alternative embodiment includes an application server engine executing content creation wizard and content entity program code segments. This is advantageous in that it is a simple version of the system suitable for minimal requirement applications.

Another aspect of the invention includes a method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider and a second provider to advertise a shared content to a collection of distributed content agents.

The first provider provides a first content and the second provider provides a second content. The first provider and second provider agree to advertise shared content containing the first content and the second content. Each of the distributed content agents uses at least one content entity and is in communication with the distributed content system.

The method includes the administrator receives message signaling the agreement and the administrator commands the distributed content system to send the shared content to the collection of distributed content agents to be used as a content entity.

This method advantageously enables content providers to carry out an agreement to share a co-branded advertising content being distributed to a collection of distributed content agents by recording the transaction with the administrator. The administrator then directs the distributed content system to carry out distributing the shared content and commanding the use of the shared content.

These and other advantages of the present invention will become apparent upon reading the following detailed descriptions and studying the various figures of the drawings.

Brief Description of the Drawings

Figure 1 depicts a typical prior art e-mail tool interacting with standard mail services and a user;

Figure 2 depicts a system flow diagram using a client e-mail interface 100 a content creation wizard 120 and a content entity 130 in accordance with one aspect of the invention;

Figure 3A depicts a user operational flowchart in accordance with an aspect of the invention; Figure 3 B depicts a software operational flowchart supporting the user operation flowchart of Figure 3A in accordance with an aspect of the invention;

Figure 3C depicts a detail flowchart of operation 312 of Figure 3B supporting the user operation flowchart of Figure 3A in accordance with an aspect of the invention;

Figure 4 depicts a refinement of the system flow diagram of Figure 2 using a client e-mail interface 100 a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention;

Figure 5A depicts a user operational flowchart for selecting a content library and a selectable content entity within the selected content library in accordance with an aspect of the invention;

Figure 5 B depicts a software operational flowchart supporting the user operation flowchart of Figure 5A for selecting a content library and a selectable content entity within the selected content library in accordance with an aspect of the invention;

Figure 6 depicts a refinement of the system flow diagram of Figure 4 incorporating an administrator 150 as well as a client e-mail interface 100 a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention;

Figure 7A depicts a user operational flowchart supporting a user 20 subscribing 24 to the augmented messaging toolkit as discussed in Figure 6 in accordance with an aspect of the invention;

Figure 7B depicts an administrator 150 operational flowchart receiving and responding to a subscription message 24 from user 20 as discussed in Figure 6 in accordance with an aspect of the invention; Figure 7C depicts a detail flowchart of administrator operation 408 of Figure 7B supporting the response to the received subscription message from client user 20 in accordance with an aspect of the invention;

Figure 7D depicts an operational flowchart supporting the client user operations of Figure 7A in which a user 20 subscribing 24 to the augmented messaging toolkit as discussed in Figure 6 in accordance with an aspect of the invention;

Figure 7E depicts an operational flowchart supporting the operations of Figure 7B in which an administrator 150 operational flowchart receiving and responding to a subscription message 24 from user 20 as discussed in Figure 6 in accordance with an aspect of the invention;

Figure 7F depicts a detail flowchart of administrator operation 508 of Figure 7E supporting the response to the received subscription message from client user 20 in accordance with an aspect of the invention;

Figure 8 depicts a refinement of the system flow diagram of Figure 6 incorporating content creation wizard reservoir 170 and content meta-library 160 as well as administrator 150, client e-mail interface 100, a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention;

Figure 9A depicts administrator operations maintaining a content creation wizard reservoir in accordance with an aspect of the invention;

Figure 9B depicts a detail flowchart of operation 432 of Figure 7C where creating a content creation wizard uses the content creation wizard reservoir in accordance with an aspect of the invention;

Figure 9C depicts operations supporting administrator operations of Figure 9A maintaining a content creation wizard reservoir in accordance with an aspect of the invention; Figure 9D depicts a detail flowchart of operation 532 of Figure 7F supporting the creation of a content creation wizard using the content creation wizard reservoir in accordance with an aspect of the invention;

Figure 9E depicts administrator operations maintaining a content meta-library in accordance with an aspect of the invention;

Figure 9F depicts detail flowchart of operation 436 of Figure 7C using the content meta-library to create the selectable content library in accordance with an aspect of the invention;

Figure 9G depicts a detail flowchart of operation 616 of Figure 9F supporting either inserting or coupling the first content entity in accordance with an aspect of the invention.

Figure 9 H depicts an operational flowchart supporting administrator operations of Figure 9E maintaining a content meta-library in accordance with an aspect of the invention;

Figure 91 depicts detail flowchart of operation 536 of Figure 7F using the content meta-library to create the selectable content library in accordance with an aspect of the invention;

Figure 9J depicts a detail flowchart of operation 716 of Figure 91 supporting either inserting or coupling the first content entity in accordance with an aspect of the invention;

Figure 9K depicts a detail flowchart of operation 250 of Figure 7A depicting accessing a subscription web page in accordance with some embodiments of the invention;

Figure 9L depicts a detail flowchart of operation 350 of Figure 7D depicting accessing a subscription web page in accordance with some embodiments of the invention; Figure 9M depicts a flowchart of client e-mail interface 100 coupling 12 standard mail services 10 and user 20 including accessing a client interface web page in accordance with an aspect of the invention;

Figure 9N depicts an operational flowchart of client e-mail interface 100 coupling 12 standard mail services 1 0 and user 20 including supporting accessing a client interface web page in accordance with an aspect of the invention;

Figure 10 depicts a refinement of the system flow diagram of Figure 8 incorporating a data base 180 supporting creation wizard reservoir 170 and content meta-library 160, administrator 150, client e-mail interface 100, a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention;

Figure 11 A depicts a detail flowchart of administrator operation 408 of Figure 7B in which the administrator responds to a subscription message by recording a subscription record in the database based upon the subscription message in accordance with an aspect of the invention;

Figure 11 B depicts a detail flowchart of operation 508 of Figure 7E in which supporting the administrator responding to a subscription message for recording a subscription record in the database based upon the subscription message in accordance with an aspect of the invention;

Figure 110 depicts the client e-mail interface recording a first e-mail message in the database whenever the user sends the first e-mail message to the standard mail service in accordance with an aspect of the invention;

Figure 11 D depicts supporting the client e-mail interface recording a first e- mail message in the database whenever the user sends the first e-mail message to the standard mail service in accordance with an aspect of the invention; Figure 12 depicts a refinement of the system flow diagram of Figure 1 0 incorporating a tracking and gathering data module 190 as well as a data base 180 supporting creation wizard reservoir 170 and content meta-library 160, administrator 150, client e-mail interface 100, a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention;

Figure 13A depicts a flowchart of administrator 150 operations supporting sending a report request to the tracking module 190 and receiving a report message from tracking module 190 in accordance with an aspect of the invention;

Figure 13B depicts a flowchart of tracking module 190 operations supporting receiving a report request from the administrator 150, accessing 194 database 180 and sending a report message to administrator 150 in accordance with an aspect of the invention;

Figure 13C depicts an operational flowchart supporting administrator 150 operations for sending a report request to the tracking module 190 and receiving a report message from tracking module 190 in accordance with an aspect of the invention;

Figure 13D depicts an operational flowchart supporting tracking module 190 operations for receiving a report request from the administrator 150, accessing 194 database 180 and sending a report message to administrator 150 in accordance with an aspect of the invention;

Figure 14 depicts schematically the capabilities of the various embodiments and their advantages compared with standard e-mail tools 20;

Figure 15 depicts client computer 26 communicating 1002 with server system 1000 with client computer 26 executing program code segments and with server system executing program code segments in accordance with an aspect of the invention; Figure 16 depicts a refinement of Figure 15, depicting client computer 26 communicating 1002 with server system 1000 communicating 2002 application server engine 2000, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments in accordance with an aspect of the invention;

Figure 17 depicts a refinement of Figure 15, depicting client computer 26 communicating 1002 with server system 1000, with client computer 26 executing program code segments including executing a web browser, which in turn executes the client e-mail interface program code segment and with server system executing program code segments in accordance with an aspect of the invention;

Figure 18 depicts a refinement of Figure 17, depicting client computer 26 communicating 1002 with server system 1000, with client computer 26 executing program code segments, with server system executing program code segments including maintaining the client e-mail interface in accordance with an aspect of the invention;

Figure 19 depicts a refinement of Figure 18, depicting client computer 26 communicating 1002 with server system 1000, with client computer 26 executing program code segments, with server system executing program code segments including client interface web page in accordance with an aspect of the invention;

Figure 20 depicts a refinement of Figure 19, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000, with client computer 26 executing program code segments, with server system executing program code segments in accordance with an aspect of the invention;

Figure 21 depicts a refinement of Figure 20, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200, with client computer 26 executing program code segments, with server system executing program code segments in accordance with an aspect of the invention;

Figure 22 depicts a refinement of Figures 21 and 16, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments in accordance with an aspect of the invention;

Figure 23 depicts a refinement of Figure 22, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments in accordance with an aspect of the invention;

Figure 24 depicts a refinement of Figure 21 , depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments in accordance with an aspect of the invention;

Figure 25 depicts a refinement of Figure 24, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments including several additional or altered program codes segments in accordance with an aspect of the invention;

Figure 26 depicts a refinement of Figures 24 and 22, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments including several additional or altered program codes segments in accordance with an aspect of the invention;

Figure 27 depicts a systems block diagram of the interactions between two intellectual property providers sharing intellectual property content using an administrator of a distributed content system to control distribution of the shared intellectual property content to distributed content agents in accordance with an aspect of the invention;

Figure 28 depicts a user view of a client user login and subscription web page in accordance with an aspect of the invention;

Figure 29A depicts a user view of a client e-mail interface web page in accordance with an aspect of the invention;

Figure 29B depicts a user view of a client e-mail interface in accordance with an aspect of the invention;

Figure 30 depicts a user view of an e-mail composition page showing letterheads (content creation wizards) and selectable content in accordance with an aspect of the invention;

Figure 31 depicts a user view of a client e-mail interface web page viewing a content rich message in accordance with an aspect of the invention;

Figure 32 depicts a user view of an administrator report request form in accordance with an aspect of the invention; Figure 33 depicts a user view of a client e-mail interface web page for a consumer affiliated with a fan club in accordance with an aspect of the invention;

Figure 34 depicts a user view of a client e-mail interface web page for a consumer affiliated with a special interest group in accordance with an aspect of the invention;

Figure 35 depicts a user view of a client e-mail interface web page for a consumer affiliated with a business concern in accordance with an aspect of the invention;

Figure 36 depicts a user view of a client e-mail interface web page for a consumer affiliated with a family in accordance with an aspect of the invention;

Figure 37 depicts a user view of a client e-mail interface web page for a consumer affiliated with business in accordance with an aspect of the invention;

Figure 38 depicts a user view of an e-mail composition page showing letterheads (content creation wizards) and selectable content and further possessing controls for display of stock tickers and site links and displaying stock ticker and site link in accordance with an aspect of the invention;

Figure 39 depicts a user view of an e-mail composition page showing letterheads (content creation wizards) and selectable content and further possessing controls for display of stock tickers and site links and not displaying stock ticker and site link in accordance with an aspect of the invention;

Figure 40 depicts a user view of a site link editor in accordance with an aspect of the invention;

Figure 41 depicts a user view of a survey editor in accordance with an aspect of the invention; Figure 42 depicts a user view of a survey editor editing a survey in accordance with an aspect of the invention;

Figure 43 depicts a user view of a site link editor adding a new site link in accordance with an aspect of the invention;

Figure 44 depicts a user view of a site link editor editing a new site link in accordance with an aspect of the invention;

Figure 45 depicts a user view of a site link editor in accordance with an aspect of the invention;

Figure 46 depicts a user view of an administrator interface web page in accordance with an aspect of the invention;

Figure 47 depicts a user view of an administrator interface web page for controlling user access to the augmented toolkit in accordance with an aspect of the invention;

Figure 48 depicts a portion of the background controls indicating selection of no background image library;

Figure 49 depicts a portion of the background controls indicating selection of the drink background image library previewed showing the drink advertisement;

Figure 50 depicts a portion of the background controls indicating selection of a background to be seen in the composition view, when it will start being used and when it will stop being used;

Figure 51 depicts a portion of the background controls indicating selection of a background to be seen in the composition view and the time intervals between its use; and

Figure 52 depicts a portion of the background controls indicating selection of a background to be seen in the composition view and the number of times it is to be used before the default background will again be used. Detailed Description of the Invention

Figure 1 depicts a typical prior art e-mail tool interacting with standard mail services and a user previously discussed in the background.

Figure 2 depicts a system flow diagram using a client e-mail interface 100 a content creation wizard 120 and a content entity 130 in accordance with one aspect of the invention.

User 20 is coupled 22 with client e-mail interface 100, which interacts 12 with standard mail services 10. Client e-mail interface 100 is coupled 122 to content creation wizard 120 as a user selectable entity, so that user 20 can select the content creation wizard 120 to create a message template. Client e- mail interface 100 is coupled 132 to content entity 130 as a user selectable entity, which further contains at least one user selectable content entity.

In certain embodiments, client e-mail interface 100 is a computer program executing on a client computer operated by user 20. In certain embodiments, client e-mail interface is a web page accessed by user 20 using a browser. In certain embodiments, client e-mail interface 100 executes within a browser as a collection of program code segments incorporating a portable computing language. In certain further embodiments, the portable computing language is related to JAVA. In other further embodiments, the portable computing language is related to HTML. In other further embodiments, the portable computing language is related to VRML. In other further embodiments, the program code segments executed within the browser to implement the client e-mail interface 100 may be from more than one portable computing language. In certain embodiments, at least one of the program code segments executed within the browser to implement the client e-mail interface 100 may be executable native code.

In certain embodiments, there are multiple content creation wizards 120. In certain embodiments, user access to one or more content creation wizards may be organized in collections of content creation wizards. In certain further embodiments, these collections may be accessed as folders or directories. In certain further embodiments, the folders or directories may be nested to create folders within folders or directories within directories.

Certain embodiments include user created selectable content entities. A further embodiment includes only user created selectable content entities. These embodiments are advantageous for individuals placing classified ads and posting announcements, such as baby pictures, invitations and surveys.

Figure 3A depicts a user operational flowchart in accordance with an aspect of the invention.

User operation 200 starts the usage of this flowchart. Arrow 202 directs the usage flow from user operation 200 to user operation 204. User operation 204 performs the client user selecting the content creation wizard coupled to the client e-mail interface creating a content e-mail template containing at least one client user selectable content site within the content e-mail template. Arrow 206 directs usage from user operation 204 to user operation 208. User operation 208 terminates the usage of this flowchart.

Arrow 210 directs the usage flow from user operation 200 to user operation 212. User operation 212 performs the client user selecting a first of the client user selectable content entities and the client user selecting a first of the client user selectable content sites within the content e-mail template to create the content e-mail template with the first content entity at the first content site. Arrow 214 directs usage from user operation 212 to user operation 208. User operation 208 terminates the usage of this flowchart.

Arrow 220 directs the usage flow from user operation 200 to user operation 222. User operation 222 performs the client user using the content e-mail template to create a first e-mail message sent by the standard mail service from the client user. Arrow 224 directs usage from user operation 222 to user operation 208. User operation 208 terminates the usage of this flowchart. Figure 3B depicts a software operational flowchart supporting the user operational flowchart in Figure 3A in accordance with an aspect of the invention.

Operation 300 starts the operations of this flowchart. Arrow 302 directs the flow of execution from operation 300 to operation 304. Operation 304 performs determining the client user selection of the content creation wizard coupled to the client e-mail interface to create a content e-mail template containing at least one client user selectable content site within the content e- mail template. Arrow 306 directs execution from operation 304 to operation 308. Operation 308 terminates the operations of this flowchart.

Arrow 310 directs the flow of execution from starting operation 300 to operation 312. Operation 312 performs determining the client user selection of a first of the client user selectable content entities and determining the client user selection of a first of the client user selectable content sites within the content e-mail template to create the content e-mail template with the first content entity at the first content site. Arrow 314 directs execution from operation 312 to operation 308. Operation 308 terminates the operations of this flowchart.

Arrow 320 directs the flow of execution from starting operation 300 to operation 322. Operation 322 performs supporting the client user using the content e-mail template to create a first e-mail message sent by the standard mail service from the client user. Arrow 324 directs execution from operation 322 to operation 308. Operation 308 terminates the operations of this flowchart.

Figure 3C depicts a detail flowchart of operation 312 of Figure 3B supporting the user operation flowchart of Figure 3A in accordance with an aspect of the invention.

Arrow 340 directs the flow of execution from starting operation 312 to operation 342. Operation 342 performs determining the client user selection of a first of the client user selectable content entities. Arrow 344 directs execution from operation 342 to operation 346. Operation 346 performs determining the client user selection of a first of the client user selectable content sites within the content e-mail template. Arrow 348 directs execution from operation 346 to operation 350. Operation 350 performs creating the content e-mail template with the first content entity at the first content site. Arrow 352 directs execution from operation 350 to operation 354. Operation 354 terminates the operations of this flowchart.

As in Figure 2, user 20 is coupled 22 with client e-mail interface 100, which interacts 12 with standard mail services 10. Client e-mail interface 100 is coupled 122 to content creation wizard 120 as a user selectable entity, so that user 20 can select the content creation wizard 120 to create a message template. Client e-mail interface 100 is coupled 132 to content entity 130 as a user selectable entity, which further contains at least one user selectable content entity.

In addition to Figure 2, content entity 130 is coupled 134 to content library 140 which is also coupled 142 to client e-mail interface 100 as a user selectable entity. In certain embodiments of the invention, content entity 130 may be directly user selectable 132 at all times. In certain other embodiments, content entity 130 is only selectable 134 based upon the selection 142 of content library 140.

Figure 5A depicts a user operational flowchart for selecting a content library and a selectable content entity within the selected content library in accordance with an aspect of the invention. Arrow 230 directs the usage flow from starting user operation 200 to user operation 232. User operation 232 performs the client user selecting a first of the client user selectable content entities of the content library. Arrow 234 directs usage from user operation 232 to user operation 236. User operation 236 terminates the usage of this flowchart.

Arrow 240 directs the usage flow from user operation 200 to user operation 242. User operation 242 performs the client user selecting the content library containing the first client user selectable content entity. Arrow 244 directs usage from user operation 242 to user operation 236. User operation 236 terminates the usage of this flowchart.

Note that in certain embodiments, the client user may only be able to select the first content entity when the content library it belongs to is selected. In certain other embodiments, the first content entity may be either directly selectable, or selectable when a specific content library containing it is selected.

Figure 5 B depicts a software operational flowchart supporting the user operation flowchart of Figure 5A for selecting a content library and a selectable content entity within the selected content library in accordance with an aspect of the invention.

Operation 360 starts the operations of this flowchart. Arrow 362 directs the flow of execution from operation 360 to operation 364. Operation 364 performs determining the client user selecting the content library containing the first client user selectable content entity. Arrow 366 directs execution from operation 364 to operation 368. Operation 368 performs determining the client user selecting a first of the client user selectable content entities of the content library. Arrow 370 directs execution from operation 368 to operation 372. Operation 372 terminates the operations of this flowchart.

Figure 6 depicts a refinement of the system flow diagram of Figure 4 incorporating an administrator 150 as well as a client e-mail interface 100 a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention.

As in Figures 2 and 4, user 20 is coupled 22 with client e-mail interface 100, which interacts 12 with standard mail services 10. Client e-mail interface 100 is coupled 122 to content creation wizard 120 as a user selectable entity, so that user 20 can select the content creation wizard 120 to create a message template. Client e-mail interface 100 is coupled 132 to content entity 130 as a user selectable entity, which further contains at least one user selectable content entity.

As in Figure 4, content entity 130 is coupled 134 to content library 140 which is also coupled 142 to client e-mail interface 100 as a user selectable entity. In certain embodiments of the invention, content entity 130 may be directly user selectable 132 at all times. In certain other embodiments, content entity 130 is only selectable 134 based upon the selection 142 of content library 140.

In addition to Figures 2 and 4, administrator 150 is coupled 152 to standard mail services 10. Client user 20 subscribes to the augmented toolkit, which creates and sends a message 24 based upon the client user 20 to the administrator 150. Administrator 150 receives the message 24 and responds by performing the following: Administrator 150 creates 124 at least one client selectable content creation wizard 120. Administrator 150 creates 144 at least one client user selectable content library 140. Administrator 150 creates 102 the client e-mail interface 100 supporting client user selectable entities including client selectable 122 content creation wizard 120 and client selectable 142 content library 140.

Figure 7A depicts a user operational flowchart supporting a user 20 subscribing 24 to the augmented messaging toolkit as discussed in Figure 6 in accordance with an aspect of the invention. User operation 250 starts the usage of this flowchart. Arrow 252 directs the usage flow from user operation 250 to user operation 254. User operation 254 performs the client user 20 creating a subscription message. Arrow 256 directs usage from user operation 254 to user operation 258. User operation 258 performs the client user 20 sending 24 the subscription message to the administrator 150. Arrow 260 directs usage from user operation 258 to user operation 262. User operation 262 terminates the usage of this flowchart.

Figure 7B depicts an administrator 150 operational flowchart receiving and responding to a subscription message 24 from user 20 as discussed in Figure 6 in accordance with an aspect of the invention.

Administrator operation 400 starts the usage of this flowchart. Arrow 402 directs the usage flow from administrator operation 400 to administrator operation 404. Administrator operation 404 performs the administrator 150 receiving the subscription message 24 from the client user 20. Arrow 406 directs usage from administrator operation 404 to administrator operation 408. Administrator operation 408 performs the administrator 150 responding to the received subscription message. Arrow 410 directs usage from administrator operation 408 to administrator operation 412. Administrator operation 412 terminates the usage of this flowchart.

Figure 7C depicts a detail flowchart of administrator operation 408 of Figure 7B supporting the response to the received subscription message from client user 20 in accordance with an aspect of the invention.

Arrow 430 directs the usage flow from starting administrator operation 408 to administrator operation 432. Administrator operation 432 performs creating 124 the client user selectable content creation wizard 120. Arrow 434 directs usage from administrator operation 432 to administrator operation 436. Administrator operation 436 performs creating 144 the client user selectable content library 140 comprised 134 of at least one client user selectable content entity 130. Arrow 438 directs usage from administrator operation 436 to administrator operation 440. Administrator operation 440 performs creating 102 the client e-mail interface 100 coupling 22 the client user 20 to 1 2 the standard mail service 10 and the client e-mail interface supporting client user selectable entities including the client user selectable 122 content creation wizard 120 and the client user selectable 142 content library 140. Arrow 442 directs usage from administrator operation 440 to administrator operation 444. Administrator operation 444 terminates the usage of this flowchart.

Figure 7D depicts an operational flowchart supporting the client user operations of Figure 7A in which a user 20 subscribing 24 to the augmented messaging toolkit as discussed in Figure 6 in accordance with an aspect of the invention.

Operation 350 starts the operations of this flowchart. Arrow 352 directs the flow of execution from operation 350 to operation 354. Operation 354 performs supporting the client user creating a subscription message. Arrow 356 directs execution from operation 354 to operation 358. Operation 358 performs supporting the client user sending the subscription message to the administrator. Arrow 360 directs execution from operation 358 to operation 362. Operation 362 terminates the operations of this flowchart.

Figure 7E depicts an operational flowchart supporting the operations of Figure 7B in which an administrator 150 operational flowchart receiving and responding to a subscription message 24 from user 20 as discussed in Figure 6 in accordance with an aspect of the invention.

Operation 500 starts the operations of this flowchart. Arrow 502 directs the flow of execution from operation 500 to operation 504. Operation 504 performs supporting the administrator receiving the subscription message from the client user. Arrow 506 directs execution from operation 504 to operation 508. Operation 508 performs supporting the administrator responding to the received subscription message. Arrow 510 directs execution from operation 508 to operation 512. Operation 512 terminates the operations of this flowchart. Figure 7F depicts a detail flowchart of administrator operation 508 of Figure 7E supporting the response to the received subscription message from client user 20 in accordance with an aspect of the invention.

Arrow 530 directs the flow of execution from starting operation 508 to operation 532. Operation 532 performs supporting creating the client selectable content creation wizard. Arrow 534 directs execution from operation 532 to operation 536. Operation 536 performs supporting creating the client selectable content library. Arrow 538 directs execution from operation 536 to operation 540. Operation 540 performs supporting creating the client e-mail interface coupling the client user to the standard mail service and the client e-mail interface supporting client user selectable entities including the client selectable content creation wizard and the client selectable content library. Arrow 542 directs execution from operation 540 to operation 544. Operation 544 terminates the operations of this flowchart.

As in Figures 2, 4 and 6, user 20 is coupled 22 with client e-mail interface 100, which interacts 12 with standard mail services 10. Client e-mail interface 100 is coupled 122 to content creation wizard 120 as a user selectable entity, so that user 20 can select the content creation wizard 120 to create a message template. Client e-mail interface 100 is coupled 132 to content entity 130 as a user selectable entity, which further contains at least one user selectable content entity.

As in Figures 4 and 6, content entity 130 is coupled 134 to content library 140 which is also coupled 142 to client e-mail interface 100 as a user selectable entity. In certain embodiments of the invention, content entity 130 may be directly user selectable 132 at all times. In certain other embodiments, content entity 130 is only selectable 134 based upon the selection 142 of content library 140.

As in Figure 6, administrator 150 is coupled 152 to standard mail services 10. Client user 20 subscribes to the augmented toolkit, which creates and sends a message 24 based upon the client user 20 to the administrator 150. Administrator 150 receives the message 24 and responds by performing the following: Administrator 150 creates 124 at least one client selectable content creation wizard 120. Administrator 150 creates 144 at least one client user selectable content library 140. Administrator 150 creates 102 the client e-mail interface 100 supporting client user selectable entities including client selectable 122 content creation wizard 120 and client selectable 142 content library 140.

In addition to Figures 2, 4 and 6, administrator 150 communicates 154 with content creation wizard reservoir 170 and communicates 156 with content meta-library 160. The creation 124 of content creation wizard 120 includes 172 selection 154 of at least one content creation wizard of content creation wizard reservoir 170. The creation 144 of content library 140 includes 162 selection 156 of at least one content entity contained in content meta-library 160.

Figure 9A depicts administrator operations maintaining a content creation wizard reservoir in accordance with an aspect of the invention.

Administrator operation 460 starts the usage of this flowchart. Arrow 462 directs the usage flow from administrator operation 460 to administrator operation 464. Administrator operation 464 performs the administrator further maintaining a content creation wizard reservoir comprised of at least one content creation wizard. Arrow 466 directs usage from administrator operation 464 to administrator operation 468. Administrator operation 468 terminates the usage of this flowchart. Figure 9B depicts a detail flowchart of operation 432 of Figure 7C where creating a content creation wizard uses the content creation wizard reservoir in accordance with an aspect of the invention.

Arrow 480 directs the usage flow from starting user operation 432 to user operation 482. User operation 482 performs selecting a first of the content creation wizards from the content creation wizard reservoir. Arrow 484 directs usage from user operation 482 to user operation 486. User operation 486 performs coupling the first content creation wizard to the client e-mail interface to create the first client selectable content creation wizard. Arrow 488 directs usage from user operation 486 to user operation 490. User operation 490 terminates the usage of this flowchart.

Figure 9C depicts operations supporting administrator operations of Figure 9A maintaining a content creation wizard reservoir in accordance with an aspect of the invention.

Operation 560 starts the operations of this flowchart. Arrow 562 directs the flow of execution from operation 560 to operation 564. Operation 564 performs supporting the administrator maintaining a content creation wizard library comprised of at least one content creation wizard. Arrow 566 directs execution from operation 564 to operation 568. Operation 568 terminates the operations of this flowchart.

Figure 9D depicts a detail flowchart of operation 532 of Figure 7F supporting the creation of a content creation wizard using the content creation wizard reservoir in accordance with an aspect of the invention.

Arrow 580 directs the flow of execution from starting operation 532 to operation 582. Operation 582 performs supporting selecting a first of the content creation wizards from the content creation wizard library. Arrow 584 directs execution from operation 582 to operation 586. Operation 586 performs supporting coupling the first content creation wizard to the client e- mail interface to create the first client selectable content creation wizard. Arrow 588 directs execution from operation 586 to operation 590. Operation 590 terminates the operations of this flowchart.

Figure 9E depicts administrator operations maintaining a content meta-library in accordance with an aspect of the invention.

Administrator operation 600 starts the usage of this flowchart. Arrow 602 directs the usage flow from administrator operation 600 to administrator operation 604. Administrator operation 604 performs the administrator further maintaining a content meta-library comprised of at least one content entity. Arrow 606 directs usage from administrator operation 604 to administrator operation 608. Administrator operation 608 terminates the usage of this flowchart.

Figure 9F depicts detail flowchart of operation 436 of Figure 7C using the content meta-library to create the selectable content library in accordance with an aspect of the invention.

Arrow 610 directs the usage flow from starting administrator operation 432 to administrator operation 612. Administrator operation 612 performs selecting a first of the content entities from the content meta-library to create a first content entity. Arrow 614 directs usage from administrator operation 612 to administrator operation 616. Administrator operation 616 performs using the first content entity to create the client selectable library. Arrow 618 directs usage from administrator operation 616 to administrator operation 620. Administrator operation 620 terminates the usage of this flowchart.

Arrow 630 directs the usage flow from starting administrator operation 616 to administrator operation 632. Administrator operation 632 performs inserting the first content entity into the client selectable content library to create a client selectable content entity. Arrow 634 directs usage from administrator operation 632 to administrator operation 636. Administrator operation 636 terminates the usage of this flowchart.

Arrow 640 directs the usage flow from administrator operation 616 to administrator operation 642. Administrator operation 642 performs coupling the first content entity to the client e-mail interface to create a client administrator selectable content entity coupled to the client e-mail interface. Arrow 644 directs usage from administrator operation 642 to administrator operation 636. Administrator operation 636 terminates the usage of this flowchart.

Figure 9 H depicts an operational flowchart supporting administrator operations of Figure 9E maintaining a content meta-library in accordance with an aspect of the invention.

Operation 700 starts the operations of this flowchart. Arrow 702 directs the flow of execution from operation 700 to operation 704. Operation 704 performs supporting the administrator maintaining a content meta-library comprised of at least one content entity. Arrow 706 directs execution from operation 704 to operation 708. Operation 708 terminates the operations of this flowchart.

Figure 91 depicts detail flowchart of operation 536 of Figure 7F using the content meta-library to create the selectable content library in accordance with an aspect of the invention.

Arrow 710 directs the flow of execution from starting operation 536 to operation 712. Operation 712 performs supporting selecting a first of the content entities from the content meta-library to create a first content entity. Arrow 714 directs execution from operation 712 to operation 716. Operation 716 performs supporting using the first content entity to create the client selectable library. Arrow 718 directs execution from operation 716 to operation 720. Operation 720 terminates the operations of this flowchart. Figure 9J depicts a detail flowchart of operation 716 of Figure 91 supporting either inserting or coupling the first content entity in accordance with an aspect of the invention.

Arrow 730 directs the flow of execution from starting operation 716 to operation 732. Operation 732 performs supporting inserting the first content entity into the client selectable content library to create a client selectable content entity. Arrow 734 directs execution from operation 732 to operation 736. Operation 736 terminates the operations of this flowchart.

Arrow 740 directs the flow of execution from starting operation 716 to operation 742. Operation 742 performs supporting coupling the first content entity to the client e-mail interface to create a client user selectable content entity coupled to the client e-mail interface. Arrow 744 directs execution from operation 742 to operation 736. Operation 736 terminates the operations of this flowchart.

Figure 9K depicts a detail flowchart of operation 250 of Figure 7A depicting accessing a subscription web page in accordance with some embodiments of the invention.

Arrow 650 directs the usage flow from starting user operation 250 to user operation 652. User operation 652 performs accessing a subscription web page. Arrow 654 directs usage from user operation 652 to user operation 656. User operation 656 terminates the usage of this flowchart.

Figure 9L depicts a detail flowchart of operation 350 of Figure 7D depicting accessing a subscription web page in accordance with some embodiments of the invention.

Arrow 750 directs the flow of execution from starting operation 350 to operation 752. Operation 752 performs supporting accessing a subscription web page. Arrow 754 directs execution from operation 752 to operation 756. Operation 756 terminates the operations of this flowchart. Figure 9M depicts a user flowchart of client e-mail interface 100 coupling 12 standard mail services 10 and user 20 including accessing a client interface web page in accordance with an aspect of the invention.

Arrow 670 directs the usage flow from starting user operation 12 to user operation 672. User operation 672 performs the client user accessing a client e-mail interface web page. Arrow 674 directs usage from user operation 672 to user operation 676. User operation 676 terminates the usage of this flowchart.

Figure 9N depicts an operational flowchart of client e-mail interface 100 coupling 12 standard mail services 10 and user 20 including supporting accessing a client interface web page in accordance with an aspect of the invention.

Arrow 750 directs the flow of execution from starting operation 12 to operation 752. Operation 752 performs supporting the client user accessing a client e- mail interface web page. Arrow 754 directs execution from operation 752 to operation 756. Operation 756 terminates the operations of this flowchart.

Figure 10 depicts a refinement of the system flow diagram of Figure 8 incorporating a data base 180 supporting creation wizard reservoir 170 and content meta-library 160, administrator 150, client e-mail interface 100, a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention.

As in Figures 2, 4, 6 and 8, user 20 is coupled 22 with client e-mail interface 100, which interacts 12 with standard mail services 10. Client e-mail interface 100 is coupled 122 to content creation wizard 120 as a user selectable entity, so that user 20 can select the content creation wizard 120 to create a message template. Client e-mail interface 100 is coupled 132 to content entity 130 as a user selectable entity, which further contains at least one user selectable content entity. As in Figures 4, 6 and 8, content entity 130 is coupled 134 to content library 140 which is also coupled 142 to client e-mail interface 100 as a user selectable entity. In certain embodiments of the invention, content entity 130 may be directly user selectable 1 32 at all times. In certain other embodiments, content entity 130 is only selectable 134 based upon the selection 142 of content library 140.

As in Figures 6 and 8, administrator 150 is coupled 152 to standard mail services 10. Client user 20 subscribes to the augmented toolkit, which creates and sends a message 24 based upon the client user 20 to the administrator 150. Administrator 150 receives the message 24 and responds by performing the following: Administrator 150 creates 124 at least one client selectable content creation wizard. Administrator 150 creates 144 at least one client user selectable content library 140. Administrator 150 creates 102 the client e-mail interface 100 supporting client user selectable entities including client selectable 122 content creation wizard 120 and client selectable 142 content library 140.

As in Figure 8, administrator 150 communicates 154 with content creation wizard reservoir 170 and communicates 156 with content meta-library 160. The creation 124 of content creation wizard 120 includes 172 selection 154 of at least one content creation wizard of content creation wizard reservoir 170. The creation 144 of content library 140 includes 162 selection 156 of at least one content entity contained in content meta-library 160.

In addition to Figures 2, 4, 6 and 8, database 180 communicates 182 with administrator 150. At the direction 182 of administrator 150, database 180 maintains 126 content creation wizard 120, maintains 144 content library 140 including 134 content entity 130 and generates 104 client e-mail interface 100.

In certain further embodiments, as directed 182 by administrator 150, database 180 maintains content creation wizard reservoir 170. Creating 172 content creation wizard 120 is performed as operations 174 upon database 180 and content creation wizard reservoir 170.

In certain further embodiments, as directed 182 by administrator 150, database 180 maintains 164 content meta-library 160, which contains content entities. Creating 162 content library 140 is performed as operations 164 upon database 180 and content meta-library 160.

Figure 11 A depicts a detail flowchart of administrator operation 408 of Figure 7B in which the administrator responds to a subscription message by recording a subscription record in the database based upon the subscription message in accordance with an aspect of the invention.

Arrow 690 directs the usage flow from starting user operation 408 to user operation 692. User operation 692 performs the administrator recording in the database to create a client subscription record based upon the received subscription record. Arrow 694 directs usage from user operation 692 to user operation 696. User operation 696 terminates the usage of this flowchart.

Figure 11 B depicts a detail flowchart of operation 508 of Figure 7E in which supporting the administrator responding to a subscription message for recording a subscription record in the database based upon the subscription message in accordance with an aspect of the invention.

Arrow 790 directs the flow of execution from starting operation 508 to operation 792. Operation 792 performs supporting the administrator recording in the database to create a client subscription record based upon the received subscription record. Arrow 794 directs execution from operation 792 to operation 796. Operation 796 terminates the operations of this flowchart.

Figure 11C depicts the client e-mail interface recording a first e-mail message in the database whenever the user sends the first e-mail message to the standard mail service in accordance with an aspect of the invention. Operation 800 starts the operations of this flowchart. Arrow 802 directs the flow of execution from operation 800 to operation 804. Operation 804 performs whenever the client user sends the first e-mail message to the standard mail service from the client e-mail interface. Arrow 806 directs execution from operation 804 to operation 808. Operation 808 performs the client e-mail interface recording a first e-mail message in the database as a first e-mail record associated with the subscription record of the client user. Arrow 810 directs execution from operation 808 to operation 812. Operation 812 terminates the operations of this flowchart.

Figure 11 D depicts supporting the client e-mail interface recording a first e- mail message in the database whenever the user sends the first e-mail message to the standard mail service in accordance with an aspect of the invention.

Operation 900 starts the operations of this flowchart. Arrow 902 directs the flow of execution from operation 900 to operation 904. Operation 904 performs whenever the client user sends the first e-mail message to the standard mail service from the client e-mail interface. Arrow 906 directs execution from operation 904 to operation 908. Operation 908 performs supporting the client e-mail interface recording a first e-mail message in the database as a first e-mail record associated with the subscription record of the client user. Arrow 910 directs execution from operation 908 to operation 912. Operation 912 terminates the operations of this flowchart.

Figure 12 depicts a refinement of the system flow diagram of Figure 1 0 incorporating a tracking and gathering data module 190 as well as a data base 180 supporting creation wizard reservoir 170 and content meta-library 160, administrator 150, client e-mail interface 100, a content creation wizard 120 and a content library 134 including a content entity 130 in accordance with one aspect of the invention.

As in Figures 2, 4, 6, 8 and 1 0, user 20 is coupled 22 with client e-mail interface 100, which interacts 12 with standard mail services 10. Client e-mail interface 100 is coupled 122 to content creation wizard 120 as a user selectable entity, so that user 20 can select the content creation wizard 120 to create a message template. Client e-mail interface 100 is coupled 132 to content entity 130 as a user selectable entity, which further contains at least one user selectable content entity.

As in Figures 4, 6, 8 and 10, content entity 130 is coupled 134 to content library 140 which is also coupled 142 to client e-mail interface 100 as a user selectable entity. In certain embodiments of the invention, content entity 130 may be directly user selectable 1 32 at all times. In certain other embodiments, content entity 130 is only selectable 134 based upon the selection 142 of content library 140.

As in Figures 6, 8 and 10, administrator 150 is coupled 152 to standard mail services 10. Client user 20 subscribes to the augmented toolkit, which creates and sends a message 24 based upon the client user 20 to the administrator 150. Administrator 150 receives the message 24 and responds by performing the following: Administrator 150 creates 124 at least one client selectable content creation wizard. Administrator 150 creates 144 at least one client user selectable content library 140. Administrator 150 creates 102 the client e-mail interface 100 supporting client user selectable entities including client selectable 122 content creation wizard 120 and client selectable 142 content library 140.

As in Figures 8 and 1 0, administrator 150 communicates 154 with content creation wizard reservoir 170 and communicates 156 with content meta- library 160. The creation 124 of content creation wizard 120 includes 172 selection 154 of at least one content creation wizard of content creation wizard reservoir 170. The creation 144 of content library 140 includes 162 selection 156 of at least one content entity contained in content meta-library 160.

As in Figure 10, database 180 communicates 182 with administrator 150. At the direction 182 of administrator 150, database 180 maintains 126 content creation wizard 120, maintains 144 content library 140 including 134 content entity 130 and generates 104 client e-mail interface 100.

In addition to Figures 2, 4, 6, 8 and 1 0, tracking/gathering data 190 communicates 192 with administrator 150 and is coupled 194 with database 180.

In certain embodiments, client e-mail interface 100 upon sending 1 2 a message using a template provided by content creation wizard 120 will record 104 in database 180 the usage of the content creation wizard 120 in database 180. Tracking/gatheringdata 190 will review 194 such records and generate a message 192 tracking such usage to administrator 150.

In certain further embodiments, client e-mail interface 100 upon sending 12 a message using a template provided by content creation wizard 120 with a content site containing a selected content entity 130 will record 104 in database 180 the usage of the content creation wizard 120 and content entity 130 in database 180. Tracking/gatheringdata 190 will review 194 such records and generate a message 192 tracking such usage to administrator 150.

In certain embodiments, administrator 150 will request 192 a specific collection of one or more queries 194 of database 180 be performed by 190 and a reporting message sent 192 to administrator 150 of the results of the performed queries.

MightyMail™ is an embodiment of the invention. MightyMail™ allows branding and suggestive content to be placed within person-to-person e-mail that is sent by individuals to individuals. This is made possible by the introduction of compelling, affinity based content (pictures, links, audio, or video) and end- user content creation tools (classified ads, calendars, surveys) which are embedded in customizable "letterheads." These letterheads are known elsewhere in this document as templates. By pollinating millions of viral e- mail messages with personalized rich content, MightyMail's mission is simple but ambitious: to become the standard platform for rich e-mail services.

Figure 13A depicts a flowchart of administrator 150 operations supporting sending a report request to the tracking module 190 and receiving a report message from tracking module 190 in accordance with an aspect of the invention.

Administrator operation 810 starts the usage of this flowchart. Arrow 812 directs the usage flow from administrator operation 810 to administrator operation 814. Administrator operation 814 performs the administrator sending the tracking module a report request message. Arrow 816 directs usage from administrator operation 814 to administrator operation 818. Administrator operation 818 performs the administrator receiving from the tracking module a report message based upon the report request message. Arrow 820 directs usage from administrator operation 818 to administrator operation 822. Administrator operation 822 terminates the usage of this flowchart.

Figure 13B depicts a flowchart of tracking module 190 operations supporting receiving a report request from the administrator 150, accessing 194 database 180 and sending a report message to administrator 150 in accordance with an aspect of the invention.

Tracking module operation 830 starts the usage of this flowchart. Arrow 832 directs the usage flow from tracking module operation 830 to tracking module operation 834. Tracking module operation 834 performs the tracking module receiving the report request message from the administrator to create a received report request message. Arrow 836 directs usage from tracking module operation 834 to tracking module operation 838. Tracking module operation 838 performs the tracking module accessing the database based upon the received report request message to create the report message. Arrow 840 directs usage from tracking module operation 838 to tracking module operation 842. Tracking module operation 842 performs the tracking module sending the report message to the administrator. Arrow 844 directs usage from tracking module operation 842 to tracking module operation 846. Tracking module operation 846 terminates the usage of this flowchart.

Figure 13C depicts an operational flowchart supporting administrator 150 operations for sending a report request to the tracking module 190 and receiving a report message from tracking module 190 in accordance with an aspect of the invention.

Operation 910 starts the operations of this flowchart. Arrow 912 directs the flow of execution from operation 910 to operation 914. Operation 914 performs supporting the administrator sending the tracking module a report request message. Arrow 916 directs execution from operation 914 to operation 918. Operation 918 performs supporting the administrator receiving from the tracking module a report message based upon the report request message. Arrow 920 directs execution from operation 918 to operation 922. Operation 922 terminates the operations of this flowchart.

Figure 13D depicts an operational flowchart supporting tracking module 190 operations for receiving a report request from the administrator 150, accessing 194 database 180 and sending a report message to administrator 150 in accordance with an aspect of the invention.

Operation 930 starts the operations of this flowchart. Arrow 932 directs the flow of execution from operation 930 to operation 934. Operation 934 performs supporting the tracking module receiving the report request message from the administrator to create a received report request message. Arrow 936 directs execution from operation 934 to operation 938. Operation 938 performs supporting the tracking module accessing the database based upon the received report request message to create the report message. Arrow 940 directs execution from operation 938 to operation 942. Operation 942 performs supporting the tracking module sending the report message to the administrator. Arrow 944 directs execution from operation 942 to operation 946. Operation 946 terminates the operations of this flowchart. Figure 14 depicts schematically the capabilities of the various embodiments and compares them with standard e-mail tools 20.

Box 990 depicts the functionality of standard mail services, which include the ability to create, send and read standard text e-mail with attachments.

Box 992 depicts the functionality of content libraries 140, including but not limited to promotions, graphics, games and links that can be easily integrated into a personal "letterhead library."

Box 994 depicts the functionality of content creation wizards 120 which include but are not limited to simplified creation of e-mail-ready classified ads, surveys, forms, business cards, letterhead, schedules, etc..

Box 996 depicts the functionality of tracking/gathering data 199 including but are not limited to complete tracking of e-mail account activity, mail content choices, user inputs, and mail impressions/click-through.

Box 998 depicts the functionality of administrator 150 including but are not limited to the ability to dynamically administer content and features within an e-mail "letterhead" for one or many e-mail accounts.

Figure 15 depicts client computer 26 communicating 1002 with server system 1000 with client computer 26 executing program code segments and with server system 1000 executing program code segments in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 1128 a program code segment for content creation wizard 1120. The server system 1000 executes 1 1 38 a program code segment for content entity 1 1 30. In certain embodiments, these program code segments are all in the same computer language. In other embodiments, differing computer languages are used to implement program code segments. The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1124. The client computer 26 executes 1 102 a program code segment for client e-mail interface 1100. The client computer 26 executes 1132 a program code segment for selecting content entity 1134. In certain embodiments, these program code segments are all in the same computer language. In other embodiments, differing computer languages are used to implement program code segments.

Figure 16 depicts a refinement of Figure 15, depicting client computer 26 communicating 1 002 with server system 1000 communicating 2002 application server engine 2000, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The application server engine 2000 executes 1126 a program code segment for content creation wizard 1120. The application server engine 2000 executes 1136 a program code segment for content entity 1130. In certain embodiments, these program code segments are all in the same computer language. In other embodiments, differing computer languages are used to implement program code segments.

The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1 124. The client computer 26 executes 1102 a program code segment for client e-mail interface 1100. The client computer 26 executes 1132 a program code segment for selecting content entity 1134. In certain embodiments, these program code segments are all in the same computer language. In other embodiments, differing computer languages are used to implement program code segments.

Figure 17 depicts a refinement of Figure 15, depicting client computer 26 communicating 1002 with server system 1000, with client computer 26 executing program code segments including executing a web browser, which in turn executes the client e-mail interface program code segment and with server system executing program code segments in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 1128 a program code segment for content creation wizard 1120. The server system 1000 executes 1138 a program code segment for content entity 1130.

The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1 124. The client computer 26 executes 1 132 a program code segment for selecting content entity 1134.

Previously, the client computer 26 executed 1102 a program code segment for client e-mail interface 1100. In this embodiment, this is effected by client computer 26 executing 1022 a program code segment for a web browser 1020, which in turn executes 1104 a program code segment implementing client e-mail interface 1100.

Figure 18 depicts a refinement of Figure 17, depicting client computer 26 communicating 1002 with server system 1000, with client computer 26 executing program code segments, with server system executing program code segments including maintaining the client e-mail interface in accordance with an aspect of the invention.

Additionally, server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110.

The client computer 26 executing 1022 a program code segment for a web browser 1020, which in turn executes 1 104 a program code segment implementing client e-mail interface 1100. The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1124. The client computer 26 executes 1132 a program code segment for selecting content entity 1134.

Figure 19 depicts a refinement of Figure 18, depicting client computer 26 communicating 1002 with server system 1000, with client computer 26 executing program code segments, with server system executing program code segments including client interface web page in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 1128 a program code segment for content creation wizard 1120. The server system 1000 executes 1138 a program code segment for content entity 1130. The server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110.

Additionally, server system 1000 executes 2108 a program code segment for client interface web page 2100.

Figure 20 depicts a refinement of Figure 19, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000, with client computer 26 executing program code segments, with server system executing program code segments in accordance with an aspect of the invention. Additionally, server system 1000 is coupled 3004 to database 3000. The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 1128 a program code segment for content creation wizard 1120. The server system 1000 executes 1138 a program code segment for content entity 1130. The server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110. The server system 1000 executes 2108 a program code segment for client interface web page 2100.

The client computer 26 executing 1022 a program code segment for a web browser 1020 , which in turn executes 1104 a program code segment implementing client e-mail interface 1100. The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1124. The client computer 26 executes 1132 a program code segment for selecting content entity 1134.

Figure 21 depicts a refinement of Figure 20, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200, with client computer 26 executing program code segments, with server system executing program code segments in accordance with an aspect of the invention.

The server system 1000 is coupled 3004 to database 3000, and additionally coupled 3004 to database engine 3100. Database engine 3100 accesses 3102 mass storage system 3200. In certain embodiments, database engine 3100 is a single computer. In certain other embodiments, database engine 3100 is a fault tolerant computer. In certain other embodiments, database engine 3100 is a redundant, fault tolerant computer. In certain other embodiments, database engine 3100 is a load balancing, redundant, fault tolerant computer system.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 1128 a program code segment for content creation wizard 1120. The server system 1000 executes 1138 a program code segment for content entity 1130. The server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110. The server system 1000 executes 2108 a program code segment for client interface web page 2100.

Figure 22 depicts a refinement of Figures 21 and 16, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments in accordance with an aspect of the invention.

Application server engine 2000 communicates 2002 with server system 1000. Application server engine 2000 communicates 3002 with database 3000 and additionally communicates 3004 to database engine 3100. In certain embodiments, application server engine 2000 is a single computer. In certain other embodiments, application server engine 2000 is a fault tolerant computer. In certain other embodiments, application server engine 2000 is a redundant, fault tolerant computer. In certain other embodiments, application server engine 2000 is a load balancing, redundant, fault tolerant computer system.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110.

The application server engine 2000 executes 1126 a program code segment for content creation wizard 1 120. The application server engine 2000 executes 1136 a program code segment for content entity 1130. The application server engine 2000 executes 2106 a program code segment for client interface web page 2100.

Figure 23 depicts a refinement of Figure 22, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments in accordance with an aspect of the invention.

The server system 1000 is coupled 3004 to database 3000, and additionally coupled 3004 to database engine 3100. Database engine 3100 accesses 3102 mass storage system 3200. Mass storage system 3200 further communicates with backup system 3300. In certain embodiments, database engine 3100 is a single computer. In certain other embodiments, database engine 3100 is a fault tolerant computer. In certain other embodiments, database engine 3100 is a redundant, fault tolerant computer. In certain other embodiments, database engine 3100 is a load balancing, redundant, fault tolerant computer system.

The application server engine 2000 executes 1126 a program code segment for content creation wizard 1120. The application server engine 2000 executes 1 136 a program code segment for content entity 1130. The application server engine 2000 executes 2106 a program code segment for client interface web page 2100.

The client computer 26 executing 1022 a program code segment for a web browser 1020, which in turn executes 1104 a program code segment implementing client e-mail interface 1100. The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1124. The client computer 26 executes 1132 a program code segment for selecting content entity 1134. Figure 24 depicts a refinement of Figure 21 , depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110. The server system 1000 executes 1128 a program code segment for content creation wizard 1120. The server system 1000 executes 1138 a program code segment for content entity 1130. The server system 1000 executes 2108 a program code segment for client interface web page 2100.

The client computer 26 executing 1022 a program code segment for a web browser 1020 , which in turn executes 1 104 a program code segment ιm plementing client e-mail interface 1100. The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1124. The client computer 26 executes 1132 a program code segment for selecting content entity 1134.

Figure 25 depicts a refinement of Figure 24, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments including several additional or altered program codes segments in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010. The server system 1000 executes 2118 a program code segment maintaining the client e-mail interface 2110. The server system 1000 executes 1 128 a program code segment for content creation wizard 1120. The server system 1000 executes 1138 a program code segment for content entity 1130. The server system 1000 executes 2108 a program code segment for client interface web page 2100.

Additionally, server system 1000 executes 1158 a program code segment for administrator 1150. The server system 1000 executes 1198 a program code segment for tracking/gathering data 1190.

The client computer 26 executing 1022 a program code segment for a web browser 1020 , which in turn executes 1 104 a program code segment implementing client e-mail interface 1100. The client computer 26 executes 1122 a program code segment for selecting content creation wizard 1124. The client computer 26 executes 1132 a program code segment for selecting content entity 1134. Figure 26 depicts a refinement of Figures 24 and 22, depicting client computer 26 communicating 1002 with server system 1000 coupled 3004 to database 3000 further containing database engine 3100 coupled 3102 to mass storage system 3200 further coupled 3302 to backup system 3300, with client computer 26 executing program code segments, with server system executing program code segments and with application server engine executing program code segments including several additional or altered program codes segments in accordance with an aspect of the invention.

The server system 1000 executes 1018 a program code segment for standard mail services 1010.

The application server engine 2000 executes 2116 a program code segment maintaining the client e-mail interface 2110. The application server engine 2000 executes 1126 a program code segment for content creation wizard and further reservoir 1122. The application server engine 2000 executes 1136 a program code segment for content entity and further meta-library 1132. The application server engine 2000 executes 2106 a program code segment for client interface web page 2100. The application server engine 2000 executes 1156 a program code segment for administrator 1150. The application server engine 2000 executes 1196 a program code segment for tracking/gathering data 1190.

Certain embodiments run on an Oracle database and Unix OS. All the application code is written using Java Servlets running on a servlet enabled web server. The Application uses a three-tiered architecture common to most internet applications: an interface layer, an application layer, and a database layer. In addition, certain embodiments use a custom mail agent that links into a standard Mail Transfer Agent. In certain embodiments, this custom mail agent will be able to be used by any standard mail protocol if one wants a separate application running within their own mail environment.

The interface layer runs on a web server and consists of HTML files. The HTML files use standard HTML plus javascript calls. Each affinity group has its own set of HTML files, .jpg images, and .gif images. There is also a common directory of HTML and gif files.

The division of files across affinity groups makes it easier to brand many sites. Branded areas of HTML and images can easily be changed as an affinity group's content is added or changed. A new directory is created for each affinity group with the specific branded files re-created in these directories. When a bug or change is made to one HTML file, this change needs to be made on all the affinity groups. This can become a large issue as more and more affinity groups are introduced. A custom tool has been built to address this. Thus, one master change is made and all files are altered accordingly.

There is one set of Java Servlets running on an application layer that serves all affinity groups. The servlets implement all application needs:

The mail environment servlets handle all the mail operations for the application. This involves all the major functions excluding the specific augmented toolkit tools functions.

For certain embodiments, message handling servlets manage incoming and outgoing messages. A message is sent through standard mail transport agents (SMTP for outgoing messages and pop3 for incoming messages). For managing incoming messages we use a commercial Post Office mail transfer agent, plus a custom built agent which takes a message, parses it, and dumps different parts of the message into the database. Other message handling operations include deleting messages or saving them to specified folders.

The folder servlets allow messages to be managed by users. This includes the ability to store messages into default folders (inbox, saved, sent, trash, etc.), but also allows users to create folders themselves. There's no limit to the number of subfolders a user can create. Other folder handling operations include deleting and moving folders.

The mail compose servlets allow a mail message to be constructed and integrate the body of a message with the augmented toolkit tools that are active for that message. The message is assembled as a multipart MIME message (MIME is the internet mail standard for adding multimedia and other formats for mail besides text). The MIME message consists of a plain text part (which allows non-HTML clients to still read the text message) and the HTML part of the message. In addition, the mail compose servlets enable attachments to be added to the message (again, constructed as a MIME type email).

For certain embodiments, tool servlets provide the rich mail functionality for the augmented toolkit application. Examples of tools include adding images, letterheads, surveys, games, etc. to outgoing emails. In certain further embodiments, while each tool consists of specific servlet code, these principles apply to all tool servlets:

In certain embodiments, all tools have some general properties: The tools are tied into the database with a specific tool ID. The tools also are classified by certain general properties. For example, some tools fall under the category of "Image-Text-Link." These are basic multimedia object tools that can be added to an email and don't require interactivity from the recipient of the email (except for a simple hypertext link). Another category is "Form Tool." Something like a survey or a quiz game falls under this category. A form tool is one that requires some interactivity (not unlike an HTML form) by the mail recipient.

In certain embodiments, all tools are tied into a user profile: One important feature with the database structure is the ability to map tools to user profiles. A permissions feature determines which tools a user has access to (defined by an affinity group administrator). Also, states of tool use can be saved by users so they can reuse old versions of tool instances.

Registration/Login: One key part of the application is caching the application as much as possible. Certain embodiments cache the most common HTML and image files. In certain further embodiments, large scale data is also cached. All data is stored in the database. Mail message header information, mail body information, user information - all this is stored in the database. Thus, the database architecture is an extremely vital part of the application.

The database schema revolves around two important pieces of data; the GROUP and the TOOL. The GROUP is the data structure of the customer and the user. The data consists of a tree structure where the highest level of the tree is the customer.

In certain embodiments, a customer consists of one or more affinity groups, and an affinity group consists of one or more users. Each member of this tree structure utilizes a permission. A permission simply describes the level of control that group member is allowed. An administrator privilege, for example, allows that group member to create and delete users or affinity groups, and has access to adding or deleting all tools.

In certain embodiments, the TOOL is the data involving MightyMail tools. In certain further embodiments, there are only a few generic tools that can create many specific tools. For example, a survey tool (one that allows a survey to be embedded in an email) is really a member of a form tool. A form tool has certain properties that the survey tool may share. A survey tool, in addition to form tool properties, also contains its own special properties. Such embodiment architectures are an object oriented design approach.

In certain embodiments, the ability to perform database analysis is a critical component of the Company's strategy, and mail account behaviors will be closely monitored. These include total messages sent from a an augmented toolkit site, messages per affinity group, messages sent per client, messages sent as part of "incentive programs", and usage of specific features. Certain embodiments work with data mining vendors (e.g. Epiphany, Personify) to insure that the architecture yields robust reporting data that can be linked with client-based "opt in" data and other inputs. This data will enable real-time direct marketing Return On Investment (ROI) reports. In certain embodiments, the application tracks both web use and message/tool use. The web use is calculated via standard log checking. More interesting is the tracking of mail message use. Certain embodiments keep track of the number of times a message is used, a tool is used, a click- through of a received message is used, etc.

As previously mentioned, all usage actions are stored in the database, thus permitting a plethora of reporting options. Reports can be generated based on users, affinity groups, or customers, as well as the usage of all the customers. Reports can be viewed based on history over any specified time. Reports can also be generated to show comparisons of where the heaviest usage is coming from - to quickly determine the most popular tools, letterheads, affinity groups, etc.

Figure 27 depicts a systems block diagram of the interactions between two intellectual property providers sharing intellectual property content using an administrator of a distributed content system to control distribution of the shared intellectual property content to distributed content agents in accordance with an aspect of the invention.

Provider A 4000 is the intellectual property owner 4002 of content A 4010. Provider A 4000 communicates 4004 with administrator 4200. Provider B 4100 is the intellectual property owner 4102 of content B 4110. Provider b 4100 communicates 4104 with administrator 4200.

Provider A 4000 and Provider B 4100 agree to advertise a shared content 4210 containing 4012 content A 4010 and containing 4112 content B 4110 in the distributed content system 4300 containing a collection of communicating distributed content agents 4310, 4320, 4330 and 4340.

Administrator 4200 is signaled regarding the agreement to advertise shared content 4210. Administrator 4200 commands distributed content system 4300 for the distributed content agents 4310, 4320, 4330 and 4340 to use the shared content 4210 as indicated by arrows 4314, 4324, 4334 and 4344 respectively.

In certain embodiments, administrator 4200 receives message signaling the agreement and administrator 4200 commands 4204 the distributed content system 4300 to send the shared content 4210 to the collection of distributed content agents to be used as a content entity.

In certain further embodiments, the distributed content system 4300 creates 4312 distributed content agent 4310 of the collection of the distributed content agents. Administrator 4200 commands 4204 the distributed content system 4300 to create 4312 the distributed content agent 4310 using 4313 the shared content 4210.

In certain further embodiments, the distributed content system 4300 maintains 4312 distributed content agent 4320 of the collection of the distributed content agents. Administrator 4200 commands 4204 the distributed content system 4300 to update 4322 the distributed content agent 4320 using 4324 the shared content 4210.

In certain further embodiments, the distributed content system 4300 creates 4312 distributed content agent 4310 of the collection of the distributed content agents. Administrator 4200 commands 4204 the distributed content system 4300 to create the distributed content agent 4310 using 4314 the shared content 4210 for use as the content entity.

In certain further embodiments, the distributed content system 4300 creates 4332 distributed content agent with client messaging interface 4330 of the collection of the distributed content agent with client messaging interfaces. Administrator 4200 commands 4204 the distributed content system 4300 to create the distributed content agent with client messaging interface 4330 using 4334 the shared content 4210 for use with client messaging interface as a selectable content entity. In further embodiments, distributed content agent with messaging interface 4330 includes an e-mail interface. In further embodiments, distributed content agent with messaging interface 4340 includes a video messaging interface.

In certain embodiments, administrator 4200 directs 4204 distributed content system 4300 to use a specific letterhead or messaging template as the default letterhead or messaging template, in accordance with certain aspects of the invention.

In certain embodiments, the administrator 4200 creates a default letterhead message designating a first letterhead. The administrator 4200 commanding 4204 the distributed content system 4300 to send the default letterhead message designating the first letterhead to the collection of distributed content agents to be used as the default message composing letterhead. The distributed content system 4300 sending the default letterhead message designating the first letterhead to the collection of distributed content agents to be used as the default message composing letterhead. Each of the collection of distributed content agents receiving the default letterhead message designating the first letterhead. Each of the collection of distributed content agents responding to the received default letterhead message designating the first letterhead.

Figure 28 depicts a user view of a client user login and subscription web page in accordance with an aspect of the invention. Note that in certain embodiments, two distinct web pages may be used to effect entry by existing users and subscribe new users.

Figure 29A depicts a user view of a client e-mail interface web page in accordance with an aspect of the invention. Note that in certain embodiments, voice actuation rather than click-able buttons may be used to implement user selections. In certain other embodiments, the display may be a multi-dimensional virtual image display, rather than a flat-screen image display. In certain other embodiments, the display of information may be effected acoustically, by audio announcing of the title and sender of received messages.

In certain other embodiments, video message toolkits, capable of receiving and transmitting video sequences and requiring a user interface may well have a user interface similar to this. Note that in certain further embodiments, the video interface may present a virtual sense of reality, embodying a stereoscopic sense of the visual imagery.

Figure 29B depicts a user view of a client e-mail interface in accordance with an aspect of the invention. Note that in certain embodiments, voice actuation rather than click-able buttons may be used to implement user selections. In certain other embodiments, the display may be a multi-dimensional virtual image display, rather than a flat-screen image display. In certain other embodiments, the display of information may be effected acoustically, by audio announcing of the title and sender of received messages.

Figure 30 depicts a user view of an e-mail composition page showing letterheads (content creation wizards) and selectable content in accordance with an aspect of the invention. Note that in certain embodiments, voice actuation rather than click-able buttons may be used to implement user selections. In certain other embodiments, the display may be a multidimensional virtual image display, rather than a flat-screen image display. In certain other embodiments, the display of information may be effected acoustically, by audio announcing of the title and sender of received messages. Figure 31 depicts another user view of a client e-mail interface web page viewing a content rich message in accordance with an aspect of the invention. Note that in certain embodiments, voice actuation rather than click-able buttons may be used to implement user selections. In certain other embodiments, the display may be a multi-dimensional virtual image display, rather than a flat-screen image display. In certain other embodiments, the display of information may be effected acoustically, by audio announcing of the title and sender of received messages.

Figure 32 depicts a user view of an administrator report request form in accordance with an aspect of the invention. The report request includes request fields for tracking the number of click-throughs per letterhead, report date, specific customers, letterheads to be accessed, letterheads sent per customer group, letterheads sent per customer, most and least used letterheads used per customer and per group.

Figure 33 depicts a user view of a client e-mail interface web page for a consumer affiliated with a fan club in accordance with an aspect of the invention. Figure 34 depicts a user view of a client e-mail interface web page for a consumer affiliated with a special interest group in accordance with an aspect of the invention. Figure 35 depicts a user view of a client e-mail interface web page for a consumer affiliated with a business concern in accordance with an aspect of the invention. Figure 36 depicts a user view of a client e-mail interface web page for a consumer affiliated with a family in accordance with an aspect of the invention. Figure 37 depicts a user view of a client e-mail interface web page for a consumer affiliated with business in accordance with an aspect of the invention. Features of these figures include embedded designations of affiliations, logos of affiliated groups and companies, links to favored sites, pictures (content entities placed at content sites in the letterhead). Additional features include stock tickers featuring real-time stock quotes. Figure 38 depicts a user view of an e-mail composition page showing letterheads (content creation wizards) and selectable content and further possessing controls for display of stock tickers and site links and displaying stock ticker and site link in accordance with an aspect of the invention. Figure 39 depicts a user view of an e-mail composition page showing letterheads (content creation wizards) and selectable content and further possessing controls for display of stock tickers and site links and not displaying stock ticker and site link in accordance with an aspect of the invention.

The background referred to in the box at left in both Figures 38 and 39 includes the background of this web page, the placement of various content entities, such as the advertisement, stock ticker and site link.

Figure 40 depicts a user view of a site link editor in accordance with an aspect of the invention. Figure 43 depicts a user view of a site link editor adding a new site link in accordance with an aspect of the invention. Figure 44 depicts a user view of a site link editor editing a new site link in accordance with an aspect of the invention.

Figure 41 depicts a user view of a survey editor in accordance with an aspect of the invention. Figure 42 depicts a user view of a survey editor editing a survey in accordance with an aspect of the invention.

Figure 45 depicts another user view of a site link editor in accordance with an aspect of the invention. This view displays a collection of standard site links as prototypes for client customizable content libraries.

Figure 46 depicts a user view of an administrator interface web page in accordance with an aspect of the invention. A primary link is the accounts link, supporting creating and managing. Another link is the tools link, supporting previewing and selecting tools from the augmented messaging toolkit for use by clients at the direction of the administrator. Figure 47 depicts a user view of an administrator interface web page for controlling user access to the augmented toolkit in accordance with an aspect of the invention. This is another administrator view of the accounts link.

Figure 48 depicts a portion of the background controls indicating selection of no background image library. Figure 49 depicts a portion of the background controls indicating selection of the drink background image library previewed showing the drink advertisement. Figure 50 depicts a portion of the background controls indicating selection of a background to be seen in the composition view, when it will start being used and when it will stop being used. Figure 51 depicts a portion of the background controls indicating selection of a background to be seen in the composition view and the time intervals between its use. Figure 52 depicts a portion of the background controls indicating selection of a background to be seen in the composition view and the number of times it is to be used before the default background will again be used.

Because these letterheads are server-based, they can be administered and tracked from any computer that has access to the web.

MightyMail begins each customer relationship with an evaluation of the customer's audience, potential for viral growth and any other issues unique to the customer needs. Then a market test is performed on a sample of the customer's audience to get a sense of unique audience behaviors and make an estimate of the number of accounts needed by the customer prior to a full- scale launch.

The preceding embodiments have been provided by way of example and are not meant to constrain the scope of the following claims.

Claims

1 . An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user comprising: a client e-mail interface coupling said client user to said standard mail service and said client e-mail interface supporting client user selectable entities; a content creation wizard coupled to said client e-mail interface as one of said client user selectable entities; at least one content entity coupled to said client e-mail interface as one of said client user selectable entities; wherein said client user selecting said content creation wizard coupled to said client e-mail interface creates a content e-mail template containing at least one client user selectable content site within said content e-mail template; wherein said client user selecting a first of said client user selectable content entities and said client user selecting a first of said client user selectable content sites within said content e-mail template creates said content e-mail template with said first content entity at said first content site; and wherein said client user using said content e-mail template creates a first e-mail message for said standard mail service from said client user.

2. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 1 ; further comprising at least one content library comprising at least one user selectable content entity coupled to said client e-mail interface as one of said client user selectable entities; wherein said client user selecting a first of said client user selectable content entities of said content library is based upon said client user selecting said content library.

3. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 2; further comprising an administrator coupled to said standard mail services; wherein said client user subscribing to said augmented messaging toolkit includes; said client user creating a subscription message; and said client user sending said subscription message to said administrator; wherein said administrator initiating a subscription for said client user includes; said administrator receiving said subscription message from said client user; and said administrator responding to said received subscription message.

4. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 3; wherein said administrator responding to said received subscription message includes; creating said client user selectable content creation wizard; creating said client user selectable content library comprised of at least one client user selectable content entity; and creating said client e-mail interface coupling said client user to said standard mail service and said client e-mail interface supporting client user selectable entities including said client user selectable content creation wizard and said client user selectable content library.

5. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 4; wherein said administrator further maintains a content creation wizard reservoir comprised of at least one content creation wizard; and wherein creating said first client selectable content creation wizards comprises selecting a first of said content creation wizards from said content creation wizard reservoir; and coupling said first content creation wizard to said client e-mail interface to create said first client selectable content creation wizard.

6. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 4; wherein said administrator further maintains a content meta-library comprised of at least one content entity; and wherein creating said client selectable content library comprises: selecting a first of said content entities from said content meta-library to create a first content entity; and using said first content entity to create said client selectable library further comprising at least one of the collection comprising: inserting said first content entity into said client selectable content library to create a client selectable content entity; and coupling said first content entity to said client e-mail interface to create a client user selectable content entity coupled to said client e-mail interface.

7. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 4; further comprising a database; wherein said administrator responding to said received subscription message further includes said administrator recording in said database to create a client subscription record of said client user based upon said received subscription record.

8. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 7; wherein said client e-mail interface recording a first e-mail message in said database as a first e-mail record associated with said subscription record of said client user said whenever said client user sends said first e-mail message to said standard mail service from said client e-mail interface.

9. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 7; further comprising a tracking module accessing said database and communicating with said administrator; and wherein said administrator sends said tracking module a report request message; and wherein said administrator receives from said tracking module a report message based upon said report request message; and wherein said tracking module receives said report request message from said administrator to create a received report request message; wherein said tracking module accesses said database based upon said received report request message to create said report message; and wherein said tracking module sends said report message to said administrator.

10. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 3; wherein said client user subscribes to said augmented messaging toolkit includes accessing a subscription web page.

11. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 3; wherein said client e-mail interface coupling said client user to said standard mail service includes said client user accessing a client e-mail interface web page.

12. An augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 11 ; wherein said administrator creates said client e-mail interface by providing said client user access to said web e-mail interface page.

13. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user containing a client e-mail interface coupling said client user to said standard mail service and said client e-mail interface supporting client user selectable entities, a content creation wizard coupled to said client e-mail interface as one of said client user selectable entities and at least one content entity coupled to said client e-mail interface as one of said client user selectable entities, comprising: said client user selecting said content creation wizard coupled to said client e-mail interface creates a content e-mail template containing at least one client user selectable content site within said content e-mail template; said client user selecting a first of said client user selectable content entities and said client user selecting a first of said client user selectable content sites within said content e-mail template to create said content e-mail template with said first content entity at said first content site; and said client user using said content e-mail template to create a first e- mail message for said standard mail service from said client user.

14. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 13; wherein said client user selectable content entities are organized into at least one content library comprising at least one user selectable content entity coupled to said client e-mail interface as one of said client user selectable entities; wherein said client user selecting a first of said client user selectable content entities of said content library further comprises said client user selecting said content library containing said first client user selectable content entity.

15. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 14; wherein said augmented messaging toolkit further comprises an administrator coupled to said standard mail services; further comprising said client user subscribing to said augmented messaging toolkit includes; said client user creating a subscription message; and said client user sending said subscription message to said administrator; and further comprising said administrator initiating a subscription for said client user includes; said administrator receiving said subscription message from said client user; and said administrator responding to said received subscription message.

16. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 15; wherein said administrator responding to said received subscription message includes; creating said client selectable content creation wizard; creating said client selectable content library; and creating said client e-mail interface coupling said client user to said standard mail service and said client e-mail interface supporting client user selectable entities including said client selectable content creation wizard and said client selectable content library.

17. A method of using an augmented messaging toolkit inter acing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 15; further comprising said administrator maintaining a content creation wizard reservoir comprised of at least one content creation wizard; and wherein creating said first client selectable content creation wizards comprises selecting a first of said content creation wizards from said content creation wizard reservoir; and coupling said first content creation wizard to said client e-mail interface to create said first client selectable content creation wizard.

18. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 15; further comprising said administrator maintaining a content meta-library comprised of at least one content entity; and wherein creating said client selectable content library comprises: selecting a first of said content entities from said content meta-library to create a first content entity; and using said first content entity to create said client selectable library further comprising at least one of the collection comprising: inserting said first content entity into said client selectable content library to create a client selectable content entity; and coupling said first content entity to said client e-mail interface to create a client user selectable content entity coupled to said client e-mail interface.

19. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 16; wherein said augmented messaging toolkit further comprises a database; further comprising said administrator responding to said received subscription message further includes said administrator recording in said database to create a client subscription record based upon said received subscription record.

20. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 19; further comprising said client e-mail interface recording a first e-mail message in said database as a first e-mail record whenever said client user sends said first e-mail message to said standard mail service from said client e-mail interface.

21. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 19; wherein said augmented messaging toolkit further comprises a tracking module accessing said database and communicating with said administrator; and further comprising: said administrator sending said tracking module a report request message; and said administrator receiving from said tracking module a report message based upon said report request message; and further comprising: said tracking module receiving said report request message from said administrator to create a received report request message; said tracking module accessing said database based upon said received report request message to create said report message; and said tracking module sending said report message to said administrator.

22. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 15; wherein said client user subscribing to said augmented messaging toolkit includes accessing a web subscription page.

23. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 15; said client user coupling to said client e-mail interface includes accessing a web e-mail interface page.

24. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 23; said administrator creating said client e-mail interface includes providing said client user access to said web e-mail interface page.

25. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user containing a client e-mail interface coupling said client user to said standard mail service and said client e-mail interface supporting client user selectable entities, a content creation wizard coupled to said client e-mail interface as one of said client user selectable entities, and at least one content entity coupled to said client e-mail interface as one of said client user selectable entities, comprising: determining said client user selection of said content creation wizard coupled to said client e-mail interface to create a content e-mail template containing at least one client user selectable content site within said content e-mail template; determining said client user selection of a first of said client user selectable content entities and determining said client user selection of a first of said client user selectable content sites within said content e-mail template to create said content e-mail template with said first content entity at said first content site; and supporting said client user using said content e-mail template to create a first e-mail message sent by said standard mail service from said client user.

26. A method of using an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 25; wherein said client user selectable content entities are organized into at least one content library comprising at least one user selectable content entity coupled to said client e-mail interface as one of said client user selectable entities; and further comprising determining said client user selecting a first of said client user selectable content entities of said content library; and further comprises determining said client user selecting said content library containing said first client user selectable content entity.

27. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 26; wherein said augmented messaging toolkit further comprises an administrator coupled to said standard mail services; further comprising supporting said client user subscribing to said augmented messaging toolkit further comprising: supporting said client user creating a subscription message; and supporting said client user sending said subscription message to said administrator; and further comprising supporting said administrator initiating a subscription for said client user includes; supporting said administrator receiving said subscription message from said client user; and supporting said administrator responding to said received subscription message.

28. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 27; wherein supporting said administrator responding to said received subscription message includes; supporting creating said client selectable content creation wizard; supporting creating said client selectable content library; and supporting creating said client e-mail interface coupling said client user to said standard mail service and said client e-mail interface supporting client user selectable entities including said client selectable content creation wizard and said client selectable content library.

29. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 27; further comprising supporting said administrator maintaining a content creation wizard library comprised of at least one content creation wizard; and wherein supporting creating said first client selectable content creation wizards comprises: supporting selecting a first of said content creation wizards from said content creation wizard library; and supporting coupling said first content creation wizard to said client e- mail interface to create said first client selectable content creation wizard.

30. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 27; further comprising supporting said administrator maintaining a content meta-library comprised of at least one content entity; and wherein supporting creating said client selectable content library comprises supporting selecting a first of said content entities from said content meta-library to create a first content entity; and supporting using said first content entity to create said client selectable library further comprising at least one of the collection comprising: supporting inserting said first content entity into said client selectable content library to create a client selectable content entity; and supporting coupling said first content entity to said client e-mail interface to create a client user selectable content entity coupled to said client e-mail interface.

31. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 28; wherein said augmented messaging toolkit further comprises a database; further comprising supporting said administrator responding to said received subscription message further includes supporting said administrator recording in said database to create a client subscription record based upon said received subscription record.

32. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 31 ; further comprising supporting said client e-mail interface recording a first e-mail message in said database as a first e-mail record whenever said client user sends said first e-mail message to said standard mail service from said client e-mail interface.

33. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 31 ; wherein said augmented messaging toolkit further comprises a tracking module accessing said database and communicating with said administrator; and further comprising: supporting said administrator sending said tracking module a report request message; and supporting said administrator receiving from said tracking module a report message based upon said report request message; and further comprising: supporting said tracking module receiving said report request message from said administrator to create a received report request message; supporting said tracking module accessing said database based upon said received report request message to create said report message; and supporting said tracking module sending said report message to said administrator.

34. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 27; wherein said client user subscribing to said augmented messaging toolkit includes accessing a web subscription page.

35. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 27; wherein supporting said client user coupling to said client e-mail interface includes supporting said client user accessing a web e-mail interface page.

36. A method of operating an augmented messaging toolkit interfacing a client user to a standard mail service supporting sending e-mail messages from said client user as recited in Claim 35; said administrator creating said client e-mail interface includes providing said client user access to said web e-mail interface page.

37. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module; including said user operating a client computer communicating via said network to a server system; wherein said client computer executing program code segments further including; a program code segment implementing said client interface; a program code segment implementing selection of said selectable content creation wizard; and a program code segment implementing selection of said selectable content entity; and wherein said server system executing program code segments further including; a program code segment implementing said standard mail service module; a program code segment implementing said selectable content creation wizard; and a program code segment implementing said selectable content entity.

38. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 37; wherein said client computer executing program code segments further including a program code segment implementing a web browser including a browser execution engine further executing program code segments; and wherein said web browser execution engine executing said program code segment implementing said client interface.

39. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 38; wherein said server system executing program code segments including a program code segment maintaining a client interface web page.

40. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 39; wherein said web browser execution engine executing said program code segment implementing said client interface includes a program code segment accessing said client interface web page;

41. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 40; wherein said program code segment implementing said client interface web page are executed by said server system.

42. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 40; wherein said client computer executed program code segment implementing said client interface are received by said client computer by accessing said client interface web page with said browser.

43. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 40; wherein said client computer executed program code segment implementing said client interface are enabled for execution on said client computer by accessing said client interface web page with said browser.

44. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 38; wherein said client computer executed program code segment implementing said client interface includes a program code segment implementing said selectable content creation wizard.

45. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 44; wherein said client computer executed program code segment implementing said selectable content creation wizard is received from execution of said server system executing program code segment implementing said selectable content creation wizard.

46. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 44; wherein said client computer executed program code segment implementing said selectable content creation wizard is enabled by execution of said server system program code segment implementing said selectable content creation wizard.

47. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content entity and with a selectable content entity and using a standard mail service module as recited in Claim 38; wherein said client computer executed program code segment implementing said client interface includes a program code segment implementing said selectable content entity.

48. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content entity and with a selectable content entity and using a standard mail service module as recited in Claim 47; wherein said client computer executed program code segment implementing said selectable content entity is received from execution of said server system program code segment implementing said selectable content entity.

49. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content entity and with a selectable content entity and using a standard mail service module as recited in Claim 47; wherein said client computer executed program code segment implementing said selectable content entity is enabled by execution of said code segment implementing said selectable content entity.

50. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content entity and with a selectable content entity and using a standard mail service module as recited in Claim 47; wherein said server system comprises a database coupled to said server system; and wherein said user operating said client computer subscribing to said augmented messaging toolkit creates a client subscriber record in said database; wherein said server system executing program code segments further comprises a program code segment maintaining said client computer executable program code segment implementing said client interface; and wherein said program code segment maintaining said client computer executable program code segment implementing said client interface accesses said client subscriber record of said database.

51. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content entity and with a selectable content entity and using a standard mail service module as recited in Claim 50; wherein said server system executing program code segments further comprising: an administrator program code segment; and a tracking program code segment; and wherein said administrator program code segment includes a program code segment commanding said tracking program code segment with a report command; and wherein said tracking program code segment includes a program code segment responding to said report command further includes; a program code segment accessing said database to create an access result; a program code segment using said access result to create a report; and a program code segment sending said report to said administrator program code segment.

52. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content entity and with a selectable content entity and using a standard mail service module as recited in Claim 51 ; wherein said administrator program code segment includes a program code segment commanding said tracking program code segment with a report command; and wherein said tracking program code segment includes a program code segment responding to said report command further includes; a program code segment accessing said database to create an access result; a program code segment using said access result to create a report; and a program code segment sending said report to said administrator program code segment.

53. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 52; wherein said server system includes an application server engine executing program code segments including at least one of the collection comprising: said program code segment implementing said selectable content creation wizard; said program code segment implementing said selectable content entity; said program code segment maintaining said client computer executable program code segment implementing said client interface; said program code segment implementing said client interface web page; said administrator program code segment; and said tracking program code segment.

54. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 53; wherein said server system includes an application server engine executing program code segments comprising: said program code segment implementing said selectable content creation wizard; said program code segment implementing said selectable content entity; said program code segment maintaining said client computer executable program code segment implementing said client interface; said program code segment implementing said client interface web page; said administrator program code segment; and said tracking program code segment.

55. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 51 ; wherein said database includes a database engine coupled to a mass storage system; wherein program code segments accessing said database include; a program code segment sending a database access request to said database engine; wherein said database engine executes program code segments comprising a program code segment receiving said database access request to create a received database access request; and a program code segment performing an access of said mass storage system based upon said received database access request.

56. A client-server system for a network supporting an augmented messaging toolkit including a client interface with a selectable content creation wizard and with a selectable content entity and using a standard mail service module as recited in Claim 37; wherein said server system includes an application server engine executing program code segments including; said program code segment implementing said selectable content creation wizard; and said program code segment implementing said selectable content entity.

57. A method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider of first content and a second provider of second content to advertise a shared content containing said first content and said second content to a collection of distributed content agents each using at least one content entity in communication with said distributed content system comprising: said administrator receives a message signaling said agreement; and said administrator commands said distributed content system to send said shared content to said collection of distributed content agents to be used as a content entity.

58. A method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider of first content and a second provider of second content to advertise a shared content containing said first content and said second content to a collection of distributed content agents in communication with said distributed content system as recited in Claim 57; wherein said distributed content system creates at least one distributed content agent of said collection of said distributed content agents; said administrator commands said distributed content system to send said shared content to said collection of distributed content agents to be used as a content entity includes said distributed content system creating said distributed content agent using said shared content.

59. A method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider of first content and a second provider of second content to advertise a shared content containing said first content and said second content to a collection of distributed content agents in communication with said distributed content system as recited in Claim 58 ; wherein said distributed content system maintains at least one distributed content agent of said collection of said distributed content agents; said administrator commands said distributed content system to send said shared content to said collection of distributed content agents to be used as a content entity includes said distributed content system maintaining said distributed content agent includes updating said distributed content agent with said shared content for use as said content entity.

60. A method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider of first content and a second provider of second content to advertise a shared content containing said first content and said second content to a collection of distributed content agents in communication with said distributed content system as recited in Claim 59; wherein at least one of said distributed content agent of said collection of said distributed content agents includes a client messaging interface with a selectable content entity.

61. A method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider of first content and a second provider of second content to advertise a shared content containing said first content and said second content to a collection of distributed content agents in communication with said distributed content system as recited in Claim 60; wherein said client messaging interface with a selectable content entity includes a client e-mail interface.

62. A method of operating a distributed content system controlled by an administrator based upon an agreement by a first provider of first content and a second provider of second content to advertise a shared content containing said first content and said second content to a collection of distributed content agents in communication with said distributed content system as recited in Claim 60; wherein said client messaging interface with a selectable content entity includes a client video mail interface.

63. A method of operating a distributed content system controlled by an administrator of a collection of distributed content agents each using a default message composing letterhead in communication with said distributed content system comprising: said administrator creating a default letterhead message designating a first letterhead; said administrator commanding said distributed content system to send said default letterhead message designating said first letterhead to said collection of distributed content agents to be used as said default message composing letterhead; said distributed content system sending said default letterhead message designating said first letterhead to said collection of distributed content agents to be used as said default message composing letterhead; each of said collection of distributed content agents receiving said default letterhead message designating said first letterhead; and each of said collection of distπbuted content agents responding to said received default letterhead message designating said first letterhead.