Email processing method and device, electronic equipment, computer readable storage medium and computer program product

Abstract

The application provides an email processing method and device, electronic equipment, computer readable storage medium and computer program product; the method comprises the following steps: in response to an email sending trigger operation, sending an email to a plurality of selected addressee objects; in response to the email being in a sent state, displaying first prompt information, wherein the first prompt information comprises a first viewing control; in response to a trigger operation for the first viewing control, displaying the plurality of addressee objects and the delivery status of the email corresponding to each addressee object respectively. Through the application, the viewing efficiency of the delivery status of the email corresponding to the plurality of addressee objects in the group sending scenario can be improved.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to an email processing method, apparatus, electronic device, computer-readable storage medium, and computer program product. Background Technology

[0002] Email is one of the most important applications of Internet services. Currently, the main protocols used for sending and receiving emails are Simple Mail Transfer Protocol (SMPP), Postal Protocol version 3 (PLP 3), and Internet Messaging Access Protocol (IMP) version 4 (IMAP 4). Certain extensions of SMPP and IMP 4 can be used for sending emails (transferring emails from the sender's terminal to the email server) and for transmitting emails over a network (transferring emails from one server to another). PLP 3 and IMP 4 can be used for receiving emails (transferring emails from the email server to the recipient's terminal). These protocols ensure that users can successfully deliver emails to their intended recipients.

[0003] However, in the solutions provided by related technologies, users need to manually check the delivery status of each email for each recipient individually, which is especially in the case of mass emails with multiple recipients, resulting in low efficiency for users to check the delivery status of emails. Summary of the Invention

[0004] This application provides an email processing method, apparatus, electronic device, computer-readable storage medium, and computer program product, which can improve the efficiency of viewing the delivery status of emails for multiple recipients in a mass mailing scenario.

[0005] The technical solution of this application embodiment is implemented as follows:

[0006] This application provides an email processing method, including:

[0007] In response to an email sending trigger action, send emails to multiple selected recipients;

[0008] In response to the email being in a sent state, a first prompt message is displayed, wherein the first prompt message includes a first viewing control;

[0009] In response to a trigger operation on the first viewing control, the plurality of recipient objects and the delivery status of the email corresponding to each recipient object are displayed.

[0010] This application provides an email processing apparatus, including:

[0011] The sending module is used to send emails to multiple selected recipients in response to an email sending trigger operation.

[0012] The display module is configured to display a first prompt message in response to the email being in a sent state, wherein the first prompt message includes a first viewing control;

[0013] The display module is further configured to, in response to a trigger operation on the first viewing control, display the plurality of recipient objects and the delivery status of the email corresponding to each recipient object.

[0014] This application provides an electronic device, including:

[0015] Memory is used to store executable instructions for a computer;

[0016] The processor, when executing computer-executable instructions stored in the memory, implements the email processing method provided in the embodiments of this application.

[0017] This application provides a computer-readable storage medium storing computer-executable instructions for implementing the email processing method provided in this application when executed by a processor.

[0018] This application provides a computer program product, including a computer program or computer executable instructions, which, when executed by a processor, implements the email processing method provided in this application.

[0019] The embodiments of this application have the following beneficial effects:

[0020] After sending emails to multiple recipients, a first notification message is displayed. Upon receiving a trigger operation on the first viewing control included in the first notification message, the multiple recipients and the delivery status of the emails corresponding to each recipient are displayed. In this way, users do not need to manually check the delivery status of the emails corresponding to each recipient one by one, which improves the efficiency of viewing the delivery status of emails corresponding to multiple recipients in the mass mailing scenario. Attached Figure Description

[0021] Figure 1 This is a schematic diagram of the architecture of the email processing system 100 provided in an embodiment of this application;

[0022] Figure 2 This is a schematic diagram of the structure of the electronic device 600 provided in the embodiments of this application;

[0023] Figure 3 This is a first flowchart illustrating the email processing method provided in this application embodiment;

[0024] Figure 4 This is a second flowchart illustrating the email processing method provided in the embodiments of this application;

[0025] Figure 5 This is a schematic diagram of the third process of the email processing method provided in the embodiments of this application;

[0026] Figure 6A This is a schematic diagram of a first application scenario of the email processing method provided in this application embodiment;

[0027] Figure 6B This is a schematic diagram of a second application scenario of the email processing method provided in the embodiments of this application;

[0028] Figure 7 This is a schematic diagram of a third application scenario of the email processing method provided in the embodiments of this application;

[0029] Figure 8 This is a schematic diagram of the fourth application scenario of the email processing method provided in the embodiments of this application;

[0030] Figure 9 This is a schematic diagram of the fifth application scenario of the email processing method provided in the embodiments of this application;

[0031] Figure 10 This is a schematic diagram of the sixth application scenario of the email processing method provided in the embodiments of this application;

[0032] Figure 11 This is a schematic diagram of the seventh application scenario of the email processing method provided in the embodiments of this application;

[0033] Figure 12A This is a schematic diagram of the eighth application scenario of the email processing method provided in the embodiments of this application;

[0034] Figure 12B This is a schematic diagram of the ninth application scenario of the email processing method provided in the embodiments of this application;

[0035] Figure 13A This is a schematic diagram of the tenth application scenario of the email processing method provided in the embodiments of this application;

[0036] Figure 13B This is a schematic diagram of the eleventh application scenario of the email processing method provided in the embodiments of this application;

[0037] Figure 14 This is a schematic diagram of the twelfth application scenario of the email processing method provided in the embodiments of this application;

[0038] Figure 15This is a schematic diagram of the fourth process of the email processing method provided in the embodiments of this application. Detailed Implementation

[0039] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0040] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0041] It is understood that in the embodiments of this application, data such as user information are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with relevant laws, regulations and standards.

[0042] In the following description, the terms “first, second, ...” are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that “first, second, ...” may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

[0043] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0044] Before providing a further detailed description of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained, and the nouns and terms involved in the embodiments of this application shall be interpreted as follows.

[0045] 1) Responding to: used to indicate the conditions or states on which the operation is performed depends. When the conditions or states on which it depends are met, one or more operations can be performed in real time or with a set delay. Unless otherwise specified, there is no restriction on the order in which the multiple operations are performed.

[0046] 2) Email (Electronic Mail): This is a communication method that uses electronic means to exchange information and is the most widely used service on the Internet. Through the network's email system, users can contact internet users anywhere in the world at a very low cost and very fast speed. Emails can be in various forms, including text, images, and audio.

[0047] In implementing the embodiments of this application, the applicant discovered that, for email information viewing scenarios, related technologies suffer from insufficient real-time prompts and potentially incorrect prompts. For example, users (i.e., senders) cannot efficiently view the delivery status of emails for each recipient (e.g., recipients, CC recipients, and BCC recipients), as some recipients may have successfully received their emails while others have failed to receive them for various reasons. Furthermore, the prompts regarding whether a recipient has rejected an email are delayed and require users to manually check their inbox, resulting in poor correlation with the original email and making it difficult for users to determine which sent email a rejected email corresponds to. Similarly, recall operations suffer from the same problems; users can only rely on the notification email after the recall is completed to determine the recall status, which is delayed and may not correspond to the original email. The above situation becomes more complex when sending and recall operations overlap. In addition, the applicant also discovered that related technologies cannot determine which folder of the recipient the email was delivered to.

[0048] In view of this, embodiments of this application provide an email processing method, apparatus, electronic device, computer-readable storage medium, and computer program product. On the one hand, it can provide users with a clear view, helping them to confirm the progress of each recipient, CC recipient, and BCC recipient, and to confirm whether the recall operation was recalled after reaching the recipient's email address, or whether it was recalled during the sending process, i.e., it did not reach the recipient's email address at all. On the other hand, it can help senders confirm that the email has been correctly delivered to the recipient's inbox, rather than being blocked by the system as spam and placed in the spam folder. The electronic device provided in the embodiments of this application will be described below. The electronic device provided in the embodiments of this application can be implemented as a terminal device, or implemented by a terminal device and a server in collaboration. The following description uses the email processing method provided in the embodiments of this application implemented by a server and a terminal device as an example.

[0049] For example, see Figure 1 , Figure 1 This is a schematic diagram of the architecture of the email processing system 100 provided in this application embodiment, as shown below. Figure 1As shown, the email processing system 100 provided in this application embodiment includes: a server 200, a network 300, a terminal device 400, and terminal devices 500-1 to 500-N (N is a positive integer greater than 1). The server 200 can be an email server, the network 300 can be a local area network or a wide area network, or a combination of both. The terminal device 400 is the terminal device associated with the sender of the email (e.g., user 1). A client 410 runs on the terminal device 400. The client 410 can be a dedicated email client or an instant messaging client with integrated email functionality. The terminal device 500-1 is the terminal device associated with the recipient of the email (e.g., user 2). A client 510-1 runs on the terminal device 500-1. The client 510-1 can be the same type of client as client 410 or a different type of client. Terminal device 500-N is the terminal device associated with email recipient N. Client 510-N runs on terminal device 500-N. Client 510-N can be the same type of client as client 410, or it can be a different type of client.

[0050] In some embodiments, the sender can select multiple recipients to be sent to in the email sending interface presented by the client 410 (e.g., assuming 10 recipients). Figure 1The client 410 sends an email to the server 200 via network 300 when it receives a click from the sender on the send control displayed in the email sending interface (recipients 1 to N). When the server 200 successfully receives the email from the client 410, it can deliver the email to each of the recipients (recipients 1 to N) according to their respective email addresses (i.e., send the received email to the terminal devices 500-1 to 500-N associated with each recipient). Simultaneously, the server 200 can send a notification message to the client 410 to inform it that the email has been successfully received. Upon receiving the notification message from the server 200, the client 410 can display a first prompt message to indicate that the email has been successfully sent. The initial notification message may also display a first viewing control. When client 410 receives a click operation from the sender on the first viewing control, it can send a delivery status query request for the email to server 200. After receiving the delivery status query request from client 410, server 200 can send the delivery result of the email to client 410. The delivery result can include the delivery status of the emails corresponding to recipients 1 to N respectively. After receiving the delivery result returned by server 200, client 410 can display the avatars or nicknames corresponding to recipients 1 to N respectively, as well as the delivery status of the email for each recipient. This effectively improves the efficiency of viewing the delivery status of emails for multiple recipients in mass mailing scenarios.

