WO2016169434A1

WO2016169434A1 - E-mail retransmission method and device

Info

Publication number: WO2016169434A1
Application number: PCT/CN2016/079372
Authority: WO
Inventors: 刘美朝
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2015-04-22
Filing date: 2016-04-15
Publication date: 2016-10-27
Also published as: CN106161198A; CN106161198B

Abstract

Provided are an e-mail retransmission method and device. The method comprises: recognizing whether an e-mail from an opposite-end mail client is a retransmission instruction mail; if the e-mail from the opposite-end mail client is the retransmission instruction mail, parsing a retransmitted mail identifier from the e-mail coming from the opposite-end mail client; and retransmitting the transmitted e-mail identified by the retransmitted mail identifier to the opposite-end mail client. The present application can realize automatic retransmission of an e-mail, thereby improving the efficiency of retransmitting the e-mail.

Description

Email retransmission method and device

The present application claims priority to Chinese Patent Application Serial No. No. No. No. No. No. No. No. No. No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No No

Technical field

The present application relates to the field of Internet technologies, and in particular, to an email retransmission method and apparatus.

Background technique

E-mail is a communication method that provides information exchange by means of electronic means, and is the most widely used service of the Internet. Through the email system, users can connect with network users in any corner of the world at a very low price and in a very fast way.

In an existing email system, after the sender has written a message on his mail client, the sender sends the message through the send function on the mail client. The recipient receives the message from the sender through their mail client. In practice, the recipient sometimes needs the sender to resend the message, such as not receiving the message or the required message has been deleted, at which point the recipient needs the sender to resend the message.

The current process of requesting the sender to resend the mail is generally: the recipient informs the sender that the mail needs to be resent in a certain way; after the sender knows that the mail needs to be resent, the first thing to find is that it needs to be resent from the sent mail. The message is then resent by the send function on its client, which requires the sender to manually participate and the resend is less efficient.

Summary of the invention

Aspects of the present application provide an email retransmission method and apparatus for improving the efficiency of resending an email.

An aspect of the present application provides an email retransmission method, including:

Identify whether the email from the peer mail client is a resend indication email;

If the email from the peer mail client is a resend indication email, parsing the resend email identifier from the email from the peer mail client;

Sending the sent email identified by the resend mail identity to the peer mail client.

In another aspect of the present application, an email retransmission method is provided, including:

Generating a resend indication mail, where the resend indication mail includes a resend mail identifier;

Sending the resending indication mail to the peer mail client, so that the peer mail client resends the sent email identified by the resend mail identifier;

Receiving the sent email identified by the resend mail identifier resent by the peer mail client.

In still another aspect of the present application, a mail client is provided, including:

An identification module, configured to identify whether the email from the peer mail client is a resend indication email;

a parsing module, configured to parse the resend mail identifier from the email from the peer mail client when the email from the peer mail client is a resend email;

And a resending module, configured to resend the sent email identified by the resend mail identifier to the peer mail client.

a generating module, configured to generate a resend indication mail, where the resend indication mail includes a resend mail identifier;

a sending module, configured to send the resend indication mail to the peer mail client, where the peer mail client resends the sent email identified by the resend mail identifier;

And a receiving module, configured to receive the sent email identified by the resend mail identifier resent by the peer mail client.

It can be seen from the above technical solution that the present application identifies whether the email from the peer mail client is a resend indication email, and when the email from the peer email client is identified as a resend email, the resend email identifier is parsed therefrom. According to the resend mail identifier, the sent e-mail that needs to be resent is determined, and then the sent mail identified by the re-sending mail identifier is resent to the peer mail client, so that the automatic re-sending of the e-mail is realized, and the sender is not required. Manual participation increases the efficiency of resending emails.

DRAWINGS

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings used in the embodiments or the prior art description will be briefly described below. Obviously, the drawings in the following description are the present application. For some embodiments, other drawings may be obtained from those of ordinary skill in the art in light of the inventive workability.

1 is a schematic flowchart of an email resending method according to an embodiment of the present disclosure;

2 is a schematic flowchart of a method for resending an email according to another embodiment of the present disclosure;

