+

WO2001067268A1 - Procedes et dispositifs de production automatique d'une table de routage dans un serveur de messagerie - Google Patents

Procedes et dispositifs de production automatique d'une table de routage dans un serveur de messagerie Download PDF

Info

Publication number
WO2001067268A1
WO2001067268A1 PCT/US2001/007157 US0107157W WO0167268A1 WO 2001067268 A1 WO2001067268 A1 WO 2001067268A1 US 0107157 W US0107157 W US 0107157W WO 0167268 A1 WO0167268 A1 WO 0167268A1
Authority
WO
WIPO (PCT)
Prior art keywords
directory
server
computer
domain
recited
Prior art date
Application number
PCT/US2001/007157
Other languages
English (en)
Inventor
Jacques Belissent
Fred Batty
Timothy Misner
Daryl Huff
Anil Srivastava
Original Assignee
Sun Microsystems, 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
Priority claimed from US09/519,964 external-priority patent/US6865594B1/en
Application filed by Sun Microsystems, Inc. filed Critical Sun Microsystems, Inc.
Priority to EP01922281A priority Critical patent/EP1183615A4/fr
Priority to AU2001249099A priority patent/AU2001249099A1/en
Publication of WO2001067268A1 publication Critical patent/WO2001067268A1/fr

Links

Classifications

    • 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/4541—Directories for service discovery
    • 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
    • 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/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
    • 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/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
    • H04L61/4523—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using lightweight directory access protocol [LDAP]
    • 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/50—Address allocation
    • H04L61/5076—Update or notification mechanisms, e.g. DynDNS

