Mail management method and system, computer equipment and storage medium

Abstract

The invention belongs to the technical field of email processing, and discloses an email management method and system, computer equipment and a storage medium. The method comprises the steps of receiving a delivery task submitted by a terminal and storing in a database; initiating a task identifier allocation request to a mailbox system; receiving a mail identifier sent by a mailbox system, associating the mail identifier with the delivery task, and storing the associated mail identifier and the delivery task in a database; sending a delayed delivery request to a mailbox system, wherein the delayed delivery request is used for indicating the mailbox system to send a lightweight mail to a recipient associated with the delivery task; a group letter request sent by the mailbox system is received, the group letter request is sent to the delivery system when the mailbox system detects a mail access request initiated by a recipient, and the group letter request comprises a mail identifier; and retrieving a database according to the group letter request and the mail identifier, generating a complete mail, and sending the complete mail to a mailbox system. The occupation of network bandwidth resources can be reduced, and the requirement for storage space can be lowered.

Description

Technical Field

[0001] The present application relates to the technical field of email processing, and in particular to an email management method, system, computer equipment, and storage medium. Background Art

[0002] When processing a template letter delivery task, existing email delivery systems must access the delivery system's management page, create a template and delivery task, and import user data into a database. The delivery system then retrieves the task data, along with the corresponding template and user data, from the database, uses the template to assemble a complete email for each user, and delivers it to the recipient's mailbox system. The service module corresponding to the recipient's mailbox system receives the email, which is then stored on the local disk by the storage module. The recipient then logs into a web client or client and requests the mailbox system's server to retrieve the email content. The storage module then loads the email content from the local disk and returns it to the web client or client. When the number of recipients for a template letter task is large, the mailbox system assembles and stores a single email for each recipient, requiring significant bandwidth and storage space, resulting in a waste of network bandwidth and storage resources. Summary of the Invention

[0003] To this end, embodiments of the present application provide an email management method, system, computer device, and storage medium that can reduce the occupancy of network bandwidth resources and lower the demand for storage space.

[0004] In a first aspect, the present application provides an email management method.

[0005] This application is achieved through the following technical solutions:

[0006] A mail management method, applied to a delivery system, comprising:

[0007] Receiving a delivery task submitted by a terminal and storing it in a database, wherein the delivery task includes a template identifier and a recipient list;

[0008] Initiate a task identifier allocation request to the mailbox system. The task identifier allocation request is used to request the mailbox system to generate an email identifier for each delivery task;

[0009] Receiving the mail identifier sent by the mailbox system, and associating the mail identifier with the delivery task and storing it in a database;

[0010] Sending a delayed delivery request to the mailbox system, wherein the delayed delivery request is used to instruct the mailbox system to send a lightweight email to the recipient associated with the delivery task;

[0011] Receive a mail grouping request sent by the mailbox system. The mail grouping request is a mail grouping request sent by the mailbox system to the delivery system when the mailbox system detects a mail access request initiated by the recipient. The mail grouping request includes a mail identifier.

[0012] The database is searched according to the group mail request and the mail identifier, a complete mail is generated, and the complete mail is sent to the mailbox system.

[0013] In a preferred example of this application, it can be further set as follows:

[0014] The mailbox system includes a task identifier allocation interface; the task identifier allocation request is initiated to the mailbox system, and the task identifier allocation request is used to request the mailbox system to generate an email identifier for each delivery task, including:

[0015] The delivery system reads pending delivery tasks from the database;

[0016] The delivery system initiates a task identifier allocation request to the task identifier allocation interface of the mailbox system.

[0017] In a preferred example of the present application, it can be further configured that the sending of the delayed delivery request to the mailbox system further includes:

[0018] Sending a mail index generation request to the mailbox system, wherein the mail index generation request is used to request the mail system to generate a mail index for each lightweight mail that has been sent;

[0019] Receive the email index sent by the mailbox system.

[0020] In a preferred example of this application, it can be further set as follows:

[0021] Receiving the sending result of the mailbox system;

[0022] When the sending result is successful, a text message carrying a link to read the message is sent to the recipient.

[0023] Secondly, this application proposes an email management method.

[0024] This application is achieved through the following technical solutions:

[0025] A mail management method, applied to a mailbox system, comprising:

[0026] Receive a task identifier allocation request from the delivery system, wherein the task identifier allocation request is used to request generation of a mail identifier for each delivery task;

[0027] Sending a mail identifier to the delivery system, where the mail identifier is used to query the corresponding mail content when assembling mail;

[0028] Receive delayed delivery requests from the delivery system and send lightweight emails to recipients associated with the delivery task;

[0029] Receiving the mail access request from the terminal, initiating a group mail request to the delivery system, wherein the group mail request is used to instruct the delivery system to generate a complete mail;

[0030] Receive a complete email sent by the delivery system, and send the complete email to the terminal.

[0031] In a preferred example of the present application, it can be further configured that the mailbox system includes a storage module, and after receiving the complete email sent by the delivery system and sending the complete email content to the terminal, it also includes:

[0032] The complete email is stored in a cache of the storage structure.

[0033] In a preferred example of the present application, it can be further configured to include:

[0034] When receiving repeated email access requests initiated by the terminal, detecting whether the email access request contains an email identifier, and if so, obtaining the complete email corresponding to the email identifier from the storage structure;

[0035] If the corresponding complete email is not obtained in the storage structure, a group email request is sent to the delivery system.

[0036] In a third aspect, the present application provides an email management system.

[0037] This application is achieved through the following technical solutions:

[0038] A mail management system, comprising:

[0039] Delivery system and mailbox system, wherein the delivery system includes a database, a delivery module and an SMS gateway, and the mailbox system includes an interface module and a storage module;

[0040] The database is used to store delivery tasks, each delivery task including a template identifier and a recipient list;

[0041] The delivery module is used to read the delivery tasks from the database and call the mailbox system to generate an email identifier for each delivery task;

[0042] The SMS gateway is used to send a short message containing a link to read the message to the recipient;

[0043] The interface module is used to generate an email identifier for a delivery task and to send a lightweight email to a recipient associated with the current delivery task;

[0044] The storage module is used to store complete emails.

[0045] Fourthly, this application is achieved through the following technical solutions:

[0046] A computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of any one of the above-mentioned mail management methods when executing the computer program.

[0047] In a fifth aspect, the present application provides a computer-readable storage medium.

[0048] This application is achieved through the following technical solutions:

[0049] A computer-readable storage medium stores a computer program, wherein the computer program implements the steps of any one of the above-mentioned mail management methods when executed by a processor.

[0050] In summary, compared with the prior art, the technical solutions provided by the embodiments of the present application have at least the following beneficial effects:

[0051] This application receives the delivery task submitted by the terminal and stores it in a database, wherein the delivery task includes a template identifier and a recipient list; initiates a task identifier allocation request to the mailbox system, and the task identifier allocation request is used to request the mailbox system to generate an email identifier for each delivery task; receives the email identifier sent by the mailbox system, and associates the email identifier with the delivery task and stores it in a database; sends a delayed delivery request to the mailbox system, and the delayed delivery request is used to instruct the mailbox system to send a lightweight email to the recipient associated with the delivery task; receives a group letter request sent by the mailbox system, and the group letter request is a group letter request issued by the mailbox system to the delivery system when it detects an email access request initiated by the recipient, and the group letter request includes an email identifier; searches the database according to the group letter request and the email identifier, generates a complete email, and sends the complete email to the mailbox system. The delivery system skips the message grouping process during the delivery phase and only sends lightweight emails to the recipients without assembling and sending complete emails. This can reduce the consumption of network bandwidth resources and storage space. When the recipient is reading the email, the mailbox system will call back the delivery system to group the email. By delaying the grouping of emails, unnecessary grouping and storage of unread emails is avoided, saving system resources and storage space. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 A flowchart of an email management method provided in one embodiment of the present application;

[0053] Figure 2A flowchart of an email management method provided in another embodiment of the present application;

[0054] Figure 3 A schematic diagram of the structure of an email management system provided in another embodiment of the present application;

[0055] Description of reference numerals:

[0056] Delivery system 1, mailbox system 2, database 1a, delivery module 1b, SMS gateway 1c, interface module 2a, storage module 2b. DETAILED DESCRIPTION