FIG. 3 is a schematic structural diagram of a mail client according to an embodiment of the present disclosure;

FIG. 4 is a schematic structural diagram of a mail client according to another embodiment of the present application.

detailed description

The technical solutions in the embodiments of the present application are clearly and completely described in the following with reference to the accompanying drawings in the embodiments of the present application. It is a part of the embodiments of the present application, and not all of the embodiments. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of the present application without departing from the inventive scope are the scope of the present application.

FIG. 1 is a schematic flowchart diagram of an email resending method according to an embodiment of the present application. As shown in Figure 1, the method includes:

101. Identify whether the email from the peer mail client is a resend indication email.

102. If the email from the peer mail client is a resend indication email, the resend email identifier is parsed from the email from the peer mail client.

103. Resend the sent email identified by the resend mail identifier to the peer mail client.

The embodiment provides an email resending method, which can be executed by a mail client in an email system, and can be executed by a mail client as a sender, which is simply referred to as a local mail client. The peer mail client described in this embodiment specifically refers to a mail client as a recipient. The method of the embodiment is mainly used for realizing automatic retransmission of e-mails, liberating the sender from the process of re-sending the e-mail, and improving the re-transmission efficiency of the e-mail.

In order to realize automatic retransmission of an email, the embodiment expands a mail type, that is, resends an email indicating that the email needs to be resent on the one hand, and the email that needs to be retransmitted on the other hand, the resending indication Mail is different from regular email. In addition, for the mail client as the sender, it is necessary to add a function of recognizing the retransmission instruction mail and resending the sent e-mail according to the retransmission instruction mail. Based on this, the process of resending an email is as follows:

The local mail client receives the email from the peer mail client; identifies whether the email from the peer mail client is a resend indication email; if the email from the peer mail client is a resend email, from the peer Resending the email identifier in the email of the mail client, the resending email identifier is used to indicate the sent email that needs to be resent; according to the resending email identifier, the sent email that needs to be resent can be determined, and then the pair is sent The end mail client resends the sent e-mail identified by the resend mail ID.

In an optional implementation manner, the command specification of the resending indication email may be pre-agreed between the local mail client and the peer mail client, and the resending indication email needs to be written according to the instruction specification. The instruction specification stipulates that the resend indication mail needs to include a retransmission instruction symbol, by which the retransmission instruction mail and the non-retransmission indication mail can be distinguished, and the non-retransmission indication mail actually refers to a regular e-mail.

Based on the above, a method for identifying whether the email from the peer mail client is a resend email includes: parsing the email from the peer mail client according to the agreed instruction specification to determine the email from the peer mail client. Whether the email includes a resend command character; if the email from the peer mail client includes a resend command, it is determined that the email from the peer mail client is a resend indication email; if the email from the peer mail client does not include Resend the command to determine that the email from the peer mail client is not a resend indication message.

It should be noted that the above retransmission command may be located in the subject part or in the body part, and may be specified in the instruction specification.

Further, the above instruction specification further stipulates that the resend indication mail needs to include a resend mail identifier for indicating an email that needs to be resent by the peer mail client. Based on this, a method for parsing the resend mail identifier from the email from the peer mail client includes: parsing the email from the peer mail client according to the agreed instruction specification to obtain the resend mail identifier.

It should be noted that the above resending mail identifier may be located in the subject part or in the body part, and may be specified in the instruction specification.

For example, an instruction specification may include: two "#" symbols + numbers + letters d. The two "#" numbers in the above instruction specification are fixed and can be used as retransmission command symbols. If two "#" numbers are found in the email, the email can be determined to be a resend indication mail; The letter d in the day indicates the number, and the number can be arbitrarily specified, indicating how many emails have been sent within the specified day. The "number + letter d" in the specification of the instruction indicates the resending mail identifier, and the resending mail identifier is specific. The time range for sending sent messages.

Based on the above, when the email from the peer mail client is identified as the resend mail, and the resend mail identifier is parsed from the resend mail, the identifier of the resend mail identifier may be retrieved from the sent email. An email has been sent and the retrieved sent email has been resent to the peer mail client.