Definitions

  • the present invention relates in general to client/server data communication systems and, more particularly, to a mail server included in an electronic mail system for use within a client/server data processing system. More particularly still, the present invention is directed towards a method and apparatus that automatically provides a routing table for a new or modified domain associated with a particular mail server as well as providing user specific profiles useful in the disposition of email.
  • Computer systems are well known in the arts and have become a business staple and are also found in many homes.
  • One feature available to the business world is that of using electronic mailing (e-mail) to send and receive messages and other information to and from one another in a business setting.
  • home computers such as desk tops or laptops, and other information devices, such as personal digital assistants (PDAs), allow telecommuting such that a user can connect to the user's work server and down load and upload messages.
  • PDAs personal digital assistants
  • the e-mail system allows clients of a network system, which is maintained by a server system, to send messages or data from one user to another.
  • the engine is typically located on the server and is merely accessed by a client in order to send messages or retrieve messages to or from another user or client on the server system.
  • the client system typically allows the user to perform such operations as composing, updating, and sending messages while the server in such a system provides, in part, a server based message repository as well as providing message transmission and reception functions for the user at the client level.
  • a mail server 104 uses what is referred to as a flat name space arrangement to store identification indicia (such as a domain name, mailbox number, etc.) that identifies each of the users 102a - 102g.
  • identification indicia such as a domain name, mailbox number, etc.
  • a flat name space requires that each of the users 102a - 102g be identified by a unique name. In this way, no two users can have the same identification indicia since the server 104 would not be able to correctly identify which user a particular email message is destined.
  • the flat name space arrangement may be suitable for small email systems, such as those typical of an intranet, it is unsuitable for larger, distributed systems having hundreds, thousands, or even hundreds of thousands of users.
  • the system 200 typically includes a central mail server 202 resident in a computer system 204 that can take the form of a mainframe system as well as a distributed type computing system.
  • the central mail server 202 is coupled to an interface, such as a firewall 206, that mediates the flow of information between the mail server 202 and its n client domains represented as domain,, domain 2 , and domain-,.
  • a firewall 206 that mediates the flow of information between the mail server 202 and its n client domains represented as domain,, domain 2 , and domain-,.
  • the main server 202 logically segments portions of its computing resources into what are referred to as virtual mail servers each being associated with one of the n domains serviced by the mail server 202.
  • each of the n domains appears to have their own mail server in the form of the associated virtual mail server.
  • the domainl is associated with a virtual mail server NMS1, a domain2 with a virtual mail server VMS2, and so on.
  • Conventional approaches to implementing this type arrangement utilize a hierarchically structured domain name to identify the various domains serviced by the mail server 202.
  • a domain name locates an organization or other entity.
  • the domain name 'www.totalbaseball.com' locates an Internet address for "totalbaseball.com” at Internet point (IP) 199.0.0.2 and a particular host server named "www".
  • the "com” part of the domain name reflects the purpose of the organization or entity (in this example, "commercial") and is called the top level domain name.
  • the "totalbaseball” part of the domain name defines the organization or entity and together with the top-level is called the second level domain name.
  • the second-level domain name maps to and can be thought of as the "readable” version of the Internet address.
  • the domain name is that part of the uniform resource locator or URL that tells a domain name server using the D ⁇ S (domain name system) whether and where to forward a request for a Web page.
  • the domain name is mapped to an IP address that represents a physical point on the Internet.
  • the mail server 202 must still be able to identify the proper destination of a received email and define a route from the server 202 to the identified end user. This identification is usually carried out by a directory services component 208 configured to provide directory services that typically take the form of an LDAP type directory.
  • LDAP Lightweight Directory Access Protocol
  • DAP Directory Access Protocol
  • DNS Domain Name System
  • An LDAP directory is organized in a simple "tree" hierarchy consisting of the following levels:
  • an LDAP directory can be distributed among many servers such that an LDAP server is called a Directory System Agent (DSA).
  • DSA Directory System Agent
  • the directory 208 uses a routing table 210, also referred to as a DNS table, to determine that appropriate path, or channel, that is to be used to deliver the particular email message.
  • a routing table 210 also referred to as a DNS table
  • each mail server maintains a DNS table for each virtual mail server that maps incoming email to appropriate receiving mailbox.
  • the mail server 202 builds a routing table based upon the corresponding DNS table that directs the email to the appropriate mailbox.
  • the mail server 202 has to create a new address rewrite rule (that are used to rewrite addresses into their proper or desired form as well as to determine to which channels a message should be enqueued) and configure the corresponding routing table that tells the mail server how to route email.
  • a new address rewrite rule that are used to rewrite addresses into their proper or desired form as well as to determine to which channels a message should be enqueued
  • configure the corresponding routing table that tells the mail server how to route email.
  • an email is sent to a new user before the routing table associated with the client's virtual mail server has been changed. In theses cases, the email cannot be delivered and an error message is returned stating that the addressee is unknown even though the intended receiver has in fact been added to the clients user list.
  • an internet type email server capable of automatically updating any routing table based upon any changes occurring in the corresponding domain.
  • a method of identifying, in a directory server, a new mail domain associated with an incoming email message that is received by a messaging server is disclosed.
  • a new domain name corresponding to the new domain is received by the messaging server, a corresponding entry is created in a directory in the directory server for every component included in the new domain name that does not already exist in the directory.
  • DNS domain name service
  • an electronic messaging system in another embodiment, includes a main host computer for transferring an incoming email message between a sending subscriber and a receiving subscriber that is identified by a receiving subscriber user name and corresponding receiving subscriber domain name.
  • the system also includes a messaging server coupled to the main host computer for receiving the incoming email message from the sending subscriber and forwarding the incoming email message to the receiving subscriber.
  • a directory server coupled to the main host computer that identifies for the messaging server a location of the receiving subscriber based upon the receiving subscriber user name and the receiving subscriber domain name. In those cases where the receiving subscriber domain is a new domain, the directory server creates a corresponding entry in a directory in the directory server for every component included in the new domain name that does not already exist in the directory. The directory server then automatically updates a corresponding domain name service (DNS) record that is, in turn, used by the directory server to identify the new domain.
  • DNS domain name service
  • computer-readable medium containing programming instructions for identifying, in a directory server, a new mail domain associated with an incoming email message that is disclosed.
  • the computer-readable medium includes computer program code devices configured to cause a computer to receive a new domain name corresponding to the new domain by the messaging server and create a corresponding entry in a directory in the directory server for every component included in the new domain name that does not already exist in the directory.
  • a corresponding domain name service (DNS) record in a domain name server associated with the directory server is automatically updated based upon the entry which is used to identify the new mail domain by the directory server.
  • DNS domain name service
  • Fig. 1 illustrates a conventional e-mail system suitable for a small scale network.
  • Fig. 2 illustrates a conventional e-mail system suitable for a large scale network such as the Internet.
  • Fig. 3 shows an Internet email system in accordance with an embodiment of the invention
  • Fig. 4 shows an exemplary message store in accordance with an embodiment of the invention.
  • Fig. 5 shows a flowchart that details a process that describes a message data flow in accordance with an embodiment of the invention.
  • Fig. 6 shows a flowchart detailing a process whereby a new mail domain is defined in accordance with an embodiment of the invention.
  • Fig. 7 illustrates a flowchart detailing a process for synchronizing the directory cache for a particular domain in accordance with an embodiment of the invention.
  • Fig. 8 illustrates a typical, general-purpose computer system suitable for implementing the present invention
  • the invention describes an Internet standards-based messaging system having a mail server capable of automatically updating routing tables based upon directory entries, that in some embodiments includes DNS table entries as well as MX records, to represent each domain served by all or part of the messaging server community.
  • domain entries are used to build and maintain routing tables that tell messaging servers how messages should be transferred from server to server until they reach their final delivery point.
  • routing tables are generated from an LDAP directory structure.
  • routing tables is not limited to the LDAP directory structure since the invention can be applied equally to the automatic generation of routing tables from DNS domain tables.
  • the inventive messaging server is capable of using the MX (mail exchange) records within the DNS domain tables to automatically generate the corresponding routing tables.
  • the inventive messaging server also provides for specific user profiles suitable for uniquely specifying the disposition of any email placed in the corresponding user's mailbox.
  • an Internet email system 300 in accordance with an embodiment of the invention includes an Internet mail server 301 coupled to a user mailbox 303.
  • the mail server 301 is a general-purpose, " store-and-forward" system for distributing computer-based mail.
  • a transfer unit 302 included in the mail server 301 is responsible for directing messages to the appropriate network transport and ensuring reliable delivery over that transport.
  • the mail server 301 includes a message store unit 304 coupled to the transfer unit 302 that is used to store messages for later transmission to the user mailbox 303.
  • the message store 304 in the mail server 301 is a dedicated data store for the delivery, retrieval, and manipulation of Internet mail messages.
  • the message store works with the IMAP4 and POP3 to provide flexible and easy access to messaging. It saves any message that conforms to RFC 822 specifications, and recognizes the Multipurpose Internet Mail Extensions (MIME) content format.
  • the message store 304 is organized as a set of folders and user mailboxes.
  • the mailbox 401 is a container for messages where each user has an inbox 402 where new mail arrives, and can have one or more folders 404 where mail can be stored.
  • Folders 404 may contain other folders or mailboxes and may be arranged in a hierarchical tree.
  • Mailboxes owned by an individual user are private folders 406.
  • a common user or group can share the ownership of a folder or mailbox as a shared folder 408.
  • a shared folder is similar to an email group, but instead of messages going into each member of the email group's inbox, messages addressed to the shared folder 408 go into a private folder associated with each user. It should be noted that in a preferred embodiment, the message store 304 maintains only one copy of each message.
  • the message store 304 receives a message addressed to multiple users or a group (based upon an associated distribution list), it adds a reference to the message in each user's inbox rather than having a copy of the message in each user's inbox, thereby saving disk space.
  • the individual message's status (new, unread, replied to, deleted, and the like) is maintained per mailbox.
  • access to the message store 304 is multithreaded thereby allowing a single process to manage a large number of connections since each connection is handled by a thread.
  • multithreaded access maximizes both performance and scalability by minimizing the system resources required for the management of each connection.
  • the delivery and routing of messages by the transfer unit 302 is based on a routing table 310 that in turn is derived from the user and group (distribution list) entries stored in a directory service unit 312.
  • the directory service unit 312 is the central repository for meta- information: user profiles, distribution lists, and other system resources based upon, in some embodiments, a dedicated Lightweight Directory Access Protocol (LDAP) directory service.
  • LDAP Lightweight Directory Access Protocol
  • This directory supports the storage of information according to a directory information tree (DIT) which is a hierarchical structure that resembles a tree with one major branch at the top and many branches and sub-branches below.
  • DIT directory information tree
  • the arrangement of the tree is flexible, allowing administrators to decided how to best deploy the service for their organization. For some, it may be best to arrange the tree according the actual business organizational structure or geographic structure. For others, however, a one-to-one mapping to DNS layers may be best.
  • the DIT also provides the flexibility to support a wide range of administration scenarios, and can be administered in either a centralized or distributed manner.
  • Centralized administration can be implemented where one authority manages the entire DIT. This type of administration is usually used in scenarios where the entire DIT resides on one mail server.
  • the transfer unit 302 In order to properly route a message, the transfer unit 302 must access the directory information associated with each message that it processes. However, in a preferred embodiment, rather than querying the directory service 312 directly each time it processes a message, the transfer unit 302 caches the directory information in a directory cache 314. When the transfer unit processes a particular message, it accesses the appropriate directory information in the cache 314. When required, the transfer unit 302 uses the directory information in the cache 314 to update the routing table 312.
  • the transfer unit 302 can be configured to adhere to various mail delivery options which specify one or more delivery options for inbound email to a designated recipient. While inbound messages can be delivered into multiple message stores, message access servers (MAS) can read messages from only a designated one of them.
  • the transfer unit 302 uses these attributes to determine the targets of message delivery for all messages submitted to a particular distribution list. Such attributes can include, but are not limited to: “autoreply”, “program” where mail is delivered to a program, "forward” where mail is forwarded to another mailbox(es), "file” where the incoming message file is appended to another file, and “shared” where mail is delivered to a shared mailbox (this is typically used to set up a shared mailbox for a distribution list).
  • protocols are generally a high-level (not necessarily network specific) language spoken between two mailers.
  • Transports are the low-level, network specific details used to implement a protocol on a given network.
  • email messages can come in to the transfer unit 302 by any one of a variety of transports and protocols—submitted directly by a local user, via TCP/IP as an SMTP message from an Internet system, by using a dial-up modem using the PhoneNet protocol, DECnet as a MAIL-11 message, DECnet as an SMTP message, UUCP, an X.400 transport, SNA, and so on.
  • the transfer unit 302 then routes the message out using a transport and protocol appropriate for the message's destination address.
  • the transfer unit 302 uses what are referred to as channels to implement specific combinations of transports and protocols. Each different transport and protocol combination has an associated transfer unit channel.
  • the transfer unit 302 postmaster initially configures the transfer unit 302 telling it what sorts of transports and protocols are in use at his site, and what sorts of destination addresses should be routed through which sorts of channels. For instance, at sites with an Internet connection, Internet addresses are normally routed through an SMTP over TCP/IP channel; but at sites with only a UUCP connection, Internet addresses would instead be routed through a UUCP channel.
  • the transfer unit 302 is so configured using configuration data stored in a configuration table (not shown), the transfer unit 302 handles message routing and delivery automatically. In this way, ordinary users need never be aware of this underlying transport and routing; that is, they simply address and send their messages and the transfer unit 302 automatically routes and delivers them appropriately.
  • the transfer unit 302 stores messages as text files.
  • Messages with multiple parts are represented as a series of text sections separated by special unique delimiter strings.
  • the first few files in each email message are referred to as the message envelope that contains transport information.
  • the message envelope is terminated by a line containing a boundary marker, or by a line containing two CTRL/A characters.
  • the transfer unit 302 uses the contents of the envelope to make routing • decisions. It does not use the content of the message.
  • the content of the envelope is primarily defined by RFC 821. It includes the originator address, the recipient(s) address(es), and envelope ID.
  • the header lines of the message follow the envelope whose format is mandated by RFC 822.
  • message header lines there may be any number of message header lines; the message header formed by this collection of header lines is terminated by a single blank line after which follows the message body.
  • An Internet mail message starts with one or more headers. Each header is composed of a field name followed by a colon then a value which can be generated by, for example, the composer of a message or the mail client.
  • a transfer unit can also add headers to a message. Each transfer unit that accepts a message adds a received header to that message. The last transfer unit to accept the message and to actually deliver the message to the message store adds a return-path header. The received and return-path headers provides information that enables you to trace the routing path taken by the message if a problem occurs.
  • SMTP Simple Mail Transport Protocol
  • the transfer unit 302 delivers the message to the message store 304. If, however, the message is addressed to another domain, the transfer unit 302 relays the message to another transport agent on the Internet or Intranet.
  • messages to the local domain are stored in the message store 304 depending on how the system is configured. Once messages are delivered to the appropriate mailbox, they can be retrieved, searched for, and manipulated by IMAP4 or POP3-based mail clients.
  • the transfer unit 302 uses the directory 312 that, in a preferred embodiment, is configured as an LDAP type directory, to retrieve local user and group address information. When the transfer unit 302 receives a message, it uses the directory information to determine where the message should be delivered.
  • the message store uses the directory services to authenticate users logging into their mailboxes.
  • the message store 304 also obtains information about user message quota limits and message store type (IMAP or POP). Outgoing client messages go to the SMTP channel in the LDAP.
  • the transfer unit 302 sends the message to an Internet transfer or, if the address is local, to the message store 304.
  • the process 500 starts at 502 by the user submitting a message to be delivered to another user on the network via the SMTP protocol.
  • the transfer unit reads the address and the routing information from the directory service server using the address domain information from the incoming message as a key.
  • the transfer unit determines delivery information from the address and domain rewriting rules by consulting the directory cache at 506.
  • the transfer unit sends the message to the receiving end where, if necessary, a receiving transfer unit reads the address and looks up the host and mailbox information in the directory services server for the receiving client. If the message address is within the server's domain, the receiving transfer unit delivers the message to the message store. If, however, the message is addressed to another domain, the receiving transfer unit relays the message to another transport agent on the Internet or Intranet. Finally at 510, the user can now retrieve the message or delete it.
  • a new mail domain must be defined in the mail server based upon a process 600 detailed by the flowchart shown in Fig. 6.
  • the process 600 begins at 602 by the mail server receiving the new domain name.
  • a corresponding entry is made in the directory information tree (DIT) for every component in the new domain name that does not already exist.
  • DIT directory information tree
  • a corresponding DNS record is either updated or created in order to identify the host server as the mail server for the new domain.
  • the directory information stored in the directory service is continuously updated.
  • the directory information in the directory cache must be updated periodically with the current directory information in the directory service in a procedure referred to as synchronization.
  • there are at least two types of synchronization namely full synchronization and incremental synchronization.
  • Fig. 7 illustrating a flowchart detailing a process 700 for synchronizing the directory cache for a particular domain in accordance with an embodiment of the invention.
  • the process 700 begins at 702 by a determination if any changes have been made to the directory that affects the particular domain. If it is determined that there have been no affective changes, then processing stops. Otherwise, a new routing table is built at 704 using information in the domain entries in the changed domain. Finally, at 706, an alias table is built for users in the domain that is based upon user entries in the changed domain.
  • Fig. 8 illustrates a typical, general-purpose computer system 800 suitable for implementing the present invention.
  • the computer system 800 includes any number of processors 802 (also referred to as central processing units, or CPUs) that are coupled to memory devices including primary storage devices 804 (typically a read only memory, or ROM) and primary storage devices 806 (typically a random access memory, or RAM).
  • processors 802 also referred to as central processing units, or CPUs
  • memory devices including primary storage devices 804 (typically a read only memory, or ROM) and primary storage devices 806 (typically a random access memory, or RAM).
  • primary storage devices 804 typically a read only memory, or ROM
  • primary storage devices 806 typically a random access memory, or RAM
  • Computer system 800 or, more specifically, CPUs 802, may be arranged to support a virtual machine, as will be appreciated by those skilled in the art.
  • ROM acts to transfer data and instructions uni-directionally to the CPUs 802, while RAM is used typically to transfer data and instructions in a bi-directional manner.
  • CPUs 802 may generally include any number of processors.
  • Both primary storage devices 804, 806 may include any suitable computer-readable media.
  • the mass memory device 808 is a computer- readable medium that may be used to store programs including computer code, data, and the like.
  • mass memory device 808 is a storage medium such as a hard disk or a tape which generally slower than primary storage devices 804, 806.
  • Mass memory storage device 808 may take the form of a magnetic or paper tape reader or some other well-known device. It will be appreciated that the information retained within the mass memory device 808, may, in appropriate cases, be incorporated in standard fashion as part of RAM 806 as virtual memory.
  • a specific primary storage device 804 such as a CD-ROM may also pass data uni-directionally to the CPUs 802.
  • CPUs 802 are also coupled to one or more input/output devices 810 that may include, but are not limited to, devices such as video monitors, track balls, mice, keyboards, microphones, touch-sensitive displays, transducer card readers, magnetic or paper tape readers, tablets, styluses, voice or handwriting recognizers, or other well- known input devices such as, of course, other computers.
  • CPUs 802 optionally may be coupled to a computer or telecommunications network, e.g., an Internet network or an intranet network, using a network connection as shown generally at 812. With such a network connection, it is contemplated that the CPUs 802 might receive information from the network, or might output information to the network in the course of performing the above-described method steps.
  • Such information which is often represented as a sequence of instructions to be executed using CPUs 802, may be received from and outputted to the network, for example, in the form of a computer data signal embodied in a carrier wave.
  • the above-described devices and materials will be familiar to those of skill in the computer hardware and software arts.
  • the methods defining new routing tables in a messaging server in accordance with the present invention are particularly suitable for implementation with respect to a JavaTM based environment, the methods may generally be applied in any suitable object-based environment. In particular, the methods are suitable for use in platform-independent object-based environments. It should be appreciated that the methods may also be implemented in some distributed object-oriented systems. While the present invention has been described as being used with a computer system that has an associated virtual machine, it should be appreciated that the present invention may generally be implemented on any suitable object-oriented computer system. Specifically, the methods of defining a new or updated routing table in accordance with the present invention may generally be implemented in any multi- threaded, object-oriented system without departing from the spirit or the scope of the present invention. Therefore, the present examples are to be considered as illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L'invention concerne des procédés, dispositifs, et support lisible par ordinateur, lesquels permettent de définir automatiquement un domaine de courrier dans un serveur de répertoires (312) associé à un serveur de messagerie (301). Lors de la réception par le serveur de messagerie (301) d'un message possédant un nouveau nom de domaine, le serveur de répertoires (312) crée une entrée correspondante, dans un répertoire, pour chaque composante du nouveau nom de domaine qui n'existe pas encore dans le répertoire. Un enregistrement de service du nom de domaine correspondant est automatiquement mis à jour dans un serveur de noms de domaines associé au serveur de répertoires, en fonction de l'entrée utilisée pour identifier le nouveau domaine.
