Mail migration method and device, electronic equipment, storage medium and program product

By generating the account group to be used in the specified server and creating a matching email account, the problem of data loss during email migration is solved, and data consistency during the complete migration of email data and invisible email migration is achieved.

CN119030950APending Publication Date: 2024-11-26TENCENT TECHNOLOGY (SHENZHEN) CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202310590181.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-23
Publication Date
2024-11-26

AI Technical Summary

Technical Problem

During the mail migration process, it is difficult for the existing technology to completely migrate email data, and there are losses, especially in invisible email migration, which makes it difficult to ensure the integrity of the data.

Method used

By generating a group of accounts to be used in the specified server, if the mail exchange record of the domain name to be migrated points to the specified server, obtain the incoming email and create a matching mailbox account to be used, automatically save the incoming email to be migrated to ensure that the data is migrated to the specified server.

Benefits of technology

The complete migration of email data is realized, data loss is avoided, and data consistency and integrity are ensured during the invisible email migration process.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119030950A_ABST
    Figure CN119030950A_ABST
Patent Text Reader

Abstract

The embodiment of the invention discloses a mail migration method and device, electronic equipment, a storage medium and a program product. The method comprises the following steps: generating a to-be-used mailbox account based on a to-be-migrated mailbox domain name; if the mail exchange record of the to-be-migrated mailbox domain name points to a specified server, a specified mail entry mail and a corresponding specified mail entry account can be obtained; and if the to-be-used mailbox account corresponding to the specified letter entering account does not exist, creating and entering a specified letter entering mail, and migrating mail data of the to-be-used mailbox account in the third-party server to a specified server. According to the method and the device, the uncreated mailbox account can be found based on the entry check, and the corresponding mailbox account is automatically created for entry, so that the mail data is prevented from being lost, and the mail data can be completely migrated in the mail migration.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to an email migration method, device, electronic device, storage medium and program product. Background Art

[0002] Email migration refers to the process of migrating the email data of an email account from one email server to another, while seamless email migration means that the email account remains unchanged before and after the email data is migrated.

[0003] Mail Exchanger (MX) record is a type of resource record in the Domain Name System (DNS) that can be used to specify the mail server that receives mails for a specific domain name. When performing seamless mail migration, the MX record of the mailbox domain name needs to be changed to achieve mail migration. However, in the current mail migration, mail data may be lost, making it difficult to migrate mail data completely. Summary of the invention

[0004] The embodiments of the present application provide an email migration method, device, electronic device, storage medium and program product, which can avoid the loss of email data during the email migration process and achieve complete migration of email data.

[0005] The present application provides an email migration method, including:

[0006] Based on the domain name of the mailbox to be migrated, generating an account group to be used in the designated server, wherein the account group to be used includes at least one mailbox account to be used;

[0007] If the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, obtaining the designated incoming mail received by the designated server and the designated incoming mail account corresponding to the designated incoming mail, the designated incoming mail account having the mailbox domain name to be migrated, and the third-party server is a mail server different from the designated server;

[0008] If there is no email account to be used that matches the designated incoming email account in the account group to be used, creating an email account to be used corresponding to the designated incoming email account in the account group to be used, and saving the designated incoming email to the email account to be used corresponding to the designated incoming email account;

[0009] Migrate the mail data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server.

[0010] The embodiment of the present application also provides an email migration device, including:

[0011] A generating module, configured to generate an account group to be used in a designated server based on the domain name of the mailbox to be migrated, wherein the account group to be used includes at least one mailbox account to be used;

[0012] An incoming mail module, used for obtaining a designated incoming mail received by the designated server and a designated incoming mail account corresponding to the designated incoming mail if the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, the designated incoming mail account having the mailbox domain name to be migrated, and the third-party server being a mail server different from the designated server;

[0013] a creation module, configured to create a to-be-used email account corresponding to the designated incoming email account in the to-be-used account group if there is no to-be-used email account matching the designated incoming email account in the to-be-used account group, and save the designated incoming email to the to-be-used email account corresponding to the designated incoming email account;

[0014] The migration module is used to migrate the email data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server.

[0015] An embodiment of the present application also provides an electronic device, including a memory storing multiple instructions; the processor loads instructions from the memory to execute the steps in any one of the email migration methods provided in the embodiments of the present application.

[0016] An embodiment of the present application also provides a computer-readable storage medium, which stores a plurality of instructions, and the instructions are suitable for a processor to load to execute the steps in any one of the email migration methods provided in the embodiments of the present application.

[0017] An embodiment of the present application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps in any one of the email migration methods provided in the embodiments of the present application.

[0018] The embodiment of the present application can generate a to-be-used account group including at least one to-be-used mailbox account according to the to-be-migrated mailbox domain name; after the mail exchange record of the to-be-migrated mailbox domain name points to the designated server, obtain the designated incoming mail and the corresponding designated incoming mail account on the designated server, and when the to-be-used mailbox account corresponding to the designated incoming mail account does not exist in the to-be-used account group, it is automatically created and the designated incoming mail is sent to avoid the loss of mail data, and then the mail data of each to-be-used mailbox account in the third-party server is migrated to the designated server. Based on the incoming mail check, it can be found that the mailbox account that has not been created, and the corresponding mailbox account is automatically created and sent to avoid the loss of mail data, so that the mail data can be completely migrated in the mail migration. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0020] Figure 1a It is a schematic diagram of an application scenario of the email migration method provided in an embodiment of the present application;

[0021] Figure 1b It is a flowchart of the email migration method provided in the embodiment of the present application;

[0022] Figure 1c It is a flowchart of domain name migration provided by an embodiment of the present application;

[0023] Figure 1d This is an overall architecture diagram of the email migration method provided in the embodiment of the present application;

[0024] Figure 1e This is a bottom-level implementation architecture diagram of the email migration method provided in the embodiment of the present application;

[0025] Figure 1f This is a bottom-level implementation architecture diagram of email migration based on exchange provided in an embodiment of the present application;

[0026] Figure 1g It is a schematic diagram of the process of synchronizing incoming emails based on exchange provided in an embodiment of the present application;

[0027] Figure 2a is a flowchart of an email migration method provided by another embodiment of the present application;

[0028] Figure 2b This is a schematic diagram of the interface for performing domain name migration provided in an embodiment of the present application;

[0029] Figure 2c This is a schematic diagram of the overall process of changing the MX record provided in the embodiment of the present application;

[0030] Figure 2d It is a schematic diagram of the overall process of the email migration method provided in the embodiment of the present application;

[0031] Figure 2e This is a schematic diagram of the interface for creating a migration task provided in an embodiment of the present application;

[0032] Figure 2f This is a schematic diagram of an interface for displaying a verification email provided in an embodiment of the present application;

[0033] Figure 2g is a schematic diagram of an interface for displaying migration progress provided in an embodiment of the present application;

[0034] Figure 3 It is a structural diagram of the mail migration device provided in an embodiment of the present application;

[0035] Figure 4 It is a schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0036] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of this application.

[0037] Embodiments of the present application provide an email migration method, device, electronic device, storage medium, and program product.

[0038] The mail migration device can be integrated into an electronic device, which can be a terminal, a server, etc. The terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop, or a personal computer (PC); the server can be a single server or a server cluster composed of multiple servers.

[0039] In some embodiments, the mail migration device may also be integrated into multiple electronic devices. For example, the mail migration device may be integrated into multiple servers, and the mail migration method of the present application may be implemented by multiple servers.

[0040] In some embodiments, the server may also be implemented in the form of a terminal.

[0041] For example, refer to Figure 1a , shows a schematic diagram of an application scenario of the email migration method provided in an embodiment of the present application. Figure 1a As shown in , the terminal 100 and the designated server 200 are located in a wireless network or a wired network, and the terminal 100 and the designated server 200 can be communicatively connected.

[0042] The terminal 100 may run an email management program, which may provide a corresponding interactive interface on the terminal 100 so that the user can start email migration based on the content displayed in the interactive interface. For example, the interactive interface may include a domain name input area, in which the user may enter the corresponding mailbox domain name to be migrated, and submit the mailbox domain name to be migrated to the designated server 200 through the terminal 100, so that the designated server 200 may generate at least one mailbox account to be used in the designated server 200 based on the mailbox domain name to be migrated, and obtain a group of accounts to be used.