[0051] It should be noted that, Figure 1 The server 200 can be a standalone physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The terminal devices (including terminal devices 400, 500-1 to 500-N) can be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, in-vehicle terminals, etc., but are not limited to these. The terminal devices (including terminal devices 400, 500-1 to 500-N) and server 200 can be directly or indirectly connected via wired or wireless communication, which is not limited in this embodiment.

[0052] In some embodiments, the terminal device can also implement the email processing method provided in this application by running various computer-executable instructions or computer programs. For example, computer-executable instructions can be microprogram-level commands, machine instructions, or software instructions. Computer programs can be native programs or software modules in an operating system; they can be native applications (APPs), i.e., programs that need to be installed in the operating system to run, such as dedicated email APPs; or they can be applets that can be embedded in any APP (e.g., instant messaging APPs), i.e., programs that only need to be downloaded to a browser environment to run. In summary, the aforementioned computer-executable instructions can be any form of instruction, and the aforementioned computer programs can be any form of application, module, or plugin.

[0053] The structure of the electronic device provided in the embodiments of this application will be further described below. Taking the electronic device as a terminal device as an example, see... Figure 2 , Figure 2 This is a schematic diagram of the structure of the electronic device 600 provided in the embodiments of this application. Figure 2 The illustrated electronic device 600 includes at least one processor 610, a memory 650, at least one network interface 620, and a user interface 630. The various components in the electronic device 600 are coupled together via a bus system 640. It is understood that the bus system 640 is used to implement communication between these components. In addition to a data bus, the bus system 640 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in… Figure 2 The general labeled all buses as Bus System 640.

[0054] The processor 610 can be an integrated circuit chip with signal processing capabilities, such as a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor, etc.

[0055] User interface 630 includes one or more output devices 631 that enable the presentation of media content, including one or more speakers and / or one or more visual displays. User interface 630 also includes one or more input devices 632, including user interface components that facilitate user input, such as a keyboard, mouse, microphone, touch screen display, camera, other input buttons and controls.

[0056] The memory 650 may be removable, non-removable, or a combination thereof. Exemplary hardware devices include solid-state storage, hard disk drives, optical disk drives, etc. The memory 650 may optionally include one or more storage devices physically located away from the processor 610.

[0057] The memory 650 may include volatile memory or non-volatile memory, or both. The non-volatile memory may be read-only memory (ROM), and the volatile memory may be random access memory (RAM). The memory 650 described in this application embodiment is intended to include any suitable type of memory.

[0058] In some embodiments, memory 650 is capable of storing data to support various operations, examples of which include programs, modules, and data structures or subsets or supersets thereof, as illustrated below.

[0059] Operating system 651 includes system programs for handling various basic system services and performing hardware-related tasks, such as the framework layer, core library layer, driver layer, etc., for implementing various basic business functions and handling hardware-based tasks;

[0060] The network communication module 652 is used to reach other computing devices via one or more (wired or wireless) network interfaces 620, exemplary network interfaces 620 including: Bluetooth, WiFi, and Universal Serial Bus (USB), etc.

[0061] Presentation module 653 is configured to enable the presentation of information (e.g., a user interface for operating peripheral devices and displaying content and information) via one or more output devices 631 (e.g., a display screen, a speaker, etc.) associated with user interface 630;

[0062] The input processing module 654 is used to detect and translate one or more user inputs or interactions from one or more input devices 632.

[0063] In some embodiments, the apparatus provided in this application can be implemented in software. Figure 2An email processing device 655 stored in memory 650 is shown. This device can be software in the form of programs and plug-ins, and includes the following software modules: a sending module 6551, a display module 6552, a switching module 6553, a classification module 6554, a disabling module 6555, an identification module 6556, a receiving module 6557, and a query module 6558. These modules are logically connected and can therefore be arbitrarily combined or further separated according to the functions implemented. It should be noted that... Figure 2 For ease of explanation, all the above modules are shown at once, but this should not be construed as excluding the implementation of the email processing device 655 which may only include the sending module 6551 and the display module 6552. The functions of each module will be described below.

[0064] The email processing method provided in this application will be specifically described below with reference to the exemplary application and implementation of the terminal device provided in the embodiments of this application.

[0065] For example, see Figure 3 , Figure 3 This is a first flowchart illustrating the email processing method provided in this application embodiment, which will be combined with... Figure 3 The steps shown are explained.

[0066] It should be noted that, Figure 3 The method illustrated can be executed by various forms of computer programs running on the terminal device, and is not limited to a client. For example, it can also be the operating system, software module, script, and applet mentioned above. Therefore, the client-side examples used below should not be considered as limiting the embodiments of this application. Furthermore, for ease of description, no specific distinction will be made between the terminal device and the client running on the terminal device below.

[0067] In step 101, in response to the email sending trigger operation, an email is sent to the selected multiple recipients.

[0068] Here, the recipient can be an individual, team, company, etc.

[0069] In some embodiments, taking an enterprise instant messaging client as an example, the enterprise instant messaging client can integrate an email function module. When a user triggers an operation on the email entry point in the enterprise instant messaging client, an email interface can be displayed, which may include a compose email entry. Upon receiving a user's trigger operation on the compose email entry, an email editing interface can be displayed. The email editing interface may display a recipient field, where the user can enter multiple recipients (e.g., multiple recipients separated by specific symbols) in the corresponding input boxes. For example, the user can select recipients from a group chat, external contacts, the enterprise address book, or email contacts. After selecting recipients, the user can edit the email subject and body and click the send control displayed in the email editing interface. After receiving the user's click on the send control, the enterprise instant messaging client will send the edited email to the email server, which may contain the email addresses corresponding to the multiple recipients selected by the user.

[0070] It should be noted that a "CC / BCC" button can also be displayed after the input box corresponding to the recipient field. When the user clicks the "CC / BCC" button, the input boxes corresponding to the CC and BCC fields can be displayed. The user can enter the CC recipients in the CC field input box, or the BCC recipients in the BCC field input box. That is to say, the multiple recipients in this embodiment can be not only recipients, but also CC recipients or BCC recipients of emails, etc. This embodiment does not specifically limit this. In this way, the user can not only clearly know the delivery status of the emails corresponding to each recipient, but also the delivery status of the emails corresponding to each CC recipient and BCC recipient.

[0071] In other embodiments, after sending emails to multiple selected recipients, the following process can also be performed: receiving the email identifier of the email, so that the delivery result of the email can be queried based on the email identifier, wherein the delivery result can include the delivery status of the emails corresponding to multiple recipients respectively.

[0072] For example, continuing with the enterprise instant messaging client as an example, after the enterprise instant messaging client sends a user-edited email to the email server, the email server can generate a unique email identifier (ID, IDentity document) for that email and return the generated email ID to the enterprise instant messaging client. Thus, when the client subsequently receives a click operation from the user on the first view control included in the initial prompt message, the enterprise instant messaging client can send a delivery status query request including the email ID to the email server, allowing the email server to query the delivery result of the email based on the email ID carried in the delivery status query request.

[0073] In step 102, in response to the email being in a sent state, a first notification message is displayed.

[0074] Here, the first prompt message may include the first view control.

[0075] In some embodiments, continuing to take an enterprise instant messaging client as an example, after receiving an email sent by the enterprise instant messaging client, the email server can send a notification message to the enterprise instant messaging client indicating that the email has been successfully received. At this time, a first prompt message (such as "sent successfully" or "email sent successfully") can be displayed in the email interface presented by the enterprise instant messaging client. The first prompt message can also display a first viewing control, which can be used to view the delivery result of the email. The delivery result can include the delivery status of emails corresponding to multiple recipients.

[0076] In step 103, in response to a trigger operation on the first viewing control, multiple recipient objects and the delivery status of the emails corresponding to each recipient object are displayed.

[0077] In some embodiments, before displaying multiple recipients and the delivery status of the email corresponding to each recipient, the following process may be performed: querying the delivery result of the email based on the email identifier, wherein the delivery result includes the delivery status of the email corresponding to each recipient.

[0078] For example, continuing with the enterprise instant messaging client as the example, when the client receives a click operation from the user on the first view control included in the first prompt information, the enterprise instant messaging client can send a delivery status query request carrying the email ID to the email server. Upon receiving the delivery status query request from the enterprise instant messaging client, the email server can first extract the email ID from the received request, and then query the delivery result of the corresponding email based on that email ID. The delivery result can include the delivery status of multiple recipients of the email. Subsequently, the email server can send the queried delivery result to the enterprise instant messaging client. After receiving the email delivery result returned by the email server, the enterprise instant messaging client can display the multiple recipients of the email (e.g., displaying the avatars or nicknames of each recipient) and the delivery status of the email for each recipient. In this way, the user can view the delivery status of emails for multiple recipients at once, without having to manually check each recipient individually, greatly reducing the user's workload and effectively improving viewing efficiency.

[0079] In some embodiments, the above-mentioned display of multiple recipients and the delivery status of emails corresponding to each recipient can be achieved by: displaying multiple recipient identifiers (e.g., recipient avatars, nicknames, etc.) corresponding to each recipient, and displaying the delivery identifier of the email around each recipient identifier (e.g., on the right or below), wherein the delivery identifier can be used to characterize the delivery status of the email to the recipient corresponding to the recipient identifier.