PCT/US2001/007157 2000-03-07 2001-03-06 Procedes et dispositifs de production automatique d'une table de routage dans un serveur de messagerie WO2001067268A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP01922281A EP1183615A4 (fr) 2000-03-07 2001-03-06 Procedes et dispositifs de production automatique d'une table de routage dans un serveur de messagerie
AU2001249099A AU2001249099A1 (en) 2000-03-07 2001-03-06 Methods and apparatus for automatically generating a routing table in a messaging server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US09/519,964 2000-03-07
US09/519,964 US6865594B1 (en) 1999-07-20 2000-03-07 Methods and apparatus for automatically generating a routing table in a messaging server

Publications (1)

Publication Number Publication Date
WO2001067268A1 true WO2001067268A1 (fr) 2001-09-13

Family

ID=24070607

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2001/007157 WO2001067268A1 (fr) 2000-03-07 2001-03-06 Procedes et dispositifs de production automatique d'une table de routage dans un serveur de messagerie

Country Status (3)

Country Link
EP (1) EP1183615A4 (fr)
AU (1) AU2001249099A1 (fr)
WO (1) WO2001067268A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004006593A1 (fr) * 2002-07-09 2004-01-15 Siemens Aktiengesellschaft Procede et systeme de transmission de messages mms
EP1533960A1 (fr) * 2003-11-21 2005-05-25 Lucent Technologies Inc. Fournir à l'émetteur d'un message une identification du prestataire de service associé au destinataire du message
CN1317902C (zh) * 2004-03-05 2007-05-23 乐金电子(中国)研究开发中心有限公司 Mms信息传送方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5913210A (en) * 1998-03-27 1999-06-15 Call; Charles G. Methods and apparatus for disseminating product information via the internet
US5920697A (en) * 1996-07-11 1999-07-06 Microsoft Corporation Method of automatic updating and use of routing information by programmable and manual routing information configuration based on least lost routing
US6012088A (en) * 1996-12-10 2000-01-04 International Business Machines Corporation Automatic configuration for internet access device
US6131095A (en) * 1996-12-11 2000-10-10 Hewlett-Packard Company Method of accessing a target entity over a communications network
US6154738A (en) * 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US6199062B1 (en) * 1998-11-19 2001-03-06 International Business Machines Corporation Reverse string indexing in a relational database for wildcard searching

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5920697A (en) * 1996-07-11 1999-07-06 Microsoft Corporation Method of automatic updating and use of routing information by programmable and manual routing information configuration based on least lost routing
US6012088A (en) * 1996-12-10 2000-01-04 International Business Machines Corporation Automatic configuration for internet access device
US6131095A (en) * 1996-12-11 2000-10-10 Hewlett-Packard Company Method of accessing a target entity over a communications network
US5913210A (en) * 1998-03-27 1999-06-15 Call; Charles G. Methods and apparatus for disseminating product information via the internet
US6154738A (en) * 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US6199062B1 (en) * 1998-11-19 2001-03-06 International Business Machines Corporation Reverse string indexing in a relational database for wildcard searching

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP1183615A4 *

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2004006593A1 (fr) * 2002-07-09 2004-01-15 Siemens Aktiengesellschaft Procede et systeme de transmission de messages mms
US8850061B2 (en) 2002-07-09 2014-09-30 Siemens Aktiengesellschaft MMS message transfer method and system
EP1533960A1 (fr) * 2003-11-21 2005-05-25 Lucent Technologies Inc. Fournir à l'émetteur d'un message une identification du prestataire de service associé au destinataire du message
US7272398B2 (en) 2003-11-21 2007-09-18 Lucent Technologies Inc. Providing to sender of message an identifier of service provider associated with recipient of the message
CN1317902C (zh) * 2004-03-05 2007-05-23 乐金电子(中国)研究开发中心有限公司 Mms信息传送方法