[0043] Then, the interactive interface can also display the migration instructions so that the user can change the mail exchanger (Mail Exchanger, MX) record of the mailbox domain to be migrated based on the migration instructions, and submit corresponding feedback information to the designated server 200 based on the interactive interface so that the designated server 200 knows that the mx record of the mailbox domain to be migrated has been changed.

[0044] Thus, the designated server 200 can be the MX record of the mailbox domain name to be migrated. When the third-party server points to the designated server 200, the designated server 200 can obtain the received designated incoming email and the designated incoming account corresponding to the designated incoming email, wherein the designated incoming account has the mailbox domain name to be migrated, and the third-party server is a mail server different from the designated server. If there is no mailbox account to be used that matches the designated incoming account in the account group to be used, a mailbox account to be used corresponding to the designated incoming account can be created in the account group to be used, and the designated incoming email can be saved in the mailbox account to be used corresponding to the designated incoming account, and then the mail data of each mailbox account to be used in the account group to be used in the third-party server can be migrated to the designated server.

[0045] At the same time, the status of email migration can be displayed in the interactive interface of the terminal, so that users can know the progress of email migration.

[0046] It should be noted that the order of the following embodiments is not intended to limit the preferred order of the embodiments.

[0047] In this embodiment, a mail migration method is provided, such as Figure 1b As shown, the specific process of the email migration method can be as follows:

[0048] S110: Generate an account group to be used in a designated server based on the domain name of the mailbox to be migrated, wherein the account group to be used includes at least one mailbox account to be used.

[0049] The mailbox domain to be migrated refers to the mailbox domain that needs to undergo mail migration. Mail migration refers to the process of migrating all mail data in an email account from one mail server to another. For example, migrating the mail data of an email account in mail server A to mail server B is called mail migration.

[0050] The email domain name refers to the part after the @ symbol in the email address. For example, if the email address is test@example.com, the email domain name is example.com. In the embodiment of the present application, the email migration is a seamless migration, that is, the user's email account remains unchanged before and after the migration. When performing email migration, the email server of the email domain name to be migrated also needs to be changed.

[0051] The designated server may provide a management terminal, and the administrator may log in to the management terminal so as to uniformly manage all the mailbox accounts under a certain mailbox domain name through the management terminal. The mailbox domain name to be migrated may be submitted to the designated server by the administrator through the management terminal, wherein an interactive interface may be provided on the management terminal so that the administrator may input the mailbox domain name to be migrated based on the content on the interactive interface. For example, a domain name input area may be provided on the interactive interface, and the administrator may input the corresponding mailbox domain name to be migrated in the domain name input area, and submit the mailbox domain name to be migrated to the designated server.

[0052] The designated server refers to the mail server to which the mail data needs to be migrated. The designated server can be set by the user himself. For example, if the user wants to migrate the mail data to mail server B, the designated server is mail server B.

[0053] The mailbox account to be used refers to the mailbox account to which the mail data is migrated, that is, the mailbox account in the designated server. After obtaining the mailbox domain name to be migrated, at least one mailbox account to be used can be generated in the designated server based on the mailbox account to be migrated to obtain the account group to be used.

[0054] In some implementations, when generating an account group to be used in a designated server based on the mailbox domain name to be migrated, the mailbox domain name to be migrated and the mail exchange record of the mailbox domain name to be migrated may be obtained; if the mail exchange record of the mailbox domain name to be migrated does not point to the designated server, an object identifier is obtained; based on the mailbox domain name to be migrated and the object identifier, a mailbox account to be used corresponding to the object identifier is generated in the designated server to obtain the account group to be used.

[0055] After obtaining the domain name of the mailbox to be migrated, you can continue to obtain the MailExchanger (MX) record of the domain name of the mailbox to be migrated, where the MX record is a type of resource record in the Domain Name System (DNS) and is used to specify the mail server that receives mails for a specific domain name.

[0056] Each MX record can contain two parts: a priority value and a mail server host name. The smaller the priority value of the MX record, the higher the priority, that is, the mail server will first try to deliver the mail to these servers. If the first server cannot receive the mail, it will try to connect to the next server with a lower priority. If all the recorded servers cannot receive the mail, the mail sending server will return the mail to the sender and notify the mail exchange error.

[0057] When obtaining the MX record of the mailbox domain to be migrated, a request may be sent to a DNS server based on the mailbox domain to be migrated, so that the DNS server can return the MX record of the mailbox domain to be migrated.

[0058] If the MX record is not empty and is not the host name of the specified server, it can be considered that the MX record of the mailbox domain name to be migrated does not point to the specified server. To ensure that the mail data can be migrated to the specified server, the object identifier can be obtained and a mailbox account to be used corresponding to the object identifier can be created in the specified server.

[0059] Among them, the object identifier can uniquely refer to the object in the designated server. The object can refer to the user. The object identifier and the user name have a corresponding relationship. The object identifier can be based on the member list uploaded by the administrator, which contains multiple user names. For example, the administrator uploads the member list in the organization to the designated server. In the designated server, each member has a corresponding object identifier. After obtaining the member name, the object identifier can be obtained based on the corresponding relationship.

[0060] Then, based on the object identifier and the domain name of the mailbox to be migrated, the mailbox account to be used corresponding to the object identifier can be generated. When generating the mailbox account to be used, it can be generated based on certain rules. For example, based on the object identifier, the name of the member can be obtained, and the full spelling of the member name, @, and the domain name of the mailbox to be migrated can be sequentially composed into the mailbox account to be used corresponding to the object identifier. For example, if the member name corresponding to a certain object identifier is Xiaohong, and the domain name of the mailbox to be migrated is a.com, then the generated mailbox account to be used is xiaohong@a.com, and if the member name corresponding to the object identifier is Xiaoming, then the generated mailbox account to be used is xiaoming@a.com.

[0061] In some implementations, the administrator can also upload the email accounts currently in use in the email domain to be migrated, and associate these email accounts with member names, and upload them all to the designated server so that the designated server can directly use the email accounts uploaded by the administrator to create corresponding email accounts to be used in the designated server, and obtain the account group to be used. At the same time, if the administrator only uploads the email accounts corresponding to some member names, the designated server can also automatically create corresponding email accounts to be used for other members.

[0062] After the account group to be used is generated, the migration instructions and feedback controls of the MX record can be displayed on the management side, so that the administrator can learn how to change the MX record of the mailbox domain name to be migrated based on the migration instructions and change the MX record. After changing the MX record, a feedback message can be sent to the designated server based on the feedback control, so that the designated server is informed that the MX record of the mailbox domain name to be migrated has been changed, and the designated server can perform subsequent operations based on the feedback message.

[0063] S120: If the mail exchange record of the to-be-migrated mailbox domain name is pointed to the designated server by a third-party server, obtain the designated incoming mail received by the designated server and the designated incoming account corresponding to the designated incoming mail.

[0064] The third-party server refers to the mail server that the MX record of the mailbox domain to be migrated points to before the change. The third-party server is a mail server different from the designated server. Since the mail data of the mailbox domain to be migrated needs to be migrated to the designated server, the MX record of the mailbox domain to be migrated needs to be changed so that the MX record of the mailbox domain to be migrated points to the designated server.

[0065] After the designated server receives the feedback message, it can be considered that the MX record of the domain name of the mailbox to be migrated has been changed. After the MX record is changed, the new MX record will be stored in the DNS server and gradually forwarded to other DNS servers. When the user queries, the DNS server will return the latest MX record. Due to the influence of DNS cache and validity period (time-to-live, TTL), the changed MX record usually takes some time to take effect.

[0066] In order to be able to know the change of MX record in time, the MX record can be regularly rotated. For example, the specified server can query the MX record of the mailbox domain name to be migrated at a preset interval; if the MX record is not empty and contains the host name of the specified server, it can be considered that the MX record modification is effective; if the MX record still does not contain the host name of the specified server, wait for the preset interval and continue to query the MX record of the mailbox domain name to be migrated. Among them, the preset interval can be set according to actual needs, for example, it can be set to 1 minute, that is, every 1 minute, query the MX record of the mailbox domain name to be migrated once.

[0067] In some implementations, in order to reduce the amount of data processing and to promptly learn that the MX record change is effective, multiple different preset intervals may be set. For example, within a first time range after receiving the feedback message, the MX record of the mailbox to be migrated is queried at a first preset interval, and within a second time range after receiving the feedback message, the MX record of the mailbox to be migrated is queried at a second preset time interval, wherein the first preset interval is greater than the second preset interval.