[0080] For example, taking 10 recipients as an example, the email reading interface can display the avatars of each of the 10 recipients. For instance, each recipient's avatar can occupy one row in the reading interface. In addition, a delivery indicator of the email sent by the sender can be displayed to the right of each recipient's avatar. This delivery indicator can be used to indicate the delivery status of the email to the recipient corresponding to that avatar. In this way, the sender can view the delivery status of the email for each recipient at once through the email reading interface, without having to manually check each recipient individually, reducing the sender's workload and effectively improving the efficiency of viewing the delivery status of emails.

[0081] In some embodiments, following the above, the above-mentioned display of multiple recipient identifiers corresponding to multiple recipient objects can be achieved in the following way: displaying multiple recipient identifiers corresponding to multiple recipient objects in the order of delivery failure, delivery in progress, and delivery success.

[0082] For example, let's take 10 recipients as an example, named recipients 1 to 10. The email delivery results returned by the email server include the delivery status of the emails for each of these 10 recipients. For instance, suppose the delivery status for recipients 1 to 5 is "delivered successfully" (meaning the emails have been successfully delivered to the 5 email addresses corresponding to recipients 1 to 5), and the delivery status for recipients 6 to 8 is "delivered unsuccessfully" (meaning the emails have been successfully delivered to the 5 email addresses corresponding to recipients 1 to 5). If the sub-email is bounced from the email addresses of recipients 6 to 8, and the delivery status of recipients 9 and 10 is "delivering", then the email reader will display the 10 recipient avatars in the following order: recipient 6, recipient 7, recipient 8, recipient 9, recipient 10, recipient 1, recipient 2, recipient 3, recipient 4, and recipient 5. This allows the email sender to prioritize viewing the recipients whose emails failed to be delivered and take appropriate action.

[0083] In other embodiments, the above-mentioned display of multiple recipient identifiers corresponding to multiple recipient objects can also be achieved by displaying multiple recipient identifiers corresponding to multiple recipient objects in descending order of interaction frequency with the sender of the email.

[0084] For example, taking 10 recipients as recipients 1 to 10, after the email sender clicks the first view control included in the first prompt message, the client (such as a dedicated email client or enterprise instant messaging client) can obtain the interaction frequency between the email sender and these 10 recipients over a period of time (e.g., the interaction frequency over the past six months). Then, it displays the recipient avatars of each of the 10 recipients in the email reading interface in descending order of interaction frequency. In other words, the more frequently a recipient interacts with the email sender, the higher their avatar will appear in the reading interface. This allows the email sender to prioritize viewing the delivery status of recipients they have interacted with frequently (who may be recipients the sender is paying close attention to).

[0085] In some embodiments, the above-mentioned display of multiple recipient identifiers corresponding to multiple recipients can also be achieved by displaying multiple recipient identifiers corresponding to multiple recipients in descending order of the degree of correlation between the recipient's job title and the email content.

[0086] For example, taking a group of 10 recipients (recipient 1 to recipient 10), when the sender clicks the first view control in the initial notification, the client (e.g., a dedicated email client or an enterprise instant messaging client) can calculate the correlation between the email content and the job titles of these 10 recipients. Then, in descending order of correlation, the client can display the 10 recipient avatars or nicknames in the email reading interface. In other words, the more relevant a recipient is to the email content, the higher their avatar will appear in the reading interface. This allows the email sender to prioritize viewing the delivery status of recipients closely related to the email content.

[0087] In some embodiments, following the above, the delivery status may include: successful delivery, failed delivery, and in progress delivery. Correspondingly, the aforementioned delivery identifier may include: a first delivery identifier indicating successful email delivery, a second delivery identifier indicating failed email delivery, and a third delivery identifier indicating that the email is being delivered. The above-mentioned display of email delivery identifiers around each recipient identifier can be achieved by performing the following processing for each recipient: When an email is successfully delivered to the recipient's email address, a first delivery identifier is displayed around the recipient identifier corresponding to that recipient; when an email is bounced from the recipient's email address, a second delivery identifier is displayed around the recipient identifier corresponding to that recipient; when an email is being delivered to the recipient's email address, a third delivery identifier is displayed around the recipient identifier corresponding to that recipient.

[0088] For example, taking Recipient 1 out of multiple recipients as an example, when an email is successfully delivered to Recipient 1's email address, a first delivery indicator indicating successful delivery can be displayed to the right of Recipient 1's identifier (such as Recipient 1's avatar or nickname). When an email is bounced from Recipient 1's email address for some reason, a second delivery indicator indicating delivery failure can be displayed to the right of Recipient 1's avatar or nickname. When an email is being delivered to Recipient 1's email address, a third delivery indicator indicating that the email is being delivered can be displayed to the right of Recipient 1's avatar or nickname. In this way, the sender of the email can clearly understand the delivery status of the email for Recipient 1 based on the delivery indicators displayed to the right of Recipient 1's avatar or nickname, and can then perform subsequent processing accordingly.

[0089] In other embodiments, following the examples above, the following processing can also be performed: in response to a triggering operation for a target recipient identifier, an email delivery details interface for the recipient corresponding to the target recipient identifier is displayed, wherein the target recipient identifier is a recipient identifier with a second delivery identifier displayed around it (i.e., the recipient identifier corresponding to the recipient for whom email delivery failed), and the email delivery details interface includes the reason why the email failed to be delivered to the recipient corresponding to the target recipient identifier.

[0090] For example, taking 10 recipients as an example, let's say they are recipients 1 to 10. In the client's email reading interface, 10 avatars corresponding to these 10 recipients can be displayed one by one. To the right of each avatar, a delivery indicator representing the delivery status of the email can also be displayed. For example, taking recipient 3 as an example, if the email is bounced from recipient 3's email address for some reason, a second delivery indicator representing the email delivery failure can be displayed to the right of recipient 3's avatar. When the email sender sees a second delivery indicator displayed to the right of recipient 3's avatar, they know the email delivery to recipient 3 failed. At this point, the email sender can click on recipient 3's avatar. Upon receiving this click, the sender will be redirected to the email delivery details page for recipient 3. This page will display the reason for the delivery failure, allowing the sender to take further action based on the cause of the failure.

[0091] In some embodiments, following the above example, the following processing can also be performed: when the email is successfully delivered to the email address of the target recipient, the third delivery identifier displayed around the recipient identifier corresponding to the target recipient will be switched to the first delivery identifier; when the email is bounced from the email address of the target recipient, the third delivery identifier displayed around the recipient identifier corresponding to the target recipient will be switched to the second delivery identifier, wherein the target recipient is the recipient among multiple recipients whose email delivery status is "delivering".

[0092] For example, taking recipient 1 out of multiple recipients as an example, assuming the email is currently being delivered to recipient 1's email address, a third delivery identifier indicating that the email is being delivered can be displayed to the right of recipient 1's avatar or nickname. At this time, the email server can also monitor recipient 1. When the email server subsequently detects that the email has been successfully delivered to recipient 1's email address, it can send a delivery success notification message to the client. The client can then switch the third delivery identifier displayed to the right of recipient 1's avatar or nickname to a first delivery identifier indicating successful email delivery. Conversely, when the email server subsequently detects that the email has bounced from recipient 1's email address, it can send a delivery failure notification message to the client. The client can then switch the third delivery identifier displayed to the right of recipient 1's avatar or nickname to a second delivery identifier indicating failed email delivery. In this way, by switching the delivery identifier, the email sender can know the final delivery status of the email corresponding to recipient 1, thus facilitating subsequent processing by the email sender.

[0093] In some embodiments, the above-mentioned display of multiple recipients and the delivery status of emails corresponding to each recipient can also be achieved in the following ways: displaying the sender identifier (e.g., the sender's avatar or nickname) corresponding to the sender of the email, and centrally displaying multiple recipient identifiers (e.g., the recipient's avatar or nickname) corresponding to multiple recipients one-to-one, wherein when the number of multiple recipient identifiers is greater than a number threshold, some of the recipient identifiers are collapsed; in response to a trigger operation on the sender identifier, displaying the email delivery details interface, wherein the delivery details interface can include the delivery status of emails corresponding to each recipient, for example, the delivery details interface can display multiple email addresses (i.e., inboxes) corresponding to multiple recipients, and the delivery status of emails corresponding to each recipient.

[0094] For example, taking a message with 10 recipients (recipients 1 to 10), when the sender clicks the first view control in the initial notification, a message reading interface can be displayed. This interface shows the sender's avatar and name (e.g., the sender's name). Additionally, the names of the 10 recipients can be displayed one-to-one after the sender's name. Alternatively, some recipients' names can be displayed after the sender's name, with the remaining names folded (e.g., using ellipses) to avoid interfering with the sender's browsing experience due to displaying too many recipient names. When the sender clicks on the sender's avatar upon receiving the email, the email delivery details screen can be displayed. This screen shows the delivery status of the emails for each of the 10 recipients. By centrally displaying multiple recipient identifiers and providing a secondary interface to show the delivery status of each recipient's email, the required display area is effectively saved. Furthermore, the delivery status of each recipient's email is only displayed when the sender needs to view the details, significantly improving the user experience.

[0095] In other embodiments, following the above, the above-described email delivery details interface can be implemented in the following way: displaying an email delivery details interface, wherein the delivery details interface may include a second viewing control; in response to a trigger operation on the second viewing control, displaying the delivery status of the email corresponding to each recipient, and if the delivery status is delivery failure, displaying the reason for the email delivery failure.

[0096] For example, continuing from the previous example with 10 recipients, the email delivery details page displays the sender's name and the names of the 10 recipients. In other words, the page fully displays the names of all 10 recipients. Below these names, a second view control is displayed. When the sender clicks the second view control, a pop-up window appears in the delivery details page, showing the delivery status of each of the 10 recipients. For example, the pop-up can display the 10 email addresses corresponding to each recipient, with the delivery status and time displayed to the right of each email address. For recipients whose delivery status is "delivery failed," the reason for the failure can be displayed, allowing the sender to take appropriate action based on the reason.