[0057] This specific embodiment is merely an explanation of the present application and is not a limitation of the present application. After reading this specification, those skilled in the art may make non-creative modifications to the present embodiment as needed, but as long as they are within the scope of the claims of the present application, they are protected by the patent law.

[0058] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0059] In this application, "indication" may include direct indication, indirect indication, explicit indication, implicit indication, and so on. When describing that a certain indication information indicates A, it can be understood that the indication information carries A, carries the identifier of A, carries B that is associated with A, carries the identifier of B that is associated with A, and so on. In other words, if the receiving side of a certain indication information can determine A based on the indication information, it can be described as the indication information indicating A, and the specific determination method is not limited. When it is understood that the indication information carries A, "indication" can be replaced with "includes". At this time, a statement similar to "send / receive indication information, the indication information indicates A" can be replaced with "send / receive A".

[0060] In addition, the term "and / or" in this application is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this application, unless otherwise specified, generally indicates that the related objects are in an "or" relationship.

[0061] In this application, the terms "first", "second", etc. are used to distinguish identical or similar items with substantially the same effects and functions. It should be understood that there is no logical or temporal dependency between "first", "second", and "nth", nor is there any limitation on the quantity and execution order.

[0062] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0063] Before introducing this application solution, we first explain the email delivery process, which involves the delivery system and mailbox system. The delivery system is responsible for generating email content and managing and scheduling email delivery tasks. The mailbox system connects to external servers and is responsible for email transmission and protocol interaction. For example, during a normal email delivery process, the delivery system generates email content, calls the mailbox system, delivers the original email, and the mailbox system pushes the email to the target email server via the SMTP protocol.

[0064] The embodiments of the present application are described in further detail below with reference to the accompanying drawings.

[0065] Reference Figure 1 As shown, the first exemplary embodiment of the present application provides a mail management method, which is applied to a delivery system and specifically includes:

[0066] S11: receiving a delivery task submitted by a terminal and storing it in a database. The delivery task includes a template identifier and a recipient list.

[0067] Specifically, it receives the delivery tasks submitted by the user through the terminal, and saves the received delivery tasks into the database. It should be noted that the delivery system receives one or more delivery tasks submitted by one or more terminals. A delivery task refers to a task that uses an email template to assemble a group of emails and send them to recipients. Each delivery task corresponds to a template identifier, which is used to specify the email template used by the delivery task. The recipient list is a collection of all target recipients corresponding to the delivery task. The recipient list records at least the target recipient's email address, name or other extensible information. At the same time, the delivery task can also include additional information for storing email sending behavior, such as the sending time, the number of retries for failed sending, etc.

[0068] S12: Initiate a task identifier allocation request to the mailbox system, where the task identifier allocation request is used to request the mailbox system to generate an email identifier for each delivery task.

[0069] Specifically, the delivery engine of the delivery system initiates a task identifier allocation request to the mailbox system, requesting the storage module of the mailbox system to generate an email identifier for each delivery task. The email identifier is a string used to locate the email content. Each delivery task corresponds to a globally unique email identifier.

[0070] S13: Receive the email identifier sent by the mailbox system, associate the email identifier with the delivery task and store it in a database.

[0071] Specifically, after receiving the mail identifier generated by the mailbox system, the delivery system associates the mail identifier with the delivery task, establishes a mapping relationship between the mail identifier and the delivery task, and stores the mapping relationship in a database of the delivery system.

[0072] The mail identifier is used by the delivery system to locate the mail content based on the mail identifier when the mailbox system sends a mail group request to the delivery system.

[0073] S14: Send a delayed delivery request to the mailbox system, where the delayed delivery request is used to instruct the mailbox system to send a lightweight email to the recipient associated with the delivery task.

[0074] In actual implementation, the delivery engine of the delivery system calls the delayed delivery interface of the mailbox system, sends a delayed delivery request through the delayed delivery interface, and delivers a lightweight email to each recipient corresponding to the current delivery task. The lightweight email includes the sender address, recipient address, email subject, and the email identifier corresponding to the delivery task.