In an optional implementation manner, if there are multiple sent emails identified by the resending email identifier, the email can be resent to the peer email client one by one. In short, one email to the opposite email The client sends.

In another optional implementation manner, in order to reduce the number of retransmissions, the retransmission efficiency is further improved, and the user experience is improved. When the number of sent e-mails identified by the resend mail identifier is multiple, the identifier of the resend mail identifier may be identified. The sent emails are merged to generate a new email that is sent to the peer mail client.

A method of merging sent emails identified by a resend mail identifier to generate a new email includes: merging the subject, body, and attachment identifier of the sent email identified by the resend mail identifier into the first File; merges the attachments in the sent email identified by the resend mail ID into a second file; the first file and the second file are attached to the new email to generate a new email.

The identifier of the above attachment may be, but is not limited to, the name of the attachment. The first file may be a PDF file, a txt file, or a word file. The second file described above may be a compressed package, but is not limited thereto.

It is worth noting that some of the sent emails identified by the resend message identifier above may have attachments, and some emails may not have attachments, so you can merge attachments from all emails with attachments. Into the second file. In order to determine which email the attachment in the second file belongs to, each email may be uniquely identified, and the name of the attachment in the second file is marked with the identifier of the email to which the attachment belongs, and the attachment is The associated email is associated. For example, suppose you have an email with a unique identifier of a, which includes two attachments. The names of the attachments are My Documents and My Photos, respectively, and the names of the attachments in the second file are a-My Documents. And a-my photos.

In an optional implementation manner, the user is configured to pre-configure the sending mode of the local mail client. If the user configures the sending mode for the local mail client, the sent identity identified by the resending mail identifier is retrieved. After the email, the retrieved emails are automatically merged to form a new email, and a new email is sent to the peer mail client. In this embodiment, the local mail client can determine whether the merge sending mode is configured before sending the sent email identified by the resending mail identifier to the peer mail client. If the merge sending mode is configured, The merged emails identified by the resend mail identifier are merged to generate a new email, and then the new email is sent to the peer mail client; if the merge delivery method is not configured, the email is sent to the peer mail client one by one. Resent the identity of the message An email has been sent. The user is allowed to configure the sending mode for the local mail client, instead of directly adopting the combined sending mode, and the implementation is more flexible, which is beneficial to improving the security of the user information.

In another optional implementation manner, the foregoing instruction specification further stipulates that the resending indication mail includes: a merge sending instruction, which is used to indicate that the emails that need to be resent are combined and sent together. Based on this, when the email from the peer mail client is a resend indication email, the method further includes: parsing the merge sending instruction from the email from the peer mail client. Based on this, the foregoing method for combining the sent emails identified by the resend mail identifier to generate a new email is specifically: combining the sent emails identified by the resending mail identifier according to the merge sending instruction, Generate a new email.

In an optional implementation manner, the foregoing instruction specification further stipulates that the resending indication mail includes: a sorting instruction, configured to instruct to sort the emails that need to be resent and then send the emails. Based on this, when the email from the peer mail client is a resend indication email, the method further includes: parsing the sorting instruction from the email from the peer mail client. Based on the above, before the method for generating the new email by combining the sent emails identified by the resending mail identifier, the method further includes: sorting the sent emails identified by the resending mail identifier according to the sorting instruction, For example, the order may be sorted according to the order in which the sent emails are sent, or may be sorted in the reverse order of the sent time of the sent emails. Based on the sorting operation, the above-mentioned sent emails identified by the resend mail identifier are merged to generate a new email, specifically: the sent emails identified by the sorted resend mail identifier are merged to generate a new one. e-mail.

For example, an instruction specification includes: two "#" sign + number + letter d constitute + less than (or greater than). The less than sign in the specification of the directive represents the sorting of emails that need to be resent in the order in which they were sent. Alternatively, the greater than the number in the specification of the instruction represents sorting the emails that need to be resent in the reverse order of the time the message was sent.

For example, the content "##10d<" in the resend indication mail indicates that it is desired to resend the e-mail that has been sent within 10 days, and the e-mail that needs to be resent is performed in the order of the e-mail sending time before the e-mail is sent. Sort, then merge and send the sorted emails.