[0097] In other embodiments, following the examples above, when displaying the sender identifier corresponding to the sender of an email, the following processing can also be performed: when an email is successfully delivered to multiple email addresses corresponding to multiple recipients (i.e., all recipients have successfully delivered the email), a delivery identifier indicating successful delivery of the email is displayed around the sender identifier; when an email is bounced from the email address of any one of the multiple recipients (i.e., there is a recipient whose delivery failed), a delivery identifier indicating failed delivery of the email is displayed around the sender identifier.

[0098] For example, taking 10 recipients as recipient 1 to recipient 10, when the email server returns a delivery result indicating that the email was successfully delivered to the 10 email addresses corresponding to these 10 recipients (i.e., all recipients were successfully delivered), a delivery icon indicating successful email delivery can be displayed to the right of the sender's avatar. When the email server returns a delivery result indicating that there are recipients among these 10 recipients whose emails were not delivered, a delivery icon indicating failed email delivery can be displayed to the right of the sender's avatar. Thus, when the sender of an email sees a delivery indicator to the right of the sender's avatar indicating that the email failed to be delivered, they can clearly know that there are recipients whose emails failed to be delivered. At this point, the sender can click on the sender's avatar to enter the email delivery details interface. The email delivery details interface displays the delivery status of the emails corresponding to each recipient. In other words, the sender can use the delivery details interface to find out which specific recipient's email failed to be delivered and the reason for the failure, so that they can take subsequent actions accordingly.

[0099] In some embodiments, the above-mentioned display of multiple recipient objects and the delivery status of emails corresponding to each recipient object can also be achieved by the following methods: classifying multiple recipient objects to obtain multiple recipient object sets, wherein one recipient object set corresponds to one delivery status of an email; for each recipient object set, centrally displaying at least one recipient object identifier corresponding to at least one recipient object included in the recipient object set, and displaying a delivery identifier used to characterize the delivery status corresponding to the recipient object set.

[0100] For example, let's take 10 recipients as an example, named recipients 1 to 10. The email delivery results returned by the email server include the delivery status of the emails for each of these 10 recipients. For instance, suppose the delivery status for recipients 1 to 5 is successful (i.e., the emails have been successfully delivered to the 5 email addresses corresponding to recipients 1 to 5), the delivery status for recipients 6 to 8 is unsuccessful (e.g., the emails bounced back to the email addresses of recipients 6 to 8), and the delivery status for recipients 9 and 10 is also unsuccessful. If the delivery status is "delivering," then the 10 recipients can be categorized according to their delivery status. For example, recipients 1 to 5 can be grouped into the same recipient set (e.g., recipient set 1, corresponding to a delivery status of "delivery successful"). Recipients 6 to 8 can be grouped into another recipient set (e.g., recipient set 2, corresponding to a delivery status of "delivery failed"). Recipients 9 and 10 can be grouped into recipient set 3, where recipient set 3 has a delivery status of "delivering." Subsequently, the 5 recipients included in recipient set 1 can be displayed centrally on the mail reading interface. The email set (recipient 1 to recipient 5) corresponds to five recipient names (e.g., these five recipient names can be displayed together on the same line in the email reading interface), and the delivery status indicator corresponding to recipient set 1 (i.e., the first delivery indicator used to indicate successful email delivery) is displayed. Similarly, the email set 2, which includes three recipients (recipient 6 to recipient 8), can also display their three recipient names corresponding to three recipients in the same line in the email reading interface, along with the delivery status indicator corresponding to recipient set 2 (i.e., the second delivery indicator used to indicate failed email delivery). Furthermore, the message reading interface can display the names of the two recipients (recipient 9 and recipient 10) in the same row as recipient set 3, along with the delivery status identifier (a third delivery identifier indicating that the email is being delivered) corresponding to recipient set 3. In this way, multiple recipients are categorized according to their delivery status, and recipients with the same delivery status are displayed together, making it convenient for email senders to view the information. This allows them to quickly understand which recipients have failed to receive their emails, which have successfully received theirs, and which are still in the process of receiving theirs.

[0101] In other embodiments, when displaying multiple recipients and the delivery status of the emails corresponding to each recipient, the following processing can also be performed: displaying other statuses of the emails corresponding to each recipient, wherein other statuses may include: read status, unread status, forwarded status, and reply status, etc.

[0102] For example, the above-mentioned display of other email statuses for each recipient can be achieved in the following way: For each recipient, perform the following processing: When the recipient has read the email, display a status indicator indicating a read status around the recipient's identifier; when the recipient has not read the email, display a status indicator indicating an unread status around the recipient's identifier; when the recipient forwards the email, display a status indicator indicating a forwarded status around the recipient's identifier; when the recipient replies to the email, display a status indicator indicating a replied status around the recipient's identifier.

[0103] For example, taking Recipient 1 out of multiple recipients as an example, besides the delivery indicator used to indicate the email's delivery status, other status indicators can also be displayed to the right of Recipient 1's avatar or nickname. For instance, if Recipient 1 has not read the email, an unread status indicator can be displayed next to the delivery indicator; if Recipient 1 has read the email, a read status indicator can be displayed next to the delivery indicator (for example, the unread status indicator can be switched to a read status indicator); if Recipient 1 forwards the email, a forwarding status indicator can be displayed next to the delivery indicator; and if Recipient 1 replies to the email, a reply status indicator can be displayed next to the delivery indicator. Thus, by displaying other status indicators next to the delivery indicator, the sender can easily understand the email's delivery status as well as other statuses, providing more information for the sender to take subsequent actions.

[0104] It should be noted that in practical applications, the status identifier of the forwarding state and the status identifier of the reply state can be the same. That is, the same status identifier can be used to represent the forwarding state and the reply state. This application embodiment does not make specific limitations on this.

[0105] In some embodiments, see Figure 4 , Figure 4 This is a second flowchart illustrating the email processing method provided in this application embodiment, as shown below. Figure 4 As shown, after execution Figure 3 After step 103 shown, you can also execute... Figure 4 Step 104 shown will combine Figure 4 The steps shown are explained.

[0106] In step 104, in response to the email recall operation, the recall status of the email corresponding to each recipient is displayed.

[0107] Here, the recall status can include recall success and recall failure. When the recall status is recall failure, the reason for the email recall failure can also be displayed.

[0108] In some embodiments, the above-mentioned display of the retraction status of each recipient's email can be achieved by: displaying the sender identifier corresponding to the sender of the email, and displaying a retraction identifier indicating that the email has been retracted around the sender identifier; in response to a triggering operation on the sender identifier, displaying the email details interface, wherein the details interface may include the retraction status of each recipient's email, for example, multiple email addresses (i.e., inboxes) corresponding to multiple recipients may be displayed in the details interface, and the retraction status of each recipient's email may be displayed, wherein the retraction status may include successful retraction (i.e., retraction has been retracted) and failed retraction.

[0109] For example, taking a message to 10 recipients (recipient 1 to recipient 10), the sender can recall an email that is already sent. For instance, when the sender triggers a recall action, a recall indicator can be displayed to the right of the sender's avatar, signifying that the email has been recalled. When the sender clicks on the sender's avatar, the email recall details screen can be displayed. This screen shows the recall status for each of the 10 recipients, which can be either "recall successful" (i.e., the email has been recalled) or "recall failed." For "recall failed," the reason for the failure can also be displayed. For example, suppose that for recipient 1, when the email is being delivered to recipient 1's email address after receiving the recall action triggered by the sender, the email can be successfully recalled. At this time, a "Recalled" message can be displayed on the right side of recipient 1's email address. In this way, the sender of the email can clearly understand the recall status of the email for each recipient.

[0110] In other embodiments, see Figure 5 , Figure 5 This is a schematic diagram of the third process of the email processing method provided in the embodiments of this application, as shown below. Figure 5 As shown, after execution Figure 3 After step 103 shown, you can also execute... Figure 5 Steps 105 and 106 shown will be combined Figure 5The steps shown are explained.

[0111] In step 105, in response to a trigger operation on the received message entry, the received message details interface is displayed.

[0112] Here, the email receipt details page can include multiple tab controls.

[0113] In some embodiments, taking an enterprise instant messaging client with integrated email functionality as an example, the email interface displayed on the enterprise instant messaging client may also include an entry point for received emails. When a user clicks on the received email entry point, a received email details interface can be displayed on the enterprise instant messaging client. This interface may display multiple tab controls, such as an "All" tab, an "Inbox and Folders" tab, a "Spam" tab, and a "Blocked" tab. Users can select different tab controls to view different emails.

[0114] In step 106, in response to the first tab control among multiple tab controls being selected, the received emails and their respective storage locations are displayed in the email record details interface.

[0115] Here, the first tab control can be the "All" tab control, and it can be selected by default in the email record details interface. For example, when the "All" tab control is selected, the email record details interface can display all emails received by the user in the last 30 days, as well as the storage location of each email. For instance, it can be displayed in the email record details interface in ascending order of receipt time, showing all emails received in the last 30 days and the storage location (e.g., email storage location) of each email. In this way, the user can clearly see the location of each email.

[0116] In some embodiments, after displaying the multiple received emails and the storage location of each email, the following processing may also be performed: in response to a viewing operation of the blocked emails among the multiple emails, displaying a details interface for the blocked emails; displaying detailed information of the blocked emails in the details interface, and disabling the interactive controls included in the details interface.

[0117] For example, in the email record details interface, in addition to displaying multiple emails and their respective storage locations, it can also display the corresponding operation entry for each email. When a user clicks on the operation entry for a blocked email (e.g., email 1), "view" and "remove" options can be displayed. When a user clicks on the "view" option, the details interface for email 1 can be displayed, showing detailed information about email 1. Since email 1 is a blocked email, the interactive controls in its details interface can be disabled. In other words, for blocked emails, users can only view the content of the email and cannot perform any corresponding operations.

[0118] It should be noted that for emails received from multiple email sources that are not blocked by the system, the interactive controls displayed in the email details page are valid when the user views the email, and the user can perform corresponding operations through the interactive controls.

