SYSTEM AND METHOD FOR RE-ROUTING OF E-MAIL MESSAGES

Abstract: A method and apparatus for the re-routing of e-mail sent to a prior address (or an address that is non-working, or temporarily inconvenient) to the new address of an intended recipient. E-mail that is to be sent to a recipient is sent to the former Internet Service Provider (ISP). Because the recipient is no longer a subscriber to the old ISP, or because the address at the old ISP is temporarily inconvenient, the e-mail is re-routed to a re-route server of the present invention. The re-route server then causes the e-mail to be sent to the correct address through a variety of processes. Alternatively, new e-mail addresses are made available at the old ISP. The old ISP can then forward e-mail messages directly to the new ISP.

Description: Title: System and Method for Re-routing of E-mail Messages Background Of The Invention The present invention is directed to a method and apparatus for redirecting network traffic. More particularly, the present invention is directed to a method and apparatus of re-routing electromc mail (or "e-mail") messages transmitted via the Internet. Background Art One of the most basic services offered by Internet Service Providers (or "ISPs") is a pπvate or corporate e-mail account that a customer may use for transmitting and receivmg electromc mail (e-mail) messages v the Internet. Each of these e-mail accounts has a umque address Internet service customers are notoπously fickle in their choice of ISPs. The customer turnover rate is typically 50% each year for most ISPs (those ISPs that do not have meaningful market competition have lower turnover, of course) When a customer closes an account at one ISP and opens a new account at another ISP, the customer cannot maintain the same e-mail address. This is a natural result of the currently used e-mail addressing convention wherein part of the address includes an identification of the ISP Thus, when the ISP changes, at least a part of the e-mail address must also change. This is inconvenient because e-mail gets lost. In the pπor art, e-mail messages sent to a defunct address (belonging to an inactive account) are either acknowledged as bemg undehverable or they are simply ignored. Colloquially, acknowledgement by an ISP that the message is undehverable as addressed is known as "bouncing" the message back to the sender Although this doesn't get the message to the intended recipient and it fails to inform the sender of a correct address (if any exists) for the intended recipient, at least it puts the sender on notice that they have attempted to use an inaccurate e-mail address. Simply ignoring an undehverable message, as is done by some ISPs, is quite non-helpful because the sender remains ignorant that the message was sent to an inaccurate address SUMMARY OF THE INVENTION The present invention is a method and apparatus for the rerouting of e-mail from a pπor or non-workmg address to the new address of a recipient. In general, two basic re-route methods are employed, varying as noted more fully below E-mail that is to be sent to a recipient is sent to the former Internet Service Provider (ISP). Smce the recipient is no longer a subscπber to the old ISP, the e-mail is re-routed to a re-route server of the present invention The re-route server then causes the e-mail to be sent to the correct address through a variety of means This embodiment provides pπvacy with respect to the new address of the recipient smce it is known only to the re-route server and NOT to the old ISP Alternatively, new e-mail addresses are made available at the old ISP The old ISP can then forward e-mail directly to the new ISP This has the advantage of a direct route from the old ISP to the new ISP However, pπvacy of the new e-mail address for the recipient is less smce the address is now known to the old ISP In either case, a business model aπses that allows this process to occur As noted above, there is a tremendous turnover in subscπbers to any particular ISP Realizing that, just as e-mail may be forwarded AWAY from an ISP, so can e-mail to other ISP's be forwarded TO the old ISP for new subscπbers Thus it is to all ISP's advantage to forward e-mail where possible In addition, user fees will be paid for this service Those entities running re-route servers could easily share revenue with the ISP's that are registered with the re-route service Thus not only will a valuable service be performed, but the ISP's can generate additional revenues from participation BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 illustrates the request handler for the " forward" implementation of the present mvention Figure 1A illustrates the e-mail re-route path through the re-route server for the forward implementation Figure IB illustrates the direct re-route path for the forward implementation Figure 2 illustrates the request handler for the alias table implementation of the present mvention Figure 2A illustrates the e-mail re-route path through the re-route server for the alias table implementation Figure 2B illustrates the direct e-mail re-route path for the alias table implementation Figure 3 illustrates the e-mail handler for a re-route customer Figure 3A illustrates the e-mail re-route path for the re-route customer Figure 4 illustrates the request handler for the DNS table implementation of the present mvention Figure 4A illustrates the e-mail re-route paths for the DNS table implementation Figure 4B illustrates the direct e-mail re-route path for the DNS table implementation of the present invention. Figure 5 illustrates a seize and forward implementation for re-route of messages. Figure 5A illustrates the e-mail path for the seize and forward implementation of the present invention. Figure 6 illustrates the request handler for the SMTP wrapper implementation of the present invention. Figure 6A illustrates the e-mail handler for the SMTP wrapper implementation of the present invention. Figure 6B illustrates the e-mail re-route path for the SMTP wrapper implementation of the present invention. Figure 7 illustrates the e-mail handler for bounced mail. Figure 7A illustrates the e-mail re-route path for bounced mail. Figure 8 illustrates the request handler for IPv6 address implementation of the present invention. Figure 8 A illustrates the e-mail re-route path for the IPv6 address implementation. Figure 8B illustrates the direct e-mail re-route path for the IPv6 address implementation. Figure 9 illustrates the X.500 database implementation of the present invention. Figure 9A illustrates the e-mail re-route path through the re-route server for the X.500 implementation of the present invention. Figure 9B illustrates the direct e-mail re-route path for the X.500 database implementation of the present invention. Figure 10 illustrates the re-route symbol implementation of the present invention. Figure 10A illustrates the e-mail handler for the re-route symbol implementation of the present invention. Figure 10B illustrates the e-mail re-route path for the e-route symbol implementation of the present invention. Figure 11 illustrates e-mail handler for the re-route extension implementation of the present invention. Figure 11 A illustrates the e-mail re-route path for the re-route extension implementation of the present invention. Figure 12 illustrates the Lightweight Directory Access Protocol (LDAP) client flow of the present mvention Figure 12A illustrates the e-mail re-route path for the LDAP implementation of the present mvention Figure 12B illustrates the direct e-mail re-route path for the LDAP implementation of the present mvention Figure 13 illustrates request handler for the Return Code implementation of the present mvention Figure 13A illustrates the e-mail re-route path for the Return Code implementation of the present mvention Figure 13B illustrates the direct e-mail re-route path for the Return Code implementation of the present invention Figure 14 illustrates the client plug in module implementation of the present mvention Figure 14A illustrates the e-mail re-route paths for the client plug in module implementation of the present mvention Figure 14B illustrates the direct e-mail re-route paths for the client plug in module implementation of the present invention Figure 15 illustrates a Re-route Add Request protocol accordmg to the present mvention Figure 16 illustrates a Re-route Delete Request protocol accordmg to the present invention Figure 17 illustrates a Re-route Edit Request protocol according to the present invention DETAILED DESCRIPTION OF THE INVENTION In the following descπption, the different embodiments of the mvention are explamed from the point of view of analyzmg how e-mail sent to a smgle mvalid (or undesrred) e-mail address is forwarded to a currently valid e-mail account This is a simplification of the general case, and is done for ease of explanation In the general case, an individual may have left behind a string of abandoned e-mail accounts that all need to be forwarded to their currently valid address When the simplified case is extrapolated to the general case, any of the embodiments descπbed below may be combined with one another to handle messages sent to different ones of the plural abandoned e-mail accounts Also for claπty of explanation, the convention is adopted that the ISP that is forwarding e-mails is called the "old ISP" and the ISP that hosts the currently valid account is called the "new ISP." The account for which the e-mail address is no longer current is called the "FROM account" and the current account, to which mail needs to be forwarded, is called the "TO account." By choice of this convention, the term "old ISP" is not meant to limit the disclosure to situations where an email account has been permanently terminated or abandoned at that ISP. Rather, the term "old ISP" is intended to encompass situations wherem a user having plural current e-mail accounts wishes to have e-mail addressed to one of those accounts temporaπly forwarded to another one of his or her accounts The .forward File Embodiment According to one embodiment of the invention, e-mail is forwarded from the old ISP to the new ISP by means of a " forward" file. The old ISP maintains the FROM account and inserts a .forward file that contains the TO account As a result, all e-mail is still routed to the old ISP The message passes through the old ISP's sendmail and the sendmail connects to the machine at the new ISP to deliver the message to the TO account (contained m the forward file) at the new ISP. This is implemented using UNIX. This embodiment requires that the old ISP keep the FROM account open after the user has abandoned it. The E-Mail Alias Embodiment Accordmg to another embodiment of the invention, the old ISP aliases the FROM account to the TO account with an /etc/aliases entry. This uses a lookup table. All e-mail is still routed to the old ISP. The message passes through the old ISP's sendmail and the sendmail connects to a new machine. A consistent address, e.g., user@re-route.com, is used for all customers, although this specific format is not meant as a limitation. Other formats are possible for this alias embodiment. A customer who cancels their re-route service agreement will still have his/her e-mail sent to another consistent address, e.g., cheapskate@re- route.com. This procedure should be supported in all Internet systems, as explamed in RFC (request for comment) 1123, which is incorporated by reference herem, in its entirety. This embodiment permits the old ISP to close the FROM account after the user has abandoned it The Transfer of Mail Exchange Authority with Pass-Through Sendmail Embodiment Accordmg to another embodiment of the mvention, the ISPs give MX Authoπty to a Re-route Central Authoπty entity (e.g., re-route.com). All e-mail destined for ISPs that have signed up with re-route.com are first routed to re-route.com. For those customers who have informed re-route.com of a change of address, the e-mail is routed to the TO account. Otherwise, the e-mail messages pass through the re-route.com system to the ISP to which they are nominally addressed. One result of this embodiment is that all e-mail for all ISPs that subscπbe to this system would need to pass through servers for the Re-route Central Authoπty entity. The Mail Exchange Routing Embodiment According to another embodiment of the mvention, a fundamental change is made to the way that e-mail is routed on the Internet The change is that client name resolver libraπes use the entirety of the addresses — both the user portion and the fully qualified domain name portion ~ for queπes. Based on this change of address interpretation, Mail Exchange Re-route Directory (MXRRD) keys can be used by Domain Name Servers to hold entries for individuals' e-mail accounts There are two alternate sub-embodiments of this re-route arrangement. One is that the Re-route Central Authoπty can be the Mail Exchange Authoπty and distπbute a master copy of a re-route mapping database. The other is that the ISPs maintain their respective Mail Exchange Authoπties and rely on the Re-route Central Authoπty to tπgger updates to the re- route mapping database Seize and Forward Embodiment In the "seize and forward" embodiment of the present invention, the ISP retains all of the customer account information However, for those customers that have left the ISP's service, all e-mail for such customers is stored at the ISP for a time. At regular intervals, the server of the present invention logs onto the server of the ISP and seizes all of the e-mail that is being stored for those accounts that are no longer active at the ISP. This "seized" or downloaded e-mail is sorted by the present mvention and for those accounts that have registered with the re-route server, the e-mail is forwarded to the new account at the new ISP Simple Mail Transfer Protocol (SMTP) Wrapper Embodiment The SMTP wrapper embodiment may be implemented via software or via hardware. In the software implementation, the SMTP wrapper is a software wrapper around an ISP's message transport system such as "sendmail," program that determines how that wrapped code is to be executed. In the hardware implementation, the SMTP wrapper is a device disposed, preferably, between an ISP and the Internet, to mtercept e-mail messages. Thus, the SMTP wrapper determines how the sendmail transport program of the ISP is to operate. In this case, the wrapper passes through e-mails that are bound for those individuals who formerly had an account at the ISP. E-mails that are passed through the ISP are sent to the server of the present mvention for forwarding to the individual at the new ISP. Bounced Mail Embodiment The bounced mail embodiment of the present mvention allows those ISP's that "bounce" mail, that is, return mail to a sender when the party to whom it is addressed is no longer available for any reason, to bounce the mail instead to the re-route server of the present invention. In this embodiment, any mail that cannot be delivered by an ISP is bounced to, for example, bounced@re-route.com. The re-route server then reviews the bounced mail to determine if it is for a person or entity that is a registered re-route user. If so, the mail is forwarded to the new address on file at the re-route server IPv6 Embodiment A pressmg problem that now exists is the potential for shortages of Internet addresses. The most viable candidate to replace the cuπent Internet Protocol is Internet Protocol Version 6 (IPv6). This protocol allows a huge number of new IP unique addresses to be possible together with new routing schemes. DNS can resolve fully qualified domam names into IP addresses. Assuming that everyone will be able to have a umque IPv6 address in the future, traffic can be re-routed to individuals based on their respective IPv6 addresses OSI X.500 Embodiment The Open Systems Interconnect (OSI) model is a model of network architecture and a suite of protocols to implement it developed by ISO as a framework for international standards in heterogeneous computer network architecture. X.500 (the set of ITU-T standards covermg electromc directory services, such as white pages, Knowbot, and whois.) can support alternate addresses for individuals/recipients of e-mail. Such an X.500 system connected to the Internet e-mail system could re-route e-mail to the alternate addresses once they have been so designated by a user. In this mstance the X 500 system receives e-mail at fromAccount If the user has a toAccount entry, the mail is re-routed. "Forwarding" Symbol in Local-Part Embodiment Internet Standard R-FC-822 defines the Internet standard format for electromc mail message headers. By usmg the "local part" of the mail message header, e-mail can be forwarded. For example, the address @gstead@mlj.com contains a symbol "@" before the name to designate a forwardmg symbol. Alternatively a new symbol such as "rr!" might be designated as the umversal re-route symbol for e-mail. While this does not designate a specific address, it does indicate to any server that the mail is to be re-routed if possible. Then certam of the other methods for re-route descπbed herein can be used such as forwardmg mail to the re-route server. In this instance, the sendmail systems must be programmed to recognize and treat a umversal symbol as meamng re-route. Re-route Extensions Embodiment The re-route extension embodiment allows users to simply append the extension ".re- route.com" to an e-mail address (e g., user@oldisp.com.re-route.com). This will provide automatic re-routing of e-mail if a recipient has so registered. If no re-route information has been provided, the e-mail is simply passed through to the oπgmal address. In this case the re- route server becomes the MX authoπty for re-route.com e-mail, thus all e-mail having the extension is re-routed to the re-route server to be reviewed LDAP Embodiment The Lightweight Directory Access Protocol (LDAP) is a protocol for accessmg on- line directory services. The e-mail client can download the fromAccount, toAccount list directly mto e-mail client software for addressing e-mail. Thus, changmg addressmg from one account another, by acquiπng the correct e-mail address, can be done at the client computer Routing of the e-mail to the correct address can then be accomplished. SMTP Return Codes It is possible for SMTP implementation to veπfy that e-mail addresses are deliverable dunng the sendmg process. If a given e-mail is not deliverable to a first, old address, the e- mail can be delivered to a second host, assuming that the appropπate address at the new second host is known. This forwarding is done directly by the old ISP, which forwards the message either to a re-route server (and then, indirectly, on to the user's new address) or directly to the user's new account at a new ISP These direct and indirect methods are explained m further detail below Client E-mail Plugin This embodiment takes advantage of the common practice of many ISPs to bounce undehverable emails back to the sending computer. A software plugm or wrapper is provided at the sendmg computer, which handles e-mail messages that are bounced back to it. When an e-mail message is bounced back, the e-mail plugm prompts the user to ask them if they would like to attempt to re-route the bounced email usmg any of the methods descπbed herem. This is done, for example via a graphical user interface having a "re-route" button that the user may click on. In the event the user chooses to click the re-route button, thereby choosing to attempt a reroutmg of the e-mail message, the e-mail message is then resent, this time addressed to the re-route server. The re-route server then forwards the message on to the correct current e-mail address for the intended recipient, assuming that the intended recipient's new e-mail address is registered with the re-route server. As noted above, the present invention compπses a method and apparatus for reroutmg e-mail destined for a person or entity formerly located at a given ISP and forwarding that e- mail to the new e-mail address for the recipient who may be located at a subsequent ISP. Referring to Figure 1, the request handler for the " forward" implementation of the present mvention is illustrated. The user who desires to have its e-mail redirected registers with the re-route server of the present invention. The re-route server sends a re-route request to the old ISP. The request is received at the old ISP 10, which is usually accompamed by a digital signature of the requesting party. The digital signature is decoded 12, and the request along with the digital signature is provided to a process for determinmg whether the re-route request message is a valid one 14. If the message is determined not to be valid, as in the case of an individual who is not a client or former client of the old ISP, for example, an error is noted and the process ends 16. If the message is a valid one, the request to re-route the e-mail is decrypted 18 and a determination is made whether authentication is required 20. If authentication is required, the user is authenticated 22. If the authentication is successful 26, the address to which the user would like mail forwarded is wπtten to a ".forward" file 24 m the storage of the old ISP. If the user can not be authenticated, the process is terminated and an authentication error is sent to the requesting party 30. On the other hand, once the new address is wπtten to the .forward file of the old ISP, the request process is completed 28, and the server simply waits for e-mail traffic addressed to the old address of the user Referring to Figure 1A, a first embodiment of the e-mail re-route path is illustrated. This figure illustrates the path of re-routed e-mail after an authenticated request is processed. Sender computer 32 sends e-mail to a recipient at the old ISP address 34 of the recipient. The old ISP 34 recognizes that the recipient is no longer subscπbing to that ISP, and designates any mail for that recipient to be sent to the re-route server 36 based upon the .forward file stored at the old ISP and designatmg the re-route server as the location m the forward file Old ISP 34 therefore forwards the recipient's e-mail over the Internet 42 to the re-route server 36 The old ISP 34 reviews the accounts of its subscπbers and matches the incoming e-mail for the recipient to an address m its forward file, which m this implementation is at the re- route server 36. Thereafter, the e-mail is re-addressed to the re-route server 36, which m turn associates that e-mail with the new address of the recipient at the new ISP The re-route server 36 then forwards the e-mail to the new ISP 38 which stores the e-mail until downloaded by the recipient's computer 40 As noted above this implementation provides secuπty for the new address of the recipient in that the address is known to the re-route server but not to the old ISP Referπng to Figure IB, a direct e-mail re-route path of the present invention is illustrated In this instance, re-route server 36 is notified by a user of the mtent to re-route mail as descπbed in Figure 1 above Re-route server provides a re-route request to the old ISP as descπbed m Figure 1 In this case however, that information to the old ISP compπses the new address of the recipient at the new ISP 38 Thereafter, a sender computer 32 sends an e- mail message to the pπor address of the recipient at the old ISP 34 ISP 34 has been notified by the re-route server 36 of the new address of the recipient The old ISP 34 then reviews its forward files, finds the re-route request of the recipient, designates mail commg to the recipient's old address with the new ISP address The message is then forwarded over the Internet 42 to the new ISP 38, which generally stores the e-mail until downloaded by the recipient 40 Referπng to Figure 2, the e-mail alias embodiment of the re-route request handler is illustrated Again, a user registers with the re-route server of the present invention The re- route server then sends a re-route request to the old ISP This alternative embodiment re- route request handler functions m a similar fashion as descπbed in Figure 1 (above), except that when a decrypted request 18 is determined to either require authentication 20, thus resulting in an authenticated user 22 and the determination that the authentication was successful 26, or alternatively, authentication is not required, an alias table is created in the old ISP wherem the recipient's former Internet address is mapped to a new address in the table Referπng to Figure 2 A, the e-mail re-route path of the alternative embodiment descπbed m Figure 2 is shown. In this instance the sender has registered with the re-route server 36 and the re-route server 36 has sent its re-route request to the old ISP naming the re- route server as the entity to be listed m the alias file of the old ISP for e-mail sent to the user. The sender's computer 32 sends an e-mail message addressed to the recipient's old e-mail address at the old ISP 34. The old ISP 34 recognizes that this is a message to be re-routed smce there is a valid re-route request stored at the old ISP The old ISP reviews its alias table and finds that the alias for the recipient is the address of the re-route server 36 The old ISP passes the message through its sendmail to the re-route server 36 The re-route server looks at its alias table for the recipient, and determines the recipient's new e-mail address. The mail is then forwarded via the Internet 42 to the new ISP 38, where it is stored until downloaded by the recipient's computer 40 Referπng to Figure 2B, the direct e-mail re-route path of the e-mail alias embodiment shown in Figure 2 is illustrated. In this instance, re-route server 36 provides the alias for the recipient to the old ISP 34 Thereafter, a sender's computer 32 sends an e-mail message to the recipient addressed to the old ISP 34 Old ISP 34 reviews its alias table to determine the new e-mail address of the recipient and re-addresses the mail directly to the new ISP 38, which m turn sends it on to the recipient 40 via the Internet 42. Referπng to Figure 3, the mail exchange authoπty with pass-through sendmail alternative embodiment re-route handler is shown. In this embodiment, the re-route server becomes the MX authoπty for the ISP(s) that register with the service. In this mstance, the figure illustrates a situation where the re-route server functions as a gateway for all e-mail destined for a number of different ISPs. In this instance, vaπous ISPs subscπbe to the re-route service, and all e-mail destmed for any of the ISPs that are subscπbers initially are routed to the re-route server. In this instance, e-mail is received at the re-route server 44 The server checks to see if the recipient is a re-route customer 46. A re-route customer is an individual who has signed up with the re-route server to have his or her e-mail forwarded to a new address. If the recipient is not a re-route customer 46, the re-route server takes no action with respect to the e-mail, but simply allows it to go forward to the recipient's ISP 48 If, however, the recipient is determmed to be a re-route customer, the e-mail is forwarded to the recipient's "toAccount" address which has been provided by the re-route customer to the re-route server 50. Referring to Figure 3 A, the e-mail re-route path of the alternative embodiment of Figure 3 is shown. Sender computer 32 addresses e-mail to a recipient. That e-mail goes directly to re-route server 36, which makes the determination as to whether the recipient is a re-route customer or not. If the individual is not a re-route customer, the e-mail is simply sent on its way to the old ISP 34. If, however, the re-route server 36 determines that the recipient is a re-route customer, the e-mail is forwarded to the new ISP 38 over the Internet 42 for storage and subsequent download to the recipient 40. Referring to Figure 4, the request handler of yet another alternative embodiment of the present invention is illustrated. This request handler operates in the same respect as Figures 1 and 2, except that, after successful authentication 20, 22, 26, or, in the case where authentication is not required, a re-route customer's "toAccount" is written to a DNS table 23, thereby providing an address for the recipient different from that to which messages might be sent. In this instance, a sender might realize that a recipient has moved but does not know the address of the recipient. In this case, the sender sends messages directly to the re-route server in anticipation that this message will be forwarded to the recipient. Referring to Figure 4 A, the e-mail re-route path of the present invention is illustrated. In this instance, sender's computer 32 sends an e-mail message directly to the re-route server 36 which has the DNS table associated with the new address of the recipient stored therein. Thereafter, re-route server 36 re-addresses the e-mail to the recipient at the new ISP 38 for delivery to the recipient 40 over the Internet 42. Referring to Figure 4B, the e-mail direct re-route path noted in Figure 4 is illustrated. Here, the sender computer sends its message to the re-route server 36. In this instance, however, the re-route server 36 provides the new address to the sender's computer 32. Thereafter, the sender's computer 32 can send e-mail to the new ISP address of the recipient 38, which is then forwarded to the recipient 40 over the Internet 42. Referring to Figure 5 the seize and forward implementation of the present invention is illustrated. The process is initiated 52. The timer is next initialized 54 to set the frequency with which e-mail is retrieved from the ISP at which a user's e-mail is located. The system at the re-route server determines whether the initialized timer has expired 56, thereby signaling that retrieval of e-mail must take place. If the timer has not expired, the re-route server waits 58 and continues to query the timer. If the timer has expired, the re-route server logs onto the old ISP 60 from which mail must be retπeved The re-route server inquires if there is mail for the specific re-route customer 62 If e-mail is present, the e-mail is retπeved by the re-route server 64 and forwarded to the customer's toAccount 66 which is known to the re-route server Thereafter the process begms agam and waits until the next retπeval time If there is no e-mail for the re-route customer, the re-route server simply waits until the next time interval for retπeval to be attempted Referπng to Figure 5A the e-mail re-route path for the seize and forward implementation is illustrated Sendmg computer 32 send e-mail to the re-route customer at the old ISP The old ISP recogmzes that this is a former subscπber and stores the e-mail Re- route server 36 makes in retπeval inquiry with the former ISP 34 Mail is then downloaded to the re-route server 36 where it is forwarded to the new address at a new ISP 38 over the internet 42 Thereafter, the recipient/re-route customer 40, retπeves the e-mail in the normal course of activities Referπng to Figure 6, the request handler for yet another alternative embodiment of the present invention is illustrated Again, this request handler functions in exactly the same manner as that descnbed in Figure 1 (above), except that rather than wπting the "toAccount" to a forward file or to an alias file, the toAccount is wπtten to a pπvate alias file for subsequent use in forwardmg e-mail to the new ISP Referπng to Figure 6A, the e-mail handler of the alternative preferred embodiment descπbed in Figure 6 is illustrated E-mail for the recipient is received 68, and a determination is made by the re-route server whether the recipient is in the pπvate alias file 70 If the individual is not m the pπvate alias file, the e-mail is presented to the old ISPs e- mail software 72 If, however, the recipient is m the pπvate alias file 70, then the e-mail is forwarded to the recipient's "toAccount" 74 The e-mail re-route path of the embodiment of Figure 6 is illustrated in Figure 6B. This re-route path is similar in all respects to that descπbed in Figure 1A, except that re-route server 36 has a pπvate alias file which determines the address to which mail for the recipient will proceed Referπng to Figure 7, another alternative embodiment of the present invention is illustrated In this instance, ISPs subscπbe to the service of the re-route mvention When an old ISP bounces mail that is sent to a former recipient who was a subscπber to the old ISP, a bounced mail message is sent both to the sender's computer and to the re-route server. Thereafter, if the re-route server determines that the mail is destined for a recipient who is a re-route customer, it is forwarded appropπately. For example, mail is received at the re-route server 76. The re-route server determines if the mail is bounced mail 78 coming from an old ISP. If the mail commg to the re-route server is not bounced mail 80, the process terminates. If the mail reaching the re-route server is bounced mail, the re-route server determines if the mail is addressed to a recipient who is a re-route customer 82. If the person to whom the bounced mail is addressed is not a re-route customer, the process is terminated 84. If, however, the e-mail is destined to a re-route customer having a "toAccount" with the re-route server, that mail is forwarded to the recipient's latest e-mail address 86 Referπng to Figure 7A, the e-mail re-route path of the embodiment noted in Figure 7 is illustrated. In this instance, sender's computer 32 sends e-mail destined to the old e-mail address of a recipient to the old ISP 34 Old ISP 34 is a subscπber to the re-route service of the present invention It sends a bounced mail message to the sender's computer 32 and also to the re-route server 36. If the recipient to whom the mail is addressed is a customer of the re-route server 36, the re-route server checks to determine the new e-mail address of the recipient and forwards the e-mail over the Internet 42 to the new ISP 38. New ISP 38 then forwards the mail to the recipient 40. Referπng to Figure 8, yet another alternative embodiment of the present mvention is illustrated. In this instance, the request handler operates in the same manner as first noted m Figure 1 (above). However, after appropπate authentication processes 20, 22, 24 the toAccount and EP address of the recipient is updated 29 Referπng to Figure 8A, the re-route path for the embodiment descπbed in Figure 8 is shown. In this instance, a sending computer 32 sends an e-mail addressed to the old ISP 34. The old ISP 34, knowing that the recipient has moved, forwards the message to the re-route server 36. The re-route server 36 has had its toAccount and IP address for the recipient updated. The e-mail address is changed by the re-route server 36 and directed to the new ISP 38 for deliver over the Internet 42 to the recipient 40. Referπng to Figure 8B, the e-mail re-route direct path is shown. In this instance, re- route server 36 provides the appropπate toAccount and IP address update to the old ISP 34. Thereafter, when the sending computer 32 sends an e-mail message to the recipient's address at the old ISP 34, the old ISP 34 can forward that e-mail to the new ISP 38 over the Internet 42 for delivery to the recipient 40. Referπng to Figure 9, an alternative embodiment of the present invention is shown. In this mstance, request handler functions m the same manner as noted in Figure 1 (above). However, after appropπate authentication processes 20, 22, 26, the toAccount is updated and wπtten to a X.500 database. The database is subsequently provided to the old ISP for processing of re-routed e-mails. Referπng to Figure 9A, the indirect e-mail re-route path of the embodiment of Figure 9 is illustrated. In this case, re-route server 36 provides the updated X.500 database to the old ISP 34 Thereafter, a sender's computer 32 sends an e-mail to a recipient at the old ISP 34 Old ISP 34 matches the incoming e-mail with the X.500 database and forward the e-mail on to the re-route server 36 via the Internet 42. The re-route server 36 then handles sending the e- mail to the recipient. The e-mail is re-addressed and sent to the new ISP 38 over the Internet 42 for subsequent delivery to the recipient 40 Referπng to Figure 9B, the direct e-mail re-route path of the embodiment of Figure 9 is illustrated. In this instance, re-route server 36 provides the updated X.500 database to the old ISP 34. Thereafter, a sender's computer 32 sends an e-mail to a recipient at the old ISP 34. Old ISP 34 matches the incommg e-mail with the X 500 database and new address for the recipient. Thereafter, the e-mail is re-addressed and sent to the new ISP 38 over the Internet 42 for subsequent delivery to the recipient 40. Referπng to Figure 10, an additional alternative embodiment of the present mvention is illustrated. In this instance, an old ISP receives e-mail 52 The server of the old ISP reviews the e-mail to determme if the e-mail contams a symbol mdicative of the fact that this e-mail is to be re-routed to another location 54. If there is no re-route symbol, processmg of the e-mail continues in the normal fashion 56 In the event that there is a re-route symbol associated with the e-mail message, the message is forwarded to the re-route server 58. Referπng to Figure 10A, e-mail handling in the re-route server is illustrated. The re- routed e-mail is received at the e-mail handler of the re-route server 60. The re-route server determines if the re-route symbol is present 62. If there is no re-route symbol, processing ceases. If there is a re-route symbol present, the re-route server determines if the recipient of the message is a re-route customer 66. If the recipient is not a re-route customer, processmg terminates 68. If the individual is a re-route customer, the e-mail is forwarded to the recipient's toAccount 70. Referπng to Figure 10B, the e-mail re-route path is shown. Sender 32 sends an e-mail message that is knows must be re-routed to the recipient. However, the sendmg computer 32 only knows the recipient's old e-mail address. Therefor, the e-mail is addressed to the old ISP 34. However, the message also compπses a re-route symbol. Old ISP 34 recogmzes the re- route symbol and sends the e-mail on to the re-route server 36. Re-route server 36 determmes if the recipient is a re-route customer and, if so, forwards the e-mail to the new ISP 38 over the Internet 42 for delivery to the recipient's computer 40 Referπng to Figure 11, yet another embodiment of the present mvention is illustrated. In this mstance, e-mail is received 72 at the re-route server The re-route server determines if there is a re-route extension on the e-mail address 74. If the extension is not present. processing ceases 76. If a re-route extension is present on the e-mail message, the re-route server determmes if the recipient is a re-route customer 78, that is, an individual who is registered for the re-route service If the individual is not a re-route customer, the message is delivered to the oπgmal ISP 80. If, however, the recipient is a re-route customer, the e-mail is forwarded to the recipient's toAccount, as stored by the re-route server 82. Referπng to Figure 11 A, the e-mail re-route path of the embodiment illustrated in Figure 1 1 is shown. Sendmg computer 32 sends an e-mail message with a re-route extension to the re-route server 36. Re-route server 36 determines if the individual to whom the message is sent is a re-route customer. If the individual is not a re-route customer, the message is sent to the old ISP 34. If the individual is a re-route customer, the message is re- routed to the new ISP 38 over the Internet 42 for delivery to the recipient 40 Referπng to Figure 12, the LDAP client functionality is shown. A request is first made to obtain an address for a recipient 84 that a sender knows has moved. The re-route LDAP server is queπed 86 for the re-route address. The re-route server determmes if a re- route address is available 88. If no address is available, the client can not re-route the e-mail 90. If a new e-mail address is available, the "to" address for the recipient is updated m the client computer 92. Thereafter, the address update is completed and e-mail messages can be sent. Referπng to Figure 12 A, the e-mail re-route path of the embodiment noted m Figure 12 is illustrated. Sending computer 32 queπes the re-route server computer 36 for a re-route address for a recipient. This is the instance where the sendmg computer knows that the recipient has moved, but is unaware of the new address. If there is a re-route address for the recipient, the mail is forwarded to the new ISP 38 over the Internet 42 for delivery to the recipient 40 In addition, the re-route server notifies the sender's computer to update its "to" address file. Referring to Figure 12B, the direct e-mail re-route path is shown. This is fairly simple after the "to" file for the recipient is updated by the re-route server 36 Thereafter, the sendmg computer 32 has the appropπate address of the new ISP 38 and mail can be forwarded to the new ISP 38 over the Internet 42 to the recipient 40. Referπng to Figure 13. a re-route request handler of yet another embodiment of the present mvention is illustrated. This request handler operates in the same fashion as first noted in Figure 1 (above). However, after the authentication procedures 20, 22, 26, the toAccount for the recipient is wπtten to an SMTP table This SMTP table 31 holds the new address for receiving e-mail Referπng to Figure 13A, the e-mail re-route path is illustrated. Sending computer 32 sends an e-mail message to the recipient's last known e-mail address at the old ISP 34. The old ISP 34, recogmzmg that this recipient is no longer at the ISP, forwards the message to the re-route server. The re-route server receives the toAccount information for the recipient and matches it to the entry in the SMTP table stored at the re-route server 36. Thereafter, the message is re-addressed and sent to the new ISP 38 over the Internet 42 for delivery to the recipient 40 Referπng to Figure 13B, the e-mail re-route direct path is illustrated. In this instance, the old ISP 34 contams the SMTP table and associated address relating to the toAccount of the recipient. The sending computer 32 sends the e-mail address to the recipient's address at the old ISP 34 Old ISP 34 matches the toAccount information to the SMTP table and forwards the e-mail over the Internet 42 to the new ISP 38 for delivery to the recipient 40. Referπng to Figure 14, a client plug-m module for the re-routmg of e-mail is illustrated. E-mail is received at the client 96. The e-mail is then reviewed to determme if it is bounced e-mail 98. If the e-mail is not bounced, the client plug-m performs no further processing 100. If the e-mail is bounced, the user is prompted to re-route the e-mail 102. The user then decides whether to re-route the e-mail 104, and if not, processmg terminates 106. If the user wants to re-route the e-mail, the e-mail is forwarded to the re-route server 108 Referπng to Figure 14A, the e-mail re-route path is shown. Sending computer 32 sends an e-mail to the old ISP 34. Old ISP 34 notes that the recipient is no longer present and bounces the e-mail back to the sendmg computer 32. Sendmg computer 32 notes that the e- mail is bounced e-mail, and therefor forwards it to the re-route server 36. Re-route server 36, recogmzmg that the recipient is a re-route customer, forwards the e-mail to the new ISP 38 over the Internet 42 for delivery to the recipient 40. Referπng to Figure 14B, the e-mail re-route path that is more direct is shown. In this mstance, sendmg computer 32 sends an e-mail to the old ISP address for the recipient 34. The old ISP bounces the e-mail back to the sendmg computer 32, having the new e-mail address via its plug-in module, then sends e-mail to the new ISP 38 over the Internet 42 for delivery to the recipient 40 Referπng to Figure 15, the Re-route Add Request flow is illustrated. A user creates the user data 200 that indicates the new e-mail address to which the user would like e-mail forwarded. The user data 200 may, alternatively, be created by the user's new ISP on the user's behalf. This user data 200 is sent to the re-route server, which compπses software for receivmg and processing user data 202. The re-route server checks the user data 204 to msure that all necessary information is present to form the re-route request and to register the user with the re-route server. If the data is in any way deficient, the re-route request is denied and a message so indicating is sent 206 to the user's computer (or the user's new ISP, as the case may be) If the data is sufficient, a re-route request is formulated 208 and sent to the re-route request handling routine 210 at the old ISP Once a re-route request is receive at the old ISP from the re-route server, the old ISP checks to determine if the request has the necessary data 214 to be acted on by the old ISP This involves the old ISP checkmg its own user records 212 to determine if the user is a subscπber to the old ISP, to update its subscπber records regardmg the status of the user, as well as to update the e-mail tables 216 at the old ISP to reflect the action needed for e-mail destined for the user. Such action has been descπbed m detail m a vaπety of embodiments (above) If the request is satisfactory m all respects, the re-route request is accepted and an acceptance message 220 is sent to the re-route server, and the e-mail re-route request is confirmed to the user 224 (or the user's new ISP, as the case may be). If the data supplied to the old ISP is not satisfactory in all respects, a re-route denial message 218 is sent to the re- route server, and a "re-route denied" message 222 is sent to the user (or the user's new ISP, as the case may be). Referring to Figure 16, the Re-route Delete Request flow is illustrated. Part of any re-route request of a user is a length of time for which the re-route request is to be in force. This may be set by the user or may be a standard amount of time set by the re-route server business rules. Once the time duration for the re-route request has expired, the re-route server generates an extension request 228 that is sent to the user's mailbox 226 or to the user's last known ISP. The system then waits for a user's response 230. If there is no response from the user within a given amount of time, a re-route delete request 232 is automatically generated by the re-route server and forwarded to the request handler 234 of the old ISP. The old ISP then updates its e-mail tables 236 by deleting the forwarding address for the user. After updating its e-mail tables 236, the old ISP sends an acknowledgment message 238 to the re-route server. The re-route server accepts the message 240, ends its re-route service for the user 242, and forwards a message so indicating to the user's mailbox 244 at the user's computer (or the user's ISP, as the case may be). Referring to Figure 17, the Re-route Update Request flow is illustrated. A user creates the updated user data 250 that indicates the updated e-mail address to which the user would like e-mail forwarded. The updated user data 250 may, alternatively, be created by the user's new ISP on the user's behalf. This updated user data 250 is sent to the re-route server, which comprises software for receiving and processing updated user data 252. The re-route server checks the updated user data 254 to insure that all necessary information is present to form the re-route update request and to register the user's updated data with the re-route server. If the data is in any way deficient, the re-route update request is denied and a message so indicating is sent 256 to the user computer (or the user's new ISP, as the case may be). If the updated data is sufficient, a re-route update request is formulated 258 and sent to the re-route update request handling routine 260 at the old ISP. Once a re-route update request is received at the old ISP from the re-route server, the old ISP checks to determine if the re-route update request has the necessary data 264 to be acted on by the old ISP. This involves the old ISP checking its own user records 262 to determme if the user was (or is) a subscπber to the old ISP, to update its subscnber records regardmg the status of the user, as well as to update the e-mail tables 266 at the old ISP. If the request is satisfactory m all respects, the re-route update request is accepted and an acceptance message 270 is sent to the re-route server, and the e-mail re-route update request is confirmed to the user 274 (or the user's new ISP, as the case may be). If the updated data supplied to the old ISP is not satisfactory m all respects, a re-route update demal message 268 is sent to the re-route server, and a "re-route update denied" message 272 is sent to the user (or the user's new ISP, as the case may be). The re-route server is implemented as follows. The e-mail re-route server receives e- mails from the Internet and re-routes them according to the rules descπbed above The e-mail server is based on known, robust, Internet e-mail server architectures. Preferably, the re-route server is one or more Umx-based machines runmng the sendmail mail software. In addition to typical e-mail processmg, the re-route server's mail software performs additional, optional operations These additional operations include: - interfacing to the re-route subscπber database/tables to query information on subscπber preferences (status, spam filtering, sender notification, virus checking, etc.) - interfacing to the re-route subscπber database/tables to insert information about current events (e-mail status, sender, date, etc.). This information will be used for billing and report generation - Additional e-mail processing (spam filtering, virus checking, sender notification, etc.) Hardware requirements depend on the number of customers, however as an example, a system that handles a moderate number of re-route subscπbers mcludes a Sun server runmng the Solans (Unix) operatmg system. A database server holds information about each customer, and about the e-mails received by the mail re-route server. This information is used for billing and report generation. The database server is based on known, robust, database server architectures. Preferably, this server is a Umx-based machine runmng Oracle or MySQL database server software. The present invention has been descπbed m terms of a number of prefeπed embodiments. However, it will be understood by those of ordmary skill m the art that vaπous modifications and improvements may be made to the invention as descπbed, without departing from the scope of the invention. The scope of the invention is limited only by the appended claims.