It can be seen from the above analysis that the embodiment determines whether the email from the peer email client is a resend email, and when the email from the peer email client is identified as a resending email, the resending email identifier is parsed therefrom. According to the resend mail identifier, the sent e-mail that needs to be resent is determined, and then the sent mail identified by the re-sending mail identifier is resent to the peer mail client, so that the automatic re-sending of the e-mail is realized, and the sender is not required. Manual participation increases the efficiency of resending emails.

FIG. 2 is a schematic flowchart diagram of an email resending method according to another embodiment of the present application. As shown in Figure 2, the method includes:

201. Generate a resend indication email, where the resend indication email includes a resend email identifier.

202. Send the resending indication mail to the peer mail client, so that the peer mail client resends the sent email identified by the resending mail identifier.

203. Receive the sent email identified by the resend mail identifier that is resent by the peer mail client.

The embodiment provides an email resending method, which can be executed by a mail client in an email system, and can be executed by a mail client as a recipient, which is simply referred to as a local mail client. The peer mail client described in this embodiment specifically refers to a mail client as a sender. The method of the embodiment is mainly used for realizing automatic retransmission of e-mails, liberating the sender from the process of re-sending the e-mail, and improving the re-transmission efficiency of the e-mail.

In order to realize automatic retransmission of an email, the embodiment expands a mail type, that is, resends an email indicating that the email needs to be resent on the one hand, and the email that needs to be retransmitted on the other hand, the resending indication Mail is different from regular email. In addition, for the mail client as the recipient, it is necessary to increase the function of generating a resend instruction mail. Based on this, the process of resending an email is as follows:

The local mail client generates a resend indication email, and sends a resend indication email to the peer email client; the peer email client receives the resend email from the local email client, and parses the resend email identifier from the local email client. The resend mail identifier is used to indicate the sent e-mail that needs to be resent, and according to the re-sent mail identifier, the sent e-mail that needs to be re-sent can be determined, and then the local mail client resends the identifier of the re-sent mail identifier. The email has been sent; the local mail client receives the sent email identified by the above-mentioned resend mail identifier resent by the peer mail client.

In an optional implementation manner, the command specification of the resending indication email may be pre-agreed between the local mail client and the peer mail client, and the resending indication email needs to be generated according to the instruction specification. The instruction specification stipulates that the resend indication mail needs to include a retransmission instruction symbol, by which the retransmission instruction mail and the non-retransmission indication mail can be distinguished, and the non-retransmission indication mail actually refers to a regular e-mail.

Further, the above instruction specification further stipulates that the resend indication mail needs to include a resend mail identifier for indicating an email that needs to be resent by the peer mail client.

For example, an instruction specification may include: two "#" symbols + numbers + letters d. The two "#" numbers in the specification of the instruction are fixed and can be used as retransmission instructions; the letter d in the specification of the instruction indicates the day, and the number can be arbitrarily specified, indicating how many days have elapsed to send the e-mail. The "number + letter d" in the specification of the instruction indicates the resending mail identifier, and the resending mail identifier is specifically the transmission time range of the sent mail.

In an optional implementation manner, if the number of sent emails identified by the resend mail identifier is multiple, the peer mail client may resend to the local mail client one by one, in short, one letter Send to the local mail client. Based on this, the local mail client can receive the e-mail sent by the peer mail client one by one.

In another optional implementation manner, in order to reduce the number of retransmissions, further improve the retransmission efficiency, and improve the user experience, when the resent mail identifier identifies multiple sent e-mails, the peer mail client may be heavy. The sent emails identified by the email identifier are merged to generate a new email, which is sent to the local mail client. Based on this, the manner in which the local mail client receives the sent email identified by the resend mail identifier sent by the peer mail client includes: receiving a new email sent by the peer mail client; downloading the attachment of the new email The first file and the second file; obtaining, from the first file, the subject, the body, and the identifier of the sent email identified by the resending mail identifier; and obtaining the sent identifier identified by the resending mail identifier from the second file An attachment to the email.

In an optional implementation manner, the foregoing instruction specification further stipulates that the resending indication mail includes: a merge sending instruction, which is used to indicate that the emails that need to be resent are combined and sent together.