[0119] In other embodiments, after displaying the multiple received emails and the storage location of each email, the following processing can be performed: in response to a block removal operation for a blocked email among the multiple emails, a second prompt message is displayed, wherein the second prompt message can be used to prompt the unblocking of emails in the mailing record that were blocked for the same reason. That is, when a block removal operation triggered by a user for a blocked email is received, the email server can be notified to redeliver emails in the mailing record that were blocked for the same reason.

[0120] For example, taking email 1 out of multiple emails as the blocked email, when a user triggers a removal action for email 1, a second message can be displayed in the inbox details. For instance, if email 1 was blocked because of an exception list, the following message could be displayed: "The sender has been removed from the exception list, and the blocking of N emails has been lifted." This means that subsequent emails sent from that address will no longer be blocked, and historical emails blocked for the same reason will be moved back to the user's inbox according to the inbox rules.

[0121] In some embodiments, following the above example, when displaying multiple received emails and the storage location corresponding to each email, the following processing can also be performed: if the operation entry corresponding to each email is displayed, then before responding to the interception removal operation for the intercepted emails among the multiple emails, the following processing can also be performed: in response to the triggering operation for the operation entry corresponding to the intercepted emails among the multiple emails, display viewing options (e.g., "View Email" option) and removal options (e.g., "Remove from Block List" option or "Remove from Abnormal List" option); identify the triggering operation for the removal option as an interception removal operation, and identify the triggering operation for the viewing option as a viewing operation for the intercepted emails.

[0122] For example, in the email record details interface, in addition to displaying multiple emails and their respective storage locations, it can also display the corresponding action entry for each email. When a user clicks on the action entry for a blocked email (e.g., email 1), the interface can display "view" and "remove" options. When a user clicks on the "remove" option, a second notification message can be displayed in the email record details interface. For example, if email 1 was blocked because of an exception list, the following second notification message can be displayed: "The sender has been removed from the exception list, and the blocking of N emails has been lifted." This means that subsequent emails sent from this address will no longer be blocked, and historical emails blocked for the same reason will be moved back to the user's inbox according to the receiving rules.

[0123] In other embodiments, following the above, when responding to the blocking removal operation for blocked emails in multiple emails, a prompt message indicating that the blocking has been lifted can also be displayed in the area used to display blocked emails in the mailing record details interface, and when a trigger operation is received for the operation entry corresponding to the blocked email, the removal option is canceled (i.e., only the view option is displayed).

[0124] For example, taking email 1 out of multiple emails as the blocked email, after receiving a user's action to remove the block for email 1, a message indicating that the block has been lifted can be displayed in the area designated for email 1 in the mailing history details interface. Simultaneously, email 1 can be moved to the user's inbox. Furthermore, when a subsequent user clicks on the corresponding action entry for email 1, only the "view" option can be displayed; that is, since email 1 has been lifted from the block, only the "view" function is retained.

[0125] In some embodiments, after displaying multiple received emails and the storage location corresponding to each email, the following processing may also be performed: in response to the selection of the second tab control among multiple tab controls, at least one email stored in the storage location corresponding to the second tab control is switched to be displayed in the mail record details interface.

[0126] For example, taking the "Inbox and Folders" tab control as the second tab control, when a user clicks on the "Inbox and Folders" tab control, the multiple emails displayed in the email history details interface can be switched to emails stored in the user's inbox and folders. In other words, users can select different tab controls to choose emails stored in different locations, making it easier for them to categorize and manage received emails.

[0127] The following will describe an exemplary application of the embodiments of this application in a real-world application scenario.

[0128] This application provides an email processing method that adds a delivery status function to the email side of an enterprise instant messaging client. Enterprise members can use this function to view the delivery status of each email to each recipient. After sending an email, the delivery status function provides users with the ability to track the email's delivery to each specific recipient, CC recipient, and BCC recipient. It also provides the ability to track the recall status when an email is recalled. Specifically, after sending an email, the overall delivery status of the current email can be displayed to the user in the email reading interface, with a secondary interface providing detailed information on the delivery status and recall details for each recipient, CC recipient, and BCC recipient. Additionally, the overall delivery status of the email can be displayed in the sent email list using small icons, for example, alongside other email statuses (e.g., whether forwarded, read status, etc.). Furthermore, this application embodiment can also provide a secondary interface for users to uniformly view and filter the received records of recently sent emails.

[0129] The email processing method provided in the embodiments of this application will be described in detail below.

[0130] For example, see the example of a desktop enterprise instant messaging app. Figure 6A , Figure 6A This is a schematic diagram of a first application scenario of the email processing method provided in this application embodiment, such as... Figure 6AAs shown, after a user sends an email, a corresponding prompt message 601 (e.g., "Sent successfully") can be displayed, and the prompt message 601 may also include a view button 602. When the user clicks the view button 602 included in the prompt message 601, the enterprise instant messaging APP can query the delivery result of the email. When the delivery result indicates that all recipients have been successfully delivered, a delivery status mark 603 indicating successful email delivery can be displayed to the right of the sender's avatar; when the delivery result indicates that some recipients have failed to receive the email (i.e., partial delivery failure), a delivery status mark 604 indicating failed email delivery can be displayed to the right of the sender's avatar. At this time, the user (i.e., the email sender) can click the view button 605 on the right to see which specific recipient failed to receive the email and the reason for the failure.

[0131] For example, see the example of a mobile enterprise instant messaging app. Figure 6B , Figure 6B This is a schematic diagram of a second application scenario of the email processing method provided in the embodiments of this application, such as... Figure 6B As shown, after a user sends an email, a corresponding notification message 606 (e.g., "Email sent successfully") can be displayed, and the notification message 606 may also include a view button 607. When the user clicks the view button 607 included in the notification message 606, the enterprise instant messaging app can check the delivery result of the email. When the delivery result indicates that all recipients have successfully delivered the email, a delivery status marker 608 indicating successful delivery, as well as the names of the sender and recipients, can be displayed to the right of the sender's avatar. When the user clicks the sender's avatar, the user can also enter the email details page, which displays the content of the email and the complete recipient list.

[0132] In some embodiments, after a user sends an email, the delivery status of the email can include delivery in progress, delivery successful, delivery failed, and partial delivery failed. In addition, if the user subsequently performs a recall operation on the email, a recall marker indicating that the email is being recalled can be displayed, and the recall result can also be notified to the user via email.

[0133] For example, see Figure 7 , Figure 7 This is a schematic diagram of a third application scenario of the email processing method provided in the embodiments of this application, such as... Figure 7As shown, for successful email delivery, a delivery status marker 701 can be displayed; for email being delivered, a delivery status marker 702 can be displayed; and for failed email delivery, a delivery status marker 703 can be displayed. Furthermore, if a recipient forwards or replies to an email after receiving it, a forwarding / reply status marker 704 can be displayed to the right of the recipient's avatar; if a recipient does not read an email after receiving it, an unread status marker 705 (e.g., a small blue dot) can be displayed to the right of the recipient's avatar.

[0134] It should be noted that for emails that have already been sent, a maximum of two markers can be displayed next to the recipient's avatar: a delivery status marker to indicate the delivery status, and a status indicator to indicate other statuses of the email (such as unread, replied, forwarded, etc.). For example, when the recipient has not read the email, a delivery status marker indicating successful delivery and a blue dot indicating unread status are displayed; if the recipient has read the email, the blue dot indicating unread status can be switched to a status indicator indicating read status (for example, a gray dot indicating read status).

[0135] In some embodiments, users can also view email delivery details within the email reading interface. For example, for sent emails, the delivery status can be displayed and delivery details can be viewed while reading the email. Specifically, for desktop enterprise instant messaging apps, delivery details can be displayed as a pop-up window when a user clicks the view button; for mobile enterprise instant messaging apps, a half-page can be raised to display the delivery details. Furthermore, delivery details can be closed, and can include the recipient, delivery status, and delivery time. In case of delivery failure, the reason for the failure can be displayed in the delivery status bar. Additionally, if the email is currently in the withdrawn state, it can be viewed by clicking the view button; for example, withdrawal details can be displayed when a user clicks the view button. It should be noted that for a single email, the delivery status displayed in the details can be divided into the following six situations: 1) Delivering: This email is currently being delivered; 2) Delivered to recipient's mailbox: This email address is also the corporate mailbox of the enterprise instant messaging client, and this email has been delivered to their email inbox. If the recipient has not received it, it may be due to certain filtering and anti-spam policies set up by their email service provider. You can confirm with the recipient and resend; 3) Delivered to recipient's server: This email address is not the corporate mailbox of the enterprise instant messaging client, but it has been delivered to the server where the recipient's mailbox is located, and the recipient's server has confirmed successful receipt. If the recipient has not received it, it may be a problem with the recipient's email service provider. You can contact the recipient's email service provider; 4) Delivery failed, bounced: This email has been bounced. In this case, the user can view the bounce message content and determine the reason for the bounce, correct it, and resend. If users are unable to resolve the issue, they can contact online customer service; 5) Delivery intercepted by the system: This means the user's email sending action was intercepted by the system. The user will see a notification when sending the email and can resend it after correction; 6) Data anomaly, status unknown: This situation occurs less than 0.01% of the time. Users can resend the email to ensure it arrives. This situation may be caused by network problems, resulting in the loss of delivery information records or the recipient's server failing to provide correct confirmation information.

[0136] For example, see the example of a desktop enterprise instant messaging app. Figure 8 , Figure 8 This is a schematic diagram of the fourth application scenario of the email processing method provided in the embodiments of this application, such as... Figure 8As shown, in the event of partial email delivery failure, users can click the view button 801 to view the delivery details of the email. For example, when the user clicks the view button 801, a pop-up window 802 can appear, displaying the delivery details of the email. For example, the pop-up window 802 can display the email address, delivery status, and delivery time for each recipient. In addition, for recipients whose delivery status is "delivery failed," the reason for the delivery failure can also be displayed.