[0075] It's also worth noting that when the mailbox system receives a delayed delivery request, it creates an email index for each recipient based on the email identifier corresponding to the current delivery task. This index is stored in the mailbox system's storage module for quick email retrieval. This index contains at least structured data such as the sender's address, recipient's address, email subject, and email sending time.

[0076] S15: Receive a group message request sent by the mailbox system. The group message request is a group message request sent by the mailbox system to the delivery system when detecting a mail access request initiated by the recipient. The group message request includes a mail identifier.

[0077] Specifically, the user logs in to the web client or clicks on the email in the client, and sends an email access request to the email server. The email server sends the email access request to the mailbox system. The mailbox system responds to the recipient's email access request and sends a group letter request to the delivery system.

[0078] S16: Search the database according to the group mail request and the mail identifier, generate a complete mail, and send the complete mail to the mailbox system.

[0079] Specifically, after the group message interface of the delivery system receives the group message request, it searches the database according to the email index and email identifier in the group message request, loads the corresponding delivery task and the template and user data corresponding to the delivery task from the database, fills the template with user data, assembles a complete email, and sends the complete email to the mailbox system.

[0080] In some embodiments, the mailbox system includes a task identifier allocation interface; wherein a task identifier allocation request is initiated to the mailbox system, and the task identifier allocation request is used to request the generation of an email identifier for each delivery task, specifically including:

[0081] The delivery system reads pending delivery tasks from the database;

[0082] The delivery system initiates a task identifier allocation request to the task identifier allocation interface of the mailbox system.

[0083] Specifically, the mailbox system is equipped with a task identifier allocation interface. This interface is configured as an HTTP interface for the delivery system to call. It can forward the delivery system's task identifier allocation request to the storage module, which generates a string used to locate the email content. After the email identifier is generated, it is sent to the delivery system through the task identifier allocation interface.

[0084] In some embodiments, sending a delayed delivery request to a mailbox system further includes:

[0085] Send a mail index generation request to the mailbox system, the mail index generation request is used to request the mail system to generate a mail index for each lightweight mail sent; receive the mail index sent by the mailbox system.

[0086] Specifically, an email index is created based on the data directory such as the sender address, recipient address, email subject, and email sending time transmitted by the delivery system.

[0087] In some embodiments, after sending the complete email to the mailbox system, the method further includes: receiving a sending result from the mailbox system;

[0088] When the sending result is successful, a text message carrying a link to read the message is sent to the recipient.

[0089] The SMS message carrying the email reading link can be used by the recipient to send an email access request to the email server via SMS.

[0090] The email management method proposed in this application omits the process of grouping complete emails during the delivery stage, and only delivers emails containing a small amount of information, shortening the delivery processing flow, reducing the transmission of email data, and improving the delivery speed of emails; when users need to check emails, emails are grouped for users who read the emails, avoiding large-scale centralized grouping, saving system computing power, and saving a lot of network bandwidth; avoiding redundant storage of a large number of similar emails, and only storing the email content of users who read the emails, saving a lot of storage resources.

[0091] Reference Figure 2 As shown, an embodiment of the present application provides an email management method, which is applied to a mailbox system and includes the following steps:

[0092] S21: Receive a task identifier allocation request from the delivery system, where the task identifier allocation request is used to request generation of a mail identifier for each delivery task.

[0093] Specifically, the mailbox system is equipped with a task identifier allocation interface, which is an HTTP interface that can be called by the delivery system. The mailbox system receives task identifier allocation requests sent by the delivery engine of the delivery system through the task identifier allocation interface. The mailbox system's storage module generates an email identifier for each delivery task. The email identifier is in the form of a string used to locate the email content.

[0094] S22: Sending a mail identifier to the delivery system. The mail identifier is used to query the corresponding mail content when grouping mails.

[0095] Specifically, after the mailbox system generates the mail identifier, it returns the mail identifier to the delivery system through the task identifier allocation interface. The delivery system stores the mail identifier in a database.

[0096] S23: Receive the delayed delivery request sent by the delivery system, and send a lightweight email to the recipient associated with the delivery task.