[0068] Among them, the first time range, the second time range, the first preset interval and the second preset interval can all be set according to actual needs. For example, the MX record usually takes 1-72 hours to take effect after modification. The first time range can be 1 hour, and the first preset interval can be 30 minutes, that is, within the first hour after receiving the feedback message, the MX record is queried every 30 minutes. The second time range can be the 2nd to 72nd hour, and the second preset interval can be 10 minutes, that is, within the 2nd to 72nd hour after receiving the feedback message, the MX record is queried every 10 minutes. By setting corresponding preset intervals in different time ranges, the query frequency of the MX record can be reduced, thereby reducing the amount of data processing and timely notifying the effectiveness of the MX record change.

[0069] If the MX record of the mailbox domain to be migrated points to the designated server, it indicates that the change to the MX record is effective. At this time, the mail server of the mailbox domain to be migrated is updated to the designated server, and the designated server can receive all emails on the mailbox domain to be migrated, that is, it can obtain the designated incoming emails and the designated incoming account corresponding to the designated incoming emails.

[0070] The designated incoming mail refers to the mail whose recipient is the designated incoming mail account, and the designated incoming mail account refers to the mailbox account with the mailbox domain name to be migrated. For example, the designated server receives mail x with the recipient test@a.com and mail y with the recipient test@b.com. Since the mailbox domain name to be migrated is a.com, test@a.com can be determined as the designated incoming mail account, and mail x is the designated incoming mail.

[0071] It should be noted that since test@b.com does not have the domain name of the mailbox to be migrated, the email can be directly returned.

[0072] S130. If there is no email account to be used that matches the designated incoming account in the account group to be used, create an email account to be used corresponding to the designated incoming account in the account group to be used, and save the designated incoming email to the email account to be used corresponding to the designated incoming account.

[0073] After obtaining the designated incoming email and the corresponding designated incoming account, it can be determined whether there is an email account to be used that matches the designated incoming account in the account group to be used.

[0074] In some embodiments, the email account to be used that matches the designated incoming account may refer to an email account to be used that is consistent with the designated incoming account. When determining whether there is an email account to be used that matches the designated incoming account in the group of accounts to be used, it may be determined whether there is the designated incoming account in the group of accounts to be used; if not, it may be determined that there is no email account to be used that matches the designated incoming account in the group of accounts to be used. For example, each email account to be used in the group of accounts to be used may be compared with the designated incoming account, and if the designated incoming account and all email accounts to be used are inconsistent, it may be determined that there is no email account to be used that matches the designated incoming account in the group of accounts to be used.

[0075] For example, the account group to be used includes test1@a.com, test2@a.com and test3@a.com, and the designated incoming mail account is test@a.com. It can be determined that there is no email account to be used corresponding to the designated incoming mail account in the account group to be used.

[0076] To avoid losing emails during the email migration process, you can create a to-be-used email account corresponding to the designated incoming account in the to-be-used account group, and save the designated incoming emails to the newly created to-be-used email account. For example, in the above example, you can create a to-be-used email account test@a.com in the to-be-used account group, and save the designated email x corresponding to the designated incoming account to test@a.com.

[0077] If there is an email account to be used that matches the designated incoming account in the account group to be used, the designated incoming email can be directly saved to the email account to be used that matches the designated incoming account to avoid email loss.

[0078] S140: Migrate the email data of each of the to-be-used email accounts in the to-be-used account group in the third-party server to the designated server.

[0079] In the account group to be used, there is a corresponding relationship between the mailbox account to be used generated based on the domain name of the mailbox to be migrated and each object identifier. The mailbox account to be used newly created based on the specified incoming account does not have a corresponding object identifier. The administrator can actively assign a corresponding object to the newly created mailbox account to bind it to the object identifier, and the mail migration is started by the object indicated by the object identifier.

[0080] In some embodiments, when migrating the email data of each email account to be used in the account group to be used in the third-party server to the designated server, a migration task corresponding to the email account to be used in the account group to be used can be created; for each migration task, the account password corresponding to the email account to be used is obtained; if the account password is consistent with the account password of the email account to be used in the third-party server, the email data corresponding to the email account to be used is pulled from the third-party server.

[0081] A migration task is an asynchronous task created by a designated server for mail data migration. One mailbox account to be used corresponds to one migration task. Based on the migration task, the mail data of the mailbox account to be used in a third-party server can be migrated to the designated server.

[0082] As an implementation method, the migration tasks can be created in batches by the administrator on the management side. For example, a domain name setting area can be displayed in the interactive interface of the management side, prompting the administrator to enter the corresponding migration domain name and migration domain name, wherein the migration domain name refers to the domain name that needs to be migrated for mail, and the migration domain name refers to the domain name to which the mail is migrated. In some implementation methods, in order to achieve seamless migration of mails, the migration domain name and the migration domain name can be the same.

[0083] After entering the domain name to be migrated in and the domain name to be migrated out, the content of the original mailbox can continue to be displayed for verification. The administrator can enter the mail service provider of the original mailbox and the corresponding receiving server, and enter any mailbox account under the domain name to be migrated out, as well as the corresponding account password for verification. After the verification is passed, the content of the uploaded migration mailbox can be displayed. The administrator uploads the mailbox account to be migrated out and the corresponding mailbox account to be migrated in to create the corresponding migration task. In the embodiment of the present application, since it is a seamless mail migration, the mailbox account to be migrated out and the mailbox account to be migrated in are the same. The administrator can only upload the corresponding mailbox account to be used, and the designated server can match the mailbox account to be migrated out through the account with the same name.

[0084] As an implementation method, the migration task can also be automatically created by a designated server. For example, if the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, the default mailbox account corresponding to the object identifier in the designated server is obtained; the default mailbox account corresponding to the object identifier is replaced with the mailbox account to be used corresponding to the object identifier; if there is a direct mailbox account corresponding to the object identifier, and the direct mailbox account has the mailbox domain name to be migrated, based on the direct mailbox account, a migration task corresponding to the mailbox account to be used is created, and the direct mailbox account interacts with the third-party server through the client.

[0085] The administrator and members can be in the same organization of the instant messaging software, which is a professional management tool specially designed for organizations and can integrate instant messaging and email functions. The default email account is an email account automatically created for members after they join the organization. When the aforementioned timed rotation detects that the MX record of the email domain name to be migrated points to the specified server, the default email account corresponding to the object identifier in the specified server can be obtained.

[0086] In order to make the mailbox account to be used generated based on the mailbox domain to be migrated effective, you can directly use the mailbox account to be used corresponding to the object identifier to replace the default mailbox account corresponding to the object identifier. For example, if the default mailbox account corresponding to an object identifier is test@a.wecom.work and the mailbox account to be used corresponding to the object identifier is test@a.com, you can directly replace test@a.wecom.work with test@a.com.

[0087] A direct-receiving email account refers to an email account that the user actively configures in advance on the client in the email function provided by the instant messaging software. The direct-receiving email account can interact with the email server corresponding to the email account based on a public protocol by the client, so as to store the acquired email data locally on the client.

[0088] In order to ensure that the original email account can be used normally while the MX record is being changed, the user can configure the original email account as a direct-receiving email account on the client before changing the MX record. When creating a direct-receiving email account, the client's query request can be received, and the Internet Protocol address corresponding to the domain name where the client is currently located is sent to the client, so that the client can obtain the email data of the direct-receiving email account from the direct-receiving server based on the Internet Protocol address and the public protocol. The direct-receiving server is the email server corresponding to the direct-receiving email account; the email data corresponding to the direct-receiving email account sent by the client is received, and the email data is synchronized to other clients that have logged into the direct-receiving email account.

[0089] When configuring a direct-receiving email account, the client can send a query request to the designated server based on the interface provided by the designated server, and the designated server can feedback the Internet Protocol (IP) address corresponding to the domain name where the client is currently located to the client based on the query request. When the user enters a certain email account as the direct-receiving email account, the client can use the IP address and the public protocol to establish a connection with the direct-receiving mail server of the direct-receiving email account, so as to directly obtain the mail data of the direct-receiving email account from the direct-receiving server and save it locally on the client. For example, the user can directly enter the email account in the domain name of the email to be migrated as the direct-receiving email account, so that during the process of changing the MX record, the migrated email account can be used normally through the direct-receiving email account.

[0090] In order to achieve the multi-terminal synchronization function, the client can upload the corresponding email data to the designated server, for example, the direct email account and the email data are stored in association, so that the email data can be synchronized to other clients that have logged into the direct email account. For example, if the user configures the direct email account test@a.com on the computer and logs into the direct email account on the mobile terminal, the corresponding email data can be automatically synchronized to the mobile terminal.

