US20030135567A1 - Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown - Google Patents
Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown Download PDFInfo
- Publication number
- US20030135567A1 US20030135567A1 US10/167,988 US16798802A US2003135567A1 US 20030135567 A1 US20030135567 A1 US 20030135567A1 US 16798802 A US16798802 A US 16798802A US 2003135567 A1 US2003135567 A1 US 2003135567A1
- Authority
- US
- United States
- Prior art keywords
- address
- server
- sending
- 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.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION 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/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/21—Monitoring or handling of messages
- H04L51/214—Monitoring or handling of messages using selective forwarding
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/48—Message addressing, e.g. address format or anonymous messages, aliases
Definitions
- the present invention relates generally to the field of electronic mail management systems, and more specifically to new and useful methods, apparatus and computer programs for automatically forwarding electronic mail to an intended recipient when the recipient is otherwise unknown to the receiving entity.
- the national and international packet switched public network has existed for some time. Although often referred to as a single technological entity, the Internet is represented by a substantial complex of communication systems ranging from conventional analog and digital telephone lines through fiber optic, microwave and satellite communications links. The physical structure of the Internet is logically unified through the establishment of common information transport protocols, and addressing and resource referencing schemes that allow quite disparate computer systems to communicate both locally and internationally with one another.
- Electronic mail over the Internet provides a quick and convenient way for computer users to communicate.
- This communication is typically initiated by a message sender who composes a message using a text editing program, provides the electronic mail address of the intended recipient, and often provides an indication of the content (subject matter) of the message by providing text in a “subject” field.
- this composed message is then sent to the recipient's computer address.
- the recipient's computer receives the message and stores it in the recipient's inbox.
- the recipient eventually reads, deletes, responds to, or otherwise processes the message stored within the inbox by using any of a number of electronic mail programs well known in the art.
- Messages formatted to the RFC822 standard have a header portion and an optional body portion that contains the text of the message.
- the header portion includes a number of fields that address and classify the message.
- the header portion of a message contains fields composed of character strings comprising a field-name followed by a colon, followed by a field-body terminated with a carriage return/line feed.
- An example header field is:
- the ⁇ cr ⁇ represents the ASCII carriage return character and the ⁇ lf ⁇ represents the ASCII line feed character.
- the header field-names are not case sensitive, thus, “to:” is equivalent to “TO:”, “To:” or “tO:”.
- Today electronic mail service is typically provided by an electronic mail server connected to the Internet.
- Another dynamic information source is provided by independently operating list servers residing on computer systems that are, in general, connected to the Internet.
- a list server is typically an automated service that functions autonomously to repeat electronic mail messages received by a publicly-known list server electronic mail account to an established list of subscribers known to the list server by explicit or fully qualified electronic mail addresses.
- the list server is thus an automated electronic/relectronic mailer that allows a one-to-many distribution of electronic mail messages through the operation of the list server.
- the relectronic mailing of electronic mail messages is typically dynamic and, therefore, persistent messages are maintained, if at all, selectively by the subscribers of a particular mailing list.
- the list servers are themselves subject to extreme variability in location and operation since only a publicly available dedicated electronic mail address is required in substance to operate a list server.
- SMS Simple mail transfer protocol
- IMAP Interim Mail Access Protocol
- MIME Multipurpose Internet Mail Extensions
- HTML Hypertext Markup Language
- the electronic mail message is sent from the sending server to a receiving server associated with the recipient of the message.
- the receiving server In order to accept the electronic mail content from the sending server, the receiving server must generally be able to validate that there is indeed a user name corresponding exactly with the electronic mail recipient's name.
- the receiving server thus checks its database of electronic mail users and validates the electronic mail recipient's name (the part of the electronic mail address before the @ sign). If the recipient's name is not validated, the receiving server generally refuses the electronic mail content and returns an error message indicating that the recipient is “unknown”.
- One general exception to the foregoing is a receiving server which accepts all the mail for a domain (“mail-bagging”), in which case only the domain name is checked and all recipient mail content is accepted, to be validated at a later time (usually) by another server.
- the sending server When the sending server receives the error message stating that the recipient is “unknown”, it generally sends a message back to the sending user that the recipient is unknown. This is typically the end of any automatic electronic mail service session. The sending user must interpret the error message (sent in various text and formats) and decide how to proceed.
- the present invention provides systems and methods for automatically determining if the recipient of electronic mail that is unknown at the receiving server has left a “forwarding address” with another server (the “forwarding listserver”), thereby allowing either the receiving server, the sending server, or the sending user (e.g., computer system), or any other party to the communication, to automatically send the electronic mail content to the (new) correct address.
- the sending user is notified as to the new electronic mail address so as to allow the sending user to update manually, or automatically via specialized software, the user's individual database of electronic mail addresses. No attempt is made to resolve an unknown user name to any of the existing user names that might be close in spelling. This would be a major security breach and go against most of the philosophy in the electronic mail concept.
- the present invention provides that some or all participants in the electronic mail process (the sending user, the sending server, the receiving server, the receiving user, and any other participant) are aware that there is an entity, the “forwarding listserver”, which may have on file and available to an electronic mail participant, the new address for a particular username which is unknown to a receiving server.
- This new address is supplied by the electronic mail user who is changing their electronic mail address (or their employer, or any other concerned party) and is organized in a commercially available database on the “forwarding listserver”.
- the new address can be supplied by any other entity, such as the user's new ISP after it receives from the user their previous e-mail address(es).
- the “forwarding listserver” includes the forwarding information (old electronic mail name and new electronic mail name).
- the “forwarding listserver” stores each set of data for a period of time, at the end of which the data is either renewed or purged (manually or automatically). Additionally, other forwarding data can be stored, such as a new postal mail address, new phone number, and other items of data. This data could be promulgated based on a variety of criteria, or be available to the Internet at large.
- a computer such as a server or a home or office computer system
- executing computer instructions are often referred to in terms, such as adding or comparing, that are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary in any of the operations described herein that form part of the present invention; the operations are machine operations.
- Useful machines for performing the operations of the invention include programmed general purpose digital computers or similar devices. In all cases the method of computation is distinguished from the method of operation in operating a computer.
- the present invention relates, in part, to method steps for operating a computer in processing electrical or other (e.g., mechanical, chemical, optical) physical signals to generate other desired physical signals. These steps are those requiring physical manipulation of physical quantities.
- the invention also relates to apparatus for performing these operations.
- This apparatus may be specially constructed for the required purposes or it may comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in a memory.
- the procedures presented herein are not inherently related to a particular computer or other apparatus.
- various general purpose machines may be used with programs written in accordance with the teachings herein, or it may prove more convenient to construct more specialized apparatus to perform the operations. The general required structure for a variety of these machines will appear from the description below.
- the invention may be embodied in a computer readable medium encoded with an electronic mail application program or other application program.
- a method for automatically resending an electronic message originally sent to a receiving user at a first address that is now invalid to a second address for the receiving user, wherein the second address has been registered with a forwarding server.
- the method typically comprises the steps of sending an electronic message from a first electronic mail domain to the first address at a second electronic mail domain, determining in the second domain that the first address is no longer valid, and automatically sending a query from the second domain to the forwarding server to determine a new address associated with the first address, wherein the forwarding server stores the first address in association with the second address.
- the method also typically includes the steps of returning the second address to the second domain, and thereafter automatically sending the electronic message to the second address.
- a method for automatically resending an electronic message originally sent to a receiving user at a first address that is now invalid to a second address for the receiving user, wherein the second address has been registered with a forwarding server.
- the method typically comprises the steps of sending an electronic message from a first electronic mail domain to the first address at a second electronic mail domain, returning a message to the first domain indicating that the first address is no longer valid, and automatically sending a query from the first domain to the forwarding server to determine a new address associated with the first address, wherein the forwarding server stores the first address in association with the second address.
- the method also typically includes the steps of returning the second address to the first domain, and thereafter automatically sending the electronic message to the second address.
- a method for automatically resending an electronic message originally sent to a receiving user at a destination address that is now invalid to a new address for the receiving user, wherein the new address has been registered with an address server.
- the method typically comprises the steps of creating an electronic message on a computer system, the electronic message having a first destination address, sending the electronic message to a first server, sending the electronic message from the first server to a second server associated with the destination address, determining in the second server that the destination address is not valid, and thereafter automatically sending a query to the address server to determine a new address associated with the destination address, wherein the address server stores the destination address in association with the new address.
- the method also typically includes the steps of returning the new address, and thereafter automatically sending the electronic message to the new address.
- an address server typically includes an address database for storing old e-mail addresses in association with new e-mail addresses for registered users.
- the address server receives a query from an e-mail server requesting a new e-mail address associated with an old e-mail address for a first user, if the first user is registered with the address server, the server searches the database for the old address and returns the new address for the first user to the e-mail server.
- an e-mail server for receiving and sending electronic messages.
- the e-mail server is configured to automatically send a request to an address server, which stores old e-mail addresses in association with new e-mail addresses for registered users, when the e-mail server receives a first electronic message from a first computer for a destination address that is no longer valid, and wherein the request requests a new address associated with the destination address.
- FIG. 1 illustrates an exemplary computer system for executing electronic mail programs that embody the invention
- FIG. 2 illustrates an exemplary network structure according, to the present invention.
- FIG. 1 illustrates an exemplary computer system 10 for executing electronic mail (e-mail) programs and other programs that embody the invention.
- Computer system 10 includes an Input/Output (“I/O”) bus 20 , a central processing unit (“CPU”) 25 and a memory section 30 .
- I/O bus 20 provides a connection to a keyboard 35 , a display unit 40 , a disk storage unit 45 , a network interface 50 , a removable storage 55 , a CD-ROM drive unit 60 and numerous other peripheral devices 65 , such as a mouse, a modem, a scanner, etc.
- CD-ROM unit 60 reads a CD-ROM medium that typically contains programs and data.
- FIG. 2 illustrates an exemplary network structure according to the present invention.
- Local domain 100 (domain 1) is communicably coupled to multiple domains, including domain 200 (domain 2), over the Internet.
- Local domain 100 includes a computer system 110 (similar to computer system 10 of FIG. 1) coupled to a modem 120 .
- Modem 120 provides a communication connection to gateway/router 130 .
- computer system 110 is directly connected to gateway/router 130 over a network, such as a local area network (LAN), wide area network (WAN) or the like.
- Gateway/router 130 provides an Internet connection, and is connected to local e-mail server 140 (domain1.com) and to local domain name server 150 .
- Second domain 200 (domain 2) includes a computer system 210 connected to second gateway/router 230 and second e-mail server 240 (domain2.com) over LAN 220 .
- Gateway router 230 is connected to second domain name server 250 .
- Forwarding address server 300 is communicably coupled to domain 1 and domain 2 over the Internet as shown in FIG. 2.
- Gateway/router 310 and domain name server 320 are optionally provided to add functionality to forwarding server 300 .
- forwarding server 300 is preferably located in an Internet domain remote from domain 1 and domain 2, however, forwarding server 300 may be located in domain 1 or domain 2.
- Forwarding server 300 preferably includes a database of new Internet addresses associated with old addresses for users that have registered these addresses with forwarding server 300 either directly or indirectly, for example, through a new ISP. To register with forwarding server 300 , all that is required is that a new address and an old address be provided to forwarding server 300 .
- Forwarding server 300 preferably stores new e-mail addresses in a table in association with old addresses, although any data structure as is well known can be used.
- FIG. 2 is merely an illustrative example of a network structure for sending, receiving and resending e-mail messages according to the present invention. Any other network structure can be used without departing from the spirit of the invention. Additionally, it will be apparent to one skilled in the art that the present invention is not limited to implementation with any particular e-mail server software or client software to perform the functions disclosed herein.
- a typical user e.g., user1@domain1.com
- computer system 110 in local domain 100 desires to send an e-mail message to another user (e.g., user2@domain2.com) at second domain 200 .
- the first user composes a message and addresses the message to the intended recipient, user2@domain2.com (as per RFC 821 and RFC 822, as amended).
- the RFC822 protocol is used to construct electronic mail messages.
- the RFC822 specification can be found on the world wide web of the Internet at address “http://www.cis.ohiostate.edu/htbin/rfc/rfc822.html”, and is incorporated by reference for all purposes.
- the present invention does not require the use of the RFC822 standard, so long as there exists a method to identify essential addressing information and associated data. This essential information includes, for example, identification of the message recipient(s) and a subject field for the message.
- the client e-mail software resident on computer system 110 packages the message text and/or attachments in proper e-mail format and sends the e-mail message through modem 120 and router/gateway 130 to the e-mail server 140 for local domain 100 (domain1).
- the e-mail message is sent over a network to e-mail server 140 .
- E-mail server 140 for domain1 queries an Internet Name Service (local hosts table, Internet Domain Name Server 150 , or various directory services) to resolve the destination domain name into an IP address, for example domain2.com for second domain 200 (domain2).
- e-mail server 140 sends the message to the Internet, addressed to the IP address for second domain 200 (e.g., domain2.com), asking for a connection.
- the message address can be generally represented as follows: DestinationUsername@DomainName.
- This message goes first to gateway/router 130 , which sends the message to second gateway/router 230 associated with second domain 200 through the various connections on the Internet.
- second gateway/router 230 receives the message, it ascertains whether the IP address is associated with second domain 200 , e.g., whether the destination e-mail server is located on local area network 220 . If so, gateway/router 230 sends the message to e-mail server 240 for second domain 200 .
- e-mail server 240 checks its internal table of domain names (the data after the @ sign) to see if it is the proper destination for that e-mail message.
- e-mail server 240 checks the destination username (the data before the @ sign) to determine whether the destination username is included in the internal table of names (and aliases). If so, e-mail server 240 accepts the connection from e-mail server 140 and the entire e-mail message (text and/or attachments) is sent from e-mail server 140 and received by e-mail server 240 . E-mail server 140 then typically changes the message status (internally) from an “outgoing” status to a “sent” status, and e-mail server 240 typically moves the incoming message (internally) from a temporary storage area to an area (“local mailbox”) for the second user's (user2@domain2.com) local retrieval and disposition.
- the second user connects at various times to e-mail server 240 from a computer, such as computer system 210 , using one of many e-mail software clients, and retrieves the e-mail message.
- the message may or may not be copied to the computer system 210 , and may or may not be deleted from the e-mail server 240 .
- e-mail server 240 sends a message to the sending e-mail server 140 indicating that the address is invalid (e.g., the user does not exist).
- This message is generally referred to as a “non-delivery report” (NDR).
- NDR non-delivery report
- Sending e-mail server 140 then generally places this NDR message in User1's mailbox area as a new message, possibly adding an explanation of the problem and other text, informing User1 that the e-mail could not be delivered due to the non-existence of the username on the destination e-mail server.
- User1 knows only that the e-mail message has not been delivered.
- the username for User2 may have been deleted from the list of users on the Domain2 e-mail server 240 for any one of many reasons.
- An example of an NDR is an Undeliverable Mail Notification Message (From RFC 821) as follows:
- R: 354 send the mail data, end with.
- This reply indicates that the receiving server knows the user's mailbox is on another host server and indicates the correct forward-path to use in the future. Note that either the host or user or both may be different.
- the receiving server generally takes responsibility for delivering the message.
- This reply indicates that the receiving server knows the user's mailbox is on another host server and indicates the correct forward-path to use. Note that either the host or user or both may be different.
- the receiving server generally refuses to accept mail for this user, and the sending server must either redirect the mail according to the information provided or return an error response to the originating user.
- receiving e-mail server 240 sends an NDR to sending e-mail server 140 .
- sending e-mail server 140 automatically sends a request to the IP address for the Forwarding server 300 , asking for a new e-mail address that corresponds to the old e-mail address.
- e-mail server 140 is preferably configured with the address for forwarding server 300 .
- Forwarding server 300 receives the request, which preferably includes the old e-mail address, and checks its database for any new address associated with the old e-mail address. If User2's new e-mail address has been registered with the forwarding server 300 , directly by User2 or through a new ISP, for example, forwarding server 300 looks up and returns the new address to sending e-mail server 140 .
- Sending e-mail server 140 then automatically resends the e-mail message destined for user2 to the new address.
- sending e-mail server 140 causes the e-mail message to be resent, for example by communicating the new address to receiving e-mail server 240 or computer system 110 with an instruction to resend to the new address.
- receiving e-mail server 240 or computer system 110 upon receipt of the instruction and new address, automatically resends the message to the new address.
- Forwarding server 300 To register with forwarding server 300 , all that is required is that a new address and an old address be submitted. Forwarding server 300 preferably stores new e-mail addresses in a table in association with old addresses, although any data structure as is well known can be used. Additionally, any directory databases including X.500, LDAP, or the like can be used. Thereafter, when a request is received to locate a new address associated with a user's old address, forwarding server 300 searches for the old address and returns the associated new address.
- receiving e-mail server 240 when receiving e-mail server 240 identifies that the recipient's username (e.g., old address) is unknown, rather than send an NDR, receiving e-mail server 240 itself automatically sends a request to the IP address for the forwarding server 300 asking for a new e-mail address for the recipient that corresponds to the old e-mail address.
- Forwarding server 300 receives the request, which preferably includes the old e-mail address, and checks for any new address in its database associated with the old e-mail address. If User2's new e-mail address has been registered with forwarding server 300 , directly or through a new ISP, for example, forwarding server 300 returns the new address to receiving e-mail server 240 .
- Receiving e-mail server 240 then automatically resends the e-mail message destined for user2 to the new address.
- receiving e-mail server 240 causes the e-mail message to be resent, for example by communicating the new address to sending e-mail server 140 or computer system 110 with an instruction to resend to the new address.
- sending e-mail server 140 or computer system 110 upon receipt of the instruction and new address, automatically resends the message to the new address. If no new address is found, forwarding server 300 returns a message to receiving e-mail server 240 indicating this fact.
- Receiving e-mail server 240 then sends an NDR to sending e-mail server 140 . Additionally, in one embodiment, receiving e-mail server 240 notifies sending e-mail server 140 that forwarding server 300 was queried.
- receiving e-mail server 240 sends an NDR to sending e-mail server 140 .
- Sending e-mail server 140 then forwards the NDR to computer system 110 .
- computer system 110 Upon receipt of the NDR, computer system 110 automatically sends a request to the IP address for forwarding server 300 , asking for a new e-mail address that corresponds to the old e-mail address.
- Forwarding server 300 receives the request, which preferably includes the old e-mail address, and checks for any new address in its database associated with the old e-mail address.
- forwarding server 300 returns the new address to computer system 110 .
- Computer system 110 then automatically resends the e-mail message destined for user2 to the new address.
- computer system 110 causes the e-mail message to be resent, for example by communicating the new address to sending e-mail server 140 or receiving e-mail server 240 with an instruction to resend to the new address.
- receiving e-mail server 240 or sending e-mail server 140 automatically resends the message to the new address.
- receiving e-mail server 240 sends an NDR, and any other computer or networking entity on the network that detects the NDR automatically sends a query to the IP address for forwarding server 300 , asking for a new e-mail address that corresponds to the old e-mail address.
- forwarding server 300 receives the request, which preferably includes the old e-mail address, it checks its database for any new address associated with the old e-mail address. If User2's new e-mail address has been registered with forwarding server 300 , directly or through a new ISP, for example, forwarding server 300 returns the new address to the requesting entity. The requesting entity then automatically resends the message to the new address, or causes the message to be sent to the new address.
- the sending user in addition to the automatic resending the e-mail message to the new address, the sending user is notified by a new e-mail message or other various means as to the new e-mail address for the recipient. The sending user is then able to manually update their address book with the new address.
- the sending user's e-mail software or address book, or other reference table) resident on computer system 110 receives the new address and automatically updates the address book with the new e-mail address for the intended recipient (i.e., user2).
- the invention can be integrated into the e-mail client software on the sender's system, into the e-mail servers' software, or a separate software application, which detects the NDR, queries the forwarding listserver, resends the mail, etc., can reside on the sender's system or any other entity in the network. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Strategic Management (AREA)
- Entrepreneurship & Innovation (AREA)
- Marketing (AREA)
- Quality & Reliability (AREA)
- Computer Hardware Design (AREA)
- Signal Processing (AREA)
- Economics (AREA)
- Computer Networks & Wireless Communication (AREA)
- Operations Research (AREA)
- Data Mining & Analysis (AREA)
- Tourism & Hospitality (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Information Transfer Between Computers (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
- The present invention relates generally to the field of electronic mail management systems, and more specifically to new and useful methods, apparatus and computer programs for automatically forwarding electronic mail to an intended recipient when the recipient is otherwise unknown to the receiving entity.
- The national and international packet switched public network, generically referred to as “the Internet” has existed for some time. Although often referred to as a single technological entity, the Internet is represented by a substantial complex of communication systems ranging from conventional analog and digital telephone lines through fiber optic, microwave and satellite communications links. The physical structure of the Internet is logically unified through the establishment of common information transport protocols, and addressing and resource referencing schemes that allow quite disparate computer systems to communicate both locally and internationally with one another.
- Electronic mail over the Internet provides a quick and convenient way for computer users to communicate. This communication is typically initiated by a message sender who composes a message using a text editing program, provides the electronic mail address of the intended recipient, and often provides an indication of the content (subject matter) of the message by providing text in a “subject” field. Using well-understood technology, this composed message is then sent to the recipient's computer address. The recipient's computer receives the message and stores it in the recipient's inbox. The recipient eventually reads, deletes, responds to, or otherwise processes the message stored within the inbox by using any of a number of electronic mail programs well known in the art.
- Because such electronic mail messages travel across networks, they generally are constructed according to the Standard for the Format of ARPA Internet Text Messages specification (RFC822). This specification can be found on the world wide web of the Internet at address “http://www.cis.ohio-state.edu/htbin/rfc/rfc822.html”. Messages formatted to the RFC822 standard have a header portion and an optional body portion that contains the text of the message. The header portion includes a number of fields that address and classify the message. For example, the header portion of a message contains fields composed of character strings comprising a field-name followed by a colon, followed by a field-body terminated with a carriage return/line feed. An example header field is:
- “To: John Doe”. {cr} {lf}
- In this example, the {cr} represents the ASCII carriage return character and the {lf} represents the ASCII line feed character. The header field-names are not case sensitive, thus, “to:” is equivalent to “TO:”, “To:” or “tO:”.
- Today electronic mail service is typically provided by an electronic mail server connected to the Internet. Another dynamic information source is provided by independently operating list servers residing on computer systems that are, in general, connected to the Internet. A list server is typically an automated service that functions autonomously to repeat electronic mail messages received by a publicly-known list server electronic mail account to an established list of subscribers known to the list server by explicit or fully qualified electronic mail addresses. The list server is thus an automated electronic/relectronic mailer that allows a one-to-many distribution of electronic mail messages through the operation of the list server. The relectronic mailing of electronic mail messages is typically dynamic and, therefore, persistent messages are maintained, if at all, selectively by the subscribers of a particular mailing list. Furthermore, the list servers are themselves subject to extreme variability in location and operation since only a publicly available dedicated electronic mail address is required in substance to operate a list server.
- Currently, when electronic mail is sent, it is packaged in various formats and sent from the sending user's computer system to an electronic mail server (sending server), via various means of electronic transmission, and a copy is generally retained on the sending machine. The sending server then packages the message into simple mail transfer protocol (SMTP) format, or Interim Mail Access Protocol (IMAP) format, or other electronic mail protocol formats, using Multipurpose Internet Mail Extensions (MIME) or Hypertext Markup Language (HTML) or other formatting protocols, and a connection is attempted with the recipient.
- During this connection, the electronic mail message is sent from the sending server to a receiving server associated with the recipient of the message. In order to accept the electronic mail content from the sending server, the receiving server must generally be able to validate that there is indeed a user name corresponding exactly with the electronic mail recipient's name. The receiving server thus checks its database of electronic mail users and validates the electronic mail recipient's name (the part of the electronic mail address before the @ sign). If the recipient's name is not validated, the receiving server generally refuses the electronic mail content and returns an error message indicating that the recipient is “unknown”. One general exception to the foregoing is a receiving server which accepts all the mail for a domain (“mail-bagging”), in which case only the domain name is checked and all recipient mail content is accepted, to be validated at a later time (usually) by another server.
- When the sending server receives the error message stating that the recipient is “unknown”, it generally sends a message back to the sending user that the recipient is unknown. This is typically the end of any automatic electronic mail service session. The sending user must interpret the error message (sent in various text and formats) and decide how to proceed.
- The ability to change electronic mail addresses expediently has not kept pace with the rapid expansion of the Internet. As a result, many electronic mail users feel that they cannot leave their existing Internet Service Provider (ISP) because when and if they do, the ISP will erase their electronic mail name from the electronic mail server. All the mail that would be sent to them at that address would therefore be returned “user unknown”. It would take many hours to change all manual and automatic electronic mail addresses from the old address to the new address. Many of the users who do indeed change ISPs are forced to retain the old ISP service for several months until they are sure that all of their electronic mail is being sent to the correct address.
- The present invention provides systems and methods for automatically determining if the recipient of electronic mail that is unknown at the receiving server has left a “forwarding address” with another server (the “forwarding listserver”), thereby allowing either the receiving server, the sending server, or the sending user (e.g., computer system), or any other party to the communication, to automatically send the electronic mail content to the (new) correct address. In addition to this automatic “forwarding”, the sending user is notified as to the new electronic mail address so as to allow the sending user to update manually, or automatically via specialized software, the user's individual database of electronic mail addresses. No attempt is made to resolve an unknown user name to any of the existing user names that might be close in spelling. This would be a major security breach and go against most of the philosophy in the electronic mail concept.
- The present invention provides that some or all participants in the electronic mail process (the sending user, the sending server, the receiving server, the receiving user, and any other participant) are aware that there is an entity, the “forwarding listserver”, which may have on file and available to an electronic mail participant, the new address for a particular username which is unknown to a receiving server. This new address is supplied by the electronic mail user who is changing their electronic mail address (or their employer, or any other concerned party) and is organized in a commercially available database on the “forwarding listserver”. Alternately, the new address can be supplied by any other entity, such as the user's new ISP after it receives from the user their previous e-mail address(es).
- The “forwarding listserver” includes the forwarding information (old electronic mail name and new electronic mail name). The “forwarding listserver” stores each set of data for a period of time, at the end of which the data is either renewed or purged (manually or automatically). Additionally, other forwarding data can be stored, such as a new postal mail address, new phone number, and other items of data. This data could be promulgated based on a variety of criteria, or be available to the Internet at large.
- The manipulations performed by a computer, such as a server or a home or office computer system, in executing computer instructions are often referred to in terms, such as adding or comparing, that are commonly associated with mental operations performed by a human operator. No such capability of a human operator is necessary in any of the operations described herein that form part of the present invention; the operations are machine operations. Useful machines for performing the operations of the invention include programmed general purpose digital computers or similar devices. In all cases the method of computation is distinguished from the method of operation in operating a computer. The present invention relates, in part, to method steps for operating a computer in processing electrical or other (e.g., mechanical, chemical, optical) physical signals to generate other desired physical signals. These steps are those requiring physical manipulation of physical quantities. Usually these quantities take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared, and otherwise manipulated. These signals are referred to as bits, values, elements, symbols characters, terms, numbers, or the like. It will be understood by those skilled in the art that all of these and similar terms are associated with the appropriate physical quantities and are merely convenient labels applied to these quantities.
- The invention also relates to apparatus for performing these operations. This apparatus may be specially constructed for the required purposes or it may comprise a general purpose computer as selectively activated or reconfigured by a computer program stored in a memory. The procedures presented herein are not inherently related to a particular computer or other apparatus. In particular, various general purpose machines may be used with programs written in accordance with the teachings herein, or it may prove more convenient to construct more specialized apparatus to perform the operations. The general required structure for a variety of these machines will appear from the description below. Additionally, the invention may be embodied in a computer readable medium encoded with an electronic mail application program or other application program.
- According to an aspect of the invention, a method is provided for automatically resending an electronic message originally sent to a receiving user at a first address that is now invalid to a second address for the receiving user, wherein the second address has been registered with a forwarding server. The method typically comprises the steps of sending an electronic message from a first electronic mail domain to the first address at a second electronic mail domain, determining in the second domain that the first address is no longer valid, and automatically sending a query from the second domain to the forwarding server to determine a new address associated with the first address, wherein the forwarding server stores the first address in association with the second address. The method also typically includes the steps of returning the second address to the second domain, and thereafter automatically sending the electronic message to the second address.
- According to another aspect of the invention, a method is provided for automatically resending an electronic message originally sent to a receiving user at a first address that is now invalid to a second address for the receiving user, wherein the second address has been registered with a forwarding server. The method typically comprises the steps of sending an electronic message from a first electronic mail domain to the first address at a second electronic mail domain, returning a message to the first domain indicating that the first address is no longer valid, and automatically sending a query from the first domain to the forwarding server to determine a new address associated with the first address, wherein the forwarding server stores the first address in association with the second address. The method also typically includes the steps of returning the second address to the first domain, and thereafter automatically sending the electronic message to the second address.
- According to yet another aspect of the present invention, a method is provided for automatically resending an electronic message originally sent to a receiving user at a destination address that is now invalid to a new address for the receiving user, wherein the new address has been registered with an address server. The method typically comprises the steps of creating an electronic message on a computer system, the electronic message having a first destination address, sending the electronic message to a first server, sending the electronic message from the first server to a second server associated with the destination address, determining in the second server that the destination address is not valid, and thereafter automatically sending a query to the address server to determine a new address associated with the destination address, wherein the address server stores the destination address in association with the new address. The method also typically includes the steps of returning the new address, and thereafter automatically sending the electronic message to the new address.
- According to a further aspect of the present invention, an address server is provided. The address server typically includes an address database for storing old e-mail addresses in association with new e-mail addresses for registered users. When the address server receives a query from an e-mail server requesting a new e-mail address associated with an old e-mail address for a first user, if the first user is registered with the address server, the server searches the database for the old address and returns the new address for the first user to the e-mail server.
- According to yet a further aspect of the invention, an e-mail server for receiving and sending electronic messages is provided. The e-mail server is configured to automatically send a request to an address server, which stores old e-mail addresses in association with new e-mail addresses for registered users, when the e-mail server receives a first electronic message from a first computer for a destination address that is no longer valid, and wherein the request requests a new address associated with the destination address.
- Reference to the remaining portions of the specification, including the drawings and claims, will realize other features and advantages of the present invention. Further features and advantages of the present invention, as well as the structure and operation of various embodiments of the present invention, are described in detail below with respect to the accompanying drawings. In the drawings, like reference numbers indicate identical or functionally similar elements.
- These and other advantages and features of the present invention will become better understood upon consideration of the following detailed description of the invention when considered in connection of the accompanying drawings, in which like reference numerals designate like parts throughout the figures thereof, and wherein:
- FIG. 1 illustrates an exemplary computer system for executing electronic mail programs that embody the invention; and
- FIG. 2 illustrates an exemplary network structure according, to the present invention.
- FIG. 1 illustrates an
exemplary computer system 10 for executing electronic mail (e-mail) programs and other programs that embody the invention.Computer system 10 includes an Input/Output (“I/O”)bus 20, a central processing unit (“CPU”) 25 and amemory section 30. I/O bus 20 provides a connection to akeyboard 35, adisplay unit 40, adisk storage unit 45, anetwork interface 50, aremovable storage 55, a CD-ROM drive unit 60 and numerous otherperipheral devices 65, such as a mouse, a modem, a scanner, etc. CD-ROM unit 60 reads a CD-ROM medium that typically contains programs and data. - FIG. 2 illustrates an exemplary network structure according to the present invention. Local domain100 (domain 1) is communicably coupled to multiple domains, including domain 200 (domain 2), over the Internet.
Local domain 100 includes a computer system 110 (similar tocomputer system 10 of FIG. 1) coupled to amodem 120.Modem 120 provides a communication connection to gateway/router 130. Alternately,computer system 110 is directly connected to gateway/router 130 over a network, such as a local area network (LAN), wide area network (WAN) or the like. Gateway/router 130 provides an Internet connection, and is connected to local e-mail server 140 (domain1.com) and to localdomain name server 150. Second domain 200 (domain 2) includes acomputer system 210 connected to second gateway/router 230 and second e-mail server 240 (domain2.com) overLAN 220.Gateway router 230 is connected to seconddomain name server 250. -
Forwarding address server 300 is communicably coupled todomain 1 anddomain 2 over the Internet as shown in FIG. 2. Gateway/router 310 anddomain name server 320 are optionally provided to add functionality to forwardingserver 300. As shown, forwardingserver 300 is preferably located in an Internet domain remote fromdomain 1 anddomain 2, however, forwardingserver 300 may be located indomain 1 ordomain 2.Forwarding server 300 preferably includes a database of new Internet addresses associated with old addresses for users that have registered these addresses with forwardingserver 300 either directly or indirectly, for example, through a new ISP. To register with forwardingserver 300, all that is required is that a new address and an old address be provided to forwardingserver 300.Forwarding server 300 preferably stores new e-mail addresses in a table in association with old addresses, although any data structure as is well known can be used. - It be apparent to one skilled in the art that FIG. 2 is merely an illustrative example of a network structure for sending, receiving and resending e-mail messages according to the present invention. Any other network structure can be used without departing from the spirit of the invention. Additionally, it will be apparent to one skilled in the art that the present invention is not limited to implementation with any particular e-mail server software or client software to perform the functions disclosed herein.
- Suppose now that a typical user (e.g., user1@domain1.com) using
computer system 110 inlocal domain 100 desires to send an e-mail message to another user (e.g., user2@domain2.com) atsecond domain 200. Using one of many various e-mail software clients, the first user composes a message and addresses the message to the intended recipient, user2@domain2.com (as per RFC 821 and RFC 822, as amended). - In a preferred embodiment of the present invention, the RFC822 protocol is used to construct electronic mail messages. The RFC822 specification can be found on the world wide web of the Internet at address “http://www.cis.ohiostate.edu/htbin/rfc/rfc822.html”, and is incorporated by reference for all purposes. However, the present invention does not require the use of the RFC822 standard, so long as there exists a method to identify essential addressing information and associated data. This essential information includes, for example, identification of the message recipient(s) and a subject field for the message.
- The client e-mail software resident on
computer system 110 packages the message text and/or attachments in proper e-mail format and sends the e-mail message throughmodem 120 and router/gateway 130 to thee-mail server 140 for local domain 100 (domain1). Alternately, the e-mail message is sent over a network toe-mail server 140.E-mail server 140 for domain1 queries an Internet Name Service (local hosts table, InternetDomain Name Server 150, or various directory services) to resolve the destination domain name into an IP address, for example domain2.com for second domain 200 (domain2). When this is successfully accomplished,e-mail server 140 sends the message to the Internet, addressed to the IP address for second domain 200 (e.g., domain2.com), asking for a connection. At this point the message address can be generally represented as follows: DestinationUsername@DomainName. - This message goes first to gateway/
router 130, which sends the message to second gateway/router 230 associated withsecond domain 200 through the various connections on the Internet. When second gateway/router 230 receives the message, it ascertains whether the IP address is associated withsecond domain 200, e.g., whether the destination e-mail server is located onlocal area network 220. If so, gateway/router 230 sends the message to e-mail server 240 forsecond domain 200. Generally, e-mail server 240 checks its internal table of domain names (the data after the @ sign) to see if it is the proper destination for that e-mail message. If this is true, e-mail server 240 checks the destination username (the data before the @ sign) to determine whether the destination username is included in the internal table of names (and aliases). If so, e-mail server 240 accepts the connection frome-mail server 140 and the entire e-mail message (text and/or attachments) is sent frome-mail server 140 and received by e-mail server 240.E-mail server 140 then typically changes the message status (internally) from an “outgoing” status to a “sent” status, and e-mail server 240 typically moves the incoming message (internally) from a temporary storage area to an area (“local mailbox”) for the second user's (user2@domain2.com) local retrieval and disposition. The second user connects at various times to e-mail server 240 from a computer, such ascomputer system 210, using one of many e-mail software clients, and retrieves the e-mail message. The message may or may not be copied to thecomputer system 210, and may or may not be deleted from the e-mail server 240. - According to one embodiment, if the destination username is not found in the internal table of names (and aliases), e-mail server240 sends a message to the sending
e-mail server 140 indicating that the address is invalid (e.g., the user does not exist). This message is generally referred to as a “non-delivery report” (NDR). Sendinge-mail server 140 then generally places this NDR message in User1's mailbox area as a new message, possibly adding an explanation of the problem and other text, informing User1 that the e-mail could not be delivered due to the non-existence of the username on the destination e-mail server. At this point, User1 knows only that the e-mail message has not been delivered. The username for User2 may have been deleted from the list of users on the Domain2 e-mail server 240 for any one of many reasons. An example of an NDR is an Undeliverable Mail Notification Message (From RFC 821) as follows: - S: MAIL FROM
- R: 250 ok
- S: RCPT TO <@HOSTX.ARPA:JOE@HOSTW.ARPA>
- R: 250 ok
- S: DATA
- R: 354 send the mail data, end with.
- S: Date: 23 Oct 81 11:22:33
- S: From: SMTP@HOSTY.ARPA
- S: To: JOE@HOSTW.ARPA
- S: Subject: Mail System Problem
- S:
- S: Sorry JOE, your message to SAM(HOSTZ.ARPA lost.
- S: HOSTZ.ARPA said this:
- S: “550 No Such User”
- S:
- R: 250 ok
- There are some cases where the destination information is incorrect, but the receiving server knows the correct destination. In such cases, one of the following replies can be used to allow the sending server to contact the correct destination.
- 251 User not local; will forward to <forward-path>
- This reply indicates that the receiving server knows the user's mailbox is on another host server and indicates the correct forward-path to use in the future. Note that either the host or user or both may be different. The receiving server generally takes responsibility for delivering the message.
- 551 User not local; please try <forward-path>
- This reply indicates that the receiving server knows the user's mailbox is on another host server and indicates the correct forward-path to use. Note that either the host or user or both may be different. The receiving server generally refuses to accept mail for this user, and the sending server must either redirect the mail according to the information provided or return an error response to the originating user.
- According to one embodiment, if the destination username is not found, receiving e-mail server240 sends an NDR to sending
e-mail server 140. Upon receipt of the NDR, sendinge-mail server 140 automatically sends a request to the IP address for theForwarding server 300, asking for a new e-mail address that corresponds to the old e-mail address. According to this embodiment,e-mail server 140 is preferably configured with the address for forwardingserver 300.Forwarding server 300 receives the request, which preferably includes the old e-mail address, and checks its database for any new address associated with the old e-mail address. If User2's new e-mail address has been registered with the forwardingserver 300, directly by User2 or through a new ISP, for example, forwardingserver 300 looks up and returns the new address to sendinge-mail server 140. - Sending
e-mail server 140 then automatically resends the e-mail message destined for user2 to the new address. Alternately, sendinge-mail server 140 causes the e-mail message to be resent, for example by communicating the new address to receiving e-mail server 240 orcomputer system 110 with an instruction to resend to the new address. In this example, upon receipt of the instruction and new address, receiving e-mail server 240 orcomputer system 110 automatically resends the message to the new address. - To register with forwarding
server 300, all that is required is that a new address and an old address be submitted.Forwarding server 300 preferably stores new e-mail addresses in a table in association with old addresses, although any data structure as is well known can be used. Additionally, any directory databases including X.500, LDAP, or the like can be used. Thereafter, when a request is received to locate a new address associated with a user's old address, forwardingserver 300 searches for the old address and returns the associated new address. - According to another embodiment, when receiving e-mail server240 identifies that the recipient's username (e.g., old address) is unknown, rather than send an NDR, receiving e-mail server 240 itself automatically sends a request to the IP address for the forwarding
server 300 asking for a new e-mail address for the recipient that corresponds to the old e-mail address.Forwarding server 300 receives the request, which preferably includes the old e-mail address, and checks for any new address in its database associated with the old e-mail address. If User2's new e-mail address has been registered with forwardingserver 300, directly or through a new ISP, for example, forwardingserver 300 returns the new address to receiving e-mail server 240. Receiving e-mail server 240 then automatically resends the e-mail message destined for user2 to the new address. Alternately, receiving e-mail server 240 causes the e-mail message to be resent, for example by communicating the new address to sendinge-mail server 140 orcomputer system 110 with an instruction to resend to the new address. In this example, upon receipt of the instruction and new address, sendinge-mail server 140 orcomputer system 110 automatically resends the message to the new address. If no new address is found, forwardingserver 300 returns a message to receiving e-mail server 240 indicating this fact. Receiving e-mail server 240 then sends an NDR to sendinge-mail server 140. Additionally, in one embodiment, receiving e-mail server 240 notifies sendinge-mail server 140 that forwardingserver 300 was queried. - According to another embodiment, if the destination username is not found, receiving e-mail server240 sends an NDR to sending
e-mail server 140. Sendinge-mail server 140 then forwards the NDR tocomputer system 110. Upon receipt of the NDR,computer system 110 automatically sends a request to the IP address for forwardingserver 300, asking for a new e-mail address that corresponds to the old e-mail address.Forwarding server 300 receives the request, which preferably includes the old e-mail address, and checks for any new address in its database associated with the old e-mail address. If User2's new e-mail address has been registered with forwardingserver 300, directly or through a new ISP, for example, forwardingserver 300 returns the new address tocomputer system 110.Computer system 110 then automatically resends the e-mail message destined for user2 to the new address. Alternately,computer system 110 causes the e-mail message to be resent, for example by communicating the new address to sendinge-mail server 140 or receiving e-mail server 240 with an instruction to resend to the new address. In this example, upon receipt of the instruction and new address, receiving e-mail server 240 or sendinge-mail server 140 automatically resends the message to the new address. - According to another embodiment, if the destination username is not found, receiving e-mail server240 sends an NDR, and any other computer or networking entity on the network that detects the NDR automatically sends a query to the IP address for forwarding
server 300, asking for a new e-mail address that corresponds to the old e-mail address. When forwardingserver 300 receives the request, which preferably includes the old e-mail address, it checks its database for any new address associated with the old e-mail address. If User2's new e-mail address has been registered with forwardingserver 300, directly or through a new ISP, for example, forwardingserver 300 returns the new address to the requesting entity. The requesting entity then automatically resends the message to the new address, or causes the message to be sent to the new address. - According to another embodiment, in addition to the automatic resending the e-mail message to the new address, the sending user is notified by a new e-mail message or other various means as to the new e-mail address for the recipient. The sending user is then able to manually update their address book with the new address. Alternately, the sending user's e-mail software (or address book, or other reference table) resident on
computer system 110 receives the new address and automatically updates the address book with the new e-mail address for the intended recipient (i.e., user2). - While the invention has been described by way of example and in terms of the specific embodiments, it is to be understood that the invention is not limited to the disclosed embodiments. To the contrary, it is intended to cover various modifications and similar arrangements as would be apparent to those skilled in the art. For example, although the original e-mail message is sent to a different Internet domain, the original message can be sent to a destination user in the same domain. Further, although it is preferred that
server 140 or server 240 automatically resends the original message, forwardingaddress server 300 can automatically send the original electronic message to the intended recipient's new address. Additionally, the invention can be integrated into the e-mail client software on the sender's system, into the e-mail servers' software, or a separate software application, which detects the NDR, queries the forwarding listserver, resends the mail, etc., can reside on the sender's system or any other entity in the network. Therefore, the scope of the appended claims should be accorded the broadest interpretation so as to encompass all such modifications and similar arrangements.
Claims (21)
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/338,834 US6427164B1 (en) | 1999-06-23 | 1999-06-23 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
US10/167,988 US20030135567A1 (en) | 1999-06-23 | 2002-06-11 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
PCT/US2002/019260 WO2003107210A1 (en) | 1999-06-23 | 2002-06-17 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/338,834 US6427164B1 (en) | 1999-06-23 | 1999-06-23 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
US10/167,988 US20030135567A1 (en) | 1999-06-23 | 2002-06-11 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
PCT/US2002/019260 WO2003107210A1 (en) | 1999-06-23 | 2002-06-17 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/338,834 Continuation US6427164B1 (en) | 1999-06-23 | 1999-06-23 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
Publications (1)
Publication Number | Publication Date |
---|---|
US20030135567A1 true US20030135567A1 (en) | 2003-07-17 |
Family
ID=32234047
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/338,834 Expired - Lifetime US6427164B1 (en) | 1999-06-23 | 1999-06-23 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
US10/167,988 Abandoned US20030135567A1 (en) | 1999-06-23 | 2002-06-11 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/338,834 Expired - Lifetime US6427164B1 (en) | 1999-06-23 | 1999-06-23 | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown |
Country Status (2)
Country | Link |
---|---|
US (2) | US6427164B1 (en) |
WO (1) | WO2003107210A1 (en) |
Cited By (32)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20020111937A1 (en) * | 2001-01-29 | 2002-08-15 | Mark Wetherbee | Method and system for permissible internet direct marketing |
US20020161613A1 (en) * | 2001-04-26 | 2002-10-31 | Fujitsu Limited | Message-address management program, recording medium carrying message-address management program, message-address management method, and message-address management apparatus |
US20030217109A1 (en) * | 2001-05-15 | 2003-11-20 | Ordille Joann J. | Method and apparatus for automatic notification and response |
US6823368B1 (en) * | 2000-09-28 | 2004-11-23 | International Business Machines Corporation | Method and system for E-mail sender chain history by adding a sender-chain filed to the E-mail header when forwarding a chain forwarded E-mail message to another recipient |
US6832246B1 (en) * | 2000-07-31 | 2004-12-14 | Pitney Bowes Inc. | Dynamic electronic forwarding system |
US20050135681A1 (en) * | 2003-12-22 | 2005-06-23 | Schirmer Andrew L. | Methods and systems for preventing inadvertent transmission of electronic messages |
US20050144157A1 (en) * | 2003-12-29 | 2005-06-30 | Moody Paul B. | System and method for searching and retrieving related messages |
US20050144561A1 (en) * | 2003-12-29 | 2005-06-30 | Moody Paul B. | System and method for deleting related messages |
US20050198256A1 (en) * | 2003-12-29 | 2005-09-08 | Moody Paul B. | System and method for building interest profiles from related messages |
US20050198143A1 (en) * | 2003-12-29 | 2005-09-08 | Moody Paul B. | System and method for replying to related messages |
US20050208941A1 (en) * | 2004-03-18 | 2005-09-22 | Ordille Joann J | Method and apparatus for a publish-subscribe system with third party subscription delivery |
US20060075031A1 (en) * | 2004-09-17 | 2006-04-06 | Wagner Dirk P | Bounce management |
US20060206938A1 (en) * | 2002-02-19 | 2006-09-14 | Postini Corporation | E-mail management services |
GB2425192A (en) * | 2004-11-25 | 2006-10-18 | Sms Card Ltd | Providing up-to-date contact information |
US20060276916A1 (en) * | 2004-12-22 | 2006-12-07 | Dearing Stephen M | System and method for electronically processing address information |
US20070094155A1 (en) * | 2005-05-17 | 2007-04-26 | Dearing Stephen M | System and method for automated management of an address database |
US20070204341A1 (en) * | 2005-11-23 | 2007-08-30 | Rand David L | SMTP network security processing in a transparent relay in a computer network |
US20070271341A1 (en) * | 2006-05-18 | 2007-11-22 | Rajan Kumar | Apparatus, system, and method for setting/retrieving header information dynamically into/from service data objects for protocol based technology adapters |
US20090030993A1 (en) * | 2007-07-26 | 2009-01-29 | Mxtoolbox | Simultaneous synchronous split-domain email routing with conflict resolution |
US20090157828A1 (en) * | 2007-12-12 | 2009-06-18 | Sumit Kumar Agrawal | Techniques for specifying recipients in an electronic mail (email) system |
US20090163177A1 (en) * | 2007-12-21 | 2009-06-25 | Fmr Llc | Guest Communication and Information Delivery User Interface |
US20090307315A1 (en) * | 2008-06-06 | 2009-12-10 | International Business Machines Corporation | Facilitating correction of incorrect identities in propagated electronic communications |
US20090307271A1 (en) * | 2008-06-06 | 2009-12-10 | International Business Machines Corporation | Autonomic correction of incorrect identities in repositories |
US20090307317A1 (en) * | 2008-06-06 | 2009-12-10 | International Business Machines Corporation | Automatically modifying distributed communications |
US20100017485A1 (en) * | 2008-07-21 | 2010-01-21 | International Business Machines Corporation | Enforcing conformance in email content |
US20100169445A1 (en) * | 2008-12-26 | 2010-07-01 | International Business Machines Corporation | Device, method, and computer program product for supporting creation of reply mail |
US7840639B1 (en) | 1999-09-21 | 2010-11-23 | G&H Nevada-Tek | Method and article of manufacture for an automatically executed application program associated with an electronic message |
US20100306324A1 (en) * | 2009-06-01 | 2010-12-02 | Bontempo Allan J | Anonymously and autonomously bridging return system and method |
US20110016203A1 (en) * | 2000-07-27 | 2011-01-20 | Bea Systems, Inc. | System and method for achieving scalability in domain computing |
US8756284B2 (en) | 2008-06-06 | 2014-06-17 | International Business Machines Corporation | Minimizing incorrectly addressed communications when working with ambiguous recipient designations |
US9092535B1 (en) | 1999-09-21 | 2015-07-28 | Google Inc. | E-mail embedded textual hyperlink object |
US9473441B2 (en) | 1999-09-21 | 2016-10-18 | Google Inc. | E-mail with discretionary functionality |
Families Citing this family (94)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6760746B1 (en) | 1999-09-01 | 2004-07-06 | Eric Schneider | Method, product, and apparatus for processing a data request |
US6854007B1 (en) * | 1998-09-17 | 2005-02-08 | Micron Technology, Inc. | Method and system for enhancing reliability of communication with electronic messages |
US7188138B1 (en) | 1999-03-22 | 2007-03-06 | Eric Schneider | Method, product, and apparatus for resource identifier registration and aftermarket services |
US9141717B2 (en) | 1999-03-22 | 2015-09-22 | Esdr Network Solutions Llc | Methods, systems, products, and devices for processing DNS friendly identifiers |
US8037168B2 (en) | 1999-07-15 | 2011-10-11 | Esdr Network Solutions Llc | Method, product, and apparatus for enhancing resolution services, registration services, and search services |
USRE43690E1 (en) | 1999-03-22 | 2012-09-25 | Esdr Network Solutions Llc | Search engine request method, product, and apparatus |
US6338082B1 (en) | 1999-03-22 | 2002-01-08 | Eric Schneider | Method, product, and apparatus for requesting a network resource |
US6505236B1 (en) * | 1999-04-30 | 2003-01-07 | Thinmail, Inc. | Network-based mail attachment storage system and method |
US6438583B1 (en) * | 1999-06-23 | 2002-08-20 | Re-Route Corporation | System and method for re-routing of e-mail messages |
US6671718B1 (en) * | 1999-06-28 | 2003-12-30 | Mark Meister | Email client application incorporating an active transmit authorization request |
USRE44207E1 (en) | 1999-09-01 | 2013-05-07 | Esdr Network Solutions Llc | Network resource access method, product, and apparatus |
US6687740B1 (en) | 1999-09-21 | 2004-02-03 | Neostar, Inc. | System, method and article of manufacture for preventing the proliferation of unwanted electronic messages |
US6704771B1 (en) | 1999-09-21 | 2004-03-09 | Neostar, Inc. | Electronic message payload for interfacing with text contained in the message |
US6564264B1 (en) * | 1999-12-08 | 2003-05-13 | At&T Corp. | System, apparatus and method for automatic address updating of outgoing and incoming user messages in a communications network |
US20020010745A1 (en) * | 1999-12-09 | 2002-01-24 | Eric Schneider | Method, product, and apparatus for delivering a message |
WO2001072011A2 (en) * | 2000-03-17 | 2001-09-27 | United States Postal Service | Methods and systems for proofing identities using a certificate authority |
US6865671B1 (en) * | 2000-04-07 | 2005-03-08 | Sendmail, Inc. | Electronic mail system with authentication methodology for supporting relaying in a message transfer agent |
US7363233B1 (en) * | 2000-04-17 | 2008-04-22 | Levine Richard C | System and method of network addressing and translation in a transportation system |
US9070105B2 (en) * | 2000-04-21 | 2015-06-30 | United States Postal Service | Systems and methods for providing change of address services over a network |
AU2001259826A1 (en) * | 2000-05-03 | 2001-11-12 | Daniel Schoeffler | Method of enabling transmission and reception of communication when current destination for recipient is unknown to sender |
US7062534B1 (en) * | 2000-05-22 | 2006-06-13 | Hewlett-Packard Development Company, L.P. | Information caching system and method |
US6604132B1 (en) * | 2000-06-09 | 2003-08-05 | David H. Hitt | System and method for embedding a physical mailing address in an electronic mail address |
AU2001271489A1 (en) * | 2000-06-27 | 2002-01-08 | Peoplestreet, Inc. | Systems and methods for managing contact information |
EP1170910A3 (en) * | 2000-07-06 | 2004-09-01 | Fujitsu Limited | Method and device for managing mail addresses |
US20020046278A1 (en) * | 2000-07-17 | 2002-04-18 | Roy Hays | Method and system for global log on in a distributed system |
US6957248B2 (en) * | 2000-07-31 | 2005-10-18 | Pitney Bowes Inc. | System and method for forwarding electronic messages |
US6895427B2 (en) | 2000-12-28 | 2005-05-17 | Pitney Bowes Inc. | System and method for cleansing addresses for electronic messages |
US7016938B1 (en) | 2000-07-31 | 2006-03-21 | Pitney Bowes Inc. | E-mail forwarding system having archival database |
US6839738B2 (en) * | 2000-12-28 | 2005-01-04 | Pitney Bowes Inc. | System and method for cleansing addresses for electronic messages |
AU2001280998A1 (en) * | 2000-08-03 | 2002-02-18 | Bruce A. Epstein | Information collaboration and reliability assessment |
US7080122B2 (en) * | 2000-08-07 | 2006-07-18 | Return Path, Inc. | System and process for updating electronic messaging accounts |
US20050192841A1 (en) * | 2000-09-01 | 2005-09-01 | Roy Hays | Method and system for collecting information before user registration |
US20020042815A1 (en) * | 2000-09-22 | 2002-04-11 | Arthur Salzfass | Automated system and method for routing undeliverable e-mail messages and otherwise managing e-mail |
US7890989B1 (en) | 2000-10-24 | 2011-02-15 | Sony Corporation | Automated context-sensitive updating on content in an audiovisual storage system |
US9143477B2 (en) * | 2000-10-25 | 2015-09-22 | Syniverse Icx Corporation | Address recognition database |
US7403970B1 (en) * | 2000-10-25 | 2008-07-22 | Verisign, Inc. | Method and apparatus for assigning a virtual address to and text-messaging to multiple text-capable destination entities |
JP3266602B1 (en) * | 2000-10-30 | 2002-03-18 | 洋一 奥寺 | Address inquiry system, computer program product and method thereof |
US7320019B2 (en) | 2000-11-30 | 2008-01-15 | At&T Delaware Intellectual Property, Inc. | Method and apparatus for automatically checking e-mail addresses in outgoing e-mail communications |
JP3848532B2 (en) * | 2000-12-18 | 2006-11-22 | 松下電器産業株式会社 | Email address change notification agent system, email address change notification agent method |
US20020078052A1 (en) * | 2000-12-19 | 2002-06-20 | Heung-For Cheng | Automatic distribution list management |
WO2002054267A1 (en) * | 2000-12-28 | 2002-07-11 | Pitney Bowes Inc. | System and method for cleansing addresses for electronic messages |
US7543026B2 (en) * | 2000-12-28 | 2009-06-02 | Quine Douglas B | System and method for address correction of electronic messages |
US7386458B2 (en) * | 2001-03-27 | 2008-06-10 | Pitney Bowes Inc. | Recipient elected messaging services for mail that is transported in trays or tubs |
US7386457B2 (en) * | 2001-03-27 | 2008-06-10 | Pitney Bowes Inc. | Messaging services for the visually impaired |
US7346591B2 (en) * | 2001-03-27 | 2008-03-18 | Pitney Bowes Inc. | Messaging services for uniquely identified mail |
US20040094615A1 (en) * | 2001-03-27 | 2004-05-20 | Pitney Bowes Incorporated | Recipient elected messaging services enabled by processing codes printed on mail |
US7389238B2 (en) * | 2001-03-27 | 2008-06-17 | Pitney Bowes Inc. | Recipient elected messaging services |
US7085811B2 (en) * | 2001-03-27 | 2006-08-01 | Pitney Bowes Inc. | Sender elected messaging services |
JP3580262B2 (en) * | 2001-03-29 | 2004-10-20 | 日本電気株式会社 | Facsimile apparatus and electronic mail transmission method |
US20020152265A1 (en) * | 2001-04-06 | 2002-10-17 | Hillel Felman | Method and apparatus for selectively releasing personal contact information stored in an electronic or telephonic database |
JP3432809B2 (en) * | 2001-06-28 | 2003-08-04 | パナソニック コミュニケーションズ株式会社 | Communication control device and communication control method |
US20030009371A1 (en) * | 2001-07-03 | 2003-01-09 | Ravi Gauba | Interactive decision-making scenarios in an audio/video broadcast |
US20030028871A1 (en) * | 2001-07-20 | 2003-02-06 | Annie Wang | Behavior profile system and method |
US20030025720A1 (en) * | 2001-08-03 | 2003-02-06 | Clement Lau | System and method for common interest analysis among multiple users |
US8583430B2 (en) * | 2001-09-06 | 2013-11-12 | J. Albert Avila | Semi-automated intermodal voice to data transcription method and apparatus |
US20030074447A1 (en) * | 2001-10-16 | 2003-04-17 | Rafey Richter A. | Intuitive mapping between explicit and implicit personalization |
US20030097412A1 (en) * | 2001-11-20 | 2003-05-22 | Kingsum Chow | Method and apparatus for forwarding electronic mail for disabled accounts |
US7333223B2 (en) * | 2001-12-06 | 2008-02-19 | Genworth Financial, Inc. | System and method for electronically delivering documents |
US20030110223A1 (en) * | 2001-12-07 | 2003-06-12 | Scott Hamilton | System and method for correcting the failed delivery of electronic documents |
US7149780B2 (en) * | 2001-12-14 | 2006-12-12 | Pitney Bowes Inc. | Method for determining e-mail address format rules |
US20030112276A1 (en) * | 2001-12-19 | 2003-06-19 | Clement Lau | User augmentation of content |
US20030135618A1 (en) * | 2002-01-17 | 2003-07-17 | Ravikumar Pisupati | Computer network for providing services and a method of providing services with a computer network |
US7228335B2 (en) * | 2002-02-19 | 2007-06-05 | Goodcontacts Research Ltd. | Method of automatically populating contact information fields for a new contract added to an electronic contact database |
US20030182379A1 (en) * | 2002-03-25 | 2003-09-25 | Henry Steven G. | Maintaining digital transmitter distribution lists |
US7596600B2 (en) * | 2002-03-28 | 2009-09-29 | Quine Douglas B | System for selective delivery of electronic communications |
JP2004005500A (en) * | 2002-03-28 | 2004-01-08 | Matsushita Electric Ind Co Ltd | Information processor and information processing program |
US7181496B1 (en) * | 2002-03-29 | 2007-02-20 | Infowave Software Inc. | Automatic email forwarding rule creation |
US20030212745A1 (en) * | 2002-05-08 | 2003-11-13 | Caughey David A. | Selective multi-step email message marketing |
US20040003030A1 (en) * | 2002-06-28 | 2004-01-01 | Ems Inc. | Mail server with forwarding function and a storage medium storing a program for the mail server |
US20040044734A1 (en) * | 2002-08-27 | 2004-03-04 | Mark Beck | Enhanced services electronic mail |
US7062564B2 (en) * | 2002-09-13 | 2006-06-13 | Cingular Wireless Ii, Llc | Systems and methods for an e-mail clearing house |
US7334020B2 (en) * | 2002-09-20 | 2008-02-19 | Goodcontacts Research Ltd. | Automatic highlighting of new electronic message address |
US20040230565A1 (en) * | 2002-10-02 | 2004-11-18 | Burke Thomas Robert | System and method for obtaining alternate contact information |
US20040093382A1 (en) * | 2002-11-13 | 2004-05-13 | Kulkarni Suhas Sudhakar | Method of transmitting an electronic mail message |
JP3990272B2 (en) * | 2002-12-20 | 2007-10-10 | 富士通株式会社 | Mailing list management system and e-mail transmission / reception device |
US7558833B2 (en) * | 2003-05-20 | 2009-07-07 | At&T Intellectual Property, I, L.P. | Method and system for selectively forwarding electronic-mail |
US7272854B2 (en) * | 2003-06-30 | 2007-09-18 | Architecture Technology Corporation | Aliasing to prevent attacks on messaging services |
US9361602B1 (en) | 2003-10-14 | 2016-06-07 | Novell, Inc. | Temporary electronic mail addresses |
EP1667388B1 (en) * | 2004-12-03 | 2010-07-14 | Research In Motion Limited | Method and apparatus for efficient resending of messages using message ID |
US7631043B2 (en) | 2004-12-03 | 2009-12-08 | Research In Motion Limited | Method and apparatus for efficiently managing “messages sent” file and resending of messages from mobile wireless communication device |
JP4400534B2 (en) * | 2005-09-06 | 2010-01-20 | 富士通株式会社 | Reservation mail transmission method and information terminal device |
WO2007098461A2 (en) * | 2006-02-21 | 2007-08-30 | Cope Ronald S | Address retrieval system and method |
US20070214221A1 (en) * | 2006-03-08 | 2007-09-13 | Raymond Reddy | Method and system for email notification using auto-forwarding and a lightweight mail notification sender |
US7921176B2 (en) * | 2007-01-03 | 2011-04-05 | Madnani Rajkumar R | Mechanism for generating a composite email |
US8868781B2 (en) * | 2007-08-28 | 2014-10-21 | Red Hat, Inc. | Service forwarding addresses in distributed computing |
US8484376B2 (en) * | 2007-10-31 | 2013-07-09 | Red Hat, Inc. | Hot-swappable services in distributed computing |
US20090144269A1 (en) * | 2007-12-03 | 2009-06-04 | Jean-Luc Collet | Resolving unknown mailboxes |
CN101521633A (en) * | 2008-02-28 | 2009-09-02 | 阿里巴巴集团控股有限公司 | Method and device for delivering message in instant communication |
US20090241177A1 (en) * | 2008-03-21 | 2009-09-24 | Computerized Screening, Inc. | Security system for a community based managed health kiosk system |
WO2012112886A2 (en) * | 2011-02-17 | 2012-08-23 | Postcard On The Run | Mobile phone application, system, and method for sending postcards and obtaining mailing addresses |
WO2015013582A1 (en) | 2013-07-25 | 2015-01-29 | Schlumberger Canada Limited | Sand control system and methodology |
CN103618808A (en) * | 2013-11-08 | 2014-03-05 | 北京奇虎科技有限公司 | Method, device and system for processing address change of server terminal |
WO2018144669A1 (en) | 2017-02-02 | 2018-08-09 | Schlumberger Technology Corporation | Downhole tool for gravel packing a wellbore |
US11075874B2 (en) | 2019-03-21 | 2021-07-27 | International Business Machines Corporation | Intelligent electronic communications across heterogeneous communication channels |
Family Cites Families (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5581757A (en) * | 1990-11-15 | 1996-12-03 | Rolm Systems | Partially replicated database for a network of store-and-forward message systems |
US5436960A (en) | 1991-05-20 | 1995-07-25 | Campana, Jr.; Thomas J. | Electronic mail system with RF communications to mobile processors and method of operation thereof |
JPH0522339A (en) | 1991-07-16 | 1993-01-29 | Toshiba Corp | Electronic mail system |
JP3200877B2 (en) | 1991-09-03 | 2001-08-20 | 株式会社日立製作所 | Office information processing system |
US5737395A (en) | 1991-10-28 | 1998-04-07 | Centigram Communications Corporation | System and method for integrating voice, facsimile and electronic mail data through a personal computer |
US5752059A (en) | 1992-12-29 | 1998-05-12 | Apple Computer, Inc. | Apparatus and method for representing electronic mail |
JPH06216935A (en) * | 1993-01-18 | 1994-08-05 | Fujitsu Ltd | Electronic mail system |
JP3168756B2 (en) * | 1993-02-24 | 2001-05-21 | ミノルタ株式会社 | Email management method of email system |
US5734901A (en) | 1993-02-26 | 1998-03-31 | Apple Computer, Inc. | Electronic mail information associated with native application data |
ATE136183T1 (en) | 1993-06-22 | 1996-04-15 | Vmx Inc | ELECTRONIC MESSAGING SYSTEM WITH INTEGRATED VOICE MESSAGES |
JPH0787128A (en) | 1993-09-16 | 1995-03-31 | Fuji Xerox Co Ltd | System for receiving electric mail |
JPH07162454A (en) | 1993-12-03 | 1995-06-23 | Fujitsu Ltd | Method and device for electronic mail linkage |
US5732126A (en) | 1993-12-22 | 1998-03-24 | International Business Machines Corporation | Telephone answering overflow to electronic mail |
US5504897A (en) | 1994-02-22 | 1996-04-02 | Oracle Corporation | Method and apparatus for processing electronic mail in parallel |
US5493564A (en) * | 1994-03-25 | 1996-02-20 | Sprint International Communications Corp. | Method and apparatus for global routing of electronic messages |
CA2122573A1 (en) | 1994-04-13 | 1995-10-14 | John M. Pratt | Dynamic electronic mail facility for applications executing in an integrated operating environment |
JPH08256216A (en) | 1995-03-16 | 1996-10-01 | Fujitsu Ltd | Incoming call transfer system and electronic mail transfer system |
US5805810A (en) | 1995-04-27 | 1998-09-08 | Maxwell; Robert L. | Apparatus and methods for converting an electronic mail to a postal mail at the receiving station |
US5826269A (en) | 1995-06-21 | 1998-10-20 | Microsoft Corporation | Electronic mail interface for a network server |
JP3490548B2 (en) | 1995-08-04 | 2004-01-26 | シャープ株式会社 | Email system |
US5812278A (en) | 1995-10-20 | 1998-09-22 | Matsushita Graphic Communication Systems, Inc. | Image communicating method, facsimile type electronic mail apparatus and facsimile apparatus |
US5832218A (en) | 1995-12-14 | 1998-11-03 | International Business Machines Corporation | Client/server electronic mail system for providng off-line client utilization and seamless server resynchronization |
US5781901A (en) | 1995-12-21 | 1998-07-14 | Intel Corporation | Transmitting electronic mail attachment over a network using a e-mail page |
US5771355A (en) | 1995-12-21 | 1998-06-23 | Intel Corporation | Transmitting electronic mail by either reference or value at file-replication points to minimize costs |
US6405243B1 (en) * | 1996-04-05 | 2002-06-11 | Sun Microsystems, Inc. | Method and system for updating email addresses |
US5826022A (en) | 1996-04-05 | 1998-10-20 | Sun Microsystems, Inc. | Method and apparatus for receiving electronic mail |
US5937161A (en) | 1996-04-12 | 1999-08-10 | Usa.Net, Inc. | Electronic message forwarding system |
US5809242A (en) | 1996-04-19 | 1998-09-15 | Juno Online Services, L.P. | Electronic mail system for displaying advertisement at local computer received from remote system while the local computer is off-line the remote system |
US5742769A (en) * | 1996-05-06 | 1998-04-21 | Banyan Systems, Inc. | Directory with options for access to and display of email addresses |
US5818447A (en) | 1996-06-06 | 1998-10-06 | Microsoft Corporation | System and method for in-place editing of an electronic mail message using a separate program |
US5841982A (en) | 1996-06-17 | 1998-11-24 | Brouwer; Derek J. | Method and system for testing the operation of an electronic mail switch |
JPH10145493A (en) * | 1996-11-12 | 1998-05-29 | Matsushita Electric Ind Co Ltd | Message store and forward switching device |
US5844969A (en) | 1997-01-23 | 1998-12-01 | At&T Corp. | Communication system, method and device for remotely re-transmitting received electronic mail directed to a destination terminal to a new destination terminal |
USD395044S (en) | 1997-05-27 | 1998-06-09 | Fujitsu Limited | "envelope for an electronic mail document" icon for a display screen |
US6122632A (en) * | 1997-07-21 | 2000-09-19 | Convergys Customer Management Group Inc. | Electronic message management system |
US6138146A (en) * | 1997-09-29 | 2000-10-24 | Ericsson Inc. | Electronic mail forwarding system and method |
JPH11146011A (en) * | 1997-11-11 | 1999-05-28 | Nec Corp | Electronic mail system, electronic mail server and communication terminal |
US6324587B1 (en) * | 1997-12-23 | 2001-11-27 | Microsoft Corporation | Method, computer program product, and data structure for publishing a data object over a store and forward transport |
US6212552B1 (en) * | 1998-01-15 | 2001-04-03 | At&T Corp. | Declarative message addressing |
US6157945A (en) * | 1998-07-01 | 2000-12-05 | Ricoh Company, Ltd. | Digital communication device and method including a routing function |
US6314454B1 (en) * | 1998-07-01 | 2001-11-06 | Sony Corporation | Method and apparatus for certified electronic mail messages |
US6442591B1 (en) * | 1998-11-02 | 2002-08-27 | International Business Machines Corporation | Method and system for automatic electronic mail address maintenance |
-
1999
- 1999-06-23 US US09/338,834 patent/US6427164B1/en not_active Expired - Lifetime
-
2002
- 2002-06-11 US US10/167,988 patent/US20030135567A1/en not_active Abandoned
- 2002-06-17 WO PCT/US2002/019260 patent/WO2003107210A1/en not_active Application Discontinuation
Cited By (63)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US9473441B2 (en) | 1999-09-21 | 2016-10-18 | Google Inc. | E-mail with discretionary functionality |
US9092535B1 (en) | 1999-09-21 | 2015-07-28 | Google Inc. | E-mail embedded textual hyperlink object |
US7840639B1 (en) | 1999-09-21 | 2010-11-23 | G&H Nevada-Tek | Method and article of manufacture for an automatically executed application program associated with an electronic message |
US8166095B2 (en) * | 2000-07-27 | 2012-04-24 | Oracle International Corporation | System and method for achieving scalability in domain computing |
US20110016203A1 (en) * | 2000-07-27 | 2011-01-20 | Bea Systems, Inc. | System and method for achieving scalability in domain computing |
US6832246B1 (en) * | 2000-07-31 | 2004-12-14 | Pitney Bowes Inc. | Dynamic electronic forwarding system |
US6823368B1 (en) * | 2000-09-28 | 2004-11-23 | International Business Machines Corporation | Method and system for E-mail sender chain history by adding a sender-chain filed to the E-mail header when forwarding a chain forwarded E-mail message to another recipient |
US20020111937A1 (en) * | 2001-01-29 | 2002-08-15 | Mark Wetherbee | Method and system for permissible internet direct marketing |
US20020161613A1 (en) * | 2001-04-26 | 2002-10-31 | Fujitsu Limited | Message-address management program, recording medium carrying message-address management program, message-address management method, and message-address management apparatus |
US8868659B2 (en) * | 2001-05-15 | 2014-10-21 | Avaya Inc. | Method and apparatus for automatic notification and response |
US20030217109A1 (en) * | 2001-05-15 | 2003-11-20 | Ordille Joann J. | Method and apparatus for automatic notification and response |
US20060206938A1 (en) * | 2002-02-19 | 2006-09-14 | Postini Corporation | E-mail management services |
US8725889B2 (en) * | 2002-02-19 | 2014-05-13 | Google Inc. | E-mail management services |
US20070156830A1 (en) * | 2002-02-19 | 2007-07-05 | Postini Corporation | E-mail management services |
US8510392B2 (en) * | 2002-05-14 | 2013-08-13 | Avaya Inc. | Method and apparatus for automatic notification and response |
US20090037548A1 (en) * | 2002-05-14 | 2009-02-05 | Avaya Inc. | Method and Apparatus for Automatic Notification and Response |
US20070203741A1 (en) * | 2002-06-26 | 2007-08-30 | Avaya Technology Corp | Method and Apparatus for Automatic Notification and Response |
US9124643B2 (en) | 2002-06-26 | 2015-09-01 | Avaya Inc. | Method and apparatus for a publish-subscribe system with templates for role-based view of subscriptions |
US20050135681A1 (en) * | 2003-12-22 | 2005-06-23 | Schirmer Andrew L. | Methods and systems for preventing inadvertent transmission of electronic messages |
US7818680B2 (en) | 2003-12-29 | 2010-10-19 | International Business Machines Corporation | Method for deleting related messages |
US20050144561A1 (en) * | 2003-12-29 | 2005-06-30 | Moody Paul B. | System and method for deleting related messages |
US8805933B2 (en) | 2003-12-29 | 2014-08-12 | Google Inc. | System and method for building interest profiles from related messages |
US7657839B2 (en) | 2003-12-29 | 2010-02-02 | International Business Machines Corporation | System for replying to related messages |
US7409641B2 (en) * | 2003-12-29 | 2008-08-05 | International Business Machines Corporation | Method for replying to related messages |
US7412437B2 (en) | 2003-12-29 | 2008-08-12 | International Business Machines Corporation | System and method for searching and retrieving related messages |
US20080295001A1 (en) * | 2003-12-29 | 2008-11-27 | International Business Machines Corporation (Ibm) | System for replying to related messages |
US20050144157A1 (en) * | 2003-12-29 | 2005-06-30 | Moody Paul B. | System and method for searching and retrieving related messages |
US7962508B2 (en) | 2003-12-29 | 2011-06-14 | International Business Machines Corporation | System and method for searching and retrieving related messages |
US20050198256A1 (en) * | 2003-12-29 | 2005-09-08 | Moody Paul B. | System and method for building interest profiles from related messages |
US20050198143A1 (en) * | 2003-12-29 | 2005-09-08 | Moody Paul B. | System and method for replying to related messages |
US20050208941A1 (en) * | 2004-03-18 | 2005-09-22 | Ordille Joann J | Method and apparatus for a publish-subscribe system with third party subscription delivery |
US8516045B2 (en) | 2004-03-18 | 2013-08-20 | Avaya Inc. | Method and apparatus for automatic notification and response based on communication flow expressions having dynamic context |
US20050210062A1 (en) * | 2004-03-18 | 2005-09-22 | Ordille Joann J | Method and apparatus for a publish-subscribe system with templates for role-based view of subscriptions |
US20050249337A1 (en) * | 2004-03-18 | 2005-11-10 | Ordille Joann J | Method and apparatus for just in time education |
US7734731B2 (en) | 2004-03-18 | 2010-06-08 | Avaya Inc. | Method and apparatus for a publish-subscribe system with third party subscription delivery |
US8495163B2 (en) | 2004-03-18 | 2013-07-23 | Avaya, Inc. | Method and apparatus for a publish-subscribe system with templates for role-based view of subscriptions |
US20060075031A1 (en) * | 2004-09-17 | 2006-04-06 | Wagner Dirk P | Bounce management |
US20070202881A1 (en) * | 2004-11-25 | 2007-08-30 | Sms Card Limited | Data processing |
GB2425192A (en) * | 2004-11-25 | 2006-10-18 | Sms Card Ltd | Providing up-to-date contact information |
US7801925B2 (en) * | 2004-12-22 | 2010-09-21 | United States Postal Service | System and method for electronically processing address information |
US20060276916A1 (en) * | 2004-12-22 | 2006-12-07 | Dearing Stephen M | System and method for electronically processing address information |
US8165909B2 (en) | 2005-05-17 | 2012-04-24 | The United States Postal Service | System and method for automated management of an address database |
US20070094155A1 (en) * | 2005-05-17 | 2007-04-26 | Dearing Stephen M | System and method for automated management of an address database |
US20070204341A1 (en) * | 2005-11-23 | 2007-08-30 | Rand David L | SMTP network security processing in a transparent relay in a computer network |
US7926108B2 (en) * | 2005-11-23 | 2011-04-12 | Trend Micro Incorporated | SMTP network security processing in a transparent relay in a computer network |
US8028025B2 (en) * | 2006-05-18 | 2011-09-27 | International Business Machines Corporation | Apparatus, system, and method for setting/retrieving header information dynamically into/from service data objects for protocol based technology adapters |
US20070271341A1 (en) * | 2006-05-18 | 2007-11-22 | Rajan Kumar | Apparatus, system, and method for setting/retrieving header information dynamically into/from service data objects for protocol based technology adapters |
US20090030993A1 (en) * | 2007-07-26 | 2009-01-29 | Mxtoolbox | Simultaneous synchronous split-domain email routing with conflict resolution |
US7818384B2 (en) * | 2007-07-26 | 2010-10-19 | Rachal Eric M | Simultaneous synchronous split-domain email routing with conflict resolution |
US20090157828A1 (en) * | 2007-12-12 | 2009-06-18 | Sumit Kumar Agrawal | Techniques for specifying recipients in an electronic mail (email) system |
US20090163177A1 (en) * | 2007-12-21 | 2009-06-25 | Fmr Llc | Guest Communication and Information Delivery User Interface |
US20090307315A1 (en) * | 2008-06-06 | 2009-12-10 | International Business Machines Corporation | Facilitating correction of incorrect identities in propagated electronic communications |
US20090307317A1 (en) * | 2008-06-06 | 2009-12-10 | International Business Machines Corporation | Automatically modifying distributed communications |
US20090307271A1 (en) * | 2008-06-06 | 2009-12-10 | International Business Machines Corporation | Autonomic correction of incorrect identities in repositories |
US8756284B2 (en) | 2008-06-06 | 2014-06-17 | International Business Machines Corporation | Minimizing incorrectly addressed communications when working with ambiguous recipient designations |
US8095604B2 (en) | 2008-06-06 | 2012-01-10 | International Business Machines Corporation | Automatically modifying distributed communications |
US8316100B2 (en) * | 2008-06-06 | 2012-11-20 | International Business Machines Corporation | Autonomic correction of incorrect identities in repositories |
US8171088B2 (en) * | 2008-06-06 | 2012-05-01 | International Business Machines Corporation | Facilitating correction of incorrect identities in propagated electronic communications |
US20100017485A1 (en) * | 2008-07-21 | 2010-01-21 | International Business Machines Corporation | Enforcing conformance in email content |
US8140628B2 (en) * | 2008-07-21 | 2012-03-20 | International Business Machines Corporation | Enforcing conformance in email content |
US8359359B2 (en) * | 2008-12-26 | 2013-01-22 | International Business Machines Corporation | Device, method, and computer program product for supporting creation of reply mail |
US20100169445A1 (en) * | 2008-12-26 | 2010-07-01 | International Business Machines Corporation | Device, method, and computer program product for supporting creation of reply mail |
US20100306324A1 (en) * | 2009-06-01 | 2010-12-02 | Bontempo Allan J | Anonymously and autonomously bridging return system and method |
Also Published As
Publication number | Publication date |
---|---|
US6427164B1 (en) | 2002-07-30 |
WO2003107210A1 (en) | 2003-12-24 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6427164B1 (en) | Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown | |
US6438583B1 (en) | System and method for re-routing of e-mail messages | |
Crocker | Internet mail architecture | |
Klensin | RFC2821: Simple mail transfer protocol | |
Klensin | Simple mail transfer protocol | |
US6993561B2 (en) | Method and apparatus for maintaining a unified view of multiple mailboxes | |
US20010049745A1 (en) | Method of enabling transmission and reception of communication when current destination for recipient is unknown to sender | |
US7689654B2 (en) | Email address verification | |
US20030200267A1 (en) | Email management system | |
US6865594B1 (en) | Methods and apparatus for automatically generating a routing table in a messaging server | |
US20020143879A1 (en) | Method and system for automatically updating electronic mail address information within an electronic mail address database | |
JP2005528052A (en) | Message processing and contact alias control based on address patterns and automatic management | |
US7058683B1 (en) | Methods and apparatus for providing a virtual host in electronic messaging servers | |
US20060101123A1 (en) | Methods and systems for selecting criteria for a successful acknowledgement message in instant messaging | |
US20040093382A1 (en) | Method of transmitting an electronic mail message | |
JPH1141275A (en) | Method and device for automatically cleaning address list of electronic mail transmitted/received on internet | |
Vaudreuil et al. | Voice profile for internet mail-version 2 | |
Crocker | RFC 5598: Internet Mail Architecture | |
WO2001067268A1 (en) | Methods and apparatus for automatically generating a routing table in a messaging server | |
Protocol | INTERNET-DRAFT John C. Klensin, Editor Expires in six months Dawn P. Mann, Co-Editor July 30, 1997 | |
Protocol | INTERNET-DRAFT John C. Klensin, Editor Expires September 9, 2000 March 9, 2000 | |
UNDEFINED | Internet Mail Architecture | |
Protocol | INTERNET-DRAFT John C. Klensin, Editor Expires December 2000 July 10, 2000 | |
Protocol | Network Working Group J. Klensin Internet-Draft April 15, 2008 Obsoletes: 2821 (if approved) Intended status: Standards Track Expires: October 17, 2008 | |
Protocol | Network Working Group J. Klensin Internet-Draft March 20, 2008 Obsoletes: 2821 (if approved) Intended status: Standards Track Expires: September 21, 2008 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: MAIL REGISTRY, INC., NEVADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:MAIL REGISTRY, INC.;REEL/FRAME:015074/0787 Effective date: 20030911 |
|
AS | Assignment |
Owner name: HANGER SOLUTIONS, LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLECTUAL VENTURES ASSETS 161 LLC;REEL/FRAME:052159/0509 Effective date: 20191206 |
|
AS | Assignment |
Owner name: INTELLECTUAL VENTURES ASSETS 161 LLC, DELAWARE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:CUFER ASSET LTD. L.L.C.;REEL/FRAME:051873/0365 Effective date: 20191126 |