Mail receiving and sending method and device of enterprise multi-mail system and electronic equipment

Abstract

The embodiment of the invention discloses a mail receiving and sending method and device for an enterprise multi-mail system and electronic equipment, and the method comprises the steps: receiving a first mail sending request from a first mail server, enabling a first mail sending box indicated by the first mail sending request to use the first mail server, and enabling a first inbox to use a second mail server; a first mail system to which the first mail server belongs and a second mail system to which the second mail server belongs are different mail systems deployed by the same enterprise; reading preset configuration information, and sending the first mail content to a transfer mailbox associated with the first inbox through a transfer server associated with the second mail server, so that the first inbox receives the first mail content; the preset configuration information comprises an association relationship between the first inbox and the transit mailbox, and an association relationship between the second mail server and the transit server. According to the embodiment of the invention, a plurality of mail systems can be simultaneously used in the same enterprise to receive and send mails.

Description

Technical Field

[0001] The present application relates to the technical field of mail sending and receiving, and in particular to a mail sending and receiving method, device and electronic equipment for an enterprise multi-mail system. Background Art

[0002] In daily business operations, companies often provide multiple email systems for internal employees to use, allowing them to send and receive emails with other internal and external personnel. Typically, only one email system is allowed within a single email domain (email suffix). Trying to use two systems simultaneously may result in system conflicts.

[0003] However, since different mail systems may have different functions, in some enterprises, some users may need to use a mail system with more functions to send and receive mails, while other users may need to use a mail system with fewer functions to send and receive mails.

[0004] Therefore, there is an urgent need for a method in which a plurality of mail systems can be used simultaneously to send and receive mails within the same enterprise. Summary of the Invention

[0005] The embodiments of the present application provide a method, device, and electronic device for sending and receiving emails in an enterprise's multiple email systems, so as to enable the simultaneous use of multiple email systems for sending and receiving emails within the same enterprise.

[0006] In a first aspect, an embodiment of the present application provides a method for sending and receiving emails in an enterprise multi-mail system, which is applied to an email management platform. The method includes:

[0007] receiving a first email sending request from a first email server; wherein the first email sending request indicates a first outbox, a first inbox, and first email content; the first outbox uses the first email server, and the first inbox uses the second email server; a first email system to which the first email server belongs and a second email system to which the second email server belongs are different email systems deployed by the same enterprise;

[0008] Read the preset configuration information, and send the first email content to the transit mailbox associated with the first inbox through the transit server associated with the second email server, so that the first inbox receives the first email content; wherein the preset configuration information includes the association relationship between the first inbox and the transit mailbox, and the association relationship between the second email server and the transit server.

[0009] In an embodiment of the present application, the first mail server belongs to the first mail system, the second mail server belongs to the second mail system, and the first mail system and the second mail system are different mail systems deployed by the same enterprise. After receiving the first mail sending request from the first mail server, the mail management platform can determine the first outbox, the first inbox and the first mail content through analysis, and determine that the first outbox uses the first mail server and the first inbox uses the second mail server. The mail management platform reads the preset configuration information. Since the preset configuration information includes the association between the first inbox and the transit mailbox, as well as the association between the second mail server and the transit server, the mail management platform can, based on the preset configuration information, send the first mail content to the transit mailbox associated with the first inbox through the transit server associated with the second mail server to enable the first inbox to receive the first mail content. Such a design allows the two mail systems to be used within the mail domain of the same enterprise, realizes the integration of the two mail systems within one mail domain, and can meet the needs of users sending and receiving mails in multiple scenarios.

[0010] In an optional embodiment, the method further includes:

[0011] In the configuration document of the first mail server, modify the first mail server to a transit server and add a transit mailbox;

[0012] In the DNS server, update the MX mail exchange record of the transit mailbox to point to the second mail server;

[0013] In the management platform of the second mail server, add a transit mailbox and establish an association between the first inbox and the transit mailbox;

[0014] Preset configuration information is generated based on the association relationship between the first inbox and the transit mailbox, and the association relationship between the second mail server and the transit server.

[0015] In the above embodiment, during the configuration information generation process, the addition of a transit mailbox and the updating of the MX mail exchange record determine the establishment of an association between the first inbox and the transit mailbox, and between the second mail server and the transit server. By combining the characteristics of the MX mail exchange record, preset configuration information can be generated. Application of this preset configuration information allows accurate routing of email content to the second mail server.

[0016] In an optional embodiment, the method further includes:

[0017] receiving a second mail sending request from a second mail server; wherein the second mail sending request indicates a second inbox, a second outbox, and second mail content; the second outbox uses the second mail server, and the second inbox uses the first mail server;

[0018] The second email content is sent to the second inbox based on a pre-created sending rule; wherein the sending rule is configured in the sending connector of the second email system; the sending rule indicates that emails sent by the second email server are allowed to be sent to other email servers except the second email server.

[0019] In the above embodiment, after receiving a first email sending request from a second email server, the email management platform can determine the second outbox, second inbox, and the second email content through analysis, and determine that the second outbox uses the second email server and the second inbox uses the first email server. The email management platform obtains a pre-created sending rule. Because this sending rule indicates that emails sent using the second email server can be sent to email servers other than the second mail server, the email management platform can send the second email content to the second inbox based on this sending rule. This design enables users within the enterprise using the second mail server to send emails to users using the first mail server.