[0137] For example, see the example of a desktop enterprise instant messaging app. Figure 9 , Figure 9 This is a schematic diagram of the fifth application scenario of the email processing method provided in the embodiments of this application, as shown below. Figure 9 As shown, when a user triggers a recall operation for a sent email, the sent email can be recalled. The user can also view the recall details of the email by clicking the view button 901. For example, when the user clicks the view button 901, a pop-up window 902 can appear, displaying the recall details of the email. For example, the pop-up window 902 can display the email address and recall result for each recipient. The recall result can include "recall successful" and "recall failed". If the recall result is "recall failed", the reason for the failure can also be displayed.

[0138] For example, see the example of a mobile enterprise instant messaging app. Figure 10 , Figure 10 This is a schematic diagram of the sixth application scenario of the email processing method provided in the embodiments of this application, as shown below. Figure 10 As shown, after sending an email, the user can view the delivery details of the email by clicking the view button 1001. For example, when the user clicks the view button 1001, a half-page 1002 can be raised to display the delivery details of the email. For example, the half-page 1002 can display the email address, delivery status, and delivery time for each recipient.

[0139] In some embodiments, see Figure 11 , Figure 11 This is a schematic diagram of the seventh application scenario of the email processing method provided in the embodiments of this application, such as... Figure 11As shown, the email processing method provided in this application embodiment also adds a new email receipt record entry 1101 in the settings, supporting users to query all email receipt records. For example, when a user clicks on the email receipt record entry 1101, an email receipt record details interface can be displayed. This interface can display multiple email storage location tabs, such as the "All" tab 1102, the "Inbox and Folders" tab, the "Spam" tab, and the "Blocked" tab. The "All" tab 1102 can be selected by default. That is, when the "All" tab 1102 is selected, the email receipt record details interface can display multiple emails received by the user in the last 30 days, along with the location of each email. When the user subsequently clicks on other email storage location tabs, the email receipt record details interface can switch between displaying emails that match the conditions corresponding to the currently selected tab. For example, assuming the user subsequently selects the "Spam" tab, the email receipt record details interface can switch between displaying emails stored in the spam folder.

[0140] For example, continuing from the above example, let's take a desktop enterprise instant messaging app as an example, such as... Figure 12A As shown, when receiving user requests... Figure 11 When viewing an email stored in the inbox, other folders, or the spam folder, as shown in the email record details interface, the email can be opened in a separate window 1201 (for example, the sender and recipient details of the email can be displayed in the separate window 1201), and users can perform various operations in the separate window 1201; or, as... Figure 12B As shown, when receiving user requests... Figure 11 When viewing a blocked email displayed in the email record details interface, the email can be opened in a separate window 1202. Since the email has been blocked and has not entered the user's folder, all buttons in the top and bottom function bars of the separate window 1202 can be disabled. For example, all interactions within the body area of ​​the electronic document are retained, except for emails for scheduled meetings and event invitations. The outer button of the scheduled meeting and event invitation card is disabled, and the attachment drop-down menu only supports previewing, while the save and copy functions are disabled. In other words, user operations are restricted for blocked emails.

[0141] For example, continuing from the above example, let's take a mobile enterprise instant messaging app as an example, such as... Figure 13A As shown, when receiving user requests... Figure 11When viewing an email stored in the inbox, other folders, or spam folder as shown in the email record details interface, the user can be redirected to the email reading page 1301, where various operations can be performed; or, as... Figure 13B As shown, when receiving user requests... Figure 11 When viewing a blocked email displayed in the email record details interface, users can be redirected to the email reading page 1302, where all buttons in the function bar are disabled. In other words, user actions are restricted for blocked emails.

[0142] In other embodiments, see Figure 14 , Figure 14 This is a schematic diagram of the twelfth application scenario of the email processing method provided in the embodiments of this application, as shown below. Figure 14 As shown, for Figure 11 The email 1401 shown in the mail record details interface is automatically blocked by the system. Users can view this email and remove it from the block list. When a user performs a removal operation, such as clicking the "Remove from Block List" option, subsequent emails from that source address will no longer be blocked. Simultaneously, previously blocked emails in the mail record will be moved back to the inbox according to the mailing rules, and a message like "The sender has been removed from the block list, and N emails have been unblocked" can be displayed. Furthermore, a message indicating that the email has been unblocked can be displayed around email 1401, and the function button can be set to only allow viewing the email. Figure 11 The email details page shows email 1402, which was blocked by the system because the user set up an exception list. Users can view this email and remove it from the exception list. When a user performs a removal operation, such as clicking the "Remove from exception list" option, subsequent emails from that source will no longer be blocked. Simultaneously, previously blocked emails in the inbox will be moved back to the user's inbox according to the inbox rules, and a message like "The sender has been removed from the exception list, and N emails have been unblocked" can be displayed. Furthermore, a message indicating that the email has been unblocked can be displayed around email 1402, and the function button can be set to only allow viewing the email.

[0143] See also Figure 14 ,for Figure 11The email 1403 shown in the mail history details interface (i.e., the email identified as spam by the system) that went to the spam folder can be viewed and removed from the block list. When the user performs a removal operation, such as when the user clicks the "Remove from Block List" option, subsequent emails from that source address will no longer go to the spam folder. Simultaneously, previously blocked emails in the mail history will be re-entered into the inbox according to the mailing rules, and the following message can be displayed: "The sender has been removed from the block list, and N emails have been unblocked." Furthermore, a message indicating that the email has been unblocked can be displayed around email 1403, and the function button can be set to only allow viewing the email. Figure 11 The email 1404 shown in the received email details interface has been successfully added to the inbox and can be viewed. It should be noted that for desktop enterprise instant messaging apps, this operation can be performed through the menu; while for mobile enterprise instant messaging apps, the operation can be performed within a user interaction component (such as an action sheet).

[0144] The following will continue to combine Figure 15 The email processing method provided in the embodiments of this application will be described.

[0145] For example, see Figure 15 , Figure 15 This is a schematic diagram of the fourth process of the email processing method provided in the embodiments of this application, which will be combined with... Figure 15 The steps shown are explained.

[0146] In step 201, the client responds to the email sending operation triggered by the user by sending an email to the CGI layer.

[0147] In some embodiments, an email function module can be integrated into the enterprise instant messaging client. Users can edit emails and click the send button in the enterprise instant messaging client. Subsequently, the enterprise instant messaging client can use an application for sending emails (such as compose_send) to send the user-edited emails to the Common Gateway Interface (CGI) layer.

[0148] In step 202, the CGI layer performs validation of different email parameters.

[0149] In step 203, the CGI layer performs format assembly for the email recipient.

[0150] In step 204, the CGI layer performs sender sending restrictions and over-capacity detection.

[0151] In step 205, the CGI layer assembles the email content into a standard email format.

[0152] In step 206, the CGI layer delivers to the BG delivery system.

[0153] In some embodiments, after assembling the email content into a standard email format, the CGI layer can deliver the assembled email to the background (BG) delivery system.

[0154] In step 207, the BG delivery system generates a unique ID.

[0155] In step 208, the BG delivery system writes the ID into the database.

[0156] In some embodiments, after generating a unique corresponding ID for the received email, the BG delivery system can write the generated ID into a database. For example, the BG delivery system can write the generated unique ID into an in-memory database based on key-value (KV) pairs.

[0157] In step 209, the database returns the write result to the BG delivery system.

[0158] In step 210, the BG delivery system returns an ID to the CGI layer.

[0159] In step 211, the CGI layer returns the ID to the client.

[0160] In step 212, the BG delivery system delivers the email.

[0161] In step 213, the BG delivery system writes the delivery result into the database.

[0162] In step 214, the client responds to the user-triggered delivery result query operation by sending a delivery result query request to the CGI layer.

[0163] In step 215, the CGI layer sends a delivery result query request carrying a unique ID to the database.

[0164] In step 216, the database returns the email delivery result to the CGI layer.

[0165] In step 217, the CGI layer returns the email delivery result to the client.

[0166] In some embodiments, the sending interface does not need to add new fields, but the return value of the sending interface needs to add a new field, `mail_status_unique_id`, to return a unique ID for querying the delivery status of the email sent. Alternatively, a new sending query interface can be added, including the `mail_status_unique_id` field, to specify which email's delivery status to query.

[0167] In other embodiments, the delivery status query interface can return the delivery status of all recipients, CCs, and BCCs for this email, including the following fields: the ID of the email requesting the delivery status (mail_status_unique_id); the error code (code), which can refer to the Hypertext Transfer Protocol (HTTP), normally returning 200; the error message (error_message), i.e., if an error occurred, returning detailed error information; next request after this timestamp (next_query_timestamp); and an array (post_status) containing the delivery status for each address. In addition, the delivery status of an email can include the following fields: the destination address; the type of the destination address, including: recipient, CC, BCC; the delivery status, including: Sending, Done, Failed, Recalling (with the result to be notified via email), and Recalled; the folder where the recipient saved the email; and the finished time.

[0168] In some embodiments, a new key-value table (i.e., mail_status) can be added to the client's data layer to store the latest delivery status returned by the server for each email. The fields are the same as those returned by the server-side query interface, serving as a cache. The mail_status_unique_id field can be used as a foreign key to associate with the table storing emails locally, allowing queries to retrieve local sending time, storage location, etc.

[0169] In other embodiments, for the email CGI request process, after sending an email, the user can use compose_send to send the email to the server and obtain mail_status_unique_id. Then, the user can call the delivery status interface to write a new entry to the key-value table (i.e., mail_status).

[0170] In some embodiments, the delivery status CGI request process may include the following steps:

[0171] Step 1: Find entries in the KV table (i.e., mail_status) whose next_query_timestamp is less than the current time.

[0172] Step 2: For each entry, first check if there is a task with the same mail_status_unique_id in the ongoing tasks. If so, discard the entry and add the mail_status_unique_id to the ongoing task list. Then, send a query request for the delivery status to the server. Finally, wait for the return in other threads.