[0097] Specifically, the mailbox system is equipped with a delayed delivery interface that can be called by the delivery system. The mailbox system receives a delayed delivery request sent by the delivery system through the delayed delivery interface, parses the delayed delivery request, and constructs a lightweight email based on the parsed result. The lightweight email includes at least the sender's address, the recipient's address, the email subject, and the email identifier corresponding to the delivery task.

[0098] It should be noted that after delivering the lightweight email, the mailbox system generates an email index for the lightweight email and stores the email index in the storage module.

[0099] S24: The receiving terminal sends a mail access request and initiates a message grouping request to the delivery system. The message grouping request is used to instruct the delivery system to generate a complete mail.

[0100] When the mailbox system receives an email access request from a user via a mail reading link or a web client, it initiates a grouping request to the delivery system. This grouping request requests the delivery system to assemble emails for the recipients specified in the grouping request. It should be noted that the mail server receives the email access request initiated by the user via the terminal and then forwards it to the mailbox system.

[0101] S25: Receive the complete email sent by the delivery system and send the complete email content to the terminal.

[0102] The mailbox system receives the complete email sent by the delivery system through the group message interface and sends the complete email to the user for review.

[0103] In some embodiments, the mailbox system includes a storage module that receives a complete email sent by a delivery system and, after sending the complete email to a terminal, further includes:

[0104] Keep the complete message in a cache of storage structures.

[0105] The mailbox system has initiated an email access request for the user and saves the assembled complete email in the cache of the storage structure.

[0106] In some embodiments, further comprising:

[0107] When receiving repeated email access requests initiated by the terminal, detecting whether the email access request contains an email identifier, and if so, obtaining the complete email corresponding to the email identifier from the storage structure;

[0108] If the corresponding complete email is not obtained in the storage structure, a group email request is sent to the delivery system.

[0109] Specifically, for email access requests repeatedly initiated by the terminal, such as the second email access request or the third email access request, the mailbox system first checks whether the email access request contains an email identifier. If it contains an email identifier, it searches the cache of the storage module based on the email identifier to see whether there is a corresponding complete email. If a complete email is saved, the complete email in the cache is directly sent to the user for viewing.

[0110] If the complete email cannot be found in the cache, a group email request is sent to the delivery system. This can avoid duplicate access when the user accesses the email multiple times and reduce network bandwidth consumption.

[0111] Reference Figure 3As shown, an exemplary embodiment of the present application provides a mail management system, which specifically includes a delivery system 1 and a mailbox system 2, wherein the delivery system 1 includes a database 1a, a delivery module 1b and an SMS gateway 1c, and the mailbox system 2 includes an interface module 2a and a storage module 2b;

[0112] Database 1a, used to store delivery tasks, each delivery task includes a template identifier and a recipient list;

[0113] Delivery module 1b is used to read the delivery tasks from the database and call the mailbox system to generate an email identifier for each delivery task;

[0114] SMS gateway 1c, used to send SMS containing a link to read the message to the recipient;

[0115] Interface module 2a, used to generate an email identifier for a delivery task and to send a lightweight email to a recipient associated with the current delivery task;

[0116] The storage module 2b is used to store complete emails.

[0117] The working process, working details and technical effects of the mail transmission system provided in this embodiment can be found in the embodiment of the mail management method above, and will not be described in detail here.

[0118] An embodiment of the present application provides a computer device, which may include a processor, memory, a network interface, and a database connected via a system bus. The processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The network interface of the computer device is configured to communicate with an external terminal via a network connection. When the computer program is executed by the processor, the processor performs the steps of the email management method described in any of the above embodiments.

[0119] The working process, working details and technical effects of the computer device provided in this embodiment can be found in the embodiment of the email management method above, and will not be described in detail here.

[0120] The present application provides a computer-readable storage medium having a computer program stored thereon. When executed by a processor, the computer program implements the steps of the email management method described in any of the above embodiments. The computer-readable storage medium refers to a medium for storing data, and may include, but is not limited to, a floppy disk, an optical disk, a hard disk, a flash memory, a USB flash drive, and / or a memory stick. The computer may be a general-purpose computer, a dedicated computer, a computer network, or other programmable device.

[0121] The working process, working details and technical effects of the computer-readable storage medium provided in this embodiment can be found in the embodiment of the email management method above, and will not be described in detail here.