[0091] If it is detected that the object identifier has a corresponding direct-receiving email account, and the direct-receiving email account has the to-be-migrated email domain name, a migration task corresponding to the to-be-used email account is created based on the direct-receiving email account.

[0092] In some implementations, when creating a migration task corresponding to an email account to be used based on a direct email account, the direct email account may be replaced with the email account to be used corresponding to the object identifier; the client is notified to save the email data of the direct email account, and a migration task corresponding to the email account to be used is created.

[0093] If there is a direct-receiving mailbox account with the mailbox domain to be migrated, you can directly replace the direct-receiving mailbox account with the mailbox account to be used, that is, the client will no longer interact with the third-party server to obtain mail data, but will switch to interacting with the third-party server through the specified server to obtain mail data. At the same time, in order to avoid mail loss, you can notify the client to retain the mail data of the direct-receiving mailbox account and create a migration task corresponding to the mailbox account to be used.

[0094] If it is detected that the object identifier has a corresponding direct-receiving mailbox account, and the direct-receiving mailbox account does not have the mailbox domain name to be migrated, the direct-receiving mailbox account can be maintained.

[0095] Based on the above content, it can be known that after the MX record points to the specified server, the specified server performs a mailbox replacement operation to automatically create a migration task. At the same time, it performs an incoming letter check to create a mailbox account to be used corresponding to the specified incoming letter account, which can avoid email loss.

[0096] Among them, the above-mentioned email migration can be divided into two steps. The first is to migrate the domain name, that is, to change the MX record of the mailbox domain name to be migrated; the second is to migrate the email data, that is, to migrate the email data after the MX record takes effect.

[0097] For a clearer description of the above process, please refer to Figure 1c , which shows a schematic diagram of the process of domain name migration. Among them, the administrator can first add the mailbox domain name to be migrated, generate and store the mailbox account to be used based on the mailbox domain name to be migrated. After the MX record has been changed, the designated server can periodically train the MX record of the mailbox domain name to be migrated. If the MX record points to the designated server, it is determined that the MX record check has passed; if the MX record does not point to the designated server, wait for the next query.

[0098] After the MX record check passes, you can perform mailbox replacement, that is, replace the default mailbox account with the mailbox account to be used, and determine whether there is a direct mailbox account with the mailbox domain to be migrated; if so, replace the direct mailbox account with the mailbox account to be used, and create a corresponding migration task; if not, maintain the direct mailbox account.

[0099] After the MX record is passed, you can also perform an incoming letter check to obtain the designated incoming email and the corresponding designated incoming account. If the designated incoming account exists in the email account to be used, the letter will be directly received. If the email account to be used does not exist, the corresponding email account to be used will be created and the letter will be received. Incoming letters that do not have the email domain name to be migrated will be directly rejected.

[0100] After creating the migration task corresponding to the mailbox account to be used based on the above method, for each migration task, the designated server can obtain the account password corresponding to the mailbox account to be used. As some implementation methods, these account passwords can be submitted to the backend server in batches by the administrator.

[0101] As another implementation, these account passwords may be submitted by the user of the email account to be used. For example, when the designated server fails to obtain the account password, it may send a verification email to the email account to be used so that the user can enter the corresponding account password and submit it to the designated server.

[0102] If the account password is consistent with the account password of the email account to be used in the third-party server, the designated server can access the third-party server to obtain the email data of the email account to be used in the third-party server, so as to migrate the email data of the email account to be used in the third-party server to the designated server.

[0103] In some implementations, the management terminal may display the progress of the mail data migration corresponding to the mailbox domain to be migrated. For example, the total number of mailbox accounts that need to be migrated under the mailbox domain to be migrated and the number of accounts that have completed the migration may be displayed.

[0104] The task status of each migration task can also be displayed so that the administrator can be informed of the migration status. For example, before the account password is obtained, the task status can be Not Started; if the account password obtained is inconsistent with the account password of the email account to be used in the third-party server, the task status can be Migrating. If the account password is inconsistent with the account password of the email account to be used in the third-party server, or if the email data cannot be pulled from the third-party server, the task status of the migration task can be updated to Migration Failed.

[0105] In some embodiments, if the account password is inconsistent with the account password of the email account to be used in the third-party server, the account password can be retrieved. For example, an email can be resent to the email account to be used so that the user can resubmit the account password. If the number of times the account password is retrieved exceeds a preset number of times, the task status corresponding to the migration task can be updated to migration failure.

[0106] In some embodiments, when pulling email data corresponding to the email account to be used from the third-party server, if all email data of the email account to be used in the third-party server are migrated to the designated server, an update notification is sent to the client so that the client deletes local email data and synchronizes the email data in the designated server; if the number of emails migrated to the designated server by the email account to be used reaches a preset number, an update notification is sent to the client so that the client deletes local email data and synchronizes the email data in the designated server.

[0107] If all emails of the mailbox account to be used in the third-party server are migrated to the designated server, that is, the migration task is completed, an update notification can be sent to the client so that the client can delete the local email data and synchronize the email data from the designated server.

[0108] If the number of emails to be migrated to the designated server using the email account reaches a preset number, an update notification can also be sent to the client so that the client can delete the local email data and synchronize the email data from the designated server. The preset number is the upper limit of the number of locally stored emails, which can be set according to actual needs, for example, 500, 600, etc.

[0109] To explain the above email migration process more clearly, please refer to Figure 1d , showing the overall architecture diagram of the mail migration method. Among them, the administrator and members are objects in the same organization, and the administrator has the authority to manage the email accounts of all members in the organization. The administrator can change the MX record of the mailbox domain name to be migrated in order to realize the migration of the mailbox domain name to be migrated. After the MX record points to the specified server, the incoming letter is switched to the specified server. The corresponding mailbox account to be used can be created and the letter can be entered to avoid mail loss. The administrator can then assign corresponding members to these mailbox accounts to be used. After the MX record points to the specified server, the mailbox account can be replaced and it can be detected whether there is a direct receiving mailbox account for the mailbox domain name to be migrated. If there is, it will be switched directly without feeling and the local mail of the client will be retained. If not, the migration task will be started directly. The administrator can also add the mailbox accounts that need to be migrated in batches to start the migration task.

[0110] Members can configure direct email accounts on the client and keep the data of the direct email accounts on the designated server. Members can also start the corresponding migration task based on email notifications. When the number of emails to be migrated in the migration task exceeds the preset number, the client can be notified to delete the local email data and switch to the data on the designated server.

[0111] The above process can also be found in Figure 1e, showing the underlying implementation architecture diagram of the mail migration method, where qywebmngsvr represents the background business logic processing of the mailbox management. The administrator initiates a request based on the management end. After adding the member migration, the logic processing can be performed. qyrialogic / bizotherlogic represents the logic of processing the direct receipt, pull / historical mail of the members in the client. The members actively initiate the request to perform the logic processing. qywwbridge represents the rpc request switching http request transit service, and wwaccounthttpbroker represents the service that needs to synchronously modify the member mailbox information when the mailbox changes. qycronsvr represents the timed rotation service to check whether the mx record of the domain name has passed, and qymqsvr represents the asynchronous task of processing the account replacement and other operations after the mx record of the domain name has passed. qyexternalmailxmq represents the asynchronous service for synchronizing historical and new mails, qyexternalmailagentsvr represents the business logic for saving direct account data, qyexternalmailpkv represents background storage, qymailmovesvr represents saving account migration data, and qynewindexsvr represents saving mail data. The above mail migration can be realized by calling the corresponding services.

[0112] In some implementations, if the third-party server is a preset server, email migration can also be performed in a specific manner, wherein the preset server can be an exchange server. That is, when the third-party server is an exchange server, email migration can be performed in a specific manner. For example, when the third-party server is an exchange server, a special entry link can be provided on the interactive interface, and the user clicks the special entry link to start the email migration in the specific manner.

[0113] As an implementation method, if the third-party server is a preset server and the account group to be used is successfully created, an initialization task corresponding to the email account to be used is created; for each initialization task, the folder of the email account to be used in the third-party server is mapped to the designated server; based on the folder, the email data of the email account to be used in the third-party server is pulled to the designated server; if the email exchange record of the email domain name to be migrated points from the third-party server to the designated server, the email account replacement processing is performed according to the email account to be used.