[0020] In an optional embodiment, the method further includes:

[0021] receiving a third mail sending request from a third mail server; wherein the third mail server is a public mailbox server; the third mail sending request indicates a third inbox, a third outbox, and third mail content; the third outbox uses the public mailbox server;

[0022] Determining that the third inbox uses a target mail server; wherein the target mail server is the first mail server or the second mail server;

[0023] The third email content is sent to the target email server, so that the target email server sends the third email content to the third inbox.

[0024] In the above embodiment, after receiving a third email sending request from a third email server, the email management platform can determine the third outbox, third inbox, and third email content through analysis, and determine that the third email server used by the third outbox is a public mailbox server, while the second inbox uses the first mail server. The email management platform determines whether the email server used by the third inbox is the first mail server or the second mail server, and then sends the third email content to the target mail server, which can then send the third email content to the third inbox. This design enables users outside the enterprise using the public mailbox server to send emails to users using the second mail server and users using the first mail server.

[0025] In an optional embodiment, the method further includes:

[0026] Obtaining a fourth mail sending request from a target server; wherein the target mail server is the first mail server or the second mail server; the fourth mail sending request indicates a fourth inbox, a fourth mail box, and fourth mail content;

[0027] Determining that the fourth mail server used by the fourth inbox is a public mailbox server;

[0028] The fourth email content is sent to the fourth email server through the target server, so that the fourth email server sends the fourth email content to the fourth inbox.

[0029] In the above embodiment, after the email management platform detects a fourth email sending request from a fourth email server, it can determine the fourth outbox, fourth inbox, and fourth email content through analysis, and determine that the fourth email server used by the fourth outbox is a public mailbox server. In other words, this is a scenario where an internal enterprise email is sent to an external enterprise. In this case, the email management platform can send the first email content to the fourth email server via the first or second mail server, and the fourth email content can be sent to the fourth inbox by the fourth mail server. This design enables users using the second mail server and users using the first mail server to send emails to users outside the enterprise using a public mailbox server.

[0030] In an optional embodiment, the method further includes:

[0031] Determining a first mailbox set using a first mail system and a second mailbox set using a second mail system;

[0032] The first user information of the first mailbox set and the second user information of the second mailbox set are synchronized, and the first password information of the first mailbox set and the second password information of the second mailbox set are synchronized.

[0033] In the above embodiment, by synchronizing user information and password information, the user's username and password can be kept consistent when the user switches from using the first mail system to the second mail system, or vice versa. In this way, within the same enterprise mail domain, the user can switch between the two mail systems.

[0034] In an optional embodiment, the first mail system is a Domino mail system, and the second mail system is an Exchange mail system;

[0035] Synchronizing first user information of a first mailbox set and second user information of a second mailbox set includes:

[0036] The AD domain control server in the second mail system is called, and the first user information and the second user information are synchronized through the LDAP service in the AD domain control server.

[0037] In the above embodiment, in the scenario where the first mail system is a Domino mail system and the second mail system is an Exchange mail system, during the synchronization of user information, the characteristics of the LDAP service in the AD domain control server of the Exchange mail system are utilized to achieve synchronization of user information.

[0038] In an optional embodiment, the first mail system is a Domino mail system, and the second mail system is an Exchange mail system;

[0039] Synchronizing first password information of a first mailbox set and second password information of a second mailbox set includes:

[0040] The domain name certificate of the second mail system is loaded into the first mail system through the key ring in the first mail system, so that the java agent established by the first mail system initializes the second password information stored in the second mail system to synchronize the first password information and the second password information.

[0041] In the above embodiment, in the scenario where the first mail system is a Domino mail system and the second mail system is an Exchange mail system, during the synchronization of password information, the key ring feature of the Domino mail system is utilized to achieve synchronization of password information.

[0042] In a second aspect, an embodiment of the present application provides an email sending and receiving device for an enterprise multi-mail system, which is applied to an email management platform, including:

[0043] The data transceiver unit is configured to: receive a first email sending request from a first email server; wherein the first email sending request indicates a first outbox, a first inbox, and first email content; the first outbox uses the first email server, and the first inbox uses the second email server; a first email system to which the first email server belongs and a second email system to which the second email server belongs are different email systems deployed by the same enterprise;

[0044] The mail processing unit is used to: read preset configuration information and send the first mail content to the transit mailbox associated with the first inbox through the transit server associated with the second mail server, so that the first inbox receives the first mail content; wherein the preset configuration information includes the association relationship between the first inbox and the transit mailbox, and the association relationship between the second mail server and the transit server.

[0045] In a third aspect, an embodiment of the present application provides an electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any of the above methods when executing the computer program.

[0046] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium having computer program instructions stored thereon, which implement the steps of any of the above methods when executed by a processor.

[0047] In a fifth aspect, an embodiment of the present application provides a computer program product, including a computer program, which implements the steps of any of the above methods when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0048] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. Obviously, the drawings introduced below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0049] Figure 1 A schematic diagram of an application scenario of a method for sending and receiving emails in an enterprise multi-mail system provided in one embodiment of the present application;