Claims: We Claim 1 A method of re-routmg e-mail compnsmg a recipient registeπng with a re-route server, the re-route server sendmg a re-route request to an old ISP, the old ISP receivmg and processmg the re-route request, and the old ISP re-routing e-mail for the recipient to a new ISP after the receipt and processmg of the re-route request 2 The method of re-routmg e-mail of claim 1, wherem the re-route server sendmg a re-route request to an old ISP further compπses the re- route server sendmg a new address for the recipient to the old ISP 3 The method of re-routing e-mail of claim 2, wherem the new address for the recipient compπses the address of the new ISP at which the recipient is located 4 The method of re-routmg e-mail of claim 2, wherem the new address for the recipient compπses the address of the re-route server 5 The method of re-routing e-mail of claim 2, further compπsing the old ISP maintaining a "FROM" account for the recipient, inserting a " forward" file compnsmg a "to" account compπsing the new address for the recipient, and forwarding e-mail for the recipient to the new address when it is received at the old ISP 6 The method of re-routing e-mail of claim 2, further compnsmg the old ISP mamtaimng and aliasing a FROM account for the recipient with an alias entry compnsmg the new address for the recipient, and forwarding e-mail for the recipient to the new address when it is received at the old ISP 7 The method of re-routmg e-mail of claim 6, wherem the alias entry is stored in a look up table 8 The method of re-routmg e-mail of claim 2, further compnsmg the old ISP maintaining an X 500 database, inserting a "to" account entry into the X 500 database compnsmg the new address of the recipient, and forwardmg e-mail to the new address when it is received at the old ISP 9 The method of re-routmg e-mail of claim 2, further compnsmg maintaining a DNS table to which the new address compnsmg a "to" account entry is wntten; and forwardmg e-mail to the new address when the DNS table is accessed. 10. The method of re-routmg e-mail of claim 2. further compnsmg: wnting a "to" account compnsmg the new address for the recipient to a pnvate alias file, passmg e-mail for other recipients whose addresses are not in the pnvate alias file to e-mail software of the ISP's; and forwarding e-mail for the recipient to the "to" account for the recipient. 1 1. The method of re-routing e-mail of claim 2, wherem the new address for the recipient is in Internet Protocol version 6 (IPv6) format; and further compπsing forwardmg e-mail for the recipient to the new address when it is received at the old ISP 12 The method of re-routmg e-mail of claim 2, further compnsmg: the re-route server generating a statistical record of the re-route request 13. The method of re-routmg e-mail of claim 12, wherem the generated statistical record includes information regarding the old ISP and the new ISP. 14 The method of re-routmg e-mail of claim 12, wherem the generated statistical record includes information indicating customer churn. 15. The method of re-routmg e-mail of claim 12, wherem the generated statistical record is added to an aggregated register of from and to data for a plurality of users 16. The method of re-routmg e-mail of claim 2, wherem the old ISP automatically forwards e-mail directed to an old address at the old ISP to the new address, consistent with Simple Mail Transfer Protocol 17. A method of re-routmg e-mail compnsmg: a recipient, that formerly had an old e-mail address at an old ISP, registering a request to re-route the recipient's e-mail with a re-route server; the old ISP stoπng e-mail for the recipient; the re-route server accessing and downloadmg the e-mail for the recipient stored at the old ISP; and the re-route server forwardmg the downloaded e-mail to a new address for the recipient. The method of re-routmg e-mail of claim 17, wherem the accessing and downloadmg occurs on a penodic basis The method of re-routmg e-mail of claim 17, wherem the request to re-route the recipient's e-mail compnses the old address of the recipient at the old ISP and the new address to which the recipient wants the recipient's e-mail forwarded A method of re-routmg e-mail compnsmg a recipient registering a request to re-route the recipient's e-mail with a re-route server, the re-route server sendmg the re-route request to an old ISP, the old ISP receivmg and processmg the re-route request, the old ISP bouncmg mail for the recipient to the re-route server when the recipient no longer has an e-mail address at the old ISP, the re-route server receivmg the bounced e-mail for the recipient, and the re-route server forwardmg the e-mail to a new address for the recipient The method of re-routmg e-mail of claim 20, wherem the request to re-route the recipient's e-mail compπses an old address of the recipient at the old ISP and the new address to which the recipient wants the recipient's e-mail forwarded A method of re-routmg e-mail compnsmg a sender of e-mail addressing e-mail to a recipient, the e-mail address compnsmg a universal re-route symbol m the local part of the e-mail address, if the recipient is not a subscnber of an old ISP, the old ISP checking if a umversal re- route symbol is present m the local part of the e-mail address, if a umversal re-route symbol is present m the local part of the e-mail address, the old ISP forwarding the e-mail to a re-route server, the re-route server receiving the forwarded e-mail and forwardmg the forwarded e- mail to a new address associated with the recipient The method of re-routing e-mail of claim 22, wherem the re-route server receivmg the forwarded e-mail further compπses the re-route server checkmg if a universal re-route symbol is present in the local part of the e-mail address, and if the recipient is a registered re-route customer, forwarding the e-mail to the new address A method of re-routmg e-mail compnsmg a sender of e-mail addressmg e-mail to a recipient, the overall e-mail address compπsing an old address of the recipient at an old ISP and a re-route extension to the e-mail address designating a re-route server; receivmg and processing the e-mail at the re-route server; the re-route server checking to determme if the recipient is a re-route customer; forwardmg the e-mail to a new address associated with the recipient if the recipient is a re-route customer. 25. The method of re-routmg e-mail of claim 24, wherem the receiving and processmg further compπses the re-route server checking if a re-route extension is present m the overall e-mail address; and ceasmg further processing if no re-route extension is present. 26. The method of re-routmg e-mail of claim 24. further compnsmg passmg the e-mail through to the old address if the recipient is not a re-route customer. 27. A method of re-routmg e-mail compnsmg: a sendmg computer querying a re-route server for an e-mail address of a recipient; the re-route server determining if an e-mail address for the recipient is available; if an e-mail address for the recipient is available, the re-route server forwardmg e-mail sent by the sendmg computer to the recipient at the e-mail address. 28. The method of re-routing e-mail of claim 27, wherem the sender computer query compnses a query under the lightweight directory access protocol (LDAP). 29 A method of re-routmg e-mail compnsmg: a sending computer querying a re-route server for an e-mail address of a recipient; the re-route server determining if an e-mail address for the recipient is available: if an e-mail address for the recipient is available, the re-route server providing that address to the sending computer; and the sendmg computer re-addressmg the e-mail to the recipient at the e-mail address. 30. The method of re-routing e-mail of claim 29, wherem the sender computer query compnses a query under the lightweight directory access protocol (LDAP). 31. A method of re-routmg e-mail compnsmg: an old ISP assigning its mail exchange authoπty to a re-route server; the re-route server receiving e-mail addressed to subscπbers at the old ISP; the re-route server comparing the addresses of subscπbers to a re-route customer list, the re-route customer list compnsmg new e-mail addresses for re-route customers; the re-route server forwardmg e-mail addressed to re-route customers to the new e- mail addresses, and the re-route server passing the e-mail through to the old ISP if the subscπber is not a re-route customer A method for re-routmg e-mail compnsmg addressmg e-mail using the user portion and the fully qualified domam name portion of e-mail addresses, creating a mail exchange re-route directory m a re-route server compnsmg an entry for a recipient's new e-mail address mapped to an old e-mail address of the recipient, peπodically distπbutmg the re-route directory to ISPs for forwarding e-mail from the old e-mail address of the recipient to the new e-mail address of the recipient A method for re-routmg e-mail compnsmg addressing e-mail using both the user portion and the fully qualified domam name portion of e-mail addresses, creating a mail exchange re-route directory in a re-route server compnsmg an entry for a recipient's new e-mail address mapped to an old e-mail address of the recipient, peπodically distnbutmg updates to the the re-route directory to ISPs for forwardmg e- mail from the old e-mail address of the recipient to the new e-mail address of the recipient A method of re-routing e-mail compnsmg sending an e-mail message, via a sendmg computer, to an old address at an old ISP, receiving, at the sending computer, a bounce message from the old ISP indicating that the old address is not valid, prompting a user, at the sendmg computer, for a command to re-route the bounced e- mail message, resending the bounced e-mail message, m the event the user issues the command to re- route, this time addressed to a re-route server, the re-route server forwardmg the resent e-mail message to the new address for the intended recipient, assummg that the intended recipient is a registered re-route customer A system for re-routmg of e-mail compnsmg a sendmg computer for sending e-mail to a recipient, a network connected to the sending computer, an old ISP, connected to the network, at which the recipient formerly was a subscπber and at which the recipient had an old e-mail address; a re-route server connected to the network for processmg re-route requests and effecting the forwarding of e-mail to the recipient; a new ISP, connected to the network, at which the recipient has a new e-mail address; and a recipient computer for receiving e-mail addressed to the recipient at the new e-mail address. 36. The system for re-routmg e-mail of claim 35, wherein the re-route server compπses a server memory embodying software instructions adapted to enable the re-route server to perform: receiving an email re-route request from the recipient, and forwardmg the re-route request to the old ISP; and wherein the old ISP compnses an old ISP memory embodymg software instructions adapted to enable the re-route server to perform: receivmg and processmg the re-route request. 37. The system for re-routmg e-mail of claim 36, wherein the re-route request received by the re-route server from the recipient compπses the new address of the recipient 38 The system for re-routmg e-mail of claim 36, wherein the re-route request forwarded to the old ISP compnse instructions for forwardmg the e-mail of the recipient to the new address for the recipient at the new ISP. 39 The system for re-routmg e-mail of claim 36, wherem the old ISP further compπses a "FROM" account for the recipient, and wherein the software instructions embodied m the old ISP memory further enable the old ISP to perform receivmg and processing the re-route request by- inserting a ".forward" file compπsing a "to" account compnsmg the new address of the recipient; and forwardmg e-mail for the recipient to the new address when it is received at the old ISP. 40 The system for re-routmg e-mail of claim 36, wherem the old ISP further compπses a "FROM" account for the recipient, and wherem the software instructions embodied m the old ISP memory further enable the old ISP to perform receivmg and processmg the re-route request by- aliasing the FROM account for the recipient with an alias entry compπsing the new address for the recipient; and forwardmg e-mail for the recipient to the new address when it is received at the old ISP 1 The system for re-routmg e-mail of claim 36, wherein the old ISP further compnses a "FROM" account for the recipient and an X.500 database in which the "FROM" account is stored, and wherein the software instructions embodied m the old ISP memory further enable the old ISP to perform receivmg and processmg the re-route request by: inserting a "to" account entry into the X.500 database compnsmg the new address of the recipient; and forwardmg e-mail to the new address when it is received at the old ISP 42 The system for re-routmg e-mail of claim 36, further compnsmg storage, in which a DNS table is stored, the DNS table compnsmg a "to" account compnsmg the new address of the recipient; and wherein the software instructions embodied in the old ISP memory further enable the old ISP to perform, forwarding e-mail for the recipient to the new address. 43. The system for re-routmg e-mail of claim 36, wherein an SMTP wrapper augments a message transport system of the old ISP; and wherem the software instructions embodied in the old ISP memory further enable the old ISP to perform: creating a pπvate alias file compnsmg a "to" account compnsmg the new address for the recipient, passing e-mail for other recipients whose addresses are not m the pπvate alias file to the message transport system of the old ISP; and forwarding e-mail for the recipient to the "to" account for the recipient 44 The system for re-routmg e-mail of claim 36, wherein the new address compnses an e-mail address m Internet Protocol version 6 (IPv6) format. 45 The system for re-routing e-mail of claim 36, wherein software mstructions embodied in the old ISP memory further enable the old ISP to perform: holdmg e-mail for the recipient for further action by the re-route server 46. The system for re-routing e-mail of claim 45, wherein the software instructions embodied in the server memory further enable the re-route server to perform- stoπng the new address of the recipient; peπodically downloading from the old ISP stored e-mail for the recipient; and forwardmg the downloaded e-mail for the recipient to the new address stored in the re-route server. 47 The system for re-routing e-mail of claim 36, wherein the software instructions embodied m the old ISP memory further enable the old ISP to perform: bouncmg e- mail that is addressed to a recipient that is no longer a subscπber to the old ISP. 48. The system for re-routing e-mail of claim 47, wherein bouncmg e-mail mcludes bouncmg e-mail to both the sendmg computer and to the re-route server. 49 The system for re-routmg e-mail of claim 48, wherem the software instructions embodied m the server memory further enable the re-route server to perform. checking to determine if the bounced e-mail is for a recipient who is registered with the re-route server; and forwardmg the bounced e-mail to the new address of the recipient if the recipient is registered with the re-route server 50 The system for re-routmg e-mail of claim 35, wherein the e-mail sent by the sending computer further compnses a umversal re-route symbol in the local part of the e-mail address thereby causing the old ISP to determine if the recipient is a current subscnber of the old ISP; the old ISP compπsing an old ISP memory embodying software instructions adapted to enable the old ISP to perform: forwarding the e-mail to the re-route server if the recipient is not a subscnber of the old ISP, the re-route server compnsmg a server memory embodying software instructions adapted to enable the re-route server to perform: detecting the presence of the umversal re-route symbol, determinmg if the recipient is a re-route subscnber; and forwarding the e-mail to the new address if the recipient is a re-route subscπber. 51 The system for re-routmg e-mail of claim 35, wherem the e-mail sent by the sending computer compπses the old address of the recipient at the old ISP and a re-route extension designating the re-route server; the server memory further embodying software instructions adapted to enable the re- route server to perform: determining if the recipient is a re-route customer; and forwardmg the e-mail to the new address if the recipient is a re-route customer 52. The system for re-routing e-mail of claim 35, wherein the sending computer compπses a sending computer memory embodying software mstructions adapted to enable the sending computer to perform first querying the re-route server to determme if the new address is available for the recipient, the re-route server compnsmg a server memory embodymg software instructions adapted to enable the re-route server to perform providmg the new address to the sendmg computer if the new address is available, and wherein the software mstructions embodied m the sending computer memory further enable the sending computer to perform forwardmg the e-mail to the new address if the new address is available The system for re-routmg e-mail of claim 52, wherem the sending computer query is under the lightweight directory access protocol (LDAP) The system for re-routing e-mail of claim 35, wherem the sending computer compnses a sending computer memory embodying software instructions adapted to enable the sending computer to perform first querying the re-route server to determme if the new address is available for the recipient, the re-route server compnsmg a server memory embodying software instructions adapted to enable the re-route server to perform determining if the new address is available, and forwardmg the e-mail to the new address if the new address is available The system for re-routmg e-mail of claim 54, wherein the sendmg computer query is under the lightweight directory access protocol (LDAP) The system for re-routmg e-mail of claim 35, wherein the re-route server further compnses Mail Exchange (MX) authonty for the old ISP, the re-route server compπsing a server memory embodying software instructions adapted to enable the re-route server to perform receivmg e-mail addressed to subscπbers of the old ISP, comparing the addresses of subscnbers to the old ISP to a re-route customer list, the re-route customer list compnsmg new addresses for re-route customers, and forwardmg the e-mail to the new addresses if the e-mail is addressed to subscnbers to the old ISP who are also subscnbers to the re-route server The system for re-routmg e-mail of claim 56, wherein the software instructions embodied m the server memory further enable the re-route server to perform passmg the e-mail through to the old ISP if the e-mail is not addressed to a re-route subscπber 8. The system for re-routmg e-mail of claim 35, wherem the re-route server further compnses a mail exchange re-route directory further compnsmg an entry for the recipient's new e-mail address mapped to the old e-mail address, each entry compnsmg a user portion and a fully qualified domam name portion; the re-route server compnsmg a server memory embodymg software mstructions adapted to enable the re-route server to perform: distnbutmg the mail exchange directory to the old ISP, thereby allowing the old ISP to forward e-mail to the new address of the recipient. 9 The system for re-routmg e-mail of claim 35, wherein the re-route server compπses a server memory embodying software mstructions adapted to enable the re-route server to perform: sendmg a re-route add request message to the old ISP upon receiving a request from the recipient for re-route service. 0 The system for re-routing e-mail of claim 59, wherein the software instructions embodied in the server memory further enables the re-route server to perform: sending a message to the recipient confirming that the request for re-route service is accepted, in the event that a message is received from the old ISP indicating that the re-route add request message has been accepted. 1 The system for re-routmg e-mail of claim 35, wherein the re-route server compπses a server memory embodying software instructions adapted to enable the re-route server to perform: sendmg a re-route delete request message to the old ISP, m the event that no re-route service extension authoπzation is mdicated by the recipient 62 The system for re-routmg e-mail of claim 61 , wherein the software instructions embodied m the server memory further enables the re-route server to perform: sending a message to the recipient indicating that re-route service is ended, m the event that a message is received from the old ISP indicating that the re-route delete request message has been accepted 63 The system for re-routing e-mail of claim 35, wherein the re-route server compnses a server memory embodying software mstructions adapted to enable the re-route server to perform- sendmg a re-route edit request message to the old ISP upon receiving a request from the recipient for updated re-route service. 64. The system for re-routing e-mail of claim 63, wherem the software instructions embodied in the server memory further enables the re-route server to perform: sending a message to the recipient confirming that the request for updated re-route service is accepted, in the event that a message is received from the old ISP indicating that the re-route edit request message has been accepted.

Inventors: KHALIL JOSEPH G, MCDOWELL MARK E, STEAD GRAHAM, KHALIL, JOSEPH, G., MCDOWELL, MARK, E., STEAD, GRAHAM
Applicants: INVERTIX LLC, INVERTIX, LLC
Application year: 2000
Main classification: H04L12
IPC codes: H04L12