[0114] If the third-party server is an exchange server, when the account group to be used is successfully created, an initialization task can be directly created for each mailbox account to be used in the account group to be used. The mailbox account to be used created here has an additional suffix compared to its corresponding outgoing mailbox account. For example, if the outgoing mailbox account is xiaohong@a.com, the corresponding mailbox account to be used is xiaohong_ew0@a.com. The initialization task is an asynchronous task. For each initialization task, the folder corresponding to the mailbox account to be used in the third-party server can be mapped to the specified server.

[0115] Among them, the folder corresponding to the email account to be used in the third-party server refers to the folder in the email account to be migrated from corresponding to the email account to be used. Among them, when the third-party server is an exchange service, the names of the email account to be used and the email account to be migrated from are different, but when it is necessary to display the email account to be used, it can be displayed as the same as the name of the migrated email account, that is, removing the suffix.

[0116] As an implementation method, when mapping the folder corresponding to the email account to be used in a third-party server to a designated server, the account password corresponding to the email account to be used can be obtained; if the account password is consistent with the account password recorded on the third-party server, a list of folders corresponding to the email account to be used in the third-party server is obtained; and in the email account to be used, a folder in the folder list is created.

[0117] Get the account and password corresponding to the email account to be used. If the account and password match the account and password recorded on the third-party server, you can directly log in to the email account to be used.

[0118] Then, the folder of the mailbox account to be used in the third-party server can be obtained, and the folder can be mapped to the mailbox account to be used in the designated server. Optionally, a list of folders of the mailbox account to be used can be obtained from the third-party server, and then a corresponding folder can be generated for the mailbox account to be used based on the list of folders in the designated server, and the mapping relationship between the folders can be recorded for subsequent use. For ease of description, the folder of the mailbox account to be used in the third-party server is recorded as the first folder, and the folder of the mailbox account to be used in the designated server is recorded as the second folder, and the first folder and the second folder have a mapping relationship.

[0119] After creating a corresponding folder for the mailbox account to be used, the mail data in each folder of the mailbox account to be migrated can be obtained from the third-party server based on the EWS protocol, and the mail data can be pulled into the corresponding folder. For example, mail statistics processing can be performed on each folder of the mailbox account to be used in the third-party server to obtain mail statistics information; based on the mail statistics information, the mail data of the mailbox account to be used in the third-party server can be pulled into the folder of the mailbox account to be used in the designated server; all incoming mails of the mailbox account to be used in the third-party server can be synchronized to the designated server.

[0120] Among them, mail statistics processing refers to counting the number of mailboxes in each folder. For example, it can be to count the number of pages of mails, that is, the attributes of mails, such as date, sender account, recipient account and other information, calculate the number of pages occupied by mails in the folder, sort the mails according to the attributes, and implement paging. For each page, the start and end positions of the mails contained can be recorded to achieve subsequent rapid positioning of mails. Then, using the mail statistics information, the mail data can be pulled to the corresponding folder of the mailbox account to be used in the specified server by paging.

[0121] In some implementations, in order to facilitate subsequent email synchronization, after the email data is pulled into the corresponding folder, the pulled emails can also be marked to avoid repeated pulling of emails in the future. Optionally, the email ID of the email account to be used in the third-party server is different from its email ID in the designated server. If the email ID in the third-party server is recorded as the first email ID, after the email data is pulled into the corresponding folder, the email ID of the email in the designated server, that is, the second email ID, is different from the first email ID. A corresponding relationship between the first email ID and the second email ID can be established to avoid repeated pulling of emails.

[0122] At the same time, the above process can also be referred to Figure 1f , shows the underlying architecture diagram of email migration based on exchange, where qybroker represents the internal business call service provided by the specified server, which can be called by the management end; MQ represents the general term for asynchronous services, including various asynchronous services, through which email data can be paged and pulled to the mailbox account to be used, and the mailbox account to be used can be initialized. wwxxbroker represents the service provided to other internal business calls; wwaccount represents the synchronous modification of member mailbox information when the mailbox changes; wwhttpbroke represents the service provided to other internal business calls based on the http protocol.

[0123] When a new email arrives in the outgoing email account corresponding to the to-be-used email account, the new email may be called an incoming email, and all incoming emails of the outgoing email account in the third-party server may be synchronized to the designated server.

[0124] In some embodiments, a subscription request may be initiated to the third-party server based on the email account to be used and the callback link address; if the subscription request is approved, incoming emails of the email account to be used are obtained based on the callback link address; if the subscription request is not approved, an email pull request may be initiated to the third-party server at a specified time interval to obtain incoming emails of the email account to be used from the third-party server.

[0125] The email account to be used can be used to determine the email account that needs to be subscribed, that is, the email account to be migrated from corresponding to the email account to be used, and specify the corresponding callback function to initiate a subscription request to the third-party server. The subscription request may include subscription parameters required for the subscription, such as subscription type, subscription time range, etc. After receiving the subscription request, the third-party server can verify the subscription request, such as verifying the subscription authority and determining whether the subscription parameters are legal. If the third-party server has the subscription authority and the subscription parameters are legal, the subscription request can be considered to be passed.

[0126] If the subscription request is approved, when the third-party server receives the corresponding incoming email, it can synchronize the incoming email to the Common Gateway Interface (CGI) service based on the callback function, so as to obtain the incoming email of the mailbox account to be used based on the CGI service.

[0127] When the CGI service detects a user operation, such as a new email, deleted email, created folder, etc., an asynchronous task can be added, and the operation can be synchronized to the mailbox account to be used based on the asynchronous task.

[0128] If the subscription request is not approved, you can actively initiate an email pull request to the third-party server to obtain incoming emails of the email account to be used from the third-party server.

[0129] For example, after the email account to be used and the corresponding account password are verified, a third-party server is accessed to determine whether an incremental update is required, and the folders of the email account to be used on the third-party server and the folders of the email account to be used on the designated mail server are compared and aligned.

[0130] Among them, when performing incremental updates, it can be determined whether the email account to be used is in the subscription push mode. If it is in the push mode and there is no notification after the preset time, the email data of the third-party server can be directly synchronized to the designated server, and based on the object operation reported by the universal gateway interface server, the operation command corresponding to the object operation can be synchronized to the third-party server.

[0131] See also Figure 1g , showing a schematic diagram of the process of synchronizing incoming emails based on exchange, wherein the scheduled rotation service can create a rotation task, and the account password will be checked each time the rotation is performed to ensure that the account password has not been changed; add a two-way synchronization task, that is, synchronize data from the exchange service to the specified server, and synchronize data to the exchange service based on user operations, add a historical email pull task, and realize the paging of historical emails, that is, the paging of email data mentioned above. Among them, in the two-way synchronization task, the user operation flow can be recorded and reported based on user operations, and then the data can be synchronized to the imap server based on the imap protocol. If the exchange service is successfully subscribed based on the ews protocol, the callback service can be updated to push the updated information in the account to the callback service, so as to obtain the user operation based on the subscription service and perform incremental updates based on the user operation.

[0132] After the MX record of the mailbox domain name to be migrated is pointed from the third-party server to the designated server, the mailbox account replacement process can be performed according to the mailbox account to be used. For example, each mailbox account to be used corresponds to an object identifier, and each object identifier also has its corresponding default mailbox account. The default mailbox account can be directly replaced with the mailbox account to be used.

[0133] Since the name of the email account to be used is different from the name of the email account to be migrated, the name of the email account to be used can be directly changed so that the name of the email account to be used is the same as the name of the corresponding email account to be migrated, so as to achieve seamless email migration. For example, the name of the email account to be used has an additional suffix compared to the email account to be migrated, so the suffix of the email account to be used can be directly deleted, that is, only the "_ew0" in xiaohong_ew0@a.com can be directly deleted to change it to xiaohong@a.com.

[0134] The email migration solution provided by the embodiment of the present application can be applied in various scenarios of email data migration. For example, taking the case where the user's email account remains unchanged before and after email migration, but only the corresponding email server changes, the solution provided by the embodiment of the present application can automatically create the email account to be used corresponding to the designated incoming email if the designated incoming account corresponding to the designated incoming email does not exist in the account group to be used, based on the received designated incoming email, after the MX record of the email domain name to be migrated points to the designated server, so as to avoid the loss of email data of the designated incoming account during the email migration process.