[0050] Figure 2 A flowchart of a method for sending and receiving emails in an enterprise multi-mail system provided in one embodiment of the present application;

[0051] Figure 3 A schematic diagram of an interface for generating preset configuration information provided in an embodiment of the present application;

[0052] Figure 4 A flowchart of another method for sending and receiving emails in an enterprise multi-mailbox system provided in one embodiment of the present application;

[0053] Figure 5 A schematic diagram of an interface for sending rules provided in one embodiment of the present application;

[0054] Figure 6 A flowchart of another method for sending and receiving emails in an enterprise multi-mailbox system provided in one embodiment of the present application;

[0055] Figure 7 A flowchart of another method for sending and receiving emails in an enterprise multi-mailbox system provided in one embodiment of the present application;

[0056] Figure 8 A schematic diagram of the structure of a mail sending and receiving device of an enterprise multi-mail system provided in one embodiment of the present application;

[0057] Figure 9 A schematic structural diagram of an electronic device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0058] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0059] For ease of understanding, the terms involved in the embodiments of this application are explained below:

[0060] (1) Mail domain is an important part of an email address. It usually refers to the part after the "@" symbol in an email address, which is used to identify the network domain or organization to which the email belongs. It is not only a basic component of the email system, but also has functions such as identifying user affiliation and managing email routing.

[0061] (2) Mail server is a computer system used to send, receive, store and manage emails. It is the core infrastructure of email communication. It transmits and manages emails by following specific network protocols.

[0062] (3) Mail system is a complete email service system that includes mail server, client software, communication protocol, user interface and related management tools, which are used to create, send, receive, store and manage emails.

[0063] The embodiments of this application involve the Domino mail system and the Exchange mail system. The Domino mail system is an email system originally developed by IBM, and the Exchange mail system is an email system developed by Microsoft. The Domino mail system and the Exchange mail system are common mail systems for large enterprises, and both can handle tens of thousands or even hundreds of thousands of users.

[0064] (4) Public mailbox refers to a free mailbox service that anyone can register for (such as Gmail and QQ mailbox). It corresponds to a corporate mailbox or a private mailbox (which requires a custom domain name and belongs to a specific organization or institution). The server used by the public mailbox is called a public mailbox server, which corresponds to a corporate mailbox server or a private mailbox server.

[0065] (5) DNS (Domain Name System) is one of the core infrastructures of the Internet. It is mainly used to convert human-readable domain names (such as www.abc.com) into computer-readable IP addresses (such as 14.215.177.38) to enable communication between network devices.

[0066] (6) A transit mailbox is a mailbox set up under a certain domain name, where all emails sent to that domain name will be automatically forwarded to another target mailbox (a personal mailbox or a mailbox on another domain name).

[0067] (7) A Mail Exchanger Record (MX record) is a resource record in the DNS that specifies the mail server (mail exchanger) responsible for processing mail for a domain. It determines which servers emails sent to the domain will be routed to for processing. The MX record for a domain may be configured to point to a third-party server that provides mail relay services. For example, the MX record for a relay mailbox may be configured to point to the relay server.

[0068] (8) The names.nsf database is the most important core database in the Domino mail system. It contains all personnel documents and server documents and is the core database for the operation of the Domino mail system.

[0069] (9) Names document is a document in the Names data. Since the database in the Domino mail system is a document-type database, user information and server information are stored in the form of documents.

[0070] (10) Mail gateway is a general-purpose mail platform that can be used to receive or forward mail, and is used to filter and control the incoming and outgoing mail.

[0071] (11) Active Directory (AD) is a directory service developed by Microsoft that is used to centrally manage resources (such as user accounts, computers, printers, file shares, etc.) in enterprise networks and provides authentication, authorization, and resource access control. AD connectivity generally refers to the process of establishing communication and authentication between a computer, device, application, or other system and Microsoft's AD service.

[0072] (12) AD domain control server refers to the Microsoft AD domain control service used in conjunction with the Exchange email system, which is responsible for user information registration and address book functions.

[0073] (13) Exchange Control Panel (ECP) refers to the core management platform of the Exchange mail system, which is used to manage various configurations of the Exchange mail system.

[0074] (14) Domain name certificate is an electronic certificate issued by a domain name service provider, which indicates the registered domain name, the name of the registered owner, the registration time and the expiration time of the domain name. The certificate can be issued by the domain name registration service provider or the purchasing agency.

[0075] (15) Domino key ring, a tool for importing domain name certificates into the Domino mail system.

[0076] (16) Active Directory Federation Services (ADFS) is a service in Microsoft Windows Server systems that is mainly used to implement cross-organizational authentication and single sign-on functions. For example, it can be used to authenticate multiple web application users during a single session.

[0077] (17) SMAL2.0 is a single sign-on (SOO) protocol for Web-based single sign-on, supporting both Domino and Exchange mail systems.