[0122] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiments can be implemented by instructing the relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).

[0123] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0124] Those skilled in the art will clearly understand that for the sake of convenience and brevity of description, the division of the above-mentioned functional units and modules is only used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the system described in this application is divided into different functional units or modules to complete all or part of the functions described above.

Claims

1. A mail management method, characterized in that: Applied to a delivery system, the method comprises: Receiving a delivery task submitted by a terminal and storing it in a database, wherein the delivery task includes a template identifier and a recipient list; Initiate a task identifier allocation request to the mailbox system. The task identifier allocation request is used to request the mailbox system to generate an email identifier for each delivery task; Receiving the mail identifier sent by the mailbox system, and associating the mail identifier with the delivery task and storing it in a database; Sending a delayed delivery request to the mailbox system, wherein the delayed delivery request is used to instruct the mailbox system to send a lightweight email to the recipient associated with the delivery task; Receive a mail grouping request sent by the mailbox system. The mail grouping request is a mail grouping request sent by the mailbox system to the delivery system when the mailbox system detects a mail access request initiated by the recipient. The mail grouping request includes a mail identifier. The database is searched according to the group mail request and the mail identifier, a complete mail is generated, and the complete mail is sent to the mailbox system.

2. The mail management method according to claim 1, wherein: The mailbox system includes a task identifier allocation interface; the task identifier allocation request is initiated to the mailbox system, and the task identifier allocation request is used to request the mailbox system to generate an email identifier for each delivery task, including: The delivery system reads pending delivery tasks from the database; The delivery system initiates a task identifier allocation request to the task identifier allocation interface of the mailbox system.

3. The mail management method according to claim 1, wherein: The sending of the delayed delivery request to the mailbox system further includes: Sending a mail index generation request to the mailbox system, wherein the mail index generation request is used to request the mail system to generate a mail index for each lightweight mail that has been sent; Receive the email index sent by the mailbox system.

4. The mail management method according to claim 3, wherein: Also includes: Receiving the sending result of the mailbox system; When the sending result is successful, a text message carrying a link to read the message is sent to the recipient.

5. A mail management method, characterized in that: Applied to a mailbox system, the method includes: Receive a task identifier allocation request from the delivery system, wherein the task identifier allocation request is used to request generation of a mail identifier for each delivery task; Sending a mail identifier to the delivery system, where the mail identifier is used to query the corresponding mail content when assembling mail; Receive delayed delivery requests from the delivery system and send lightweight emails to recipients associated with the delivery task; Receiving the mail access request from the terminal, initiating a group mail request to the delivery system, wherein the group mail request is used to instruct the delivery system to generate a complete mail; Receive a complete email sent by the delivery system, and send the complete email to the terminal.

6. The mail management method according to claim 5, characterized in that: The mailbox system includes a storage module, which receives complete emails sent by the delivery system and sends the complete email content to the terminal, and further includes: The complete email is stored in a cache of the storage structure.

7. The mail management method according to claim 6, characterized in that: Also includes: When receiving repeated email access requests initiated by the terminal, detecting whether the email access request contains an email identifier, and if so, obtaining the complete email corresponding to the email identifier from the storage structure; If the corresponding complete email is not obtained in the storage structure, a group email request is sent to the delivery system.

8. A mail management system, characterized in that: include: Delivery system and mailbox system, wherein the delivery system includes a database, a delivery module and an SMS gateway, and the mailbox system includes an interface module and a storage module; The database is used to store delivery tasks, each delivery task including a template identifier and a recipient list; The delivery module is used to read the delivery tasks from the database and call the mailbox system to generate an email identifier for each delivery task; The SMS gateway is used to send a short message containing a link to read the message to the recipient; The interface module is used to generate an email identifier for a delivery task and is also used to send a lightweight email to a recipient associated with the current delivery task; The storage module is used to store complete emails.

9. A computer device, characterized in that: The method comprises a memory, a processor and a computer program stored in the memory, wherein the processor executes the computer program to implement the steps of the method according to any one of claims 1 to 4, or is used to execute the steps of the method according to any one of claims 5 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of the method according to any one of claims 1 to 4, or is used to execute the steps of the method according to any one of claims 5 to 7.

Images