[0135] Through the method provided in the embodiment of the present application, when the MX record is changed, the user can set a direct mailbox account so that the migrated mailbox account can be used normally during the mail migration process. After the MX record points to the specified server, the mailbox replacement can be performed to make the assigned mailbox account effective, and the incoming letter check is performed, and the non-existent designated incoming letter account is automatically created and the letter is entered, so as to avoid the situation in which the mail data of the account cannot be migrated due to the non-existence of the corresponding account in the specified server during the mail migration process, and then the mail is lost, so as to ensure that the mail data can be completely migrated during the mail migration.

[0136] The method described in the above embodiment will be further described in detail below.

[0137] In this embodiment, the method of the embodiment of the present application will be described in detail by taking seamless email migration as an example.

[0138] like Figure 2a As shown in the figure, the specific process of a mail migration method is as follows:

[0139] S210: Obtain the domain name of the mailbox to be migrated and the mail exchange record of the domain name of the mailbox to be migrated.

[0140] S220: If the mail exchange record does not point to a designated server, generate an account group to be used, wherein the account group to be used includes at least one mailbox account to be used.

[0141] When performing seamless email migration, the administrator can initiate domain name migration on the management end, so as to enter the corresponding mailbox domain name to be migrated and submit it to the designated server. For example, there are 5 members in an organization, namely Xiaohong, Xiaocheng, Xiaohuang, Xiaolu and Xiaoqing, among which Xiaoqing is the administrator.

[0142] For example, see Figure 2b, showing a schematic diagram of the interface for domain name migration, wherein Xiaoqing can enter the mailbox domain name "@a.com" to be migrated in the corresponding input box under the prompt "Please enter the corporate mailbox domain name", and then click the "Next" control to submit the mailbox domain name @a.com to be migrated to the designated server, so that the designated server can obtain the MX record of @a.com. If the MX record does not point to the designated server, the administrator is prompted to upload a file. When the administrator clicks Next, the uploaded file can be submitted to the designated server so that the designated server can generate a to-be-used account group containing at least one to-be-used mailbox account.

[0143] Also see Figure 2c , showing the overall process diagram of changing MX records. After allocating the email account to be used, the migration instructions and feedback controls of the MX records can continue to be displayed, so that the administrator can change the MX record of @a.com based on the migration instructions, and after the change is completed, a feedback message can be sent to the designated server based on the feedback control, so that the designated server will know that the MX record of the email domain name to be migrated has been modified, so that the designated server can perform subsequent operations based on the feedback message.

[0144] S230: If the mail exchange record points to a designated server, perform mail account replacement processing based on the mail account to be used.

[0145] S240: If the mail exchange record points to a designated server, obtain a designated incoming mail and a designated incoming account corresponding to the designated incoming mail.

[0146] S250. If there is no email account to be used that matches the designated incoming account in the account group to be used, create an email account to be used corresponding to the designated incoming account in the account group to be used, and save the incoming email to the email account to be used corresponding to the designated incoming account.

[0147] The designated server can then periodically poll the MX record of @a.com to determine whether the change in the MX record is effective. If the MX record points to the designated server, the change is considered effective, and the email account to be used can be used to replace the email account. Among them, the 5 members in the organization have a default email account generated for them when they join the organization. For example, it is an email account with an email domain name of @domain.wecom.work. The default email account can be directly replaced with the email account to be used. Among them, when generating the email account to be used, since the administrator has uploaded the member list, the email account to be used has been bound to the member's ID, so the member's default email account can be replaced with the email account to be used.

[0148] For example, Xiaohong's default email account is xiaohong@domain.wecom.work, and the email account to be used is xiaohong@a.com, then xiaohong@domain.wecom.work can be directly replaced with xiaohong@a.com.

[0149] In some implementations, members can proactively configure a direct-receiving email account for the email domain to be migrated so that the email account can be used normally during the MX record change process. If Xiaohong configures a direct-receiving email account for the email domain to be migrated, the direct-receiving email account can be replaced, its direct-receiving email account can be cancelled, and the client can be notified to retain the corresponding email data.

[0150] After the MX record takes effect, you can also perform an incoming mail check, that is, all incoming mails from a.com are received by the designated server. If you receive a mail from test@a.com at this time, but there is no test@a.com account in the mailbox account to be used, then create the mailbox account and send the mail to the mailbox. Please continue to refer to Figure 2c After MX takes effect, members can enter their account and password to start email migration in the client to pull historical emails and start migration. All members can receive corresponding email notifications. To ensure that email notifications can be seen by members, messages can be sent to inactive users based on instant messaging software. The management end can receive the effectiveness notification, and the homepage of the management mailbox can show that it has taken effect.

[0151] S260: Migrate the email data of each of the to-be-used email accounts in the to-be-used account group in the third-party server to the designated server.

[0152] Then, after the MX record changes take effect, you can migrate the data. Figure 2d , which shows the overall process diagram of the email migration method. A corresponding interactive interface can be provided on the management end to instruct the administrator to create a migration task. For example, see Figure 2e , shows a schematic diagram of the interface when creating a migration task, in which the administrator can enter the domain name and the migration-out domain name. In the embodiment of the present application, the migration-in domain name and the migration-out domain name can both be a.com. The administrator then clicks Next to configure the original mailbox parameters. For example, the original mailbox server provider, the receiving server, and the corresponding port information can be entered, and any original mailbox account and password of the mailbox domain name to be migrated can be entered for verification, and then Next is clicked. If the verification is successful, the interface for batch uploading of migration mailboxes can be displayed. The administrator can only upload the corresponding mailbox accounts to be used, and the specified server can match the corresponding migration-out mailbox accounts through the accounts with the same name.

[0153] If the verification fails, the corresponding help page can be displayed to provide some solutions, such as prompting the user to check whether the password is correct, whether there is an independent password, whether the parameters are set correctly, whether secure login is enabled, etc. If the above methods still cannot verify successfully, you can get a transit domain name and perform data migration based on the transit domain name.

[0154] Then, in order to start the migration task, the administrator can enter the corresponding account and password when uploading the migration email account. If the administrator does not enter the corresponding account and password, a verification email can be sent to the user so that the user can submit the account and password based on the verification email. For example, see Figure 2f , shows a schematic diagram of the interface for displaying a verification email, wherein after the user clicks on "Verify Now" in the email content, an interface for inputting the account and password can be displayed. After the user enters the password, he clicks on "Verify Now" to submit the password to the specified server to start the migration task corresponding to xiaohong@a.com.

[0155] After the migration task is started, the migration progress can be displayed on the management side. For example, Figure 2g , showing a schematic diagram of the interface for displaying the migration progress. Among them, the overall migration progress of the mailbox domain a.com to be migrated can be displayed. For example, there are 320 accounts in a.com, the number of accounts that have been migrated, the number of accounts that are being migrated, etc. At the same time, the migration status of each mailbox account to be used can also be displayed, which is convenient for the administrator to grasp the specific migration status.

[0156] As can be seen from the above, the embodiment of the present application can generate a to-be-used account group including at least one to-be-used mailbox account according to the to-be-migrated mailbox domain name; after the mail exchange record of the to-be-migrated mailbox domain name points to the designated server, obtain the designated incoming mail and the corresponding designated incoming mail account on the designated server, and when the to-be-used mailbox account corresponding to the designated incoming mail account does not exist in the to-be-used account group, it is automatically created, and the designated incoming mail is sent to avoid mail data loss, and then the mail data of each to-be-used mailbox account in the third-party server is migrated to the designated server. Based on the incoming mail check, the mailbox account that has not been created can be found, and after the active creation, the loss of mail in the mail migration can be avoided, and comprehensive mail migration can be achieved.

[0157] In order to better implement the above method, the embodiment of the present application also provides a mail migration device, which can be integrated in an electronic device, and the electronic device can be a terminal, a server, etc. Among them, the terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop, a personal computer, etc.; the server can be a single server or a server cluster composed of multiple servers.

[0158] For example, in this embodiment, the method of the embodiment of the present application will be described in detail by taking the mail migration device being specifically integrated in the server as an example.

[0159] For example, Figure 3 As shown, the mail migration device 300 may include a generation module 310 , an incoming mail module 320 , a creation module 330 and a migration module 340 .

[0160] A generating module 310, configured to generate an account group to be used in a designated server based on the domain name of the mailbox to be migrated, wherein the account group to be used includes at least one mailbox account to be used;

[0161] The incoming mail module 320 is used to obtain the designated incoming mail received by the designated server and the designated incoming mail account corresponding to the designated incoming mail if the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by the third-party server, the designated incoming mail account has the mailbox domain name to be migrated, and the third-party server is a mail server different from the designated server;