[0078] (18) Next hop address. In the process of sending and receiving emails, the "next hop address" refers to the address of the next email server to be reached in the transmission path from the sender to the recipient. The transmission of emails will be forwarded through multiple intermediate servers. When an email is sent from one server to another, the address of the next target server is the next hop address. This address is determined based on the routing information of the email and the network topology. By continuously determining and jumping to the next hop address, the email can eventually reach the recipient's mailbox server accurately. For example, if user A sends an email to user B, the email is first sent from user A's email client to the sending server where it is located. The sending server determines the next server address to which the email will be forwarded based on the recipient address and its own routing table. This address is the next hop address, and the email will be sent to the server. The server then continues to determine the next hop address, and the cycle continues until the email reaches user B's receiving server.

[0079] Any number of elements in the drawings is for illustration and not limitation, and any naming is for distinction only and does not have any limiting meaning.

[0080] In the related art, an enterprise usually only supports one email system. If they coexist, it may cause system conflicts. However, as enterprises have increasingly higher requirements for email sending and receiving, the demand for using two email systems within the same enterprise, that is, within the same email domain, is becoming increasingly strong.

[0081] To this end, the present application provides a method for sending and receiving emails in an enterprise multi-mail system, which enables the enterprise to integrate and use two email systems.

[0082] After introducing the design concepts of the embodiments of this application, the following briefly introduces the application scenarios to which the technical solutions of the embodiments of this application can be applied. It should be noted that the application scenarios introduced below are only used to illustrate the embodiments of this application and are not limiting. In specific implementations, the technical solutions provided by the embodiments of this application can be flexibly applied according to actual needs.

[0083] refer to Figure 1 , which is a schematic diagram of an application scenario of a method for sending and receiving emails in an enterprise multi-mail system provided by an embodiment of the present application. The method is applied to an email management platform, which can be a platform deployed on an enterprise server for managing various email servers.

[0084] In an embodiment of the present application, the first mail system to which the first mail server belongs and the second mail system to which the second mail server belongs are different mail systems deployed by the same enterprise. For example, the first mail system is a Domino mail system, and the first mail server is a Domino mail server; the second mail system is an Exchange mail system, and the second mail server is an Exchange mail server.

[0085] Generally, mail sending and receiving is divided into the following categories: sending and receiving mail between the Domino mail system and the Exchange mail system within the enterprise, sending mail from the Domino mail system and the Exchange mail system within the enterprise to public mailboxes outside the enterprise, and sending mail from public mailboxes outside the enterprise to the Domino mail system and the Exchange mail system within the enterprise.

[0086] Of course, the method provided in the embodiment of the present application is not limited to Figure 1 The application scenarios shown can also be used in other possible application scenarios, and the embodiments of the present application are not limited thereto. Figure 1 The functions that can be implemented by each device in the application scenario shown will be described in subsequent method embodiments and will not be described in detail here.

[0087] To further illustrate the technical solutions provided by the embodiments of the present application, the following is a detailed description of the technical solutions in conjunction with the accompanying drawings and specific implementation methods. Although the embodiments of the present application provide the method operation steps as shown in the following embodiments or drawings, more or fewer operation steps may be included in the method based on routine or no creative work. In steps where there is no necessary causal relationship logically, the execution order of these steps is not limited to the execution order provided in the embodiments of the present application.

[0088] The following combination Figure 1 The application scenario shown illustrates the technical solution provided by the embodiment of this application.

[0089] refer to Figure 2 The present invention provides a method for sending and receiving emails in an enterprise multi-mail system, the method comprising at least the following steps:

[0090] S201: Receive a first mail sending request from a first mail server.

[0091] S202: Read the preset configuration information and send the first email content to the transit mailbox associated with the first inbox via the transit server associated with the second mail server, so that the first inbox receives the first email content.

[0092] In an embodiment of the present application, the first mail server belongs to the first mail system, the second mail server belongs to the second mail system, and the first mail system and the second mail system are different mail systems deployed by the same enterprise. After receiving the first mail sending request from the first mail server, the mail management platform can determine the first outbox, the first inbox and the first mail content through analysis, and determine that the first outbox uses the first mail server and the first inbox uses the second mail server. The mail management platform reads the preset configuration information. Since the preset configuration information includes the association between the first inbox and the transit mailbox, as well as the association between the second mail server and the transit server, the mail management platform can, based on the preset configuration information, send the first mail content to the transit mailbox associated with the first inbox through the transit server associated with the second mail server to enable the first inbox to receive the first mail content. Such a design allows the two mail systems to be used within the mail domain of the same enterprise, realizes the integration of the two mail systems within one mail domain, and can meet the needs of users sending and receiving mails in multiple scenarios.

[0093] Taking the example of a Domino mail system as the first mail system and a Domino mail server as the first mail server, and an Exchange mail system as the second mail system and an Exchange mail server as the first mail server, the mail sending and receiving process is described in four cases:

[0094] The first scenario: A user in an enterprise using the Domino mail system sends mail to a user using the Exchange mail system.

[0095] In step S201, the email management platform receives a first email sending request from a first email server and analyzes the first email sending request to determine a first outbox, a first inbox, and the first email content. In this case, the first outbox uses a Domino email server and the first inbox uses an Exchange email server.

