EP1234417B1 - Electronic mail server - Google Patents

Electronic mail server Download PDF

Info

Publication number
EP1234417B1
EP1234417B1 EP00984666A EP00984666A EP1234417B1 EP 1234417 B1 EP1234417 B1 EP 1234417B1 EP 00984666 A EP00984666 A EP 00984666A EP 00984666 A EP00984666 A EP 00984666A EP 1234417 B1 EP1234417 B1 EP 1234417B1
Authority
EP
European Patent Office
Prior art keywords
mail
character set
account
message
server
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP00984666A
Other languages
German (de)
English (en)
French (fr)
Other versions
EP1234417A2 (en
Inventor
Edmon Chung
Jim Lam
David Leung
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Afilias Ltd
Original Assignee
Neteka Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Neteka Inc filed Critical Neteka Inc
Publication of EP1234417A2 publication Critical patent/EP1234417A2/en
Application granted granted Critical
Publication of EP1234417B1 publication Critical patent/EP1234417B1/en
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/30—Managing network names, e.g. use of aliases or nicknames
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/45—Network directories; Name-to-address mapping
    • H04L61/4552—Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2101/00—Indexing scheme associated with group H04L61/00
    • H04L2101/30—Types of network names
    • H04L2101/32—Types of network names containing non-Latin characters, e.g. Chinese domain names
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
    • Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y10S707/00—Data processing: database and file management or data structures
    • Y10S707/99931—Database or file accessing
    • Y10S707/99932—Access augmentation or optimizing

Definitions

  • the present invention relates to a system and method for facilitating the transmission and delivery of electronic mail over a wide area network.
  • the present invention relates to an electronic mail server configured to recognize e-mail account identifiers consisting of non-ASCII characters.
  • each network device In order to facilitate communication between communication devices over a network, each network device is typically assigned a unique numeric network address. A user associated with one of the network devices then need only provide the network transport layer with the numeric network address of the intended target to communicate with the target.
  • this system functions satisfactorily in small network where users only communicate with a small number of network communication devices, the system cannot be readily transported to large networks since it would require each network user to remember a large number of unique numeric network addresses. For this reason, the domain name system (DNS) was proposed by Mockapetris in 1987 (RFC 1034 and RFC 1035, Network Working Group; presently available at "http://www.ietf.org”) as a mechanism for facilitating communication between communication devices over the Internet.
  • DNS domain name system
  • the DNS facilitates Internet communication by associating domain names with the numeric (IP, "Internet Protocol”) network addresses.
  • the DNS basically consists of resource records, domain name servers, and resolvers. Each resource records includes information concerning each network node, including the IP address of the network node, and the domain names associated with the IP address. Together, the resource records provide the Internet with a tree-structured domain name space.
  • Domain name servers are Internet servers which retain information concerning the domain name space. In particular, each domain name server has a file (“zone file”) which retains resource records associated with its own subset of the domain name space. These records are referred to as "authoritative" records.
  • domain name servers also temporarily cache copies of resource records acquired from other domain name servers in order to improve the performance of the retrieval process when non-local data is requested by a resolver.
  • Resolvers are local programs which extract information from domain name servers in response to client requests.
  • the domain name associated with a network device at particular IP address has a top level label field, and one or more lower level label fields.
  • the label fields comprising a domain name are separated from one another through a delimiter (".”), and are each positioned in the domain name according to their respective relative levels in the domain name hierarchy.
  • each e-mail account is represented on a e-mail server as a distinct directory, each containing a sub-directory for caching incoming e-mail messages and a sub-directory for caching outgoing e-mail messages.
  • the originator's e-mail server Upon receipt of the e-mail message from the originator, the originator's e-mail server assigns a globally unique message identifier (determined in accordance with the time of receipt of the e-mail message), extracts the domain name of the recipient's e-mail server from the e-mail message, and transmits the extracted domain name to a domain name resolver for determination of the IP address of the recipient's e-mail server.
  • the resolver queries a root DNS server with the top level label identified in the domain name to obtain the IP address of the DNS server which has the zone file associated with the top level domain.
  • the resolver then accesses the identified DNS server using the obtained IP address, and with the label occupying the next highest position in the domain name hierarchy (the label immediately to the left of the top level label in the domain name) obtains the IP address of the DNS server which has the zone file associated with the queried label. The process continues until each label in the domain name has been resolved, at which point the last queried DNS server provides the resolver with the IP address of the network device having the specified domain name. The resolver then transmits the received IP address to the originator's e-mail server.
  • the originator's e-mail server Upon receipt of the IP address assigned to the recipient's e-mail server, the originator's e-mail server establishes a communications channel with the recipient's e-mail server and then transmits the e-mail message over the communications channel, typically using Simple Mail Transfer Protocol (commonly referred to as "SMTP"; described in detail in RFC 821 and RFC 1869, "http://www.ietf.org").
  • SMTP Simple Mail Transfer Protocol
  • the originator's e-mail server After an initial handshaking stage during which the recipient's e-mail server acknowledges that it is willing to receive an e-mail message and that the recipient has established an e-mail account thereon, the originator's e-mail server transmits the e-mail message to the recipient's e-mail server and then closes the communications channel.
  • the recipient's e-mail server caches the e-mail message in the directory associated with the recipient.
  • the recipient To retrieve the e-mail message, the recipient establishes a communications channel with the recipient's e-mail server, and retrieves the e-mail message over the communications channel, typically using Post Office Protocol - Version 3 (commonly referred to as "POP3"; described in detail in RFC 1939 and RFC 2449, "http://www.ietf.org”).
  • POP3 Post Office Protocol - Version 3
  • the recipient authenticates itself with the e-mail server using an assigned username and password. After the recipient successfully authenticates itself, the recipient is then able to initiate transmission of the e-mail message over the communications channel to the recipient's local computer.
  • the DNS system is case insensitive, so that two domain names which have identical spellings but whose component letters do not correspond in terms of their respective cases, will resolve to the same network address.
  • most e-mail servers only accept, for inclusion as part of an e-mail account name, the hyphen, the numbers 0 to 9 and the letters 'A' to 'Z' and 'a' to '2', thereby limiting the number of account names available.
  • US-A-5 333 317 describes a directory database in which an e-mail account is associated with an e-mail address.
  • the patent neither describes nor suggests e-mail accounts or e-mail addresses having characters other than the ASCII character set,
  • RFC 2047 titled "MIME Part Three: Message Header Extensions for non-ASCII text" relates to a mechanism for allowing the user of non-ASCII characters as part of a message header, but not as part of the e-mail address itself.
  • RFC 2277 titled "IETF Policy on Character Sets and Languages" relates to a basic policy for developing protocol capable of interacting with different character sets. However, like the previous two references, it does not teach the use of non-ASCII characters as part of an e-mail address.
  • EP-A-0 565 850 relates to a system for integrating messages from different media types into a single in-basket. Like all of the previous references, it does not teach the use of non-ASCII characters as part of an e-mail address.
  • an electronic mail server and a method for facilitating e-mail communication over a network which address deficiencies of the prior art electronic mail systems.
  • the electronic mail server includes an account name database and an account name processor in communication with the account name database for providing a response to a message received over the network.
  • the message includes an e-mail account name label comprising at least one account name character (having an account name character set type), with the character set type including a non-ASCII compatible character set.
  • the account name database includes a number of database records, each identifying an e-mail account name comprising at least one record character having a record character set type, and a record character set identifier identifying the record character set type.
  • the account name processor includes a correlation processor and a response processor.
  • the correlation processor is configured to determine the correlation between the received e-mail account name label and the respective e-mail account names in accordance with the associated character set type.
  • the response processor is in communication with the correlation processor and provides the response to the message in accordance with the correlation indication.
  • the method for facilitating e-mail communication includes the steps of (1) receiving at an e-mail server a message comprising an e-mail account name label, the e-mail server maintaining at least one e-mail account each associated with an e-mail account name, with the account name label comprising at least one account name character having an account name character set type and with the character set type including a non-ASCII compatible character set; (2) determining the correlation between the received e-mail account name label and the respective e-mail account names in accordance with the associated character set type; and (3) responding to the message in accordance with the correlation indication.
  • an electronic message for facilitating electronic communication.
  • the electronic message includes a header portion and a data portion associated with the header portion.
  • the header portion includes an e-mail account name label, with the account name label comprising at least one account name character (having an account name character set type), and with the character set type including a non-ASCII compatible character set.
  • the data portion includes an originator field identifying an originator of the message and a recipient field identifying a recipient of the message, with one of the fields being associated with the e-mail account name label.
  • an electronic mail account name database for facilitating electronic communication.
  • the account name database includes at least one database record, each comprising (1) an account name label associated with an e-mail account name, with the account name label including at least one record character having a record character set type; and (2) a record character set identifier identifying the record character set type.
  • an electronic mail system comprising a plurality of network clients 102, a plurality of a plurality of name resolution servers 104, a plurality of network address servers 106, a plurality of e-mail transmission servers 200, a plurality of e-mail delivery servers 500, and a communications network 108 interconnecting the network clients 102, the name resolution servers 104, the network address servers 106, the e-mail transmission servers 200 and the e-mail delivery servers 500.
  • the communications network 108 comprises the Internet
  • the e-mail transmission servers 200 comprise SMTP-based servers
  • the e-mail delivery servers 500 comprise POP3-based servers.
  • the communications network 108 may also comprise other network forms, such as an intranet or a wireless network, and the e-mail servers 200, 500 may employ protocols other than SMTP and POP3, if desired. Further, each e-mail transmission server 200 may be paired with an e-mail delivery servers 500, with both servers 500 residing on a common computer.
  • each network client 102 comprises a personal computer equipped with software for communicating with the name resolution servers 104 and the e-mail servers 200, 500 over the communications network 108.
  • the name resolution servers 104 and the network address servers 106 respectively comprise domain name resolvers and domain name servers, as described by Mockapetris in RFC 1034 and RFC 1035. Since RFC 1034 and RFC 1035 are publicly available documents, and since the structure and operation of domain name resolvers and domain name servers are well known to those skilled in the art, no description of the name resolution servers 104 and the network address servers 106 is required.
  • each e-mail transmission server 200 comprises a network interface 202 for communicating with the network clients 102 and other e-mail transmission servers 200 over the communications network 108, and a central processing unit (CPU) 204 in communication with the network interface 202, and a non-volatile memory (NVM) 206 and a volatile memory (RAM) 208 in communication with the CPU 204.
  • the NVM 206 comprises a magnetic or optical storage device, and includes a non-volatile account name database 210 which has records identifying each e-mail account managed by the e-mail transmission server 200, and an e-mail message database 212 which stores e-mail messages received from network clients 102.
  • the e-mail message database 212 comprises a plurality of directories or electronic folders, each being associated with a respective e-mail account and including an inbox sub-directory and an outbox sub-directory.
  • the NVM 206 also includes processor instructions for the CPU 204 which establish in the RAM 208 a volatile account name database 214 as a copy of the non-volatile account name database 210, and a memory object defining an account name processor 216 in communication with the account name database 214.
  • the account name database 214 is established in the RAM 208 to increase the speed of the account name resolving process and may be dispensed with in applications where speed is not a paramount concern.
  • the account name database 214 of each e-mail transmission server 200 includes a plurality of database records 300, each being associated with an e-mail account.
  • the structure of a typical database record is shown in Fig. 3.
  • each database record 300 includes a plurality of characters 302 which together define an e-mail account name 304a, and a character set identifier 306a identifying the character set of which the characters 302 comprising the e-mail account name 304a are members.
  • the character codes used to define an e-mail account name using one character set could define another e-mail account name using another character set.
  • each database record 300 includes a plurality of alias e-mail account names 304b, 304c, 304d each having an associated (different) character set identifier (306b, 306c, 306d).
  • the e-mail account names 304a, 304b use the same character codes, but employ different character sets (Chinese character sets Big5 and GB2312) to define the respective e-mail account names.
  • the e-mail account names 304a, 304c employ different character sets (Chinese Character sets Big5 and GB2312), but define the same account name using different character codes.
  • the e-mail account names 304c, 304d again employ different character sets (Chinese Character sets Big5 and GB2312), but use the same character codes to define different account names.
  • the e-mail transmission server 200 is able to resolve an account name defined using any of a plurality of different character sets, even if the e-mail address received does not include a character set identifier (described below).
  • a character set identifier such as a Unicode-based character set
  • the account name processor 216 is shown comprising a correlation processor 218 and a response processor 220 in communication with the correlation processor 218.
  • the correlation processor 218 is configured to determine a correlation between the account name component of an e-mail address, and the account names 304 identified in the account name database 214.
  • the correlation processor 218 of each e-mail transmission server 200 is configured to determine whether an e-mail account name component of an e-mail message received over the communications network 108 has a corresponding entry in the e-mail transmission server's 200 account name database 214.
  • the response processor 220 is configured to provide a response to the received e-mail message in accordance with the correlation indication.
  • each e-mail transmission server 200 is configured to recognize a plurality of different character sets, including a non-ASCII compatible character set (such as UTF-8: an 8-bit Unicode-based character set) to facilitate communication of e-mails (having multinational characters in the account name fields) with 8-bit e-mail servers.
  • a non-ASCII compatible character set such as UTF-8: an 8-bit Unicode-based character set
  • each e-mail transmission server 200 is configured to recognize a 7-bit ACE (ASCII Compatible Encoding) character set for backwards compatibility with 7-bit e-mail servers.
  • ACE ASCII Compatible Encoding
  • e-mail message 400 (which could be transmitted between an originating e-mail transmission server 200 and a recipient e-mail transmission server 200) is shown in Fig. 4.
  • the e-mail message 400 is similar to the standard message format for Internet text messages described in detail in RFC 822 (available at "http://www.ietf.org") in that the e-mail message 400 includes a message ID 402, a text header portion 404 and a text body or data portion 406 associated with the header portion 404.
  • the header portion 404 includes a plurality of header lines 408, each including a field identifier 410, a plurality of characters 412 which define an account "nickname" 414, and a plurality of characters 416 associated with the field identifier 410 which define an e-mail account name 418.
  • the account names 418 respectively associated with the "M-FROM” and “M-REPLY-TO" field identifiers 410 are used by the e-mail transmission server 200 for the representation of account names using multinational characters.
  • the "M-FROM” field identifier 410 defines the account name of the originator of the e-mail message, while the "M-REPLY-TO" field identifier 410 defines the account name to which replies should be transmitted.
  • the "FROM” and “REPLY-TO” field identifiers 410 serve a similar purpose respectively as the "M-FROM” and “M-REPLY-TO” field identifiers 410, except that the account names associated with the "FROM” and “REPLY-TO” field identifiers 410 are defining using an ACE character set to ensure backwards compatibility with non-compliant client servers 102.
  • the e-mail delivery server 500 is substantially similar in structure to the e-mail transmission server 200. As shown in Fig. 5, each e-mail delivery server 500 comprises a network interface 502 for communicating with the network clients 102 and the e-mail transmission servers 200 over the communications network 108, and a central processing unit (CPU) 504 in communication with the network interface 502, and a non-volatile memory (NVM) 506 and a volatile memory (RAM) 508 in communication with the CPU 504.
  • the NVM 506 comprises a magnetic or optical storage device, and includes a non-volatile account name database 510 which has records identifying each e-mail account managed by the e-mail delivery server 500, and a message database 512 for caching incoming e-mail messages.
  • the NVM 506 also includes processor instructions for the CPU 504 which establish in the RAM 508 a volatile account name database 514 as a copy of the non-volatile account name database 510, and a memory object defining an account name processor 516 in communication with the account name database 514.
  • the account name database 514 of each e-mail delivery server 500 includes a plurality of database records 300, each being associated with an e-mail account.
  • the account name processor 516 is shown comprising a correlation processor 518 and a response processor 520 in communication with the correlation processor 518.
  • the correlation processor 518 is configured to determine a correlation between an account name received from a user of a network client 102, and the account names identified in the account name database 514 to determine whether the received account name is valid.
  • the response processor 520 is configured to provide a response to the network client 102 in accordance with the correlation indication.
  • each e-mail server 200, 500 reads its respective database into its respective RAM. Then, at step 500, one of the network clients 102 causes one of the e-mail transmission servers 200 (the "originating" e-mail transmission server 200) to open a communications channel with another one of the e-mail transmission servers 200 (the "receiving" e-mail transmission server 200) over the communications network 108 in order to send an e-mail message 400 to a recipient having an e-mail account established at the receiving e-mail transmission server 200. Consistent with the SMTP protocol, preferably each e-mail transmission server 200 is configured to wait for a connection on TCP port 25 for the initiation of an e-mail transmission request.
  • the originating server 200 transmits a command to the receiving server 200, requesting that the receiving server 200 indicate whether it is capable of processing e-mail messages 400 having e-mail addresses incorporating multilingual characters and, if so, to provide the originating server 200 with a list of character sets recognized by the receiving server 200.
  • the originating server 200 attempts to negotiate a suitable character set with the receiving server 200.
  • the originating server 200 selects one of the identified character sets and transmits a "MAIL FROM" command to the receiving server 200, together with the account name of the originator of the e-mail message 400 encoded in the selected character set and a "CHARSET" parameter defining the selected character set.
  • the account name processor 216 of the receiving server 200 determines whether the received "CHARSET” parameter identifies one of the character sets recognized by the receiving server 200. If the "CHARSET” parameter is recognized, the receiving server 200 replies with a positive acknowledgement, whereas if the "CHARSET” parameter is not recognized, the receiving server 200 replies with an error message.
  • the originating server 200 transmits a "RCPT TO" command to the receiving server 200, together with the account name of the recipient of the e-mail message 400 encoded in the selected character set.
  • the account name processor 216 of the receiving server 200 queries its account name database 214 with the received account name and the "CHARSET" parameter to determine whether the account name is valid. Alternately, if the originating server 200 does not provide the "CHARSET" parameter, the account name processor 216 of the receiving server 200 queries its account name database 214 with the received account name for an entry which matches an e-mail account name 304a or one of the alias account names 304b, 304c, 304d.
  • the originating server 200 Upon receipt of a positive response from the receiving server 200, at step 512 the originating server 200 transmits the data portion of the e-mail message 400 to the receiving server 200 and then closes the communications channel with the receiving server 200. Alternately, in one variation, the originating server 200 only transmits the header portion 404 to the receiving server 200, together with a pointer to the data portion 406 where the data portion 406 is stored in the e-mail message database 212 on the originating server 200. This variation is particularly advantageous where the originator of the e-mail message 400 identifies several recipients for the e-mail message 400, all who have e-mail accounts established on the same receiving server 200 since it conserves disk space on the receiving server 200.
  • the originating server 200 transmits the header portion 404 and the data portion 406 to the receiving server 200, and the receiving server 200 maintains in its e-mail message database 212 a single copy of the received e-mail message 400, and then provides the e-mail delivery server 500 with the header portion 404 and a pointer to the data portion 406 where the data portion 406 is stored in the e-mail message database 212 on the receiving server 200.
  • a sample SMTP session between an originating e-mail transmission server 200 (C) and a receiving e-mail transmission server 200 (S) is shown below, with the command “EHLO” being a command from the SMTP-extension, requesting a listing of supported modes and character sets from the receiving server 200.
  • the selected character set is UTF-8, and the response "MATRX" to the "EHLO" command identifies that the receiving server 200 is compliant with the subject protocol:
  • the "CHARSET” parameter is dispensed with, and the "MAIL FROM” and “RCPT TO” commands are respectively replaced with the "M-MAIL FROM” and “M-RCPT TO” commands which indicate by way of implication that the UTF-8 character set is selected.
  • a sample SMTP session using these additional commands is shown below:
  • the originating server 200 determines that the receiving server 200 is not capable of processing e-mail messages 400 having e-mail addresses incorporating multilingual characters, the originating server 200 should attempt to send any multilingual names in ACE format.
  • the originating server 200 transmits a BIG5-encoded account name encoded in RACE format:
  • each e-mail delivery server 500 is configured to wait for a connection on TCP port 110 for the initiation of an e-mail delivery request.
  • the receiving server 200 transmits a command to the delivery server 500, requesting that the delivery server 500 indicate whether it is capable of processing e-mail messages 400 having e-mail addresses incorporating multilingual characters and, if so, to provide the receiving server 200 with a list of character sets recognized by the delivery server 500.
  • the receiving server 200 attempts to negotiate a suitable character set with the delivery server 500.
  • the receiving server 200 selects one of the identified character sets and transmits a "USER" command to the delivery server 500, together with the account name of the recipient of the e-mail message 400 encoded in the selected character set and a "CHARSET" parameter defining the selected character set.
  • the account name processor 516 of the delivery server 500 determines whether the received "CHARSET” parameter identifies one of the character sets recognized by the delivery server 500. If the "CHARSET" parameter is recognized, the account name processor 516 queries its account name database 514 with the received account name and the "CHARSET” parameter to determine whether the account name is valid. At step 522, the receiving server 200 then transmits the e-mail message 400 (or the header portion 404 and a pointer to the data portion 406, as discussed above) to the delivery server 500, and closes the communications channel with the delivery server 500.
  • a sample POP3 session between a receiving e-mail transmission server 200 (C) and an e-mail delivery server 500 (S) is shown below, with the command "CAPA" being a command from the POP3-extension, requesting a listing of supported modes and character sets from the delivery server 500:

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)
  • Debugging And Monitoring (AREA)
  • Multi Processors (AREA)
  • Small-Scale Networks (AREA)
  • Non-Silver Salt Photosensitive Materials And Non-Silver Salt Photography (AREA)
  • Saccharide Compounds (AREA)
  • Pharmaceuticals Containing Other Organic And Inorganic Compounds (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
EP00984666A 1999-11-26 2000-11-27 Electronic mail server Expired - Lifetime EP1234417B1 (en)

Applications Claiming Priority (5)

Application Number Priority Date Filing Date Title
US16762499P 1999-11-26 1999-11-26
US167624P 1999-11-26
CA002312540A CA2312540A1 (en) 2000-06-27 2000-06-27 Network address name resolution server
CA2312540 2000-06-27
PCT/CA2000/001394 WO2001039457A2 (en) 1999-11-26 2000-11-27 Electronic mail server

Publications (2)

Publication Number Publication Date
EP1234417A2 EP1234417A2 (en) 2002-08-28
EP1234417B1 true EP1234417B1 (en) 2007-08-08

Family

ID=4166585

Family Applications (2)

Application Number Title Priority Date Filing Date
EP00984665A Expired - Lifetime EP1234434B1 (en) 1999-11-26 2000-11-27 Network address server
EP00984666A Expired - Lifetime EP1234417B1 (en) 1999-11-26 2000-11-27 Electronic mail server

Family Applications Before (1)

Application Number Title Priority Date Filing Date
EP00984665A Expired - Lifetime EP1234434B1 (en) 1999-11-26 2000-11-27 Network address server

Country Status (10)

Country Link
US (1) US20070073839A1 (ja)
EP (2) EP1234434B1 (ja)
JP (2) JP4975926B2 (ja)
CN (2) CN1285199C (ja)
AT (2) ATE288166T1 (ja)
AU (2) AU2131401A (ja)
CA (1) CA2312540A1 (ja)
DE (2) DE60017788T2 (ja)
ES (2) ES2239630T3 (ja)
WO (2) WO2001039431A2 (ja)

Families Citing this family (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB0206849D0 (en) 2002-03-22 2002-05-01 Nokia Corp Communication system and method
CN1315283C (zh) * 2003-08-15 2007-05-09 华为技术有限公司 在通信网络中集成管理和发放业务的方法
CN100418089C (zh) * 2003-08-20 2008-09-10 苹果公司 加速本地高速缓存中资源记录到期的方法和装置
FR2871013B1 (fr) * 2004-06-01 2007-02-23 Alcatel Sa Routage pour detection de serveurs au sein d'un reseau de communication
DE102005029661B3 (de) * 2005-06-21 2006-11-30 Siemens Ag Verfahren zur Namensauflösung und Namensauflösungs-Server
EP2027701A4 (en) * 2006-06-15 2010-06-30 Ericsson Telefon Ab L M NAME ADDRESS MANAGEMENT IN COMMUNICATION NETWORKS
US8234379B2 (en) 2006-09-14 2012-07-31 Afilias Limited System and method for facilitating distribution of limited resources
EP2253110A4 (en) * 2008-03-10 2011-10-19 Afilias Ltd ALTERNATIVE CONFIGURATION FOR ELECTRONIC MAIL ADDRESS
KR101715810B1 (ko) * 2008-03-10 2017-03-13 아필리어스 리미티드 플랫폼 독립적인 ｉｄｎ 이메일 저장소 변환
ATE544274T1 (de) 2008-08-01 2012-02-15 Research In Motion Ltd Elektronisches e-mail-system mit funktionen zur formatierung von nachrichten mittels zeichensätzen und zugehörige verfahren
US9177264B2 (en) 2009-03-06 2015-11-03 Chiaramail, Corp. Managing message categories in a network
US8315607B2 (en) * 2009-04-06 2012-11-20 Htc Corporation Method and system for filtering incoming messages to a mobile device
US8819148B2 (en) * 2010-03-10 2014-08-26 Afilias Limited Alternate E-mail delivery
US8725815B2 (en) * 2011-03-30 2014-05-13 Afilias Limited Transmitting messages between internationalized email systems and non-internationalized email systems
US20120296990A1 (en) * 2011-05-16 2012-11-22 Uomini Robert G Shared content server for electronic messages
US8635292B2 (en) * 2011-05-16 2014-01-21 Robert Uomini Method for reduction of disk space usage of electronic messages in a network
US8805943B2 (en) * 2012-03-08 2014-08-12 Microsoft Corporation Optimized routing for proxy use
CN104516862B (zh) * 2013-09-29 2018-05-01 北大方正集团有限公司 一种选择读取目标文档的编码格式的方法及其系统
US9553833B2 (en) * 2013-12-06 2017-01-24 Verizon Patent And Licensing Inc. Confidential messages in a group chat
CN104915347B (zh) * 2014-03-11 2019-04-12 腾讯科技（北京）有限公司 网页地址的处理方法、装置及系统
CN110636374A (zh) * 2018-06-22 2019-12-31 北京京东尚科信息技术有限公司 用于查找信息的方法和装置

Family Cites Families (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
AU631276B2 (en) * 1989-12-22 1992-11-19 Bull Hn Information Systems Inc. Name resolution in a directory database
JP3011505B2 (ja) * 1991-11-07 2000-02-21 株式会社東芝 電子メールシステム
US5333266A (en) * 1992-03-27 1994-07-26 International Business Machines Corporation Method and apparatus for message handling in computer systems
JP3168756B2 (ja) * 1993-02-24 2001-05-21 ミノルタ株式会社 電子メールシステムのメール管理方法
US5826269A (en) * 1995-06-21 1998-10-20 Microsoft Corporation Electronic mail interface for a network server
US5682158A (en) * 1995-09-13 1997-10-28 Apple Computer, Inc. Code converter with truncation processing
US6292770B1 (en) * 1997-01-22 2001-09-18 International Business Machines Corporation Japanese language user interface for messaging system
US5835912A (en) * 1997-03-13 1998-11-10 The United States Of America As Represented By The National Security Agency Method of efficiency and flexibility storing, retrieving, and modifying data in any language representation
US5929792A (en) * 1997-06-30 1999-07-27 Sun Microsystems, Inc. Method and apparatus for encoding multiple character sets
JP3439330B2 (ja) * 1997-09-25 2003-08-25 日本電気株式会社 電子メールサーバ
FI105971B (fi) * 1998-04-30 2000-10-31 Nokia Mobile Phones Ltd Menetelmä ja laitteisto sähköpostin käsittelemiseksi
US6560596B1 (en) * 1998-08-31 2003-05-06 Multilingual Domains Llc Multiscript database system and method
US6807254B1 (en) * 1998-11-06 2004-10-19 Nms Communications Method and system for interactive messaging
US6539118B1 (en) * 1998-12-31 2003-03-25 International Business Machines Corporation System and method for evaluating character sets of a message containing a plurality of character sets
US6314469B1 (en) * 1999-02-26 2001-11-06 I-Dns.Net International Pte Ltd Multi-language domain name service
US6182148B1 (en) * 1999-03-18 2001-01-30 Walid, Inc. Method and system for internationalizing domain names
JP2000267965A (ja) * 1999-03-19 2000-09-29 Shidan Jo Ｕｒｌと電子メールアドレスの異言語間変換システム

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
ES2293931T3 (es) 2008-04-01
DE60035896D1 (de) 2007-09-20
JP2003528485A (ja) 2003-09-24
DE60035896T2 (de) 2008-05-15
EP1234434A2 (en) 2002-08-28
US20070073839A1 (en) 2007-03-29
JP4975926B2 (ja) 2012-07-11
CN1423880A (zh) 2003-06-11
CN1285199C (zh) 2006-11-15
DE60017788D1 (de) 2005-03-03
JP4759709B2 (ja) 2011-08-31
CA2312540A1 (en) 2001-12-27
ATE369683T1 (de) 2007-08-15
EP1234417A2 (en) 2002-08-28
EP1234434B1 (en) 2005-01-26
ES2239630T3 (es) 2005-10-01
JP2003528486A (ja) 2003-09-24
CN100473072C (zh) 2009-03-25
WO2001039431A3 (en) 2001-12-13
ATE288166T1 (de) 2005-02-15
AU2131401A (en) 2001-06-04
WO2001039431A2 (en) 2001-05-31
CN1423885A (zh) 2003-06-11
AU2131501A (en) 2001-06-04
WO2001039457A3 (en) 2001-12-13
DE60017788T2 (de) 2006-01-05
WO2001039457A2 (en) 2001-05-31

Similar Documents

Publication Publication Date Title
US7136901B2 (en) Electronic mail server
US20070073839A1 (en) Electronic Mail Server
US7844716B2 (en) Instant messaging architecture and system for interoperability and presence management
US20110258272A1 (en) Facilitating transmission of an email of a well behaved sender by extracting email parameters and querying a database
US6427164B1 (en) Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown
US7499976B2 (en) Warning and avoidance of sending email messages to unintended recipients
US7502923B2 (en) Systems and methods for secured domain name system use based on pre-existing trust
WO2002031702A1 (en) Registering and using multilingual domain names
US20020188690A1 (en) System and method for checking and correcting electronic mail address
US7103635B2 (en) Really simple mail transport protocol
US8458264B1 (en) Email proxy server with first respondent binding
CA2392624C (en) Electronic mail server
US20100306316A1 (en) Method for provision of an address in a data network
JP2003521844A (ja) 単一のアドレスストリングを用いてさまざまな通信アプリケーションを横断して通信するためのシステム及び方法
CA2392619C (en) Network address server
KR20010104567A (ko) 중복 아이디 사용을 지원하는 전자메일 시스템 및 그를이용한 전자메일 서비스 방법
JP2004072248A (ja) メールサーバ装置
JP2000148636A (ja) アドレス統合方法、装置、及び記録媒体

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020620

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

AX Request for extension of the european patent

Free format text: AL;LT;LV;MK;RO;SI

17Q First examination report despatched

Effective date: 20060724

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIC1 Information provided on ipc code assigned before grant

Ipc: H04L 12/58 20060101AFI20070302BHEP

Ipc: H04L 29/12 20060101ALI20070302BHEP

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

REF Corresponds to:

Ref document number: 60035896

Country of ref document: DE

Date of ref document: 20070920

Kind code of ref document: P

REG Reference to a national code

Ref country code: SE

Ref legal event code: TRGR

RAP2 Party data changed (patent owner data changed or rights of a patent transferred)

Owner name: AFILIAS LIMITED

BECA Be: change of holder's address

Owner name: AFILIAS LTDOFFICE 100, 52 BROOMHILL ROAD, TALLAGHT

Effective date: 20070808

BECH Be: change of holder

Owner name: AFILIAS LTD

Effective date: 20070808

REG Reference to a national code

Ref country code: ES

Ref legal event code: PC2A

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: NL

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

NLV1 Nl: lapsed or annulled due to failure to fulfill the requirements of art. 29p and 29m of the patents act
REG Reference to a national code

Ref country code: CH

Ref legal event code: PL

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: LI

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: CH

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

ET Fr: translation filed
REG Reference to a national code

Ref country code: ES

Ref legal event code: FG2A

Ref document number: 2293931

Country of ref document: ES

Kind code of ref document: T3

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DK

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

Ref country code: GR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20071109

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: PT

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20080108

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MC

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20071130

26N No opposition filed

Effective date: 20080509

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CY

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20071127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: TR

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20070808

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 16

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 17

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 18

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IE

Payment date: 20191125

Year of fee payment: 20

Ref country code: DE

Payment date: 20191119

Year of fee payment: 20

Ref country code: SE

Payment date: 20191126

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: ES

Payment date: 20191202

Year of fee payment: 20

Ref country code: BE

Payment date: 20191125

Year of fee payment: 20

Ref country code: IT

Payment date: 20191120

Year of fee payment: 20

Ref country code: FR

Payment date: 20191128

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20191129

Year of fee payment: 20

REG Reference to a national code

Ref country code: DE

Ref legal event code: R071

Ref document number: 60035896

Country of ref document: DE

REG Reference to a national code

Ref country code: GB

Ref legal event code: PE20

Expiry date: 20201126

REG Reference to a national code

Ref country code: IE

Ref legal event code: MK9A

REG Reference to a national code

Ref country code: BE

Ref legal event code: MK

Effective date: 20201127

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20201127

Ref country code: GB

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20201126

REG Reference to a national code

Ref country code: ES

Ref legal event code: FD2A

Effective date: 20210309

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: ES

Free format text: LAPSE BECAUSE OF EXPIRATION OF PROTECTION

Effective date: 20201128