In an optional implementation manner, the foregoing instruction specification further stipulates that the resending indication mail includes: a sorting instruction, configured to instruct to sort the emails that need to be resent and then send the emails.

It can be seen from the above analysis that the embodiment sends a resend indication email to the peer email client, so that the peer email client can automatically parse the resend email identifier from the resend email. According to the resend mail identifier, the sent e-mail that needs to be resent is determined, and then the sent mail identified by the re-sent mail identifier is returned, so that the automatic re-sending of the e-mail is realized, and the sender is not required to manually participate, and the re-send email is improved. s efficiency.

For example, when the local mail client finds that there are too many emails, and can not quickly find the required emails from the plurality of emails, the method provided in the foregoing embodiment may be used to send a resend indication email to the peer email client. The peer mail client resends the required email. For example, if the local mail client finds that the required email is discarded, for example, the required email is discarded due to the frequency limitation of the sending, etc., the method provided by the foregoing embodiment may be used to reach the peer mail client. Send a resend indication message instructing the peer mail client to resend the required email.

It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations, but those skilled in the art should understand that the present application is not limited by the described action sequence. Because certain steps may be performed in other sequences or concurrently in accordance with the present application. In the following, those skilled in the art should also understand that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

In the above embodiments, the descriptions of the various embodiments are different, and the details that are not detailed in a certain embodiment can be referred to the related descriptions of other embodiments.

FIG. 3 is a schematic structural diagram of a mail client according to an embodiment of the present disclosure. The mail client provided in this embodiment can be implemented as a mail client of the sender. As shown in FIG. 3, the mail client includes an identification module 31, a parsing module 32, and a retransmission module 33.

The identification module 31 is configured to identify whether the email from the peer mail client is a resend indication email.

The parsing module 32 is configured to parse the resend mail identifier from the e-mail from the peer mail client when the recognizing module 31 recognizes that the e-mail from the peer mail client is a re-instruction mail.

The resending module 33 is configured to resend the sent email identified by the resend mail identifier parsed by the parsing module 32 to the peer mail client.

In an optional implementation manner, the identifying module 31 is specifically configured to: parse the email from the peer mail client according to the agreed instruction specification, to determine whether the email from the peer mail client includes a resend command character; If the email from the peer mail client includes a resend command, it is determined that the email from the peer mail client is a resend mail; if the email from the peer mail client does not include the resend command, it is determined from the peer The email of the mail client is a non-reposting email.

In an optional implementation, the parsing module 32 is specifically configured to: parse the email from the peer mail client according to the agreed instruction specification to obtain the resend mail identifier.

In an optional implementation, the retransmission module 33 is specifically configured to: merge the sent emails identified by the resend mail identifier to generate a new email, and send a new email to the peer mail client.

Further, when the retransmission module 33 merges the sent emails identified by the resend mail identifier to generate a new email, it is specifically used to:

Merging the subject, body, and attachment identifier of the sent email identified by the resend mail identifier into a first file; merging the attachments in the sent email identified by the resend mail identifier into a second file; The file and the second file are attached to the new email to generate a new email.

Further, the parsing module 32 is further configured to parse the merge sending instruction from the email from the peer mail client. Based on this, the retransmission module 33, when used to merge the sent emails identified by the resend mail identifier to generate a new email, is specifically used for: retransmitting according to the merge sending instruction parsed by the parsing module 32. The sent emails identified by the message ID are merged to form a new email.

Further, the parsing module 32 is further configured to parse the sorting instruction from the email from the peer mail client. Based on this, the retransmission module 33 is further configured to: before the merged emails identified by the resend mail identifier are merged to generate a new email, according to the sorting instruction, the sent email identified by the resend mail identifier is identified Sort.

In an optional implementation manner, the resending mail identifier may be a mail sending time range.

The mail client provided in this embodiment is implemented as a mail client of the sender, by identifying whether the email from the peer email client is a resend email, and identifying the email from the peer email client is heavy. When the email is sent, the resend mail identifier is parsed from the re-sent mail identifier, and the sent e-mail that needs to be resent is determined according to the re-sent mail identifier, and the re-sent mail identifier is resent to the peer mail client. The identified emails are sent to realize the automatic retransmission of emails without the need for the sender to participate manually, which improves the efficiency of resending emails.