[0096] Regarding S202, the email management platform stores preset configuration information, where the preset configuration information includes the association between the first inbox and the transit mailbox, and the association between the second email server and the transit server.

[0097] The following steps A1-A4 illustrate the process of generating preset configuration information:

[0098] A1: In the configuration document of the first mail server, change the first mail server to a transit server and add a transit mailbox.

[0099] You can create a separate domain name for internal mail routing, such as a@bbb.com, called a transit mailbox. For example, the first inbox is represented by a@aaa.com, and the transit server is represented by "Other Server." In this step, in the Domino mail server configuration document, change "Domino Mail Server" to "Other Server." Figure 3 This is a schematic diagram of an interface for generating preset configuration information provided by an embodiment of the present application. In which, "Forwarding Address" represents a transit mailbox, "Other Internet Mail" represents a transit server, and the Internet address represents the first mail inbox.

[0100] A2: In the DNS server, update the mail exchange record of the transit mailbox to point to the second mail server.

[0101] Combining the concepts of DNS server and mail exchange record, it can be known that the mail exchange record information of the transit mailbox is updated to point to the second mail server. Such a setting can ensure that the first mail content successfully reaches the Exchange mail server.

[0102] A3: In the management platform of the second mail server, add a transit mailbox and establish an association between the first inbox and the transit mailbox.

[0103] In addition, by adding the transit mailbox to the ECP platform of the Exchange mail server, you can establish an association between a@aaa.com and a@bbb.com.

[0104] A4: Generate preset configuration information based on the association between the first inbox and the transit mailbox, and the association between the second mail server and the transit server

[0105] The above process is the process of generating preset configuration information. In the email sending and receiving process in this case, the email management platform reads the preset configuration information and can send the first email content to a@bbb.com associated with a@aaa.com through the transit server associated with the Exchange email server, so that a@aaa.com receives the first email content.

[0106] In a specific example, when another Domino user sends mail to a@aaa.com, to ensure that the mail is correctly delivered to the Exchange mail server, you can change the mail system in the user's names document to "Other Internet Mail," change the forwarding address to a@bbb.com, and point bbb.com's MX record to the Exchange mail server in the DNS server. This will allow the mail to be successfully delivered to the Exchange mail server. Furthermore, through the Exchange mail server's ECP platform, add another internet address, a@bbb.com, to the user's internet address a@aaa.com. This way, the mail that just entered the Exchange mail server can be successfully routed to its final address.

[0107] The second situation: users in the enterprise who use the Exchange mail system send mails to users who use the Domino mail system.

[0108] Figure 4 This is a flow chart of another method for sending and receiving emails in an enterprise multi-mailbox system provided in an embodiment of the present application. Figure 4 At least the following steps are included:

[0109] S401: Receive a second mail sending request from a second mail server.

[0110] The email management platform receives the second email sending request from the second email server and can analyze the second email sending request to determine the second outbox, the second inbox, and the second email content. In this case, the second outbox uses an Exchange email server and the second inbox uses a Domino email server.

[0111] S402: Send the second email content to the second inbox based on the pre-created sending rule.

[0112] Optionally, in a scenario where internal users using an Exchange mail server send mail to users using a Domino mail system, the mail management platform can configure a sending rule in the "ECP-Mail Flow-Send Connector" of the Exchange mail system. The sending rule indicates that mails sent from the Exchange mail server are allowed to be sent to mail servers other than the Exchange mail server. Figure 5 This is a schematic diagram of an interface for sending rules provided in one embodiment of the present application. Figure 5 The sending rules and other rules are shown in FIG. , and other rules are not described here in detail.

[0113] Combining the first and second scenarios, we've completed the configuration of internal-to-internal mail routing. Specifically, we leveraged a separate domain name as the delivery medium between the two mail systems, enabling mail routing within the same domain. Through this series of configurations and minimal development, we achieved deep integration between the Domino and Exchange mail systems. This addressed the requirements for user synchronization, single sign-on, and fast mail routing within the same domain between the two systems, all with a single configuration.

[0114] The third situation: the public mailbox outside the enterprise sends mails to the Domino mail system and Exchange mail system within the enterprise.

[0115] Figure 6 This is a flow chart of another method for sending and receiving emails in an enterprise multi-mailbox system provided in an embodiment of the present application. Figure 6 At least the following steps are included:

[0116] S601: Receive a third mail sending request from a third mail server.

[0117] The email management platform receives the third email sending request from the third email server and can analyze the third email sending request to determine the third outbox, the third inbox, and the third email content. In this case, the third outbox uses a public mailbox server.

[0118] S602: Determine that the third inbox uses the target mail server.

[0119] The target mail server is the first mail server or the second mail server, that is, the third inbox uses an Exchange mail server or a Domino mail server.

[0120] S603: Send the third email content to the target email server, so that the target email server sends the third email content to the third inbox.

[0121] In this case, the email management platform can send the three email contents to an Exchange email server or a Domino email server, which can then be routed to a third inbox through the corresponding email service.