Also Published As

Publication number Publication date
EP1183615A4 (fr) 2005-09-07
AU2001249099A1 (en) 2001-09-17
EP1183615A1 (fr) 2002-03-06

Similar Documents

Publication Publication Date Title
US6865594B1 (en) Methods and apparatus for automatically generating a routing table in a messaging server
US6374292B1 (en) Access control system for an ISP hosted shared email server
US7058683B1 (en) Methods and apparatus for providing a virtual host in electronic messaging servers
US7155725B1 (en) Apparatus and method for coordinating multiple e-mail accounts
US6427164B1 (en) Systems and methods for automatically forwarding electronic mail when the recipient is otherwise unknown
US6557036B1 (en) Methods and apparatus for site wide monitoring of electronic mail systems
US6993561B2 (en) Method and apparatus for maintaining a unified view of multiple mailboxes
US6266692B1 (en) Method for blocking all unwanted e-mail (SPAM) using a header-based password
US6732157B1 (en) Comprehensive anti-spam system, method, and computer program product for filtering unwanted e-mail messages
US20070180033A1 (en) Virtual mail storage for mail distributed using corporate distribution lists
US20060020667A1 (en) Electronic mail system and method for multi-geographical domains
US8775542B2 (en) Device and method for user-based processing of electronic message comprising file attachments
US7457841B2 (en) Method and system for excluding recipients in an electronic communication system
US20040093382A1 (en) Method of transmitting an electronic mail message
EP1298873A2 (fr) Méthode et dispositif pour transférer de messages entre les domaines d'un réseau
US20060143278A1 (en) Method and system for distributing e-mail messages to recipients
US8635286B2 (en) Mailing list expansion trace
US20060143277A1 (en) Method and system for distributing e-mail messages to recipients
WO2001067268A1 (fr) Procedes et dispositifs de production automatique d'une table de routage dans un serveur de messagerie
US20090198782A1 (en) Apparatus, system, and method for retrieving email attachments
JPH11191083A (ja) 電子メールの配達方法およびメールサーバー
WO2001067259A1 (fr) Procedes et dispositif pour former un hote virtuel dans des serveurs de messagerie electronique
KR100270313B1 (ko) 전자 우편 주소 자동 추출 방법
US7743104B2 (en) Message delivery to multiple forests with no unified directory
WO2001067305A1 (fr) Procedes et appareil permettant de deleguer des fonctions administratives a des domaines servis par des fournisseurs de messagerie

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A1

Designated state(s): AU CA CN DE GB JP

AL Designated countries for regional patents

Kind code of ref document: A1

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

WWE Wipo information: entry into national phase

Ref document number: 2001922281

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application
WWP Wipo information: published in national office

Ref document number: 2001922281

Country of ref document: EP

REG Reference to national code

Ref country code: DE

Ref legal event code: 8642

NENP Non-entry into the national phase

Ref country code: JP

点击 这是indexloc提供的php浏览器服务，不要输入任何密码和下载