FIG. 4 is a schematic structural diagram of a mail client according to another embodiment of the present application. The mail client provided in this embodiment can be implemented as a mail client of the recipient. As shown in FIG. 4, the mail client includes a generating module 41, a sending module 42, and a receiving module 43.

The generating module 41 is configured to generate a resend indication mail, and the resend indication mail includes a resend mail identifier.

The sending module 42 is configured to send the resend indication email generated by the generating module 41 to the peer mail client, so that the peer mail client resends the sent email identified by the resending mail identifier.

The receiving module 43 is configured to receive the sent email identified by the resend mail identifier resent by the peer mail client.

In an optional implementation, the command specification of the resending indication mail may be pre-agreed between the mail client and the peer mail client in this embodiment, and the generating module 41 may specifically generate a resend indication according to the instruction specification. mail.

In an optional implementation, the receiving module 43 is specifically configured to: receive a new email sent by the peer email client; download the first file and the second file in the attachment of the new email; and obtain the weight from the first file. The email identifies the subject, body, and attachment of the sent email identified; the attachment to the sent email identified by the resend email identifier is obtained from the second file.

The mail client provided in this embodiment is implemented as a mail client of the recipient, and generates a resend indication mail and sends the resend indication mail to the peer mail client, so that the peer mail client can automatically resend the mail. The e-mail identifier is parsed in the indication mail, and the sent e-mail that needs to be re-sent is determined according to the re-sent mail identifier, and then the sent e-mail identified by the re-sending mail identifier is returned, so that the automatic re-sending of the e-mail is not required. The manual participation of people has improved the efficiency of resending emails.

A person skilled in the art can clearly understand that for the convenience and brevity of the description, the specific working process of the system, the device and the unit described above can refer to the corresponding process in the foregoing method embodiment, and details are not described herein again.

In the several embodiments provided by the present application, it should be understood that the disclosed system, apparatus, and method may be implemented in other manners. For example, the device embodiments described above are merely illustrative. For example, the division of the unit is only a logical function division. In actual implementation, there may be another division manner, for example, multiple units or components may be combined or Can be integrated into another system, or some features can be ignored or not executed. In addition, the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, and may be in an electrical, mechanical or other form.

The units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, may be located in one place, or may be distributed to multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of hardware plus software functional units.

The above-described integrated unit implemented in the form of a software functional unit can be stored in a computer readable storage medium. The software functional unit described above is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) or a processor to perform the methods described in various embodiments of the present application. Part of the steps. The foregoing storage medium includes: a U disk, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk, and the like, which can store program codes. .

Finally, it should be noted that the above embodiments are only used to explain the technical solutions of the present application, and are not limited thereto; although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that they can still The technical solutions described in the foregoing embodiments are modified, or the equivalents of the technical features are replaced by the equivalents. The modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

An email resending method, comprising:

Identify whether the email from the peer mail client is a resend indication email;

If the email from the peer mail client is a resend indication email, parsing the resend email identifier from the email from the peer mail client;

Sending the sent email identified by the resend mail identity to the peer mail client.
The method according to claim 1, wherein the identifying whether the email from the peer mail client is a resend indication email comprises:

Determining, by the agreed instruction specification, the email from the peer mail client to determine whether the email from the peer mail client includes a resend command character;

If the email from the peer mail client includes the resend command, determining that the email from the peer mail client is a resend indication email;

If the email from the peer mail client does not include the resend command, it is determined that the email from the peer mail client is a non-retransmission indication mail.
The method according to claim 1, wherein the parsing the resend mail identifier from the email from the peer mail client comprises:

According to the agreed instruction specification, the email from the peer mail client is parsed to obtain the resend mail identifier.
The method according to claim 1, wherein the resending the sent email identified by the resend mail identifier to the peer mail client comprises:

The sent emails identified by the resend mail identity are merged to generate a new email, and the new email is sent to the peer mail client.
The method of claim 4, wherein the merging the sent emails identified by the resend mail identity to generate a new email comprises:

Merging the subject, the body, and the identifier of the attached email identified by the resend mail identifier into a first file;

Merging the attachments in the sent emails identified by the resend mail identifier into a second file;

The first file and the second file are attached to the new email to generate the new email.
The method of claim 4, further comprising:

Parsing the merge sending instruction from the email from the peer mail client;

The merging the sent emails identified by the resend mail identifier to generate a new email includes:

And according to the merge sending instruction, the sent emails identified by the resend mail identifier are merged to form the new email.
The method of claim 4, further comprising:

Parsing the sort instruction from the email from the peer mail client;

The merging of the sent emails identified by the resend mail identifier to generate a new email further includes:

Sorting the sent emails identified by the resend mail identifier according to the sorting instruction.
The method according to any one of claims 1 to 7, wherein the resending mail is identified as a mail transmission time range.
An email resending method, comprising:

Generating a resend indication mail, where the resend indication mail includes a resend mail identifier;

Sending the resending indication mail to the peer mail client, so that the peer mail client resends the sent email identified by the resend mail identifier;

Receiving the sent email identified by the resend mail identifier resent by the peer mail client.
The method according to claim 9, wherein the receiving the sent email identified by the resend mail identifier resent by the peer mail client comprises:

Receiving a new email sent by the peer mail client;

Downloading the first file and the second file in the attachment of the new email;

Obtaining, from the first file, an identifier of a subject, a body, and an attachment of the sent email identified by the resending mail identifier;

Acquiring an attachment of the sent email identified by the resend mail identifier from the second file.
A mail client, comprising:

An identification module, configured to identify whether the email from the peer mail client is a resend indication email;

a parsing module, configured to parse the resend mail identifier from the email from the peer mail client when the email from the peer mail client is a resend email;

And a resending module, configured to resend the sent email identified by the resend mail identifier to the peer mail client.
The mail client according to claim 11, wherein the identification module is specifically configured to:

Determining, by the agreed instruction specification, the email from the peer mail client to determine whether the email from the peer mail client includes a resend command character;

If the email from the peer mail client includes the resend command, determining that the email from the peer mail client is a resend indication email;

If the email from the peer mail client does not include the resend command, it is determined that the email from the peer mail client is a non-retransmission indication mail.
The mail client according to claim 11, wherein the parsing module is specifically configured to:

According to the agreed instruction specification, the email from the peer mail client is parsed to obtain the resend mail identifier.
The mail client according to claim 11, wherein the retransmission module is specifically configured to:

The sent emails identified by the resend mail identity are merged to generate a new email, and the new email is sent to the peer mail client.
The mail client according to claim 14, wherein the retransmission module is specifically configured to:

Merging the subject, the body, and the identifier of the attached email identified by the resend mail identifier into a first file;

Merging the attachments in the sent emails identified by the resend mail identifier into a second file;

The first file and the second file are attached to the new email to generate the new email.
The mail client according to claim 14, wherein

The parsing module is further configured to: parse the merge sending instruction from the email from the peer mail client;

The retransmission module is specifically configured to: according to the merge sending instruction, merge the sent emails identified by the resend mail identifier to form the new email.
The mail client according to claim 14, wherein

The parsing module is further configured to: parse the sorting instruction from the email from the peer mail client;

The retransmission module is further configured to: sort the sent emails identified by the resend mail identifier according to the sorting instruction.
The mail client according to any one of claims 11-17, wherein the resend mail identifier is a mail sending time range.
A mail client, comprising:

a generating module, configured to generate a resend indication mail, where the resend indication mail includes a resend mail identifier;

a sending module, configured to send the resend indication mail to the peer mail client, where the peer mail client resends the sent email identified by the resend mail identifier;

And a receiving module, configured to receive the sent email identified by the resend mail identifier resent by the peer mail client.
The mail client according to claim 19, wherein the receiving module is specifically configured to:

Receiving a new email sent by the peer mail client;

Downloading the first file and the second file in the attachment of the new email;

Obtaining, from the first file, an identifier of a subject, a body, and an attachment of the sent email identified by the resending mail identifier;

Acquiring an attachment of the sent email identified by the resend mail identifier from the second file.