[0122] In a specific example, conditional mail forwarding is configured in the mail gateway. A separate mail routing rule is created for Internet addresses (email addresses, also known as third inboxes) that need to be routed to the Exchange mail server. For example, if the third inbox is a@aaa.com, mail to the next address is forwarded to the Exchange server, while all other mail is forwarded to the Domino mail server by default.

[0123] The fourth situation: users in the enterprise who use the Domino mail system and users who use the Exchange mail system send mails to a public mailbox outside the enterprise.

[0124] Figure 7 This is a flow chart of another method for sending and receiving emails in an enterprise multi-mailbox system provided in an embodiment of the present application. Figure 7 At least the following steps are included:

[0125] S701: Obtain a fourth email sending request from a target server.

[0126] The target mail server is the first mail server or the second mail server; the fourth mail sending request indicates a fourth outbox, a fourth inbox and fourth mail content.

[0127] The mail management platform obtains and analyzes the fourth mail sending request from the Exchange mail server or Domino mail server to determine the fourth outbox, the fourth inbox, and the content of the fourth mail.

[0128] S702: Determine that the fourth mail server used by the fourth inbox is a public mailbox server.

[0129] S703: Send the fourth email content to the fourth email server through the target server, so that the fourth email server sends the fourth email content to the fourth inbox.

[0130] The fourth email content is sent to the fourth inbox via an Exchange mail server or a Domino mail server.

[0131] In this case, you can point the external next-hop addresses of the Domino mail server and the exchange mail server to the mail gateway.

[0132] Based on the above technical solution, the following pre-processing process can also be performed before sending or receiving emails:

[0133] Preprocessing process 1. Initialization process of username and password.

[0134] B1: Determine a first mailbox set using a first mail system and a second mailbox set using a second mail system.

[0135] For example, if a company has 100 employees, including 20 leaders at a certain level or above, 80 ordinary employees can use the Domino email system, while the 20 leaders can use the Exchange email system. In this way, the first mailbox set is for the 80 ordinary employees, and the second mailbox set is for the 20 leaders.

[0136] Whether using the Domino or Exchange mail system, users must register for the first time. This includes creating an AD connection, creating a user object, setting user attributes, and adding the user to AD. Setting user attributes includes setting a username and password.

[0137] B2: Synchronize the first user information of the first mailbox set and the second user information of the second mailbox set, and synchronize the first password information of the first mailbox set and the second password information of the second mailbox set.

[0138] The first user information and the second user information may be synchronized through step B21, and the first password information and the second password information may be synchronized through step B22.

[0139] B21: Call the AD domain control server in the second mail system and synchronize the first user information and the second user information through the LDAP service in the AD domain control server.

[0140] For example, in a Domino database, a Java agent may be established to call the LDAP service in the Microsoft AD domain controller to achieve user synchronization between Domino and the AD domain, that is, to achieve synchronization of the first user information and the second user information.

[0141] B22: The domain name certificate of the second mail system is loaded into the first mail system through the key ring in the first mail system, so that the Java agent established by the first mail system initializes the second password information stored in the second mail system to synchronize the first password information and the second password information.

