US8275838B2 - Conditioned delivery of electronic mail - Google Patents

Conditioned delivery of electronic mail Download PDF

Info

Publication number
US8275838B2
US8275838B2 US10/640,849 US64084903A US8275838B2 US 8275838 B2 US8275838 B2 US 8275838B2 US 64084903 A US64084903 A US 64084903A US 8275838 B2 US8275838 B2 US 8275838B2
Authority
US
United States
Prior art keywords
mail
delivery
conditions
recipients
message
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Fee Related, expires
Application number
US10/640,849
Other versions
US20050038862A1 (en
Inventor
Susann Marie Keohane
Gerald Francis McBrearty
Shawn Patrick Mullen
Jessica Murillo
Johnny Meng-Han Shieh
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
International Business Machines Corp
Original Assignee
International Business Machines Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by International Business Machines Corp filed Critical International Business Machines Corp
Priority to US10/640,849 priority Critical patent/US8275838B2/en
Assigned to INTERNATIONAL BUSINESS MACHINES CORPORATION reassignment INTERNATIONAL BUSINESS MACHINES CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: Keohane, Susann M., MURILLO, JESSICA, SHIEH, JOHNNY MENG-HAN, MCBREARTY, GERALD F., MULLEN, SHAWN P.
Publication of US20050038862A1 publication Critical patent/US20050038862A1/en
Priority to US12/176,393 priority patent/US8352556B2/en
Application granted granted Critical
Publication of US8275838B2 publication Critical patent/US8275838B2/en
Expired - Fee Related legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00Administration; Management
    • G06Q10/10Office automation; Time management
    • G06Q10/107Computer-aided management of electronic mailing [e-mailing]

Definitions

  • the present invention relates in general to data processing systems, and in particular, for electronic mail client systems including mechanisms for automatically controlling the delivery of e-mail to selected recipients based on criteria set by the sender.
  • Electronic mail (e-mail) processing in modern data processing systems are typically based on a client/server model.
  • An e-mail client usually deployed on a user's workstation or personal computer receives user input and generates an e-mail message which is typically transferred to the server, generically referred to as a mail transfer agent (MTA).
  • MTA mail transfer agent
  • the MTA then transfers the mail to one or more intermediate MTAs and ultimately to an MTA corresponding to the recipient of the e-mail message (as determined by the e-mail address of the addressee). Transfer of the e-mail message commonly uses the Simple Mail Transfer Protocol (SMTP).
  • SMTP Simple Mail Transfer Protocol
  • a user may request confirmation of delivery of the e-mail to a recipient's mailbox, or confirmation that the e-mail has been opened by the recipient.
  • an e-mail client allows a user to selectively enable these delivery confirmation options.
  • the e-mail message may include sensitive information that should be distributed to and read by a particular set of recipients before being distributed more widely.
  • the distribution of an e-mail announcement concerning organizational changes within the enterprise. It may be desirable to distribute the announcement first to managers within the enterprise, then to employees affected by the changes and lastly to all employees. It may be further desired to delay distribution to one or more of the categories of recipients based on the delivery status of prior recipients.
  • e-mail protocols provide for delivery confirmation, options to be selected by the user.
  • delivery confirmation options to be selected by the user.
  • systems and methods for controlling the distribution of e-mail among recipients in response to user-specified conditions are provided.
  • a method for conditional delivery of e-mail includes transmitting a first e-mail message to one or more first addressees. Message delivery notifications corresponding to a delivery status of said first e-mail message with respect to corresponding ones of said one or more addressees are received. In response to these, it is determined if a preselected set of conditions for delivery of said e-mail message to one or more second addressees is satisfied.
  • FIG. 1 illustrates an architecture for e-mail messaging which may be used in conjunction with the principles of the present invention
  • FIG. 2 illustrates, in flowchart form, a methodology for controlling distribution of e-mail among recipients
  • FIG. 3 illustrates, in block diagram form, a data processing system which may be used in conjunction with the methodologies incorporating the present inventive principles.
  • a mechanism for conditioned distribution of e-mail is provided.
  • Delivery of an e-mail message to selected second recipients may be conditioned on a set of preselected conditions, in particular to a set of conditions associated with the delivery of the e-mail to a set of first recipients.
  • a determination is made if the delivery conditions are satisfied, and delivery to the set of second recipients made accordingly.
  • Delivery to a set of third recipients may be likewise conditioned on another set of conditions.
  • FIG. 1 schematically illustrate e-mail exchange architecture which may be used in conjunction with the present invention.
  • the e-mail exchange architecture illustrated in FIG. 1 includes mail clients 102 a and 102 b .
  • a mail client typically provides the user interface to an e-mail exchange system.
  • E-mail clients may be stand-alone applications such as Eudora a well-known cross-platform e-mail client.
  • Unix and Unix-like platforms, such as Linux provide e-mail clients such as Pine and Mutt.
  • Microsoft Outlook includes an e-mail client. Messages generated by the user for transmission, typically via a network, to the mail addressee are sent to a Mail Transfer Agent (MTA), typically using the Simple Mail Transfer Protocol (SMTP).
  • MTA Mail Transfer Agent
  • SMTP Simple Mail Transfer Protocol
  • MTAs queue e-mail messages for relay toward the destination.
  • MTA 104 a maintains queue 106 a and MTA 104 b maintains queue 106 b .
  • an MTA may queue e-mail the delivery of which is conditioned, and whose delivery is pending while the conditions remain unsatisfied.
  • Mail is forwarded between MTAs, typically using the SMTP.
  • an e-mail sent by a user of mail client 102 a may generate an e-mail message addressed to the user of mail client 102 b , such message may be transferred first to MTA 104 a which may queue the message in queue 106 a . The message may then be forwarded to MTA 104 b which provides the egress mail server for mail client 102 b .
  • MTA 104 b which provides the egress mail server for mail client 102 b .
  • Mail clients such as mail clients 102 a and 102 b , typically include a mechanism to selectively enable the user to specify delivery confirmation options, referred to as Delivery Status Notification (DSN). Often this is selected via a graphical user interface (GUI) (not shown) as for example in Microsoft® Outlook, but could be specified by a command or command keyword-value pair in a command-line interface (CLI), as in Pine. Additionally, RFC2298-compliant MUAs provide for optionally receiving a “read” notification, that may enable the return of a notification to the sender that the e-mail has been displayed on the recipients PC or workstation.
  • GUI graphical user interface
  • CLI command-line interface
  • RFC2298-compliant MUAs provide for optionally receiving a “read” notification, that may enable the return of a notification to the sender that the e-mail has been displayed on the recipients PC or workstation.
  • RFC2298 specifies an defines a MIME content-type that may be used by a MUA or electronic mail gateway to report the disposition of a message after it has been successfully delivered to a recipient.
  • RFC2298 provides specifications for an extensible message format for message delivery notifications (MDNs).
  • MDNs message delivery notifications
  • a specification for DSNs is provided in RFC1894.
  • a DSN is requested in the SMTP transaction between the sender's e-mail client and the sender's MTA, in accordance with RFC1891, SMTP Service Extension for Delivery Status Notifications.
  • a DSN does not report on the disposition of an e-mail once it is delivered to the recipient's MUA, but only provides information on the success or failure of the delivery of the e-mail to the recipient's MUA.
  • an MDN may be requested for that purpose.
  • Such notification mechanisms may be used in conjunction with the controlled distribution of e-mail in accordance with the principles of the present invention, as discussed below. These may be used by a conditional delivery system which may be incorporated in an MUA, such as conditional delivery system 110 a and 110 b , in accordance with the present invention.
  • FIG. 2 illustrates, in flowchart form, a methodology 200 for providing conditional distribution of e-mail in accordance with an embodiment of the present invention.
  • Methodology 200 may be used by a conditional delivery module in an MUA, such as conditional delivery module 110 a, b FIG. 1 .
  • Delivery options may include a message priority and conditional delivery requirements.
  • Present e-mail clients such as Outlook and Eudora provide for user selectable message priority set via a GUI based user input, an options dialog pane in Outlook and a popup list in Eudora.
  • Such user interfaces may be similarly employed to enter delivery options and parameters specifying values for the conditional delivery of e-mail messages to particular recipients or groups of recipients. Conditions may be specified for each recipient or group of recipients.
  • Such requirements may, for example, condition the delivery of a message to particular recipients or groups of recipients on the receipt of the message by other recipients, receipt of the message by a specified number of selected recipients or groups of recipients, or a specified fraction of a number of selected recipients.
  • Conditions may also be measured by a number of messages opened by the selected recipients. Note that the present inventive principles may be applied to any set of conditions that may be associated with the delivery of e-mail to particular recipients or groups of recipients.
  • unconditioned e-mail are transmitted to the recipients (i.e. addressees) of these messages.
  • the e-mail sent in step 206 may include a request for an MDN (in accordance with RFC2298, as noted above) to acknowledge the display of the message.
  • a Delivery Status Notification (DSN) may be requested in accordance with RFC1891. Whether either or both is requested depends on the conditional delivery requirements. For example, if the conditions include requirements with respect to the display of the message by the recipients of the e-mail sent in step 206 , then an MDN may be requested. If the conditions include delivery requirements, then a DSN may be requested. If the conditions refer to both display and delivery, both an MDN and a DSN may be requested.
  • Unconditioned e-mail are those e-mail that have no delivery conditions associated therewith. If there are no conditioned e-mail, process 200 returns to step 202 via step 208 . Otherwise, if in step 208 there are conditioned e-mail, this mail is queued in step 210 , pending satisfaction of the conditions, as described in conjunction with steps 212 - 218 .
  • Existing e-mail clients such as Eudora include provisions for queuing e-mail messages for later transmission; additionally, e-mail clients such as Microsoft® Outlook include mechanisms for saving drafts of sent e-mail.
  • step 212 process 200 loops, watching for DSNs and MDNs with respect to the e-mail sent in step 206 .
  • Step 212 may parse incoming messages to detect fields in the DSNs and MDNs.
  • DSNs and MDNs may collectively be referred to herein as “return receipts”.
  • the MIME subtype field in accordance with RFC2298 contains “disposition-notification” and the disposition-field contains a disposition-type, one value of which, “displayed” reflects that the subject e-mail has been displayed by an MUA reading the recipient's mailbox.
  • fields in an MDN conforming to RFC2298 are defined according to the rules of RFC822.
  • RFC822 is the Internet e-mail standard.
  • RFC822-compliant-header parsers are available in programming languages such as Java and Perl, and may be adaptable for use to parse a MDN conforming to RFC2298. Additionally, with respect to DSNs publicly available “bounced message parsers” may be adapted to determine receipt of an e-mail message by the addressee.
  • One such parser is a regular expression based “bounced” mail parsers written in Perl for analyzing and reporting elements of RFC1894 DSN. This parser also may be adapted for parsing MDNs. (Such Perl modules may be found at the Comprehensive Perl Archive Network (CPAN) which is a central repository for Perl software (www.cpan.org). Artisans of ordinary skill would recognize that Perl is a scripting language particularly adapted for text processing and available across platforms.)
  • CPAN Comprehensive Perl Archive Network
  • step 214 it is determined if the conditions with respect to the conditioned e-mail are satisfied. For example, if the condition required that a specified percentage of the addressees of the e-mail sent in step 206 have opened that e-mail, in step 214 , process 200 would calculate the percentage based upon a count of the number of delivery notifications received, and compare that value with the required value. If the condition is satisfied, in step 216 the conditioned mail is sent to the next recipient of recipient group. Note that the content of the conditioned mail need not the same as the content of the mail upon which the delivery of the mail in step 216 is conditioned. In other words, the messages may, or may not be the same.
  • the conditions set for the delivery of the e-mail to the next set of recipients, and the determination that the conditions have been satisfied does not depend on the contents of the messages themselves.
  • the rationale for conditioning the delivery of the e-mail may be predicated on the contents of the messages.
  • the sensitive nature of the contents may be the reason for conditioning the delivery of the e-mail.
  • the e-mail message may include sensitive information that should be distributed to and read by a particular set of recipients before being distributed more widely.
  • the distribution of an e-mail announcement concerning organizational changes within the enterprise. It may be desirable to distribute the announcement first to managers within the enterprise, then to employees affected by the changes and lastly to all employees. It may be further desired to delay distribution to one or more of the categories of recipients based on the delivery status of prior recipients.
  • Another application of the present invention may be to coordinate tasks in a projects. For example, in a code development project if there are several defects that all need to be fixed before the next level of code is built, then an email notification to the builders may be automatically deferred until the developers responsible for the corrective action received this email. Similarly, if a file has been modified by several different people and these modifications must be undone, an email may be sent asking each person to undo their change. However, rather than sending the note to everyone and making them coordinate making the changes manually, the mail would be delivered to each successive person that needs to undo modifications after each person reads the email reducing the need to manual coordinate the modifications.
  • Process 200 then returns to step 208 , and continues to loop over steps 208 - 218 until all conditioned mail has been sent. Note that the conditions set for each set of conditioned e-mail may be different. If no such mail remains, process 200 returns to step 202 .
  • step 218 it is determined if the conditions are overridden. In other words, in step 218 it is determined if the conditioned mail should be sent although the conditions are not satisfied.
  • Step 218 may, for example, be performed by the user's mail client (MUA) generating an dialog pane querying the user if he or she wants to send the conditioned mail although the conditions have not yet been satisfied.
  • MUA user's mail client
  • a textual query may be displayed to the user in a command line interface based e-mail client.
  • step 218 may be enabled via a delivery option/parameter specified by the user in step 204 . If the conditioned messages are to be sent anyway, step 218 proceeds by the “Yes” branch to step 216 . Otherwise, step 218 returns to step 212 , and process 200 continues to receive message delivery notifications pending satisfaction of the delivery conditions.
  • FIG. 3 illustrates an exemplary hardware configuration of data processing system 300 in accordance with the subject invention.
  • the system in conjunction with the methodology illustrated in FIG. 2 may be used to provide controlled distribution of e-mail among selected recipients or groups of recipients.
  • system 300 may, in one embodiment may provide operations performed in an e-mail client with respect to receiving user input and setting e-mail delivery options in response thereto.
  • system 300 may provide operations in a mail client with respect to the receipt of message delivery notifications and determining if delivery conditions have been satisfied.
  • Data processing system 300 includes central processing unit (CPU) 310 , such as a conventional microprocessor, and a number of other units interconnected via system bus 312 .
  • CPU central processing unit
  • Data processing system 300 also includes random access memory (RAM) 314 , read only memory (ROM) 316 and input/output (I/O) adapter 318 for connecting peripheral devices such as disk units 320 to bus 312 , user interface adapter 322 for connecting keyboard 324 , mouse 326 , trackball 332 and/or other user interface devices such as a touch screen device (not shown) to bus 312 .
  • System 300 also includes communication adapter 334 for connecting data processing system 300 to a data processing network, enabling the system to communicate with other systems, and display adapter 336 for connecting bus 312 to display device 338 .
  • CPU 310 may include other circuitry not shown herein, which will include circuitry commonly found within a microprocessor, e.g. execution units, bus interface units, arithmetic logic units, etc. CPU 310 may also reside on a single integrated circuit.
  • Preferred implementations of the invention include implementations as a computer system programmed to execute the method or methods described herein, and as a computer program product.
  • sets of instructions for executing the method or methods are resident in the random access memory 314 of one or more computer systems configured generally as described above. These sets of instructions, in conjunction with system components that execute them may control the distribution of e-mail among recipients (or sets of recipients in accordance with user-specified criteria as described hereinabove.
  • the set of instructions may be stored as a computer program product in another computer memory, for example, in disk drive 320 (which may include a removable memory such as an optical disk or floppy disk for eventual use in the disk drive 320 ).
  • the computer program product can also be stored at another computer and transmitted to the users work station by a network or by an external network such as the Internet.
  • a network such as the Internet.
  • the physical storage of the sets of instructions physically changes the medium upon which is the stored so that the medium carries computer readable information.
  • the change may be electrical, magnetic, chemical, biological, or some other physical change. While it is convenient to describe the invention in terms of instructions, symbols, characters, or the like, the reader should remember that all of these in similar terms should be associated with the appropriate physical elements.
  • the invention may describe terms such as comparing, validating, selecting, identifying, or other terms that could be associated with a human operator.
  • terms such as comparing, validating, selecting, identifying, or other terms that could be associated with a human operator.
  • no action by a human operator is desirable.
  • the operations described are, in large part, machine operations processing electrical signals to generate other electrical signals.

Abstract

A system and method for conditioned distribution of e-mail is provided. Delivery of an e-mail message to selected second recipients (equivalently addressees) may be conditioned on a set of preselected conditions, in particular to a set of conditions associated with the delivery of the e-mail to a set of first recipients. In response to message delivery notifications corresponding to the set of first recipients, a determination is made if the delivery conditions are satisfied, and delivery to the set of second recipients made accordingly. Delivery to a set of third recipients may be likewise conditioned on another set of conditions.

Description

TECHNICAL FIELD
The present invention relates in general to data processing systems, and in particular, for electronic mail client systems including mechanisms for automatically controlling the delivery of e-mail to selected recipients based on criteria set by the sender.
BACKGROUND INFORMATION
Electronic mail (e-mail) processing in modern data processing systems are typically based on a client/server model. An e-mail client, usually deployed on a user's workstation or personal computer receives user input and generates an e-mail message which is typically transferred to the server, generically referred to as a mail transfer agent (MTA). The MTA then transfers the mail to one or more intermediate MTAs and ultimately to an MTA corresponding to the recipient of the e-mail message (as determined by the e-mail address of the addressee). Transfer of the e-mail message commonly uses the Simple Mail Transfer Protocol (SMTP).
In accordance with these e-mail protocols, a user may request confirmation of delivery of the e-mail to a recipient's mailbox, or confirmation that the e-mail has been opened by the recipient. Typically an e-mail client allows a user to selectively enable these delivery confirmation options. However, there is no mechanism to customize the delivery of e-mail.
In some circumstances, it may be desirable to control the distribution of an e-mail message to selected recipients. For example, the e-mail message may include sensitive information that should be distributed to and read by a particular set of recipients before being distributed more widely. Consider, within an enterprise, the distribution of an e-mail announcement concerning organizational changes within the enterprise. It may be desirable to distribute the announcement first to managers within the enterprise, then to employees affected by the changes and lastly to all employees. It may be further desired to delay distribution to one or more of the categories of recipients based on the delivery status of prior recipients.
As noted above, e-mail protocols provide for delivery confirmation, options to be selected by the user. However, there is a need in the art for systems and methods for controlling the distribution of e-mail among recipients in response to user-specified conditions.
SUMMARY OF THE INVENTION
The aforementioned needs are addressed by the present invention. Accordingly, there is provided in one embodiment of the present invention a method for conditional delivery of e-mail. The method includes transmitting a first e-mail message to one or more first addressees. Message delivery notifications corresponding to a delivery status of said first e-mail message with respect to corresponding ones of said one or more addressees are received. In response to these, it is determined if a preselected set of conditions for delivery of said e-mail message to one or more second addressees is satisfied.
The foregoing has outlined rather generally the features and technical advantages of one or more embodiments of the present invention in order that the detailed description of the invention that follows may be better understood. Additional features and advantages of the invention will be described hereinafter which may form the subject of the claims of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
For a more complete understanding of the present invention, and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:
FIG. 1 illustrates an architecture for e-mail messaging which may be used in conjunction with the principles of the present invention;
FIG. 2 illustrates, in flowchart form, a methodology for controlling distribution of e-mail among recipients; and
FIG. 3 illustrates, in block diagram form, a data processing system which may be used in conjunction with the methodologies incorporating the present inventive principles.
DETAILED DESCRIPTION
A mechanism for conditioned distribution of e-mail is provided. Delivery of an e-mail message to selected second recipients (equivalently addressees) may be conditioned on a set of preselected conditions, in particular to a set of conditions associated with the delivery of the e-mail to a set of first recipients. In response to message delivery notifications corresponding to the set of first recipients, a determination is made if the delivery conditions are satisfied, and delivery to the set of second recipients made accordingly. Delivery to a set of third recipients may be likewise conditioned on another set of conditions.
In the following description, numerous specific details are set forth such to provide a thorough understanding of the present invention. For example, particular e-mail transport protocols may be referred to, however, it would be recognized by those of ordinary skill in the art that the present invention may be practiced without such specific details, and in other instances, well-known circuits have been shown in block diagram form in order not to obscure the present invention in unnecessary detail. Refer now to the drawings, wherein depicted elements are not necessarily shown to scale and wherein like or similar elements are designated by the same reference numeral through the several views.
FIG. 1 schematically illustrate e-mail exchange architecture which may be used in conjunction with the present invention. The e-mail exchange architecture illustrated in FIG. 1 includes mail clients 102 a and 102 b. A mail client typically provides the user interface to an e-mail exchange system. E-mail clients may be stand-alone applications such as Eudora a well-known cross-platform e-mail client. Additionally, Unix and Unix-like platforms, such as Linux, provide e-mail clients such as Pine and Mutt. On Windows platforms, Microsoft Outlook includes an e-mail client. Messages generated by the user for transmission, typically via a network, to the mail addressee are sent to a Mail Transfer Agent (MTA), typically using the Simple Mail Transfer Protocol (SMTP). The architecture of FIG. 1, two MTAs, 104 a and 104 b are illustrated. MTAs queue e-mail messages for relay toward the destination. MTA 104 a maintains queue 106 a and MTA 104 b maintains queue 106 b. Additionally, as discussed in conjunction with FIG. 2 below, an MTA may queue e-mail the delivery of which is conditioned, and whose delivery is pending while the conditions remain unsatisfied. Mail is forwarded between MTAs, typically using the SMTP. Thus, an e-mail sent by a user of mail client 102 a, for example, may generate an e-mail message addressed to the user of mail client 102 b, such message may be transferred first to MTA 104 a which may queue the message in queue 106 a. The message may then be forwarded to MTA 104 b which provides the egress mail server for mail client 102 b. It would be appreciated by those of ordinary skill in the art that the architecture of FIG. 1 is exemplary, and in particular, the typical routing of an e-mail message may include the relay of the message by more than two MTAs.
Mail clients, such as mail clients 102 a and 102 b, typically include a mechanism to selectively enable the user to specify delivery confirmation options, referred to as Delivery Status Notification (DSN). Often this is selected via a graphical user interface (GUI) (not shown) as for example in Microsoft® Outlook, but could be specified by a command or command keyword-value pair in a command-line interface (CLI), as in Pine. Additionally, RFC2298-compliant MUAs provide for optionally receiving a “read” notification, that may enable the return of a notification to the sender that the e-mail has been displayed on the recipients PC or workstation. (RFCs are Internet documents which are used to promulgate Internet standards; RFCs are available from the Internet Engineering Task Force (http://www.ietf.org).) RFC2298 specifies an defines a MIME content-type that may be used by a MUA or electronic mail gateway to report the disposition of a message after it has been successfully delivered to a recipient. In particular, RFC2298 provides specifications for an extensible message format for message delivery notifications (MDNs). A specification for DSNs is provided in RFC1894. (A DSN is requested in the SMTP transaction between the sender's e-mail client and the sender's MTA, in accordance with RFC1891, SMTP Service Extension for Delivery Status Notifications.) A DSN does not report on the disposition of an e-mail once it is delivered to the recipient's MUA, but only provides information on the success or failure of the delivery of the e-mail to the recipient's MUA. As noted above, an MDN may be requested for that purpose. Such notification mechanisms may be used in conjunction with the controlled distribution of e-mail in accordance with the principles of the present invention, as discussed below. These may be used by a conditional delivery system which may be incorporated in an MUA, such as conditional delivery system 110 a and 110 b, in accordance with the present invention.
Refer now to FIG. 2 which illustrates, in flowchart form, a methodology 200 for providing conditional distribution of e-mail in accordance with an embodiment of the present invention. Methodology 200 may be used by a conditional delivery module in an MUA, such as conditional delivery module 110 a, b FIG. 1.
Note that the flowcharts provided herein are not necessarily indicative of the serialization of operations being performed in an embodiment of the present invention. Steps disclosed within these flowcharts may be performed in parallel. The flowcharts are indicative of those considerations that may be performed to produce the operations available to provide controlled distribution of e-mail based on user-specified criteria. It is further noted that the order presented is illustrative and does not necessarily imply that the steps must be performed in the order shown.
User input specifying the delivery options and associated parameter values associated therewith are received in step 204. Delivery options may include a message priority and conditional delivery requirements. Present e-mail clients such as Outlook and Eudora provide for user selectable message priority set via a GUI based user input, an options dialog pane in Outlook and a popup list in Eudora. Such user interfaces may be similarly employed to enter delivery options and parameters specifying values for the conditional delivery of e-mail messages to particular recipients or groups of recipients. Conditions may be specified for each recipient or group of recipients. Such requirements may, for example, condition the delivery of a message to particular recipients or groups of recipients on the receipt of the message by other recipients, receipt of the message by a specified number of selected recipients or groups of recipients, or a specified fraction of a number of selected recipients. Conditions may also be measured by a number of messages opened by the selected recipients. Note that the present inventive principles may be applied to any set of conditions that may be associated with the delivery of e-mail to particular recipients or groups of recipients.
In step 206, unconditioned e-mail are transmitted to the recipients (i.e. addressees) of these messages. Note that the e-mail sent in step 206 may include a request for an MDN (in accordance with RFC2298, as noted above) to acknowledge the display of the message. Additionally, a Delivery Status Notification (DSN) may be requested in accordance with RFC1891. Whether either or both is requested depends on the conditional delivery requirements. For example, if the conditions include requirements with respect to the display of the message by the recipients of the e-mail sent in step 206, then an MDN may be requested. If the conditions include delivery requirements, then a DSN may be requested. If the conditions refer to both display and delivery, both an MDN and a DSN may be requested.
Unconditioned e-mail, are those e-mail that have no delivery conditions associated therewith. If there are no conditioned e-mail, process 200 returns to step 202 via step 208. Otherwise, if in step 208 there are conditioned e-mail, this mail is queued in step 210, pending satisfaction of the conditions, as described in conjunction with steps 212-218. Existing e-mail clients, such as Eudora include provisions for queuing e-mail messages for later transmission; additionally, e-mail clients such as Microsoft® Outlook include mechanisms for saving drafts of sent e-mail.
In step 212, process 200 loops, watching for DSNs and MDNs with respect to the e-mail sent in step 206. Step 212 may parse incoming messages to detect fields in the DSNs and MDNs. (DSNs and MDNs may collectively be referred to herein as “return receipts”.) For example, the MIME subtype field in accordance with RFC2298 contains “disposition-notification” and the disposition-field contains a disposition-type, one value of which, “displayed” reflects that the subject e-mail has been displayed by an MUA reading the recipient's mailbox. Note that fields in an MDN conforming to RFC2298 are defined according to the rules of RFC822. RFC822, is the Internet e-mail standard. RFC822-compliant-header parsers are available in programming languages such as Java and Perl, and may be adaptable for use to parse a MDN conforming to RFC2298. Additionally, with respect to DSNs publicly available “bounced message parsers” may be adapted to determine receipt of an e-mail message by the addressee. One such parser is a regular expression based “bounced” mail parsers written in Perl for analyzing and reporting elements of RFC1894 DSN. This parser also may be adapted for parsing MDNs. (Such Perl modules may be found at the Comprehensive Perl Archive Network (CPAN) which is a central repository for Perl software (www.cpan.org). Artisans of ordinary skill would recognize that Perl is a scripting language particularly adapted for text processing and available across platforms.)
If, in step 212, a status notification is received, in step 214 it is determined if the conditions with respect to the conditioned e-mail are satisfied. For example, if the condition required that a specified percentage of the addressees of the e-mail sent in step 206 have opened that e-mail, in step 214, process 200 would calculate the percentage based upon a count of the number of delivery notifications received, and compare that value with the required value. If the condition is satisfied, in step 216 the conditioned mail is sent to the next recipient of recipient group. Note that the content of the conditioned mail need not the same as the content of the mail upon which the delivery of the mail in step 216 is conditioned. In other words, the messages may, or may not be the same. The conditions set for the delivery of the e-mail to the next set of recipients, and the determination that the conditions have been satisfied does not depend on the contents of the messages themselves. Of course, the rationale for conditioning the delivery of the e-mail may be predicated on the contents of the messages. For example, the sensitive nature of the contents may be the reason for conditioning the delivery of the e-mail.
Thus, in some circumstances, it may be desirable to control the distribution of an e-mail message to selected recipients. For example, the e-mail message may include sensitive information that should be distributed to and read by a particular set of recipients before being distributed more widely. Consider, within an enterprise, the distribution of an e-mail announcement concerning organizational changes within the enterprise. It may be desirable to distribute the announcement first to managers within the enterprise, then to employees affected by the changes and lastly to all employees. It may be further desired to delay distribution to one or more of the categories of recipients based on the delivery status of prior recipients.
Another example may arise in distributing organizational information When a second (that is, upper) line manager reads the note, the first line managers (lower) are then sent the note. When a first line manager read the note his/her department would then get the note.
Another application of the present invention may be to coordinate tasks in a projects. For example, in a code development project if there are several defects that all need to be fixed before the next level of code is built, then an email notification to the builders may be automatically deferred until the developers responsible for the corrective action received this email. Similarly, if a file has been modified by several different people and these modifications must be undone, an email may be sent asking each person to undo their change. However, rather than sending the note to everyone and making them coordinate making the changes manually, the mail would be delivered to each successive person that needs to undo modifications after each person reads the email reducing the need to manual coordinate the modifications.
Process 200 then returns to step 208, and continues to loop over steps 208-218 until all conditioned mail has been sent. Note that the conditions set for each set of conditioned e-mail may be different. If no such mail remains, process 200 returns to step 202.
Returning to step 214, based on the message delivery notifications, the delivery conditions have not been satisfied, in step 218, it is determined if the conditions are overridden. In other words, in step 218 it is determined if the conditioned mail should be sent although the conditions are not satisfied. Step 218 may, for example, be performed by the user's mail client (MUA) generating an dialog pane querying the user if he or she wants to send the conditioned mail although the conditions have not yet been satisfied. The use of such dialogs to alert or query users would be understood by persons of ordinary skill in the art. Similarly, a textual query may be displayed to the user in a command line interface based e-mail client. Note, that in an embodiment of the present invention, step 218 may be enabled via a delivery option/parameter specified by the user in step 204. If the conditioned messages are to be sent anyway, step 218 proceeds by the “Yes” branch to step 216. Otherwise, step 218 returns to step 212, and process 200 continues to receive message delivery notifications pending satisfaction of the delivery conditions.
FIG. 3 illustrates an exemplary hardware configuration of data processing system 300 in accordance with the subject invention. The system in conjunction with the methodology illustrated in FIG. 2 may be used to provide controlled distribution of e-mail among selected recipients or groups of recipients. In particular system 300 may, in one embodiment may provide operations performed in an e-mail client with respect to receiving user input and setting e-mail delivery options in response thereto. In another embodiment system 300 may provide operations in a mail client with respect to the receipt of message delivery notifications and determining if delivery conditions have been satisfied. Data processing system 300 includes central processing unit (CPU) 310, such as a conventional microprocessor, and a number of other units interconnected via system bus 312. Data processing system 300 also includes random access memory (RAM) 314, read only memory (ROM) 316 and input/output (I/O) adapter 318 for connecting peripheral devices such as disk units 320 to bus 312, user interface adapter 322 for connecting keyboard 324, mouse 326, trackball 332 and/or other user interface devices such as a touch screen device (not shown) to bus 312. System 300 also includes communication adapter 334 for connecting data processing system 300 to a data processing network, enabling the system to communicate with other systems, and display adapter 336 for connecting bus 312 to display device 338. CPU 310 may include other circuitry not shown herein, which will include circuitry commonly found within a microprocessor, e.g. execution units, bus interface units, arithmetic logic units, etc. CPU 310 may also reside on a single integrated circuit.
Preferred implementations of the invention include implementations as a computer system programmed to execute the method or methods described herein, and as a computer program product. According to the computer system implementation, sets of instructions for executing the method or methods are resident in the random access memory 314 of one or more computer systems configured generally as described above. These sets of instructions, in conjunction with system components that execute them may control the distribution of e-mail among recipients (or sets of recipients in accordance with user-specified criteria as described hereinabove. Until required by the computer system, the set of instructions may be stored as a computer program product in another computer memory, for example, in disk drive 320 (which may include a removable memory such as an optical disk or floppy disk for eventual use in the disk drive 320). Further, the computer program product can also be stored at another computer and transmitted to the users work station by a network or by an external network such as the Internet. One skilled in the art would appreciate that the physical storage of the sets of instructions physically changes the medium upon which is the stored so that the medium carries computer readable information. The change may be electrical, magnetic, chemical, biological, or some other physical change. While it is convenient to describe the invention in terms of instructions, symbols, characters, or the like, the reader should remember that all of these in similar terms should be associated with the appropriate physical elements.
Note that the invention may describe terms such as comparing, validating, selecting, identifying, or other terms that could be associated with a human operator. However, for at least a number of the operations described herein which form part of at least one of the embodiments, no action by a human operator is desirable. The operations described are, in large part, machine operations processing electrical signals to generate other electrical signals.
Although the present invention and its advantages have been described in detail, it should be understood that various changes, substitutions and alterations can be made herein without departing from the spirit and scope of the invention is defined by the appended claims.

Claims (7)

1. A method for conditional delivery of e-mail comprising:
transmitting a first e-mail message to a first group of individuals, wherein the first group of individuals are associated with a plurality of first addresses;
receiving one or more return receipts, the return receipts corresponding to a receipt status of said first e-mail message with respect to corresponding ones of said plurality of first addresses;
determining, in response to said return receipts, if a first preselected set of conditions is satisfied, then a second e-mail message is delivered to a second group of individuals associated with a plurality of second addresses, wherein said first preselected set of conditions comprises a receipt of said first e-mail message by a first specified fraction of said plurality of first addresses, wherein said first preselected set of conditions further comprises display of said first e-mail message by a second specified fraction of said plurality of first addresses, wherein said first group of individuals are different from said second group of individuals.
2. The method of claim 1 further comprising, if said first preselected set of conditions is satisfied, sending said second e-mail message to said one or more second addressees.
3. The method of claim 1 further comprising queuing said second e-mail message for delivery to said one or more second addressees.
4. The method of claim 3 further comprising receiving said first preselected set of conditions for delivery of said second e-mail message to one or more second addressees in response to user input.
5. The method of claim 4 further comprising determining if said first preselected set of conditions is overridden.
6. The method of claim 2 further comprising if, in response to one or more return receipts for said second e-mail message, a second preselected set of conditions for delivery of a third message to one or more third addressees is satisfied, sending a third e-mail message to said one or more third addressees.
7. The method of claim 2 wherein a content of said second e-mail message differs from a content of said first e-mail message.
US10/640,849 2003-08-14 2003-08-14 Conditioned delivery of electronic mail Expired - Fee Related US8275838B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US10/640,849 US8275838B2 (en) 2003-08-14 2003-08-14 Conditioned delivery of electronic mail
US12/176,393 US8352556B2 (en) 2003-08-14 2008-07-20 Conditioned delivery of electronic mail

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
US10/640,849 US8275838B2 (en) 2003-08-14 2003-08-14 Conditioned delivery of electronic mail

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/176,393 Continuation US8352556B2 (en) 2003-08-14 2008-07-20 Conditioned delivery of electronic mail

Publications (2)

Publication Number Publication Date
US20050038862A1 US20050038862A1 (en) 2005-02-17
US8275838B2 true US8275838B2 (en) 2012-09-25

Family

ID=34136191

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/640,849 Expired - Fee Related US8275838B2 (en) 2003-08-14 2003-08-14 Conditioned delivery of electronic mail
US12/176,393 Expired - Fee Related US8352556B2 (en) 2003-08-14 2008-07-20 Conditioned delivery of electronic mail

Family Applications After (1)

Application Number Title Priority Date Filing Date
US12/176,393 Expired - Fee Related US8352556B2 (en) 2003-08-14 2008-07-20 Conditioned delivery of electronic mail

Country Status (1)

Country Link
US (2) US8275838B2 (en)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110252105A1 (en) * 2008-10-07 2011-10-13 Seung-Yong Lee Mobile communication system and method for the requesting of positive delivery reports from individual group members

Families Citing this family (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7406505B2 (en) * 2004-04-29 2008-07-29 International Business Machines Corporation Managing on-demand email storage
US7996471B2 (en) * 2004-07-13 2011-08-09 At&T Intellectual Property I, L.P. Electronic message distribution system
US20060075031A1 (en) * 2004-09-17 2006-04-06 Wagner Dirk P Bounce management
US20070073816A1 (en) * 2005-09-28 2007-03-29 Shruti Kumar Method and system for providing increased information and improved user controls for electronic mail return receipts
US20070143409A1 (en) * 2005-12-16 2007-06-21 Microsoft Corporation Email transport rule recipient tree condition
US8219623B2 (en) * 2005-12-16 2012-07-10 Microsoft Corporation Email transport rule per-recipient condition
US20070143413A1 (en) * 2005-12-16 2007-06-21 Microsoft Corporation Email transport rule recipient flat declaration condition
US8005903B2 (en) * 2006-12-13 2011-08-23 International Business Machines Corporation Method and apparatus for managing locally stored E-mail messages
US20090138558A1 (en) * 2007-11-27 2009-05-28 International Business Machines Corporation Automated Methods for the Handling of a Group Return Receipt for the Monitoring of a Group Delivery
US20090138557A1 (en) * 2007-11-27 2009-05-28 International Business Machines Corporation Delegation of e-mail return receipts
US8280965B2 (en) * 2008-12-10 2012-10-02 International Business Machines Corporation Method and system for managing electronic mail
US20110047406A1 (en) * 2009-08-24 2011-02-24 General Devices Systems and methods for sending, receiving and managing electronic messages
US9088534B2 (en) 2010-12-07 2015-07-21 International Business Machines Corporation Systems and methods for providing a recipient of an electronic communication with data used to determine whether to respond to the electronic communication
US9824377B1 (en) 2012-06-21 2017-11-21 Amazon Technologies, Inc. Round-robin e-mail scheduling
US9230245B1 (en) * 2012-06-21 2016-01-05 Amazon Technologies, Inc. Deliverability-based e-mail sending
US9264393B2 (en) 2013-02-13 2016-02-16 International Business Machines Corporation Mail server-based dynamic workflow management
US10043143B2 (en) 2014-01-07 2018-08-07 International Business Machines Corporation Automatic floor-level retail operation decisions using video analytics
US10785172B2 (en) * 2014-05-23 2020-09-22 Verizon Patent And Licensing Inc. Method and apparatus for delivering messages based on user activity status
CN106209582B (en) * 2016-06-29 2020-05-05 北京奇虎科技有限公司 Message information processing method and device and terminal equipment

Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6021433A (en) * 1996-01-26 2000-02-01 Wireless Internet, Inc. System and method for transmission of data
US6076101A (en) * 1996-09-12 2000-06-13 Fujitsu Limited Electronic mail processing system with bonus point tracking
US6199102B1 (en) * 1997-08-26 2001-03-06 Christopher Alan Cobb Method and system for filtering electronic messages
US20020019852A1 (en) * 1999-12-15 2002-02-14 Reuben Bahar Method and system for confirming proper receipt of e-mail transmitted via a communications network
US20020026488A1 (en) * 2000-08-24 2002-02-28 Hideharu Ogawa Server device and method for providing e-mail service, and information recording medium recording a program for realizing the service
US20020075521A1 (en) * 2000-12-14 2002-06-20 Fuji Xerox Co., Ltd. Internet facsimile and control method thereof
US20020095508A1 (en) * 2001-01-17 2002-07-18 Takashi Okazawa Communication control device, apparatus, method of notification, recording medium, and program
US20020144148A1 (en) * 2001-04-03 2002-10-03 Tony Hashem Method and system for secure transmission of information
US20020143879A1 (en) * 2001-03-28 2002-10-03 Peter Sommerer Method and system for automatically updating electronic mail address information within an electronic mail address database
US20030009383A1 (en) * 2001-04-27 2003-01-09 Canon Kabushiki Kaisha Collection information management server and collection information management method
US20030023695A1 (en) * 1999-02-26 2003-01-30 Atabok Japan, Inc. Modifying an electronic mail system to produce a secure delivery system
US20030110223A1 (en) * 2001-12-07 2003-06-12 Scott Hamilton System and method for correcting the failed delivery of electronic documents
US20030172120A1 (en) * 1999-07-28 2003-09-11 Tomkow Terrence A. System and method for verifying delivery and integrity of electronic messages
US20040003283A1 (en) * 2002-06-26 2004-01-01 Goodman Joshua Theodore Spam detector with challenges
US20040003352A1 (en) * 2002-06-27 2004-01-01 Bargeron David M. Notification of activity around documents
US20040172454A1 (en) * 2002-11-18 2004-09-02 Barry Appelman Reconfiguring an electronic message to effect an enhanced notification
US20050015450A1 (en) * 2003-07-17 2005-01-20 International Business Machines Corporation System and method for alerting electronic mail users of undeliverable recipients
US6854007B1 (en) * 1998-09-17 2005-02-08 Micron Technology, Inc. Method and system for enhancing reliability of communication with electronic messages
US20050177622A1 (en) * 2000-07-31 2005-08-11 Spielman Brenda G. Scalable IP-based notification architecture for unified messaging
US20060195554A1 (en) * 1996-01-26 2006-08-31 Payne John M System and method for transmission of data
US20060195537A1 (en) * 2003-02-19 2006-08-31 Postini, Inc. Systems and methods for managing directory harvest attacks via electronic messages
US20080071928A1 (en) * 2000-10-30 2008-03-20 Norihiro Koizumi Address inquiry system, computer software product, and address inquiry method

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6073142A (en) * 1997-06-23 2000-06-06 Park City Group Automated post office based rule analysis of e-mail messages and other data objects for controlled distribution in network environments
US6507866B1 (en) * 1999-07-19 2003-01-14 At&T Wireless Services, Inc. E-mail usage pattern detection
US6868498B1 (en) * 1999-09-01 2005-03-15 Peter L. Katsikas System for eliminating unauthorized electronic mail
US7822977B2 (en) * 2000-02-08 2010-10-26 Katsikas Peter L System for eliminating unauthorized electronic mail
US7380126B2 (en) * 2001-06-01 2008-05-27 Logan James D Methods and apparatus for controlling the transmission and receipt of email messages
US20050193113A1 (en) * 2003-04-14 2005-09-01 Fujitsu Limited Server allocation control method
US7389510B2 (en) * 2003-11-06 2008-06-17 International Business Machines Corporation Load balancing of servers in a cluster
US7703101B2 (en) * 2004-02-13 2010-04-20 International Business Machines Corporation Autonomic workload classification using predictive assertion for wait queue and thread pool selection

Patent Citations (22)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6021433A (en) * 1996-01-26 2000-02-01 Wireless Internet, Inc. System and method for transmission of data
US20060195554A1 (en) * 1996-01-26 2006-08-31 Payne John M System and method for transmission of data
US6076101A (en) * 1996-09-12 2000-06-13 Fujitsu Limited Electronic mail processing system with bonus point tracking
US6199102B1 (en) * 1997-08-26 2001-03-06 Christopher Alan Cobb Method and system for filtering electronic messages
US6854007B1 (en) * 1998-09-17 2005-02-08 Micron Technology, Inc. Method and system for enhancing reliability of communication with electronic messages
US20030023695A1 (en) * 1999-02-26 2003-01-30 Atabok Japan, Inc. Modifying an electronic mail system to produce a secure delivery system
US20030172120A1 (en) * 1999-07-28 2003-09-11 Tomkow Terrence A. System and method for verifying delivery and integrity of electronic messages
US20020019852A1 (en) * 1999-12-15 2002-02-14 Reuben Bahar Method and system for confirming proper receipt of e-mail transmitted via a communications network
US20050177622A1 (en) * 2000-07-31 2005-08-11 Spielman Brenda G. Scalable IP-based notification architecture for unified messaging
US20020026488A1 (en) * 2000-08-24 2002-02-28 Hideharu Ogawa Server device and method for providing e-mail service, and information recording medium recording a program for realizing the service
US20080071928A1 (en) * 2000-10-30 2008-03-20 Norihiro Koizumi Address inquiry system, computer software product, and address inquiry method
US20020075521A1 (en) * 2000-12-14 2002-06-20 Fuji Xerox Co., Ltd. Internet facsimile and control method thereof
US20020095508A1 (en) * 2001-01-17 2002-07-18 Takashi Okazawa Communication control device, apparatus, method of notification, recording medium, and program
US20020143879A1 (en) * 2001-03-28 2002-10-03 Peter Sommerer Method and system for automatically updating electronic mail address information within an electronic mail address database
US20020144148A1 (en) * 2001-04-03 2002-10-03 Tony Hashem Method and system for secure transmission of information
US20030009383A1 (en) * 2001-04-27 2003-01-09 Canon Kabushiki Kaisha Collection information management server and collection information management method
US20030110223A1 (en) * 2001-12-07 2003-06-12 Scott Hamilton System and method for correcting the failed delivery of electronic documents
US20040003283A1 (en) * 2002-06-26 2004-01-01 Goodman Joshua Theodore Spam detector with challenges
US20040003352A1 (en) * 2002-06-27 2004-01-01 Bargeron David M. Notification of activity around documents
US20040172454A1 (en) * 2002-11-18 2004-09-02 Barry Appelman Reconfiguring an electronic message to effect an enhanced notification
US20060195537A1 (en) * 2003-02-19 2006-08-31 Postini, Inc. Systems and methods for managing directory harvest attacks via electronic messages
US20050015450A1 (en) * 2003-07-17 2005-01-20 International Business Machines Corporation System and method for alerting electronic mail users of undeliverable recipients

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Greg Alwang, "Really Secure E-Mail Plug-In, SurfControl's SuperScout Email Filter," PC Magazine, p. 42 (Jun. 26, 2001).
Susanne Bjorner, "Day Tripping to Internet World. (Fall 1996 Trade Show)" Searcher,vol. 5, No. 2, p. 50(12) (Feb. 1997).

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110252105A1 (en) * 2008-10-07 2011-10-13 Seung-Yong Lee Mobile communication system and method for the requesting of positive delivery reports from individual group members
US8914448B2 (en) * 2008-10-07 2014-12-16 Samsung Electronics Co., Ltd Mobile communication system and method for the requesting of positive delivery reports from individual group members

Also Published As

Publication number Publication date
US20080288601A1 (en) 2008-11-20
US20050038862A1 (en) 2005-02-17
US8352556B2 (en) 2013-01-08

Similar Documents

Publication Publication Date Title
US8352556B2 (en) Conditioned delivery of electronic mail
US7603420B2 (en) Method and apparatus for automatic e-mail response interruption based on user activity
US9531656B2 (en) System, method, and computer program product for determining whether an electronic mail message is compliant with an etiquette policy
US8407297B2 (en) Systems and methods to receive information from a groupware client
US7890585B2 (en) Second person review of email
US7076241B1 (en) System and method for selectively transmitting electronic messages
US8230019B2 (en) Alerting electronic mail users of undeliverable recipients
US7191221B2 (en) Method for managing electronic mail receipts using audio-visual notification enhancements
US8266230B2 (en) Active removal of e-mail recipient from replies and subsequent threads
US20030050988A1 (en) E-mail system providing filtering methodology on a per-domain basis
US8799369B2 (en) Recipient-controlled remote E-mail alerting and delivery
US6832243B1 (en) Methods and apparatus for defining, observing and evaluating message delivery outcome on a per-message basis
US20080250112A1 (en) Method and Apparatus for Determining Whether an Email Message is Ready for Transmission
US7030730B1 (en) System and method for formatting an electronic message
US20150081816A1 (en) Electronic message management system
US20060277258A1 (en) Managing and organizing electronic mail messages via a cross tabulation summary or a histogram
JP2002149571A (en) Method for displaying and controlling electronic mail using diary form
US20130204952A1 (en) Method and system for electronic collaboration
US10432776B1 (en) Managing unanswered digital communications
US11470031B2 (en) Electronic mail format protocol for instructing automatic behavior of electronic devices executing an electronic mail client application
US20210396262A9 (en) Automated delivery of alerts with confirmation of receipt
JP4572702B2 (en) Electronic document approval program, electronic document approval method, and electronic document approval apparatus
JP2001167008A (en) Mail data managing device and storage medium with stored mail data managing program
TW200535654A (en) Method and system of managing event information with an electronic form system
JPH0879299A (en) Electronic bulletin board reference control system

Legal Events

Date Code Title Description
AS Assignment

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KEOHANE, SUSANN M.;MCBREARTY, GERALD F.;MULLEN, SHAWN P.;AND OTHERS;REEL/FRAME:014404/0379;SIGNING DATES FROM 20030806 TO 20030807

Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KEOHANE, SUSANN M.;MCBREARTY, GERALD F.;MULLEN, SHAWN P.;AND OTHERS;SIGNING DATES FROM 20030806 TO 20030807;REEL/FRAME:014404/0379

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

REMI Maintenance fee reminder mailed
LAPS Lapse for failure to pay maintenance fees
STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20160925