Browse Prior Art Database

Service for Intelligent Message Routing Upon Failure

IP.com Disclosure Number: IPCOM000207981D
Publication Date: 2011-Jun-17
Document File: 3 page(s) / 22K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a method to enhance communication systems delivery failure features, and make such systems more intuitive and usable.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 47% of the total text.

Page 01 of 3

Service for Intelligent Message Routing Upon Failure

Electronic mail (email) is a method of exchanging digital messages from an author to one or more recipients. Modern email operates across the Internet or other computer networks. Today's email systems are based on a store-and-forward model. Email servers accept, forward, deliver and store messages. Neither the users nor their computers are required to be online simultaneously; they need connect only briefly, typically to an email server, for as long as it takes to send or receive messages. An email message consists of three components, the message envelope, the message header, and the message body. The message header contains control information, including, minimally, an originator's email address and one or more recipient addresses. Usually descriptive information is also added, such as a subject header field and a message submission date/time stamp.

Presently, email systems respond to address changes with delivery failures. The person who sends this email to a corporation does not know the underlying cause for the delivery failure. For example, the individual may no longer work at the company. Additionally, the company this person represented does not know that a contact attempt has been initiated and as a result may be at an information disadvantage.

There are no known methods to address this problem.

This invention provides one means of solving this problem, so as to increase usability of such systems, and improved feedback to the users.

The classic solution for handling such changes of communication changes was the sendmail-recognized file ".forward." The .forward file specified where mail should be sent, and is sometimes employed when a user moves to a new email address.

The disclosed invention enhances communication systems by providing several novel methods for handling associated delivery failures. In one embodiment, the message (e.g., email) is automatically forwarded to the original addressees' manager. In another embodiment, an automatically crafted response is sent to the individual who initiated contact, informing them whom to contact. Additional embodiments are also disclosed in the following sections.

Several related methods of solving this problem are indicated below.

Manager Forwarding Method Steps
1. User sends an email or other communications to one or more contacts
2. One or more contacts is no longer available at the specified address
3. Optionally, keyword analysis occurs to determine whether additional action should be taken

4. Invention initiates novel action to send the communication to a specified manager, which may be hard-coded or determined via look-up (e.g., from an Lightweight Directory Access Protocol (LDAP) directory at last time employee

1


Page 02 of 3

was in such a system)

Manager/Department Response Method Steps
1. User sends an email or other communications to one or more contacts
2. One or more contacts is no longer available at the specified a...