[0142] For example, since initializing the AD password (the user's password in the Exchange mail system) requires LDAP protocol encryption, you can use the Domino mail system's keyring configuration to load the Exchange mail system's domain name certificate into the Domino mail system. This allows you to use the Domino mail system's Java agent to initialize the AD user's password, thus enabling synchronization between the Domino mail system and the AD (Exchange mail system) user.

[0143] This setting can ensure that a user's username and password are synchronized after switching from a Domino mail system to an Exchange mail system, or vice versa.

[0144] Pre-processing process 2: Single sign-on setting process.

[0145] Since both the Domino mail system and the Exchange mail system support the SAML 2.0 protocol, you can build a Microsoft ADFS server and use the SAML 2.0 protocol to perform single sign-on for the web login of the Domino mail system and the Exchange mail system.

[0146] Through such a setting, single sign-on of Domino mail system and Exchange mail system can be achieved, thereby ensuring the sending and receiving of mails.

[0147] In summary, the embodiments of this application take into account the need to coexist with two mail systems in the same mail domain in certain scenarios. Therefore, they utilize a variety of technology stacks, including Java, Lotus Script, LdAP, Domino, Exchange, AD, and ADFS, to achieve the integration of two enterprise-level mail systems. This allows some employees of an enterprise to use the Exchange mail system, while others can use the Domino mail system.

[0148] It should be noted that, in actual application, multiple mail systems may be set up. This is just an example and does not constitute a specific limitation.

[0149] like Figure 8 As shown, based on the same inventive concept as the above-mentioned email sending and receiving method of the enterprise multi-mail system, the embodiment of the present application also provides an email sending and receiving device for the enterprise multi-mail system, which is applied to the email management platform and includes a data sending and receiving unit 81 and an email processing unit 82.

[0150] The data transceiver unit 81 is configured to receive a first email sending request from a first email server; the first email sending request indicates a first outbox, a first inbox, and first email content; the first outbox uses the first email server, and the first inbox uses the second email server; the first email system to which the first email server belongs and the second email system to which the second email server belongs are different email systems deployed by the same enterprise;

[0151] The mail processing unit 82 is configured to read preset configuration information and send the first mail content to the transit mailbox associated with the first inbox via the transit server associated with the second mail server, so that the first inbox receives the first mail content; wherein the preset configuration information includes the association relationship between the first inbox and the transit mailbox, and the association relationship between the second mail server and the transit server.

[0152] In an optional embodiment, the system further includes a configuration unit configured to:

[0153] In the configuration document of the first mail server, modify the first mail server to a transit server and add a transit mailbox;

[0154] In the DNS server, update the mail exchange record of the transit mailbox to point to the second mail server;

[0155] In the management platform of the second mail server, add a transit mailbox and establish an association between the first inbox and the transit mailbox;

[0156] Preset configuration information is generated based on the association relationship between the first inbox and the transit mailbox, and the association relationship between the second mail server and the transit server.

[0157] In an optional implementation, the data transceiver unit 81 is further configured to:

[0158] receiving a second mail sending request from a second mail server; wherein the second mail sending request indicates a second inbox, a second outbox, and second mail content; the second outbox uses the second mail server, and the second inbox uses the first mail server;

[0159] The mail processing unit 82 is further used to: send the second mail content to the second inbox based on a pre-created sending rule; wherein the sending rule is configured in the sending connector of the second mail system; the sending rule indicates that mails sent by the second mail server are allowed to be sent to other mail servers except the second mail server.

[0160] In an optional implementation, the data transceiver unit 81 is further configured to:

[0161] receiving a third mail sending request from a third mail server; wherein the third mail server is a public mailbox server; the third mail sending request indicates a third inbox, a third outbox, and third mail content; the third outbox uses the public mailbox server;

[0162] The mail processing unit 82 is further configured to:

[0163] Determining that the third inbox uses a target mail server; wherein the target mail server is the first mail server or the second mail server;

[0164] The third email content is sent to the target email server, so that the target email server sends the third email content to the third inbox.

[0165] In an optional embodiment, the mail processing unit 82 is further configured to:

[0166] Obtaining a fourth mail sending request from a target server; wherein the target mail server is the first mail server or the second mail server; the fourth mail sending request indicates a fourth inbox, a fourth mail box, and fourth mail content;

[0167] Determining that the fourth mail server used by the fourth inbox is a public mailbox server;

[0168] The fourth email content is sent to the fourth email server through the target server, so that the fourth email server sends the fourth email content to the fourth inbox.

[0169] In an optional embodiment, the mail processing unit 82 is further configured to:

[0170] Determining a first mailbox set using a first mail system and a second mailbox set using a second mail system;

[0171] The first user information of the first mailbox set and the second user information of the second mailbox set are synchronized, and the first password information of the first mailbox set and the second password information of the second mailbox set are synchronized.

[0172] In an optional embodiment, the first mail system is a Domino mail system, and the second mail system is an Exchange mail system;

[0173] The mail processing unit 82 is specifically used for:

[0174] The AD domain control server in the second mail system is called, and the first user information and the second user information are synchronized through the LDAP service in the AD domain control server.

[0175] In an optional embodiment, the first mail system is a Domino mail system, and the second mail system is an Exchange mail system;

[0176] The mail processing unit 82 is specifically used for:

[0177] The domain name certificate of the second mail system is loaded into the first mail system through the key ring in the first mail system, so that the java agent established by the first mail system initializes the second password information stored in the second mail system to synchronize the first password information and the second password information.

[0178] The mail sending and receiving device of the enterprise multi-mail system proposed in the embodiment of the present application adopts the same inventive concept as the mail sending and receiving method of the above-mentioned enterprise multi-mail system and can achieve the same beneficial effects, which will not be repeated here.

[0179] Based on the same inventive concept as the above-mentioned method for sending and receiving emails in the enterprise multi-mail system, the embodiment of the present application also provides an electronic device, which can be a desktop computer, a portable computer, a smart phone, a tablet computer, a personal digital assistant (PDA), a server, etc. Figure 9 As shown, the electronic device may include a processor 901 and a memory 902 .

[0180] The processor 901 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor.

[0181] Memory 902 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. Memory can include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disc, etc. Memory is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 602 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0182] Those skilled in the art will appreciate that all or part of the steps of the above-mentioned method embodiments may be implemented by hardware associated with program instructions, and the aforementioned program may be stored in a computer-readable storage medium. When the program is executed, the program executes the steps of the above-mentioned method embodiments. The above-mentioned computer storage medium may be any available medium or data storage device that can be accessed by a computer, including but not limited to: mobile storage devices, random access memory (RAM), magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CDs, DVDs, BDs, HVDs, etc.), and semiconductor storage (such as ROMs, EPROMs, EEPROMs, non-volatile memories (NAND FLASH), solid-state drives (SSDs)), and other media that can store program codes.

[0183] Alternatively, if the above-mentioned integrated unit of the present application is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for making a computer device (which can be a personal computer, a server, or a network device, etc.) execute all or part of the methods of each embodiment of the present application. The aforementioned storage medium includes: a mobile storage device, a random access memory (RAM), a magnetic storage device (such as a floppy disk, a hard disk, a magnetic tape, a magneto-optical disk (MO), etc.), an optical storage device (such as a CD, DVD, BD, HVD, etc.), and a semiconductor memory (such as a ROM, EPROM, EEPROM, a non-volatile memory (NAND FLASH), a solid-state drive (SSD)) and other various media that can store program code.

