Mail cross-site recall method, system and device and storage medium
By inserting a unique identifier into the mail system and using the SMTP protocol to build and verify the recall request email, the problem of low success rate of cross-platform email recall is solved, and the compatibility and success rate of cross-site email recall is improved.
Patent Information
- Application Number
- CN202510556373.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-04-29
- Publication Date
- 2025-07-25
AI Technical Summary
The success rate of cross-platform recall of existing mail systems is low, especially the lack of unified interactive interfaces between systems of different manufacturers, making it difficult to realize cross-site email recall function.
By inserting a unique identifier into the sending system, sending emails using the SMTP protocol, and building a signed recall request email, the receiving system verifies the legality and searches and deletes the emails based on the unique identifier.
It realizes compatibility and success rate improvement of cross-site email recalls, ensures recall functions between different mail systems, and avoids recall failures caused by gateway problems.
Smart Images
Figure CN120378397A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the technical field of email communication, and in particular to a method, system, device, and storage medium for cross-site recall of emails. Background Art
[0002] Email recall means that after the sender sends an email, for various reasons (such as incorrect information or incomplete information in the email), the sender needs to withdraw the sent email. Currently, the email recall function is limited to being implemented within the same email system. There is a lack of a unified interaction interface between different manufacturers' systems, making it difficult to implement the email recall function for different manufacturers' email systems; or it only supports cross-site recall between specific manufacturer systems that use the same private communication protocol. The above problems lead to a low success rate of cross-platform recall in existing email systems. Summary of the Invention
[0003] Therefore, the embodiments of this application provide a method, system, device, and storage medium for cross-site recall of emails, which realizes the recall of sent emails across sites.
[0004] In a first aspect, this application provides a method for cross-site recall of emails.
[0005] This application is achieved through the following technical solutions:
[0006] A method for cross-site recall of emails includes:
[0007] The sending system inserts a unique identifier into the email to be sent and sends the email to be sent to the receiving system through the SMTP protocol;
[0008] The sending system receives a recall request initiated by the user, constructs a signed recall request email, and the recall request email contains the unique identifier of the email to be recalled;
[0009] The sending system sends the recall request email to the receiving system;
[0010] The receiving system receives the recall request email and verifies the legitimacy of the recall request email;
[0011] After verifying that it belongs to a legitimate recall request email, the receiving system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation based on the unique identifier, and deletes the email that matches the unique identifier of the email to be recalled.
[0012] In a preferred example of this application, it can be further set that the sending system inserts a unique identifier into the email to be sent, including:
[0013] The sending system generates a unique identifier for the email to be sent through the UUID method and inserts the unique identifier into the email to be sent.
[0014] In a preferred example of the present application, it can be further set that the sending system receives a recall request initiated by the user and constructs a signed recall request email, including:
[0015] Construct the email header and email body of the recall request email. Among them, the email header includes the sender address, recipient address, email subject, sending date, email type, and header signature field; the email body includes the original sender address, email subject, and unique identifier of the email to be recalled.
[0016] In a preferred example of the present application, it can be further set that the receiving system receives the recall request email and verifies the legality of the recall request email, including:
[0017] Verify the legality of the sending address of the recall request email through email anti-forgery technology;
[0018] Verify the email header of the recall request email and check whether the email type contains "recall";
[0019] Use the DomainKeys Identified Mail algorithm to verify the legality of the header signature field of the recall request email.
[0020] In a preferred example of the present application, it can be further set that when the sending system sends the recall request email to the receiving system, it also includes:
[0021] The sending system sends an EHLO command to the receiving system;
[0022] Receive the extended attribute list returned by the receiving system through the EHLO command;
[0023] Judge whether the extended attribute list includes "CSMO recall".
[0024] In a preferred example of the present application, it can be further set that after deleting the emails that match the unique identifier of the email to be recalled, it also includes:
[0025] The receiving system sends a recall result notification email to the sending system.
[0026] In a second aspect, the present application provides a cross-site email recall system.
[0027] The present application is achieved through the following technical solutions:
[0028] A cross-site email recall system includes a sending system and a receiving system;
[0029] The sender system is used to insert a unique identifier into the email to be sent and send the email to be sent to the recipient system through the SMTP protocol; receive the recall request initiated by the user, construct a signed recall request email, where the unique identifier of the email to be recalled is included in the recall request email, and send the recall request email to the recipient system;
[0030] The recipient system is used to receive the recall request email and verify the legality of the recall request email; after verifying that it belongs to a legal recall request email, the recipient system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation based on the unique identifier, and deletes the email that matches the unique identifier of the email to be recalled found by the search.
[0031] In a preferred example of the present application, it can be further set that the sender system is specifically used to generate the unique identifier of the email to be sent by the UUID method and insert the unique identifier into the email to be sent.
[0032] In a third aspect, the present application is achieved through the following technical solutions:
[0033] A computer device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of any of the above email cross-site recall methods.
[0034] In a fourth aspect, the present application provides a computer-readable storage medium.
[0035] The present application is achieved through the following technical solutions:
[0036] A computer-readable storage medium stores a computer program. When the computer program is executed by a processor, it implements the steps of any of the above email cross-site recall methods.
[0037] In summary, compared with the prior art, the beneficial effects brought by the technical solutions provided in the embodiments of the present application at least include:
[0038] The sender system of this application inserts a unique identifier into the email to be sent, and sends the email to be sent to the recipient system through the SMTP protocol; the sender system receives a recall request initiated by the user, constructs a signed recall request email, and the unique identifier of the email to be recalled is included in the recall request email; the sender system sends the recall request email to the recipient system; the recipient system receives the recall request email and verifies the legitimacy of the recall request email; after verifying that it belongs to a legitimate recall request email, the recipient system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation according to the unique identifier, and deletes the emails that match the unique identifier of the email to be recalled found in the search.
[0039] This application sends emails containing extended MIME fields through the SMTP protocol for email recall, ensuring compatibility with different email servers and expanding the application scope of cross-site recall; the SMTP protocol is used between email systems to send recall emails, avoiding the problem of recall failure caused by the inability to recognize non-SMTP private protocols due to gateway issues. The recall method of this application can be applied to the same email system or different email systems, improving the success rate of email recall. Brief Description of the Drawings
[0040] Figure 1 It is a schematic flowchart of the email cross-site recall method provided by an embodiment of this application. Detailed Embodiments
[0041] This specific embodiment is only an interpretation of this application and does not limit this application. After reading this specification, those skilled in the art can make modifications to this embodiment without creative contributions as needed, but as long as it is within the scope of the claims of this application, it is protected by the patent law.
[0042] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are some but not all of the embodiments of this application. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without making creative efforts belong to the scope of protection of this application.
[0043] In addition, the term "and / or" in this application is only a description of the association relationship of associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist simultaneously, and B exists alone. In addition, the character " / " in this application generally represents an "or" relationship between the associated objects before and after, unless otherwise specified.
[0044] In this application, terms such as "first" and "second" are used to distinguish identical or similar items with basically the same functions. It should be understood that there is no logical or chronological dependency between "first", "second", and "nth", nor are the quantity and execution order limited.
[0045] In the embodiments of this application, words such as "exemplary" or "for example" are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.
[0046] The embodiments of this application will be further described in detail below with reference to the accompanying drawings of the specification.
[0047] Refer to Figure 1 As shown, the first exemplary embodiment of this application provides a method for cross-site recall of emails, which includes:
[0048] S1: The sending system inserts a unique identifier into the email to be sent and sends the email to be sent to the receiving system through the SMTP protocol.
[0049] Specifically, the sending end of the sending system composes the content of the email to be sent through an email client or a web-based email box, including the recipient address, subject, body, and / or attachment content. When the sending system generates the data structure of the email, it generates a globally unique identifier for each email to be sent, adds a new header field X-UNIQUE-ID to the email to be sent, and inserts the unique identifier corresponding to the email to be sent into the header field X-UNIQUE-ID. The unique identifier is used to uniquely identify the email. After receiving the email, the receiving system uses the unique identifier to establish a corresponding relationship with the email for subsequent searching of the email using the unique identifier.
[0050] The sending system establishes a connection with the SMTP server of the sending system, sends SMTP commands to interact with the SMTP server of the sending system, and sends the email to be sent containing the unique identifier to the SMTP server of the sending system; after receiving the email, the SMTP server of the sending system forwards the email to the SMTP server of the receiving system according to the recipient address information in the email. After receiving the email, the SMTP server of the receiving system stores it in the receiving system and waits for the recipient to collect it through the client or the web-based email box.
[0051] S2: The sending system receives a recall request initiated by the user, constructs a signed recall request email, and the recall request email contains the unique identifier of the email to be recalled.
[0052] The sender user at the sender system end can select the email to be recalled in the sent email list through the email client or the web version of the email interface, and click the "Recall" button or perform a similar operation to initiate a recall request. The recall request contains the unique identifier of the email that the sender user needs to recall.
[0053] After receiving the recall request, the sender system starts to construct a recall request email according to the recall request. In the recall request email, an extended MIME field is added to indicate that this email is a recall email, and the unique identifier of the email to be recalled and the list of users to be recalled are added to the email body of the recall request email.
[0054] S3: The sender system sends the recall request email to the recipient system.
[0055] After constructing the recall request email, the sender system sends the recall request email to the recipient system through the SMTP protocol. Similarly, the sender system establishes a connection with the SMTP server of the sender system, transfers the recall request email to the SMTP server of the sender system, the SMTP server of the sender system sends the recall request email to the SMTP server of the recipient system, and the SMTP server of the recipient system stores it in the recipient system after receiving the recall request email.
[0056] S4: The recipient system receives the recall request email and verifies the legality of the recall request email.
[0057] After receiving the recall request email, the recipient system verifies the legality of the recall request email, including but not limited to sender identity verification, email format verification, digital signature verification, and time validity verification. It can ensure that the recall request email comes from a legally authorized user and prevent the recall of emails by misusing identities.
[0058] S5: After verifying that it belongs to a legal recall request email, the recipient system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation according to the unique identifier, and deletes the emails found in the recipient's inbox that match the unique identifier of the email to be recalled.
[0059] After the recipient system confirms the legality of the recall request email, it extracts the unique identifier of the email to be recalled from the recall request email; it also needs to extract the list of recipients to be recalled from the rcpt to command, access the recipient's inbox data based on the recipient list, search the recipient's inbox data according to the unique identifier, and check whether each email in the recipient's inbox contains a field that matches the extracted unique identifier; if an email that matches the unique identifier of the email to be recalled is found, the recipient system deletes the email from the recipient's inbox.
[0060] After the receiving system deletes the email, a recall result notification email is sent to the sending system. The recall result notification email contains the result of the recall operation, such as successful recall, failed recall, and reasons for failure, etc.
[0061] In some embodiments, the sending system inserts a unique identifier into the email to be sent, including:
[0062] The sending system generates a unique identifier for the email to be sent through the UUID method and inserts the unique identifier into the email to be sent.
[0063] Specifically, a UUID code generation is integrated into the email system. The sending system calls the generated UUID code to generate a unique identifier for the email, converts it into a string format, and inserts the unique identifier in string format into the X-UNIQUE-ID field of the email header. This unique identifier X-UNIQUE-ID is used to uniquely identify the email and ensure global uniqueness across all systems.
[0064] When the sending system performs email delivery, it checks the email header of the email to be sent to confirm whether the X-UNIQUE-ID field exists in the email header of the email to be sent. If not, the X-UNIQUE-ID field needs to be added to the email header of the email to be sent. Ensure that all emails delivered contain a unique identifier.
[0065] In some embodiments, the sending system receives a recall request initiated by the user and constructs a signed recall request email, including:
[0066] Construct the email header and email body of the recall request email. Among them, the email header includes the sender address, recipient address, email subject, sending date, email type, and header signature field; the email body includes the original sender address, email subject, and unique identifier of the email to be recalled.
[0067] Specifically, the sending system sends a signed recall request email to the receiving system. The header of the recall request email must include the following fields: From: xxx, To: xxx, Subject: Recall Email: xxx, Date: xxx, X-CSMO-Type: recall, X-CSMO-Signature: xxx. Among them, From: xxx represents the sender address, To: xxx represents the recipient address, Subject: Recall Email: xxx represents the email subject, Date: xxx represents the sending date, X-CSMO-Type: recall represents the operation type as a recall email, and X-CSMO-Signature: xxx represents the signature field of the recall request email.
[0068] The body of the recall request email includes Sender: xxx, Subject: xxx, X-UNIQUE-ID: xxx. Among them, Sender: xxx represents the original sender address, which is the same as the address in the mailfrom command; Subject: xxx represents the email subject, which is optional and only used for tracking, not a necessary attribute; X-UNIQUE-ID: xxx represents the unique identifier, which is used to locate the email to be recalled.
[0069] In some embodiments, the recipient system receives the recall request email and verifies the legitimacy of the recall request email, including:
[0070] Verify the legitimacy of the sender address of the recall request email through email anti-forgery technology;
[0071] Verify the email header of the recall request email and check whether the email type contains recall;
[0072] Verify the legitimacy of the header signature field of the recall request email using the DomainKeys Identified Mail (DKIM) algorithm.
[0073] Specifically, the recipient system parses the server IP address of the sender of the recall request email and verifies whether the server IP address sending the recall request email is in the allowed list. If the server IP address is not in the allowed list, it is marked as a suspicious email or rejected.
[0074] Parse the information in the email header, check whether there is an X-CSMO-Type field in the email header, and whether the X-CSMO-Type field is recall. If the X-CSMO-Type field does not exist or exists but its value is not recall, it is processed as a normal email delivery.
[0075] Verify the signature of the X-CSMO-Signature field of the recall request email using the DomainKeys Identified Mail (DKIM) algorithm to ensure the integrity and legitimacy of the email.
[0076] In some embodiments, before the sender system sends the recall request email to the recipient system, it further includes:
[0077] The sender system sends an EHLO command to the recipient system;
[0078] Receive the extended attribute list returned by the recipient system through the EHLO command;
[0079] Judge whether the extended attribute list includes CSMO recall.
[0080] Specifically, in the SMTP protocol, the EHLO command is used for the initial greeting and negotiation between the client and the server. Through the EHLO command, the client can obtain a list of extended attributes supported by the server; by parsing the list of extended attributes returned by the server, all the extended attributes supported by the server are extracted, and it is checked whether the extracted extended attributes contain CSMOrecall to determine whether the receiving system supports cross-site recall. Among them, CSMO represents cross-site mail operation, and recall represents the recall function.
[0081] In some embodiments, after deleting the emails that match the unique identifier of the email to be recalled found by the search, it further includes:
[0082] The receiving system sends a recall result notification email to the sending system.
[0083] Among them, a recall result notification email is generated and sent to the user specified by the mailfrom command. Specifically, the header format of the recall result notification email is X-CSMO-Type: recall-report, X-CSMO-Signature: xxx, From: xxx, To: xxx, Subject: Recall Result: xxx, Date: xxx. X-CSMO-Type is the operation type, and recall-report represents the recall result report.
[0084] The format of the body of the recall result notification email includes: Sender: xxx, Subject: xxx, X-UNIQUE-ID: xxx, To: xxx, Code: xxx, Desc: xxx, To: xxx, Code: xxx, Desc: xxx. Among them, Sender: xxx represents the recipient who receives the recall result notification email after the system processes the recall email request, that is, the original sender of the email; Subject represents the original email subject, which is only used for tracking and is not an essential attribute; X-UNIQUE-ID represents the X-UNIQUE-ID of the original email; To represents the recipient who needs to be recalled, and each line represents a recipient.
[0085] Another exemplary embodiment of the present application provides a mail cross-site recall system, specifically including:
[0086] It includes a sending system and a receiving system. The sending system and the receiving system belong to the same mail system or different mail systems; the sending system includes the sending system, and the receiving system includes the receiving system;
[0087] The sender system is used to insert a unique identifier into the email to be sent and send the email to be sent to the recipient system through the SMTP protocol; receive the recall request initiated by the user, construct a signed recall request email, where the unique identifier of the email to be recalled is included in the recall request email, and send the recall request email to the recipient system;
[0088] The recipient system is used to receive the recall request email and verify the legitimacy of the recall request email; after the recall request email is verified to be legitimate, the recipient system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation based on the unique identifier, and deletes the email that matches the unique identifier of the email to be recalled found by the search.
[0089] In some embodiments, the sender system is specifically used to generate the unique identifier of the email to be sent by the UUID method.
[0090] For the specific limitations of the email cross-site recall system provided in this embodiment, reference can be made to the embodiments of the email cross-site recall method in the foregoing text, and details will not be elaborated here. Each module in the above email cross-site recall system can be implemented in whole or in part by software, hardware, and their combinations. The above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0091] An embodiment of the present application provides a computer device, which may include a processor, a memory, a network interface, and a database connected through a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, the processor is caused to execute the steps of the email cross-site recall method in any of the above embodiments.
[0092] For the working process, working details, and technical effects of the computer device provided in this embodiment, reference can be made to the embodiments of the email cross-site recall method in the foregoing text, and details will not be elaborated here.
[0093] An embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the email cross-site recall method in any of the above embodiments are implemented. Wherein, the computer-readable storage medium refers to a carrier for storing data, and may include, but is not limited to, floppy disks, optical discs, hard disks, flash memories, USB flash drives, and / or memory sticks, etc. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices.
[0094] For the working process, working details, and technical effects of the computer-readable storage medium provided in this embodiment, reference may be made to the embodiments of the email cross-site recall method in the foregoing text, and details will not be repeated here.
[0095] Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be completed by instructing relevant hardware through a computer program. The computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it may include the processes of the embodiments of the above methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application may include non-volatile and / or volatile memories. Non-volatile memories may include read-only memories (ROMs), programmable ROMs (PROMs), electrically programmable ROMs (EPROMs), electrically erasable programmable ROMs (EEPROMs), or flash memories. Volatile memories may include random access memories (RAMs) or external cache memories. By way of illustration and not limitation, RAMs are available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and Rambus dynamic RAM (RDRAM), etc.
[0096] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, it should be considered as the scope described in this specification.
[0097] Those skilled in the art can clearly understand that, for the convenience and brevity of description, only the above division of each functional unit and module is used as an example. In actual applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the system described in this application can be divided into different functional units or modules to complete all or part of the functions described above.
Claims
1. A method for cross-site recall of emails, characterized in that, Including: The sender system inserts a unique identifier into the email to be sent and sends the email to be sent to the recipient system via the SMTP protocol; The sender system receives a recall request initiated by the user, constructs a signed recall request email, and the recall request email contains the unique identifier of the email to be recalled; The sender system sends the recall request email to the recipient system; The recipient system receives the recall request email and verifies the legality of the recall request email; After verifying that it belongs to a legal recall request email, the recipient system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation according to the unique identifier, and deletes the emails that match the unique identifier of the email to be recalled.
2. The email cross-site recall method according to claim 1, wherein The sender system inserts a unique identifier into the email to be sent, including: The sender system generates a unique identifier for the email to be sent by the UUID method and inserts the unique identifier into the email to be sent.
3. The email cross-site recall method according to claim 1, characterized in that The sender system receives a recall request initiated by the user and constructs a signed recall request email, including: Construct the email header and email body of the recall request email. Among them, the email header includes the sender address, recipient address, email subject, sending date, email type, and header signature field; the email body includes the original sender address, email subject, and unique identifier of the email to be recalled.
4. The method for cross-site recall of emails according to claim 3, wherein, The recipient system receives the recall request email and verifies the legality of the recall request email, including: Verify the legality of the sender address of the recall request email through email anti-forgery technology; Verify the email header of the recall request email and check whether the email type contains "recall"; Use the DomainKeys Identified Mail algorithm to verify the legality of the header signature field of the recall request email.
5. The email cross-site recall method according to claim 1, characterized in that Before the sender system sends the recall request email to the recipient system, it also includes: The sender system sends an EHLO command to the recipient system; Receive the extended attribute list returned by the recipient system through the EHLO command; Judge whether the extended attribute list includes "CSMO recall".
6. The method for cross-site recall of emails according to claim 1, characterized in that, After deleting the emails that match the unique identifier of the email to be recalled, it also includes: The recipient system sends a recall result notification email to the sender system.
7. A cross-site recall system for emails, characterized in that, Including a sender system and a recipient system; The sender system is used to insert a unique identifier into the email to be sent, send the email to be sent to the recipient system via the SMTP protocol; receive a recall request initiated by the user, construct a signed recall request email, and the recall request email contains the unique identifier of the email to be recalled, and send the recall request email to the recipient system; The recipient system is used to receive the recall request email and verify the legality of the recall request email; After verifying that it belongs to a legal recall request email, the recipient system extracts the unique identifier of the email to be recalled from the recall request email, performs an email search operation according to the unique identifier, and deletes the emails that match the unique identifier of the email to be recalled.
8. The email cross-site recall system according to claim 7, wherein The sender system is specifically used to generate a unique identifier for the email to be sent by the UUID method and insert the unique identifier into the email to be sent.
9. A computer device, characterized in that, It includes a memory, a processor, and a computer program stored in the memory. The processor executes the computer program to implement the steps of the method according to any one of claims 1 to 6.
10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.