[0162] A creation module 330 is used to create a to-be-used email account corresponding to the designated incoming email account in the to-be-used account group if there is no to-be-used email account matching the designated incoming email account in the to-be-used account group, and save the designated incoming email to the to-be-used email account corresponding to the designated incoming email account;

[0163] The migration module 340 is used to migrate the email data of each of the to-be-used email accounts in the to-be-used account group in the third-party server to the designated server.

[0164] In some embodiments, the generation module 310 further includes:

[0165] A domain name acquisition unit, used to acquire the domain name of the mailbox to be migrated and the mail exchange record of the domain name of the mailbox to be migrated;

[0166] an identification acquisition unit, configured to acquire an object identification if the mailbox exchange record of the mailbox domain name to be migrated does not point to the designated server;

[0167] The generating unit is used to generate a mailbox account to be used corresponding to the object identifier in a designated server based on the mailbox domain name to be migrated and the object identifier, so as to obtain the account group to be used.

[0168] In some embodiments, the migration module 340 further includes:

[0169] A task creation unit, configured to create a migration task corresponding to the mailbox account to be used in the account group to be used;

[0170] A verification unit, configured to obtain, for each migration task, an account and password corresponding to the email account to be used;

[0171] The migration unit is used to pull the email data corresponding to the email account to be used from the third-party server if the account password is consistent with the account password of the email account to be used in the third-party server.

[0172] In some embodiments, the migration unit is further configured to:

[0173] If all the email data of the mailbox account to be used in the third-party server are migrated to the designated server, an update notification is sent to the client so that the client can delete the local email data and synchronize the email data in the designated server;

[0174] If the number of emails migrated from the mailbox account to be used to the designated server reaches a preset number, an update notification is sent to the client so that the client can delete local email data and synchronize email data in the designated server.

[0175] In some embodiments, the email account to be used and the object identifier have a corresponding relationship, and the creation unit is further used to:

[0176] If the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, obtaining a default mailbox account corresponding to the object identifier in the designated server;

[0177] Replace the default email account corresponding to the object identifier with the email account to be used corresponding to the object identifier;

[0178] If there is a direct email account corresponding to the object identifier, and the direct email account has the email domain name to be migrated, a migration task corresponding to the email account to be used is created based on the direct email account, and the direct email account interacts with the third-party server through the client.

[0179] In some embodiments, the creating unit is further configured to:

[0180] Replacing the direct receiving email account with the email account to be used corresponding to the object identifier;

[0181] The client is notified to save the mail data of the direct-receiving mailbox account, and a migration task corresponding to the mailbox account to be used is created.

[0182] In some embodiments, the email migration device 300 further includes a direct receipt creation module, which is used to:

[0183] Sending the Internet Protocol address of the third-party server to the client, so that the client can obtain the email data of the direct-receiving mailbox account from the direct-receiving server based on the Internet Protocol address and the public protocol, and the direct-receiving server is the email server corresponding to the direct-receiving mailbox account;

[0184] Receive the email data corresponding to the direct-receiving email account sent by the client, and synchronize the email data to other clients that log in to the direct-receiving email account.

[0185] In some embodiments, the incoming letter module 320 is further configured to:

[0186] If there is an email account to be used that matches the designated incoming email account in the account group to be used, the designated incoming email is saved in the email account to be used that matches the designated incoming email account.

[0187] In some embodiments, the email migration apparatus 300 further includes a designated migration module for:

[0188] If the third-party server is a preset server and the account group to be used is successfully created, an initialization task corresponding to the email account to be used is created;

[0189] For each initialization task, mapping the folder of the mailbox account to be used in the third-party server to the designated server;

[0190] Based on the folder, pull the email data of the mailbox account to be used in the third-party server to the designated server;

[0191] If the mail exchange record of the mailbox domain name to be migrated is directed from the third-party server to the designated server, the mailbox account replacement process is performed according to the mailbox account to be used.

[0192] In some embodiments, the specified migration module is further configured to:

[0193] Performing mail statistics processing on each folder of the mailbox account to be used in the third-party server to obtain mail statistics information;

[0194] Based on the email statistical information, pull the email data of the email account to be used in the third-party server to the folder of the email account to be used in the designated server;

[0195] All incoming emails of the mailbox account to be used in the third-party server are synchronized to the designated server.

[0196] In some embodiments, the specified migration module is further configured to:

[0197] Initiate a subscription request to the third-party server based on the email account to be used and the callback link;

[0198] If the subscription request is approved, obtaining incoming emails of the mailbox account to be used based on the callback link;

[0199] If the subscription request is not approved, an email pull request is initiated to the third-party server at a specified interval, so as to obtain incoming emails of the mailbox account to be used from the third-party server.

[0200] In specific implementation, the above units can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units can refer to the previous method embodiments, which will not be repeated here.

[0201] As can be seen from the above, the mail migration device of this embodiment can generate a to-be-used account group including at least one to-be-used mailbox account according to the to-be-migrated mailbox domain name; after the mail exchange record of the to-be-migrated mailbox domain name points to the designated server, obtain the designated incoming mail and the corresponding designated incoming mail account on the designated server, and when the to-be-used mailbox account corresponding to the designated incoming mail account does not exist in the to-be-used account group, it is automatically created and the designated incoming mail is entered to avoid the loss of mail data, and then the mail data of each to-be-used mailbox account in the third-party server is migrated to the designated server. Based on the incoming mail check, it can be found that the mailbox account that has not been created, and the corresponding mailbox account is automatically created and entered to avoid the loss of mail data, so that the mail data can be completely migrated in the mail migration.

[0202] The embodiment of the present application also provides an electronic device, which can be a terminal, a server, etc. The terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop, a personal computer, etc. The server can be a single server or a server cluster composed of multiple servers, etc.

[0203] In some embodiments, the mail migration device may also be integrated into multiple electronic devices. For example, the mail migration device may be integrated into multiple servers, and the mail migration method of the present application may be implemented by multiple servers.

[0204] In this embodiment, the electronic device of this embodiment is a server as an example for detailed description, for example, Figure 4 As shown, it shows a schematic diagram of the structure of the electronic device involved in the embodiment of the present application, specifically:

[0205] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, an input module 404, and a communication module 405. Those skilled in the art will appreciate that Figure 4 The electronic device structure shown in the figure does not constitute a limitation on the electronic device, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0206] The processor 401 is the control center of the electronic device. It uses various interfaces and lines to connect various parts of the entire electronic device. By running or executing software programs and / or modules stored in the memory 402 and calling data stored in the memory 402, it performs various functions of the electronic device and processes data, thereby monitoring the electronic device as a whole. In some embodiments, the processor 401 may include one or more processing cores; in some embodiments, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 401.

[0207] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0208] The electronic device also includes a power supply 403 for supplying power to various components. In some embodiments, the power supply 403 can be logically connected to the processor 401 through a power management system, so as to manage charging, discharging, and power consumption through the power management system. The power supply 403 can also include any components such as one or more DC or AC power supplies, recharging systems, power failure detection circuits, power converters or inverters, and power status indicators.

[0209] The electronic device may further include an input module 404, which may be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0210] The electronic device may further include a communication module 405. In some embodiments, the communication module 405 may include a wireless module. The electronic device may perform short-range wireless transmission through the wireless module of the communication module 405, thereby providing the user with wireless broadband Internet access. For example, the communication module 405 may be used to help the user send and receive emails, browse web pages, and access streaming media.

[0211] Although not shown, the electronic device may further include a display unit, etc., which will not be described in detail herein. Specifically in this embodiment, the processor 401 in the electronic device will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby realizing various functions, as follows:

[0212] Based on the domain name of the mailbox to be migrated, generating an account group to be used in a designated server, wherein the account group to be used includes at least one mailbox account to be used;

[0213] If the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, obtaining the designated incoming mail received by the designated server and the designated incoming mail account corresponding to the designated incoming mail, the designated incoming mail account having the mailbox domain name to be migrated, and the third-party server is a mail server different from the designated server;

[0214] If there is no email account to be used that matches the designated incoming email account in the account group to be used, creating an email account to be used corresponding to the designated incoming email account in the account group to be used, and saving the designated incoming email to the email account to be used corresponding to the designated incoming email account;

[0215] Migrate the mail data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server.

[0216] The specific implementation of the above operations can be found in the previous embodiments, which will not be described in detail here.