[0184] Based on the same inventive concept, embodiments of the present application further provide a computer program product, comprising computer program code. When executed on a computer, the computer program code causes the computer to execute any of the hard disk data reading methods discussed above. Because the principles underlying the problems solved by the computer program product are similar to those of the hard disk data reading method, the implementation of the computer program product can be referenced to the implementation of the method, and any repetitions will not be repeated.

[0185] The above embodiments are only used to provide a detailed introduction to the technical solutions of the present application. However, the description of the above embodiments is only used to help understand the methods of the embodiments of the present application and should not be understood as limiting the embodiments of the present application. Any changes or substitutions that can be easily conceived by those skilled in the art should be included in the scope of protection of the embodiments of the present application.

Claims

1. A method for sending and receiving mails in an enterprise multi-mail system, characterized in that: Applied to email management platforms, including: receiving a first email sending request from a first email server; wherein the first email sending request indicates a first outbox, a first inbox, and first email content; the first outbox uses the first email server, and the first inbox uses a second email server; a first email system to which the first email server belongs and a second email system to which the second email server belongs are different email systems deployed by the same enterprise; Read the preset configuration information, and send the first email content to the transit mailbox associated with the first inbox through the transit server associated with the second email server, so that the first inbox receives the first email content; wherein the preset configuration information includes the association relationship between the first inbox and the transit mailbox, and the association relationship between the second email server and the transit server.

2. The method according to claim 1, characterized in that The method further comprises: In the configuration document of the first mail server, modify the first mail server to the transit server and add a transit mailbox; In the DNS server, the mail exchange record of the transit mailbox is updated to point to the second mail server; In the management platform of the second mail server, adding the transit mailbox and establishing an association relationship between the first inbox and the transit mailbox; The preset configuration information is generated according to the association relationship between the first inbox and the transit mailbox, and the association relationship between the second mail server and the transit server.

3. The method according to claim 1, characterized in that The method further comprises: receiving a second mail sending request from a second mail server; wherein the second mail sending request indicates a second inbox, a second outbox, and second mail content; the second outbox uses the second mail server, and the second inbox uses the first mail server; The second email content is sent to the second inbox based on a pre-created sending rule; wherein the sending rule is configured in the sending connector of the second email system; the sending rule indicates that emails sent by the second email server are allowed to be sent to other email servers except the second email server.

4. The method according to claim 1, wherein The method further comprises: receiving a third mail sending request from a third mail server; wherein the third mail server is a public mailbox server; the third mail sending request indicates a third inbox, a third outbox and third mail content; the third outbox uses the public mailbox server; Determining that the third inbox uses a target mail server; wherein the target mail server is the first mail server or the second mail server; The third email content is sent to the target email server, so that the target email server sends the third email content to a third inbox.

5. The method according to claim 1, wherein The method further comprises: Obtaining a fourth mail sending request from a target server; wherein the target mail server is the first mail server or the second mail server; the fourth mail sending request indicates a fourth inbox, a fourth mail box, and fourth mail content; Determining that the fourth mail server used by the fourth inbox is a public mailbox server; The fourth email content is sent to the fourth email server through the target server, so that the fourth email server sends the fourth email content to the fourth inbox.

6. The method according to claim 1, characterized in that The method further comprises: Determining a first mailbox set using the first mail system and a second mailbox set using the second mail system; The first user information of the first mailbox set and the second user information of the second mailbox set are synchronized, and the first password information of the first mailbox set and the second password information of the second mailbox set are synchronized.

7. The method according to claim 6, characterized in that The first mail system is a Domino mail system, and the second mail system is an Exchange mail system; The synchronizing the first user information of the first mailbox set and the second user information of the second mailbox set includes: The AD domain control server in the second mail system is called, and the first user information and the second user information are synchronized through the LDAP service in the AD domain control server.

8. The method according to claim 6, characterized in that The first mail system is a Domino mail system, and the second mail system is an Exchange mail system; The synchronizing the first password information of the first mailbox set and the second password information of the second mailbox set includes: The domain name certificate of the second mail system is loaded into the first mail system through the key ring in the first mail system, so that the Java agent established by the first mail system initializes the second password information stored in the second mail system to synchronize the first password information and the second password information.

9. An email sending and receiving device for an enterprise multi-mail system, characterized in that: Applied to email management platforms, including: A data transceiver unit is configured to: receive a first email sending request from a first email server; wherein the first email sending request indicates a first outbox, a first inbox, and first email content; the first outbox uses the first email server, and the first inbox uses a second email server; a first email system to which the first email server belongs and a second email system to which the second email server belongs are different email systems deployed by the same enterprise; An email processing unit, configured to read preset configuration information and send the first email content to a transit mailbox associated with the first inbox via a transit server associated with the second email server, so that the first inbox receives the first email content; wherein the preset configuration information includes an association relationship between the first inbox and the transit mailbox, and an association relationship between the second email server and the transit server.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 8 are implemented.

Images