[0173] Step 3: Find the entry in the KV table (i.e., mail_status) whose next_query_timestamp is greater than the current time, sort the found entries in order, take the first entry in the sorted result, and then calculate the waiting time.

[0174] Step 4: Wait, and return to Step 1 after the waiting time has elapsed.

[0175] Step 5: If the server returns the requested content, update the entry with the same mail_status_unique_id in the KV table (i.e., mail_status). At the same time, notify the client that the mail_status_unique_id entry has been updated so that the client can decide whether to update the interface. Finally, cancel the current wait and return to step 3.

[0176] In summary, the email processing method provided in this application has the following beneficial effects:

[0177] Research results show that in external email communication, the secure delivery of emails is one of the most important concerns for users, even directly influencing companies' choice of email service providers. The email processing method provided in this application enhances users' sense of security regarding the stable delivery of emails and provides the ability to query receipt records, thereby ensuring that all sent and received emails (including filtered and blocked emails) are traceable and retrievable.

[0178] The following description continues to illustrate the exemplary structure of the email processing apparatus 655 provided in the embodiments of this application as a software module. In some embodiments, such as Figure 2 As shown, the software modules stored in the email processing device 655 in the memory 650 may include: a sending module 6551 and a display module 6552.

[0179] The sending module 6551 is used to send emails to multiple selected recipients in response to an email sending trigger operation; the display module 6552 is used to display a first prompt message in response to the email being in a sent state, wherein the first prompt message includes a first viewing control; the display module 6552 is also used to display multiple recipients and the delivery status of the emails corresponding to each recipient in response to a trigger operation on the first viewing control.

[0180] In some embodiments, the display module 6552 is further configured to display multiple recipient identifiers corresponding to multiple recipient objects, and display an email delivery identifier around each recipient object identifier, wherein the delivery identifier is used to characterize the delivery status of the email to the recipient object corresponding to the recipient object identifier.

[0181] In some embodiments, the delivery status includes: successful delivery, failed delivery, and in progress delivery. The delivery identifier includes: a first delivery identifier indicating successful email delivery, a second delivery identifier indicating failed email delivery, and a third delivery identifier indicating that the email is being delivered. The display module 6552 is further configured to perform the following processing for each recipient: when the email is successfully delivered to the recipient's email address, display the first delivery identifier around the recipient identifier corresponding to the recipient; when the email is bounced from the recipient's email address, display the second delivery identifier around the recipient identifier corresponding to the recipient; when the email is being delivered to the recipient's email address, display the third delivery identifier around the recipient identifier corresponding to the recipient.

[0182] In some embodiments, the display module 6552 is further configured to display an email delivery details interface for the recipient corresponding to the target recipient identifier in response to a trigger operation for the target recipient identifier, wherein the target recipient identifier is a recipient identifier with a second delivery identifier displayed around it, and the email delivery details interface includes the reason why the email delivery to the recipient corresponding to the target recipient identifier failed.

[0183] In some embodiments, the email processing apparatus 655 further includes a switching module 6553, configured to switch the third delivery identifier displayed around the recipient identifier corresponding to the target recipient to the first delivery identifier when the email is subsequently successfully delivered to the email address of the target recipient; or configured to switch the third delivery identifier displayed around the recipient identifier corresponding to the target recipient to the second delivery identifier when the email is subsequently bounced from the email address of the target recipient; wherein the target recipient is the recipient whose email delivery status is "delivering".

[0184] In some embodiments, the display module 6552 is further configured to perform any of the following processes: displaying multiple recipient identifiers corresponding to multiple recipient objects in the order of delivery failure, delivery in progress, and delivery success; displaying multiple recipient identifiers corresponding to multiple recipient objects in the order of interaction frequency with the sender of the email from high to low; and displaying multiple recipient identifiers corresponding to multiple recipient objects in the order of correlation between the recipient's job title and the email content from high to low.

[0185] In some embodiments, the display module 6552 is further configured to display the sender identifier corresponding to the sender of the email, and centrally display multiple recipient identifiers corresponding to multiple recipients, wherein when the number of multiple recipient identifiers is greater than a quantity threshold, some of the multiple recipient identifiers are collapsed; and to display the email delivery details interface in response to a trigger operation on the sender identifier, wherein the delivery details interface includes the delivery status of the email corresponding to each recipient.

[0186] In some embodiments, when displaying the sender identifier corresponding to the sender of an email, the display module 6552 is further configured to perform the following processing: when the email is successfully delivered to multiple email addresses corresponding to multiple recipients, a delivery identifier indicating successful email delivery is displayed around the sender identifier; when the email is bounced by the email address of any one of the multiple recipients, a delivery identifier indicating failed email delivery is displayed around the sender identifier.

[0187] In some embodiments, the display module 6552 is further configured to display an email delivery details interface, wherein the delivery details interface includes a second viewing control; in response to a trigger operation on the second viewing control, the delivery status of the email corresponding to each recipient is displayed, and if the delivery status is delivery failure, the reason for the email delivery failure is displayed.

[0188] In some embodiments, the email processing apparatus 655 further includes a classification module 6554 for classifying multiple recipients to obtain multiple recipient sets, wherein a recipient set corresponds to a delivery status of an email; and a display module 6552 for centrally displaying at least one recipient identifier corresponding to at least one recipient included in each recipient set, and displaying a delivery identifier for indicating the delivery status corresponding to the recipient set.

[0189] In some embodiments, when displaying multiple recipients and the delivery status of the email corresponding to each recipient, the display module 6552 is further configured to perform the following processing: display other statuses of the email corresponding to each recipient, wherein the other statuses include: read status, unread status, forwarded status, and reply status.

[0190] In some embodiments, the display module 6552 is further configured to perform the following processing for each recipient: when the recipient has read the email, display a status indicator indicating a read status around the recipient identifier corresponding to the recipient; when the recipient has not read the email, display a status indicator indicating an unread status around the recipient identifier corresponding to the recipient; when the recipient forwards the email, display a status indicator indicating a forwarding status around the recipient identifier corresponding to the recipient; and when the recipient replies to the email, display a status indicator indicating a reply status around the recipient identifier corresponding to the recipient.

[0191] In some embodiments, after displaying multiple recipients and the delivery status of the email corresponding to each recipient, the display module 6552 is further configured to perform the following processing: in response to the email recall operation, displaying the recall status of the email corresponding to each recipient, and if the recall status is recall failure, displaying the reason for the email recall failure.

[0192] In some embodiments, the display module 6552 is further configured to display a sender identifier corresponding to the sender of the email, and display a recall identifier indicating that the email has been recalled around the sender identifier; and to display a details interface of the email in response to a triggering operation on the sender identifier, wherein the details interface includes the recall status of the email corresponding to each recipient.

[0193] In some embodiments, the display module 6552 is further configured to display a message receipt details interface in response to a trigger operation on the message receipt entry, wherein the message receipt details interface includes multiple tab controls; and to display multiple received emails and the storage location corresponding to each email in the message receipt details interface in response to the first tab control among the multiple tab controls being selected.

[0194] In some embodiments, after displaying the received multiple emails and the storage location corresponding to each email, the display module 6552 is further configured to perform the following processing: in response to a viewing operation of the blocked emails among the multiple emails, displaying a details interface of the blocked emails; displaying detailed information of the blocked emails in the details interface; the email processing device 655 further includes a disabling module 6555 for disabling the interactive controls included in the details interface.

[0195] In some embodiments, after displaying the multiple received emails and the storage location corresponding to each email, the display module 6552 is further configured to perform the following processing: in response to the interception removal operation for the intercepted emails in the multiple emails, displaying a second prompt message, wherein the second prompt message is used to prompt the unblocking of emails in the received records that were intercepted for the same reason.

[0196] In some embodiments, when displaying multiple received emails and the storage location corresponding to each email, the display module 6552 is further configured to display the operation entry corresponding to each email; and to perform the following processing before responding to the interception removal operation for the intercepted emails in the multiple emails: in response to the triggering operation for the operation entry corresponding to the intercepted emails in the multiple emails, displaying viewing options and removal options; the email processing device 655 further includes an identification module 6556, configured to identify the triggering operation for the removal option as an interception removal operation, and to identify the triggering operation for the viewing option as a viewing operation for the intercepted emails.

[0197] In some embodiments, when responding to a block removal operation for a blocked email among multiple emails, the display module 6552 is further configured to perform the following processing: display a prompt message indicating that the block has been lifted in the area used to display the blocked email in the mail record details interface, and cancel the display of the removal option when a trigger operation is received for the operation entry corresponding to the blocked email.

[0198] In some embodiments, after displaying multiple received emails and the storage location corresponding to each email, the display module 6552 is further configured to perform the following processing: in response to the selection of a second tab control among multiple tab controls, switching the display of at least one email stored in the storage location corresponding to the second tab control in the mail record details interface.

[0199] In some embodiments, the email processing apparatus 655 further includes a receiving module 6557 and a query module 6558, wherein the receiving module 6557 is used to receive the email identifier of the email after the sending module 6551 sends the email to a plurality of selected recipients; the query module 6558 is used to query the delivery result of the email based on the email identifier before the display module 6552 displays the plurality of recipients and the delivery status of the email corresponding to each recipient, wherein the delivery result includes the delivery status of the email corresponding to each recipient.

[0200] It should be noted that the description of the apparatus in this application is similar to the description of the method embodiments described above, and has similar beneficial effects as the method embodiments; therefore, it will not be repeated. For any technical details not covered in the email processing apparatus provided in this application, please refer to... Figure 3 , Figure 4 ,or Figure 5 The meaning is understood in accordance with the description of any of the accompanying drawings.

[0201] This application provides a computer program product comprising a computer program or computer-executable instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer-executable instructions from the computer-readable storage medium and executes the computer-executable instructions, causing the computer device to perform the email processing method described above in this application.