[0217] As can be seen from the above, this embodiment can generate a to-be-used account group including at least one to-be-used mailbox account according to the to-be-migrated mailbox domain name; after the mail exchange record of the to-be-migrated mailbox domain name points to the designated server, obtain the designated incoming mail and the corresponding designated incoming mail account on the designated server, and when the to-be-used mailbox account corresponding to the designated incoming mail account does not exist in the to-be-used account group, it is automatically created and the designated incoming mail is entered to avoid the loss of mail data, and then the mail data of each to-be-used mailbox account in the third-party server is migrated to the designated server. Based on the incoming mail check, it can be found that the mailbox account that has not been created, and the corresponding mailbox account is automatically created and entered to avoid the loss of mail data, so that the mail data can be completely migrated in the mail migration.

[0218] A person of ordinary skill in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be completed by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0219] To this end, an embodiment of the present application provides a computer-readable storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute the steps in any of the email migration methods provided in the embodiments of the present application. For example, the instructions can execute the following steps:

[0220] Based on the domain name of the mailbox to be migrated, generating an account group to be used in a designated server, wherein the account group to be used includes at least one mailbox account to be used;

[0221] If the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, obtaining the designated incoming mail received by the designated server and the designated incoming mail account corresponding to the designated incoming mail, the designated incoming mail account having the mailbox domain name to be migrated, and the third-party server is a mail server different from the designated server;

[0222] If there is no email account to be used that matches the designated incoming email account in the account group to be used, creating an email account to be used corresponding to the designated incoming email account in the account group to be used, and saving the designated incoming email to the email account to be used corresponding to the designated incoming email account;

[0223] Migrate the mail data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server.

[0224] The storage medium may include: a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0225] According to one aspect of the present application, a computer program product or a computer program is provided, the computer program product or the computer program including computer instructions, the computer instructions being stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the methods provided in various optional implementations of the mail migration aspects provided in the above embodiments.

[0226] Since the instructions stored in the storage medium can execute the steps in any one of the email migration methods provided in the embodiments of the present application, the beneficial effects that can be achieved by any one of the email migration methods provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0227] The above is a detailed introduction to an email migration method, device, electronic device, storage medium and program product provided in the embodiments of the present application. Specific examples are used in this article to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, based on the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A mail migration method, It is characterized in that The method comprises: Based on the domain name of the mailbox to be migrated, generating an account group to be used in a designated server, wherein the account group to be used includes at least one mailbox account to be used; If the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, obtaining the designated incoming mail received by the designated server and the designated incoming mail account corresponding to the designated incoming mail, the designated incoming mail account having the mailbox domain name to be migrated, and the third-party server is a mail server different from the designated server; If there is no email account to be used that matches the designated incoming email account in the account group to be used, creating an email account to be used corresponding to the designated incoming email account in the account group to be used, and saving the designated incoming email to the email account to be used corresponding to the designated incoming email account; Migrate the mail data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server.

2. The method according to claim 1, It is characterized in that The step of generating the account group to be used in the designated server based on the mailbox domain name to be migrated includes: Obtain the domain name of the mailbox to be migrated and the mail exchange record of the domain name of the mailbox to be migrated; If the mailbox exchange record of the mailbox domain name to be migrated does not point to the designated server, obtaining an object identifier; Based on the to-be-migrated mailbox domain name and the object identifier, a to-be-used mailbox account corresponding to the object identifier is generated in a designated server to obtain the to-be-used account group.

3. The method according to claim 1, It is characterized in that The step of migrating the email data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server includes: Creating a migration task corresponding to the mailbox account to be used in the account group to be used; For each of the migration tasks, obtaining the account and password corresponding to the email account to be used; If the account password is consistent with the account password of the email account to be used in the third-party server, the email data corresponding to the email account to be used is pulled from the third-party server.

4. The method according to claim 3, It is characterized in that The step of pulling email data corresponding to the email account to be used from the third-party server includes: If all the email data of the mailbox account to be used in the third-party server are migrated to the designated server, an update notification is sent to the client so that the client can delete the local email data and synchronize the email data in the designated server; If the number of emails migrated from the mailbox account to be used to the designated server reaches a preset number, an update notification is sent to the client so that the client can delete local email data and synchronize email data in the designated server.

5. The method according to claim 3, It is characterized in that The mailbox account to be used and the object identifier have a corresponding relationship, and in the creating of the account group to be used, the migration task corresponding to the mailbox account to be used includes: If the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, obtaining a default mailbox account corresponding to the object identifier in the designated server; Replace the default email account corresponding to the object identifier with the email account to be used corresponding to the object identifier; If there is a direct email account corresponding to the object identifier, and the direct email account has the email domain name to be migrated, a migration task corresponding to the email account to be used is created based on the direct email account, and the direct email account interacts with the third-party server through the client.

6. The method according to claim 5, It is characterized in that The step of creating a migration task corresponding to the mailbox account to be used based on the direct receiving mailbox account includes: Replacing the direct receiving email account with the email account to be used corresponding to the object identifier; The client is notified to save the mail data of the direct-receiving mailbox account, and a migration task corresponding to the mailbox account to be used is created.

7. The method according to claim 5, It is characterized in that The method further comprises: Sending the Internet Protocol address of the third-party server to the client, so that the client can obtain the email data of the direct-receiving mailbox account from the direct-receiving server based on the Internet Protocol address and the public protocol, and the direct-receiving server is the email server corresponding to the direct-receiving mailbox account; Receive the email data corresponding to the direct-receiving email account sent by the client, and synchronize the email data to other clients that log in to the direct-receiving email account.

8. The method according to claim 1, It is characterized in that The method further comprises: If there is an email account to be used that matches the designated incoming email account in the account group to be used, the designated incoming email is saved in the email account to be used that matches the designated incoming email account.

9. The method according to claim 1, It is characterized in that The method further comprises: If the third-party server is a preset server and the account group to be used is successfully created, an initialization task corresponding to the email account to be used is created; For each initialization task, mapping the folder of the mailbox account to be used in the third-party server to the designated server; Based on the folder, pull the email data of the mailbox account to be used in the third-party server to the designated server; If the mail exchange record of the mailbox domain name to be migrated is directed from the third-party server to the designated server, the mailbox account replacement process is performed according to the mailbox account to be used.

10. The method according to claim 9, It is characterized in that Pulling the email data of the mailbox account to be used in the third-party server to the designated server based on the folder includes: Performing mail statistics processing on each of the folders of the mailbox account to be used in the third-party server to obtain mail statistics information; Based on the email statistical information, pull the email data of the email account to be used in the third-party server to the folder of the email account to be used in the designated server; All incoming emails of the mailbox account to be used in the third-party server are synchronized to the designated server.

11. The method according to claim 10, It is characterized in that The step of synchronizing all incoming emails of the mailbox account to be used in the third-party server to the designated server includes: Initiate a subscription request to the third-party server based on the email account to be used and the callback link; If the subscription request is approved, obtaining incoming emails of the mailbox account to be used based on the callback link; If the subscription request is not approved, an email pull request is initiated to the third-party server at a specified interval, so as to obtain incoming emails of the mailbox account to be used from the third-party server.

12. A mail migration device, It is characterized in that The device comprises: A generating module, configured to generate an account group to be used in a designated server based on the domain name of the mailbox to be migrated, wherein the account group to be used includes at least one mailbox account to be used; An incoming mail module, used for obtaining a designated incoming mail received by the designated server and a designated incoming mail account corresponding to the designated incoming mail if the mail exchange record of the mailbox domain name to be migrated is pointed to the designated server by a third-party server, the designated incoming mail account having the mailbox domain name to be migrated, and the third-party server being a mail server different from the designated server; a creation module, configured to create a to-be-used email account corresponding to the designated incoming email account in the to-be-used account group if there is no to-be-used email account matching the designated incoming email account in the to-be-used account group, and save the designated incoming email to the to-be-used email account corresponding to the designated incoming email account; The migration module is used to migrate the email data of each of the mailbox accounts to be used in the account group to be used in the third-party server to the designated server.

13. An electronic device, It is characterized in that It comprises a processor and a memory, wherein the memory stores a plurality of instructions; the processor loads instructions from the memory to execute the steps in the mail migration method according to any one of claims 1 to 11.

14. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a plurality of instructions, and the instructions are suitable for being loaded by a processor to execute the steps in the mail migration method according to any one of claims 1 to 11.

15. A computer program product, It is characterized in that The invention comprises a computer program / instruction, which implements the steps of the mail migration method according to any one of claims 1 to 11 when executed by a processor.