[0202] This application provides a computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are executed by a processor, they cause the processor to perform the email processing method provided in this application. For example, ... Figure 3 , Figure 4 ,or Figure 5 The email processing method is shown.

[0203] In some embodiments, the computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, flash memory, magnetic surface memory, optical disk, or CD-ROM; or it may be a variety of devices including one or any combination of the above-mentioned memories.

[0204] In some embodiments, executable instructions may take the form of a program, software, software module, script, or code, written in any form of programming language (including compiled or interpreted languages, or declarative or procedural languages), and may be deployed in any form, including as a standalone program or as a module, component, subroutine, or other unit suitable for use in a computing environment.

[0205] As an example, executable instructions can be deployed to execute on a single electronic device, or on multiple electronic devices located in one location, or on multiple electronic devices distributed across multiple locations and interconnected via a communication network.

[0206] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. An email processing method, characterized in that, The method includes: In response to an email sending trigger action, send emails to multiple selected recipients; In response to the email being in a sent state, a first prompt message is displayed, wherein the first prompt message includes a first viewing control; In response to a trigger operation on the first viewing control, the plurality of recipient objects and the delivery status of the email corresponding to each recipient object are displayed.

2. The method according to claim 1, characterized in that, The display of the plurality of recipients and the delivery status of the email corresponding to each recipient includes: Each of the multiple recipients is displayed with a corresponding recipient identifier, and a delivery identifier of the email is displayed around each recipient identifier. The delivery identifier is used to indicate the delivery status of the email to the recipient corresponding to the recipient identifier.

3. The method according to claim 2, characterized in that, The delivery status includes: delivery successful, delivery failed, and delivery in progress. The delivery identifiers include: a first delivery identifier indicating successful email delivery, a second delivery identifier indicating failed email delivery, and a third delivery identifier indicating that the email is being delivered. The step of displaying the email delivery identifier around each recipient identifier includes: For each of the recipients, the following processing is performed: When the email is successfully delivered to the recipient's email address, the first delivery identifier is displayed around the recipient's identifier corresponding to the recipient; When the email is bounced from the recipient's email address, the second delivery identifier is displayed around the recipient's identifier. When the email is being delivered to the recipient's email address, the third delivery identifier is displayed around the recipient's identifier.

4. The method according to claim 3, characterized in that, The method further includes: In response to a trigger operation targeting a target recipient identifier, an email delivery details interface for the recipient corresponding to the target recipient identifier is displayed. The target recipient identifier is the recipient identifier surrounded by the second delivery identifier. The email delivery details interface includes the reason why the email failed to be delivered to the recipient corresponding to the target recipient identifier.

5. The method according to claim 3, characterized in that, The method further includes: When the email is successfully delivered to the target recipient's email address, the third delivery identifier displayed around the recipient's identifier will be switched to the first delivery identifier. When the email is subsequently bounced from the target recipient's email address, the third delivery identifier displayed around the recipient identifier corresponding to the target recipient will be switched to the second delivery identifier. The target recipient is the recipient whose email delivery status is "delivery in progress".

6. The method according to claim 2, characterized in that, The step of displaying the multiple recipient identifiers corresponding to the multiple recipients includes: Perform any of the following processes: Display the multiple recipient identifiers corresponding to the multiple recipients in the order of delivery failure, delivery in progress, and delivery success; The multiple recipient identifiers corresponding to the multiple recipients are displayed in descending order of interaction frequency with the sender of the email. The recipient identifiers are displayed one-to-one with each recipient in descending order of the correlation between the recipient's job title and the content of the email.

7. The method according to claim 1, characterized in that, The display of the plurality of recipients and the delivery status of the email corresponding to each recipient includes: The sender identifier corresponding to the sender of the email is displayed, and multiple recipient identifiers corresponding to the multiple recipients are displayed in a centralized manner. When the number of multiple recipient identifiers exceeds a number threshold, some of the recipient identifiers are collapsed. In response to a trigger operation targeting the sender identifier, the delivery details interface of the email is displayed, wherein the delivery details interface includes the delivery status of the email corresponding to each recipient.

8. The method according to claim 7, characterized in that, When displaying the sender identifier corresponding to the sender of the email, the method further includes: When the email is successfully delivered to the multiple email addresses corresponding to the multiple recipients, a delivery icon indicating that the email was successfully delivered is displayed around the sender's identifier; When the email is bounced by the email address of any of the multiple recipients, a delivery indicator indicating that the email delivery failed is displayed around the sender identifier.

9. The method according to claim 7, characterized in that, The interface displaying the delivery details of the email includes: The delivery details interface of the email is displayed, wherein the delivery details interface includes a second viewing control; In response to a trigger operation on the second viewing control, the delivery status of the email corresponding to each recipient is displayed, and if the delivery status is delivery failure, the reason for the email delivery failure is displayed.

10. The method according to claim 1, characterized in that, The display of the plurality of recipients and the delivery status of the email corresponding to each recipient includes: The multiple recipients are classified to obtain multiple recipient sets, wherein each recipient set corresponds to a delivery status of the email. For each set of recipient objects, at least one recipient object identifier corresponding to at least one recipient object included in the set of recipient objects is centrally displayed, and a delivery identifier used to characterize the delivery status corresponding to the set of recipient objects is displayed.

11. The method according to any one of claims 1 to 10, characterized in that, When displaying the plurality of recipients and the delivery status of the email corresponding to each recipient, the method further includes: Display other statuses of the email corresponding to each recipient, including: read status, unread status, forwarded status, and replied status.

12. The method according to claim 11, characterized in that, The display of other statuses of the email corresponding to each recipient includes: For each of the recipients, the following processing is performed: When the recipient has read the email, a status indicator representing the read status is displayed around the recipient identifier corresponding to the recipient. When the recipient has not read the email, a status indicator representing the unread status is displayed around the recipient identifier corresponding to the recipient. When the recipient forwards the email, a status indicator representing the forwarding status is displayed around the recipient identifier corresponding to the recipient. When the recipient replies to the email, a status indicator representing the reply status is displayed around the recipient's identifier.

13. The method according to any one of claims 1 to 10, characterized in that, After displaying the plurality of recipients and the delivery status of the email corresponding to each recipient, the method further includes: In response to the email recall operation, the recall status of the email corresponding to each recipient is displayed, and if the recall status is recall failure, the reason for the email recall failure is displayed.

14. The method according to any one of claims 1 to 10, characterized in that, The step of displaying the recall status of the email corresponding to each recipient includes: Display the sender identifier corresponding to the sender of the email, and display a recall identifier indicating that the email has been recalled around the sender identifier; In response to a trigger operation for the sender identifier, a details screen for the email is displayed, wherein the details screen includes the recall status of the email for each recipient.

15. The method according to any one of claims 1 to 10, characterized in that, The method further includes: In response to a trigger operation on the mail receipt entry, a mail receipt details interface is displayed, wherein the mail receipt details interface includes multiple tab controls; In response to the first tab control among the plurality of tab controls being selected, the received emails and the storage location of each email are displayed in the email record details interface.

16. The method according to claim 15, characterized in that, After displaying the multiple received emails and the storage location of each email, the method further includes: In response to a viewing operation for the blocked emails among the multiple emails, a details interface for the blocked emails is displayed; The details page displays the details of the blocked email and disables the interactive controls included in the details page.

17. The method according to claim 15, characterized in that, After displaying the multiple received emails and the storage location of each email, the method further includes: In response to the blocking removal operation for the blocked emails in the multiple emails, a second prompt message is displayed, wherein the second prompt message is used to prompt the unblocking of emails in the mailing record that were blocked for the same reason.

18. The method according to claim 17, characterized in that, When displaying the received multiple emails and the storage location corresponding to each email, the method further includes: Display the corresponding operation entry for each of the aforementioned emails; Prior to the intercept removal operation for the intercepted emails among the multiple emails, the method further includes: In response to the triggered operation of the operation entry corresponding to the blocked email in the multiple emails, the view option and the remove option are displayed; The triggering operation for the removal option is identified as the interception removal operation, and the triggering operation for the view option is identified as the view operation for the intercepted email.

19. The method according to claim 18, characterized in that, In response to the intercept removal operation for the intercepted emails among the multiple emails, the method further includes: In the email record details interface, the area used to display the blocked email will show a message indicating that the blocking has been lifted. When a trigger operation is received for the operation entry corresponding to the blocked email, the removal option will be removed.

20. The method according to claim 15, characterized in that, After displaying the multiple received emails and the storage location of each email, the method further includes: In response to the selection of the second tab control among the plurality of tab controls, at least one email stored in the storage location corresponding to the second tab control is switched to be displayed in the mail receipt details interface.

21. The method according to any one of claims 1 to 10, characterized in that, After sending emails to the selected multiple recipients, the method further includes: The email identifier that received the email; Before displaying the plurality of recipients and the delivery status of the email corresponding to each recipient, the method further includes: The email delivery result is queried based on the email identifier, wherein the delivery result includes the delivery status of the email corresponding to each recipient.

22. An email processing device, characterized in that, The device includes: The sending module is used to send emails to multiple selected recipients in response to an email sending trigger operation. The display module is configured to display a first prompt message in response to the email being in a sent state, wherein the first prompt message includes a first viewing control; The display module is further configured to, in response to a trigger operation on the first viewing control, display the plurality of recipient objects and the delivery status of the email corresponding to each recipient object.

23. An electronic device, characterized in that, include: Memory is used to store executable instructions for a computer; A processor, when executing computer-executable instructions stored in the memory, implements the email processing method according to any one of claims 1 to 21.

24. A computer-readable storage medium storing computer-executable instructions, characterized in that, When the computer-executable instructions are executed by a processor, they implement the email processing method according to any one of claims 1 to 21.

25. A computer program product comprising a computer program or computer-executable instructions, characterized in that, When the computer program or computer-executable instructions are executed by a processor, the email processing method according to any one of claims 1 to 21 is implemented.

Images