CN102984051A - Mail sending method, mail receiving method and mail management system - Google Patents

Abstract

The invention relates to the field of computers, and discloses a mail sending method, a receiving method and a mail management system. The mail receiving method is as follows: connect to the mail server, log in at least one mailbox in the mailbox list, and receive the mail in the mailbox; add the received mail to the mail list; determine the connection between the received mail and each user account Mapping relationship; according to the mapping relationship, each of the mails in the mailing list is transferred to each of the corresponding user accounts, so that each user can log in to the user account and manage the calls to the user account mail. The adoption of the technical solution can facilitate the arrangement of internal resources and information of the enterprise, and avoid the loss of potential customers and business opportunities.

Description

A mail sending method, receiving method and mail management system

technical field

The invention relates to the field of computers, in particular to a mail sending method, a receiving method and a mail management system.

Background technique

In the process of communication between enterprises and customers, data or materials are often exchanged by mail. Existing enterprises use a single person and a single mailbox to send and receive emails. Everyone has their own mailbox, and the sending and receiving of emails is managed by individuals. For sales or customer service personnel in the enterprise, there are some potential customers and business opportunities in their mailboxes, and due to the frequent changes of such personnel, their mailboxes are often revoked or no longer used, which will cause customers and business opportunities for the enterprise Loss. In addition, new employees cannot check or manage the emails of resigned employees after joining the company, which is not conducive to the handover of work; or superior managers cannot check or manage emails of subordinate employees during the work process, lacking monitoring of subordinate employees with guidance.

Contents of the invention

The first purpose of the embodiments of the present invention is to provide a method for receiving emails. The application of this technical solution can facilitate the arrangement of internal resources and information of the enterprise, and avoid the loss of potential customers and business opportunities.

The second purpose of the embodiments of the present invention is to provide a method for sending emails. The application of this technical solution can facilitate the arrangement of internal resources and information of the enterprise, and avoid the loss of potential customers and business opportunities.

The third purpose of the embodiment of the present invention is to provide an email management system, the application of this technical solution can facilitate the organization of internal resources and information of the enterprise, and avoid the loss of potential customers and business opportunities.

In the first aspect, a method for receiving mail provided by an embodiment of the present invention includes:

Connect to the mail server, log in at least one mailbox in the mailbox list, and receive the mail in the mailbox;

adding said received mail to a mailing list;

determining the mapping relationship between the received email and each user account;

According to the mapping relationship, each of the emails in the email list is transferred to each of the corresponding user accounts, so that each user can log into the user account and manage the emails transferred to the user account.

With reference to the first aspect, in the first implementation manner, the determining the mapping relationship between the received email and each user account specifically includes:

determining the mapping relationship between the received mail and each of the user accounts according to the calling record of each mail in the mail list;

Or according to the address mapping table preset in the mail list, determine the mapping relationship between the received mail and each of the user accounts;

Wherein, the address mapping table includes: the mapping relationship between the customer's email address and each of the user accounts.

In combination with the first implementation of the first aspect, in the second implementation, the determining the mapping relationship between the received email and each user account further includes:

The user actively determines the mapping relationship between the received email and each of the user accounts.

In combination with the first aspect, in the third implementation manner, the connection to the mail server, logging into at least one mailbox in the mailbox list, and receiving the mail in the mailbox, specifically:

Connect to at least one of the mail servers, log in to at least one of the mailboxes according to the mailbox information stored in the mailbox list, and receive the mail in the mailbox;

Wherein, the mailbox information includes: mailbox account, mailbox password, mail transfer protocol, post office protocol, and port information of the mail server.

In a second aspect, the present invention provides a method for sending mail, including:

The user logs in the user account and adds the email to be sent to the mailing list;

According to the calling records in the mailing list, determine the sending mailbox of the mail to be sent;

Connect to the mail server, log in the sending mailbox, and send the waiting mail.

With reference to the second aspect, in the first implementation form, the determining the sending mailbox of the email to be sent according to the calling record of the mailing list specifically includes:

The sending mailbox of the email to be sent is determined according to the sending mailbox with the highest usage frequency of the user account in the call record.

In combination with the second aspect, in the second implementation manner, the connecting to the mail server, logging into the sending mailbox, and sending the to-be-sent mail specifically include:

Log in to the mail server according to the mailbox information stored in the mailbox list, and send the mail to be sent.

In a third aspect, this embodiment provides a mail management system, including: a mail sending and receiving module, a mail management module, a mapping determination module, and a mail calling module;

The mail sending and receiving module is used to connect to the mail server, log in at least one mailbox in the mailbox list, and receive or send the mail in the mailbox;

The mail management module is electrically connected to the mail sending and receiving module, and is used to add the received or sent mails to a mailing list;

The mapping determination module is electrically connected to the mail management module and the mail calling module, and is used to determine the mapping relationship between each mail and each user account according to the information of each mail in the mail list;

The mail invoking module is electrically connected to the mapping determination module and the mail management module, and is used to transfer each of the mails in the mail list to the corresponding user accounts according to the mapping relationship, so as to For each user to log in to the user account, manage the emails transferred to the user account.

With reference to the third aspect, in the first implementation manner, the mail sending and receiving module is specifically configured to: connect to at least one of the mail servers, log in to at least one of the mailboxes according to the mailbox information stored in the mailbox list, and receive or send the mail in the said mailbox;

Wherein, the mailbox information includes: mailbox account, mailbox password, mail transfer protocol, post office protocol, and port information of the mail server.

With reference to the third aspect, in the second implementation manner, the mail management module is further configured to: manage each of the mails in the mailing list;

Specifically including: writing, replying, forwarding, deleting the email, and saving the email as a draft.

With reference to the third aspect, in a third implementation manner, the mapping determining module is specifically configured to: determine the mapping relationship between each of the emails and each of the user accounts according to the email address of each of the emails in the email list ;

Wherein, there is a mapping relationship between each email and at least one user account.

With reference to the third aspect, in a fourth implementation manner, the mapping determining module is further configured to: actively determine a mapping relationship between each of the emails in the email list and each of the user accounts.

With reference to the third aspect, in a fifth implementation manner, the system further includes:

A user account management module, configured to manage each of the user accounts.

In combination with the third aspect or any one of the first to fifth implementation manners, in the sixth implementation manner, the system further includes:

A statistical module, electrically connected to the mail management module, for counting the frequency of occurrence of keywords or sentences input by the user in each of the mail contents, obtaining statistical results, and providing the statistical results to the user.

It can be seen from the above that by applying the technical solution of this embodiment, in the mail management process, employees of the enterprise only need to create a user account in the management system, and log in to the management system with the user account to write, receive, and send normal emails. And other mail management functions. The management system archives and backs up the emails sent and received by each employee, and transfers the emails to different user accounts to complete the work of different needs. Compared with the existing technology, each employee has his own mailbox, and the management of emails is also managed separately, and the utilization rate of emails and information sharing are low. However, by adopting the technical solution of the present invention, the management system can uniformly manage and call the sending and receiving mailboxes and sending and receiving mails, which is beneficial to the arrangement of internal resources and information of the enterprise.

Furthermore, due to the unified management of emails, even if an employee resigns or is transferred, the employee’s company emails are still archived. Just transfer the email to the user account of the new employee to realize the handover of part of the work and improve the efficiency of the handover . In addition, it can also ensure that the potential customers and business opportunities in the mail of the resigned employee will not be lost.

Further, the system provides a statistics module, which is used to count the content of all emails in the enterprise according to the frequency of occurrence of the input keywords or sentences in each email, and analyze the products and customers most concerned about by customers according to the statistical results. The most frequently asked questions, after the new product comes out, those customers have demand intentions for this product, etc., in order to further tap potential customers and business opportunities in emails, as well as improve products and enterprise service quality.

Description of drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the following will briefly introduce the drawings that need to be used in the description of the embodiments or the prior art. Obviously, the accompanying drawings in the following description are only These are some embodiments of the present invention. For those skilled in the art, other drawings can also be obtained according to these drawings without any creative effort.

FIG. 1 is a schematic flowchart of a mail receiving method provided in Embodiment 1 of the present invention;

FIG. 2 is a schematic flowchart of a method for sending an email provided in Embodiment 2 of the present invention;

FIG. 3 is a schematic structural diagram of an email management system provided by Embodiment 3 of the present invention.

Detailed ways

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only some, not all, embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative efforts fall within the protection scope of the present invention.

Example 1:

Referring to Fig. 1, the present embodiment provides a method for receiving mail, and its main steps are as follows,

Step 101: Connect to the mail server, log in to at least one mailbox in the mailbox list, and receive the mail in the mailbox.

In this embodiment, but not limited to, at least one mail server can be connected, and single or multiple different mailboxes can be registered in the mail server. In this management system, a mailbox list is preset, and the list records information of at least one mailbox. The mailbox information includes: account number and password of the mailbox in the mail server to which it belongs, mail transfer protocol, post office protocol, and access port information of the mail server.

In this embodiment, according to the mailbox information provided by the mailbox list, connect to the mail server, log in to each mailbox, and receive mails in each mailbox.

In this embodiment, the user can, but is not limited to, use a browser on a terminal without this system installed, log in to the mailbox according to the mailbox information, and directly manage the mail in the mailbox, which improves the convenience of the user.

Step 102: Add the received mail to a mailing list.

In this embodiment, the mailing list includes: the mails input by the user account to be sent to the customer, and the mails sent by the customer and received by the mailbox. The mailing list archives and backs up each mail, and stores and records each mail.

Step 103: Determine the mapping relationship between the received email and each user account.

In this embodiment, determining the mapping relationship between each mail and each user account is specifically: according to the address of the recipient of the received mail, query the call record stored in the mail list, and according to the mapping between the address and the user account in the call record Relationship, to determine the mapping relationship between the email and the user account.

If the address of the mailbox is received by the system for the first time, query the preset address mapping table. The address mapping table contains the mapping relationship between the customer's email address and the corresponding administrator or user account. According to the address mapping table, determine the email The mapping relationship with the user account.

In this embodiment, the address mapping table may be but not limited to be stored in a mailing list, or in an external customer relationship management system.

In this embodiment, the system administrator may, but is not limited to, actively determine or modify the mapping relationship between any email and any user account. The mapping relationship may include, but is not limited to: viewing the mapping relationship, replying to the mapping relationship, and the like. For example, if the system administrator determines or modifies the mapping relationship between a certain user account and a certain email, and determines the mapping relationship as a viewing or replying mapping relationship, then when the email is transferred to the user account, the user can Log in to the system with the user account, and complete the email management function of viewing or replying to the email, so as to realize the sharing and arrangement of resources or information within the enterprise.

When actively modifying the mapping relationship, you can, but not limited to, modify all or part of the mail mapping relationship of a user account. It can be seen that the mapping relationship is added to any user account, or the mapping relationship is deleted.

In this embodiment, any email in the email list may, but is not limited to, have a mapping relationship with multiple user accounts. Any user account may, but is not limited to, have multiple mapping relationships for the same email.

Step 104: According to the mapping relationship, transfer each mail in the mail list to each corresponding user account.

In this embodiment, one or more emails may be transferred to any user account, but not limited to. When each user needs to manage emails, the user logs in his own user account to manage the emails transferred to the user account. According to different types of mapping relationships between the user account and the mail, different mail management functions are provided to the user account. For example, if the mapping relationship between a certain user account and a certain email is only a reply mapping relationship, when the user account invokes the email, the user account can only manage the reply to the email.

It can be seen from the above that with this technical solution, in the mail receiving process, the mails are uniformly received, the received mails are stored in the mailing list, and then according to the previous calling records or address mapping table, it is determined that the received mails are related to each user Account mapping relationship. According to the mapping relationship, each email in the mailing list is transferred to each user account, so that the user can log in to the user account and manage the emails transferred to the user account. Compared with the existing technology, each employee has his own mailbox, and the management of emails is also managed separately, and the utilization rate of emails and information sharing are low. However, by adopting the technical scheme of the present invention, the management system can uniformly manage and call the received mails, which is beneficial to the arrangement of internal resources and information of the enterprise.

Furthermore, due to the unified management of emails, even if an employee resigns or is transferred, the employee’s company emails are still archived. Just transfer the email to the user account of the new employee to realize the handover of part of the work and improve the efficiency of the handover . In addition, it can also ensure that the potential customers and business opportunities in the mail of the resigned employee will not be lost.

Example 2:

Referring to Fig. 2, the present embodiment provides a method for sending mail, the main steps of which include:

Step 201: the user logs in the user account, and adds the email to be sent to the mailing list.

In this embodiment, when the user needs to send an email, the user logs into the email management system with the user account and enters the management interface of the user account. When the user completes the writing of the email in the management interface and sends it out, the email to be sent will be added to the mailing list, so that the email to be sent can be archived and backed up.

Step 202: Determine the sending mailbox of the email to be sent according to the calling record in the mailing list.

In this embodiment, according to the calling record in the mailing list, determine the sending mailbox of the mail to be sent, specifically: query the sending mailbox with the highest frequency of use of the user account in the calling record, and determine the sending mailbox of the waiting mail.

Step 203: Connect to the mail server, log in the sending mailbox, and send the waiting mail.

In this embodiment, according to the determined sending mailbox, query the preset mailbox information, connect to the mail server, log in the sending mailbox, and send the pending mail. The mailbox information includes: mailbox account, mailbox password, mail transfer protocol, post office protocol, and port information of the mail server.

It can be seen from the above that, with this technical solution, in the mail sending process, the mails are uniformly received, the mails to be sent are stored in the mailing list, and the sending mailbox of the mails to be sent is determined according to the previous calling records. According to the determined sending mailbox, query the preset mailbox information, connect to the mail server, log in the sending mailbox, and send the pending mail. Compared with the existing technology, each employee has his own mailbox, and the management of emails is also managed separately, and the utilization rate of emails and information sharing are low. However, by adopting the technical scheme of the present invention, the management system can uniformly manage and call the received mails, which is beneficial to the arrangement of internal resources and information of the enterprise.

Furthermore, due to the unified management of emails, even if an employee resigns or is transferred, the employee’s company emails are still archived. Just transfer the email to the user account of the new employee to realize the handover of part of the work and improve the efficiency of the handover . In addition, it can also ensure that the potential customers and business opportunities in the mail of the resigned employee will not be lost.

Example 3:

Referring to FIG. 3 , this embodiment provides an email management system, including: an email sending and receiving module 301 , an email management module 302 , a user account management module 303 , a mapping determination module 304 , an email calling module 305 , and a statistics module 306 .

The connection mechanism and working principle of each part are as follows:

The mail sending and receiving module 301 is configured to connect to the mail server, log in at least one mailbox in the mailbox list, and receive or send the mail in the mailbox.

In this embodiment, the mail sending and receiving module 301 may, but is not limited to, connect to at least one mail server, and register single or multiple different mailboxes in the mail server. In this management system, a mailbox list is preset, and the list records information of at least one mailbox. The mailbox information includes: account number and password of the mailbox in the mail server to which it belongs, mail transfer protocol, post office protocol, and access port information of the mail server.

In this embodiment, the user can, but is not limited to, use a browser on a terminal without this system installed, log in to the mailbox according to the mailbox information, and directly manage the mail in the mailbox, which improves the convenience of the user.

The mail sending and receiving module 301 can connect to the mail server according to the mailbox information provided by the mailbox list, log in to each mailbox, receive or send the mails in each mailbox, and realize the external communication of mails.

The mail management module 302 is electrically connected with the mail sending and receiving module 301, and is used for adding mails received or sent by the mail sending and receiving module 301 to the mailing list, and managing each mail in the mailing list.

In this embodiment, the mailing list includes: the mails input by the user account to be sent to the customer, and the mails sent by the customer and received by the management system. The mailing list archives and backs up each mail, and stores and records each mail.

In this embodiment, the email management module 302 may, but is not limited to, have common email processing functions including: composing, sending, saving drafts, replying, forwarding, deleting, contact management and other functions.

The user account management module 303 is configured to manage each user account.

In this embodiment, the user account management module 303 may, but is not limited to, manage user accounts, passwords and specific information. For example, add, delete, and modify new user accounts, and set permissions for user accounts. The permission setting of the user account is specifically: modifying the mapping relationship between the user account and each mail in the mailing list.

The mapping determination module 304 is electrically connected with the mail management module 302, the user account management module 303, and the mail calling module 305, and is used to determine the mapping relationship between each mail and each user account according to the information of each mail in the mail list.

In this embodiment, according to the information of each mail, determining the mapping relationship between each mail and each user account is specifically: if the mail in the mail list is input by the user account and needs to send mail, then according to the recipient address of the mail, query Mail call record, according to the mapping relationship between the address and the user account in the call record, determine the mapping relationship between the mail and the user account; For the mail calling record, the mapping relationship between the email and the user account is determined according to the mapping relationship between the address and the user account in the calling record.

If the address of the mailbox is received or sent by the system for the first time, query the preset address mapping table, which contains the mapping relationship between the customer's email address and the corresponding manager or user account. According to the address mapping table, determine The mapping relationship between the email and the user account.

In this embodiment, the address mapping table may be but not limited to be stored in an external customer relationship management system. When querying, the management system can directly connect to the customer relationship management system to read data to determine the mapping relationship.

In this embodiment, the system administrator may, but is not limited to, actively determine or modify the mapping relationship between any email and any user account. The mapping relationship may include, but is not limited to: viewing the mapping relationship, replying to the mapping relationship, and the like. For example, if the system administrator determines or modifies the mapping relationship between a certain user account and a certain email, and determines the mapping relationship as a viewing or replying mapping relationship, then when the email is transferred to the user account, the user can Log in to the system with the user account and complete the email management function of viewing or replying to the email, so as to realize the sharing and arrangement of resources or information within the enterprise.

When actively modifying the mapping relationship, you can, but not limited to, modify all or part of the mail mapping relationship of a user account. It can be seen that the mapping relationship is added to any user account, or the mapping relationship is deleted.

The mail call module 305 is electrically connected to the mapping determination module 304 and the mail management module respectively, and is used to transfer each mail in the mail list to each corresponding user account according to the determined mapping relationship, so that each user can log in to the user account , to manage the emails transferred to the user account.

In this embodiment, the mail calling module 305 may, but not limited to, call one or more mails to any user account. The mail is stored in the management system, and when each user account needs to manage the mail, the management system calls the mail that has a mapping relationship with the user account. According to different types of mapping relationships between the user account and the mail, different mail management functions are provided to the user account. For example, if the mapping relationship between a certain user account and a certain email is a reply mapping relationship, when the user account invokes the email, the user account can only manage the reply to the email.

The statistical module 306 is electrically connected with the mail management module 302, and is used for counting the occurrence frequency of keywords or sentences input by the user in each mail content, obtaining statistical results, and providing the statistical results to the user.

In this embodiment, the keywords or sentences may be, but not limited to, products of the enterprise, questions raised by customers, and opinions of customers on the products. Counting the frequency of keywords or sentences appearing in each email in this system can analyze the products that customers are most concerned about, the most frequently asked questions by customers, and those customers who have demand intentions for this product after the new product comes out, etc., which is conducive to mining emails. potential customers and business opportunities.

It can be seen from the above that by adopting the technical solution of this embodiment, in the mail management process, the employees of the enterprise only need to create a user account in the management system, and log in to the management system with the user account, that is, they can write, receive, and send normal emails. The mail management function does not affect the normal work of enterprise employees. At the same time, the management system archives and backs up the emails sent and received by each employee, and transfers the emails to different user accounts to complete the work of different needs. Compared with the existing technology, each employee has his own mailbox, and the management of emails is also managed separately, and the utilization rate of emails and information sharing are low. However, by adopting the technical solution of the present invention, the management system can uniformly manage and call the sending and receiving mailboxes and sending and receiving mails, which is beneficial to the arrangement of internal resources and information of the enterprise.

Furthermore, due to the unified management of emails, even if an employee resigns or is transferred, the employee’s company emails are still archived. Just transfer the email to the user account of the new employee to realize the handover of part of the work and improve the efficiency of the handover . In addition, it can also ensure that the potential customers and business opportunities in the mail of the resigned employee will not be lost.

Further, the system provides a statistical module 306, which is used to count the content of all mails in the enterprise according to the frequency of occurrence of the input keywords or sentences in each of the mails, and analyze the products, products, and The most frequently asked questions by customers, and those customers' demand intentions for this product after the new product comes out, etc., in order to further tap potential customers and business opportunities in emails, as well as improve products and enterprise service quality.

The device embodiments described above are only illustrative, and the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in One place, or it can be distributed to multiple network elements. Part or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. It can be understood and implemented by those skilled in the art without any creative efforts.

Through the above description of the implementations, those skilled in the art can clearly understand that each implementation can be implemented by means of software plus a necessary general hardware platform, and of course also by hardware. Based on this understanding, the essence of the above technical solution or the part that contributes to the prior art can be embodied in the form of software products, and the computer software products can be stored in computer-readable storage media, such as ROM/RAM, magnetic CD, CD, etc., including several instructions to make a computer device (which may be a personal computer, server, or network device, etc.) execute the methods described in various embodiments or some parts of the embodiments.

The implementation methods described above do not constitute a limitation to the scope of protection of the technical solution. Any modifications, equivalent replacements and improvements made within the spirit and principles of the above implementation methods shall be included in the protection scope of the technical solution.

Claims (14)

1. A method for receiving mail, comprising: Connect to the mail server, log in at least one mailbox in the mailbox list, and receive the mail in the mailbox; adding said received mail to a mailing list; determining the mapping relationship between the received email and each user account; According to the mapping relationship, each of the emails in the email list is transferred to each of the corresponding user accounts, so that each user can log into the user account and manage the emails transferred to the user account. 2. The receiving method according to claim 1, characterized in that, The determining the mapping relationship between the received email and each user account specifically includes: determining the mapping relationship between the received mail and each of the user accounts according to the calling record of each mail in the mail list; Or according to the address mapping table preset in the mail list, determine the mapping relationship between the received mail and each of the user accounts; Wherein, the address mapping table includes: the mapping relationship between the customer's email address and each of the user accounts. 3. The receiving method according to claim 2, characterized in that, The determining the mapping relationship between the received email and each user account further includes: The user actively determines the mapping relationship between the received email and each of the user accounts. 4. The receiving method according to claim 1, characterized in that, Said connecting to the mail server, logging into at least one mailbox in the mailbox list, and receiving the mail in the mailbox, specifically: Connect to at least one of the mail servers, log in to at least one of the mailboxes according to the mailbox information stored in the mailbox list, and receive the mail in the mailbox; Wherein, the mailbox information includes: mailbox account, mailbox password, mail transfer protocol, post office protocol, and port information of the mail server. 5. A method for sending an email, comprising: The user logs in the user account and adds the email to be sent to the mailing list; According to the calling records in the mailing list, determine the sending mailbox of the mail to be sent; Connect to the mail server, log in the sending mailbox, and send the waiting mail. 6. The sending method according to claim 5, characterized in that, According to the calling record of the mailing list, determining the sending mailbox of the mail to be sent specifically includes: The sending mailbox of the email to be sent is determined according to the sending mailbox with the highest usage frequency of the user account in the call record. 7. The sending method according to claim 5, characterized in that, The connecting to the mail server, logging into the sending mailbox, and sending the mail to be sent specifically includes: Log in to the mail server according to the mailbox information stored in the mailbox list, and send the mail to be sent. 8. A mail management system, characterized in that, comprising: a mail sending and receiving module, a mail management module, a mapping determination module, and a mail calling module; The mail sending and receiving module is used to connect to the mail server, log in at least one mailbox in the mailbox list, and receive or send the mail in the mailbox; The mail management module is electrically connected to the mail sending and receiving module, and is used to add the received or sent mails to a mailing list; The mapping determination module is electrically connected to the mail management module and the mail calling module, and is used to determine the mapping relationship between each mail and each user account according to the information of each mail in the mail list; The mail invoking module is electrically connected to the mapping determination module and the mail management module, and is used to transfer each of the mails in the mail list to the corresponding user accounts according to the mapping relationship, so as to For each user to log in to the user account, manage the emails transferred to the user account. 9. The system of claim 8, wherein: The mail sending and receiving module is specifically configured to: connect to at least one of the mail servers, log in at least one of the mailboxes according to the mailbox information stored in the mailbox list, and receive or send the mail in the mailbox; Wherein, the mailbox information includes: mailbox account, mailbox password, mail transfer protocol, post office protocol, and port information of the mail server. 10. The system of claim 8, wherein: The mail management module is also used for: managing each of the mails in the mailing list; Specifically including: writing, replying, forwarding, deleting the email, and saving the email as a draft. 11. The system of claim 8, wherein: The mapping determination module is specifically configured to: determine the mapping relationship between each email and each user account according to the email address of each email in the email list; Wherein, there is a mapping relationship between each email and at least one user account. 12. The system of claim 8, wherein: The mapping determination module is further configured to: actively determine the mapping relationship between each of the emails in the email list and each of the user accounts. 13. The system of claim 8, further comprising: A user account management module, configured to manage each of the user accounts. 14. The system according to any one of claims 8 to 13, further comprising: A statistical module, electrically connected to the mail management module, for counting the frequency of occurrence of keywords or sentences input by the user in each of the mail contents, obtaining statistical results, and providing the statistical results to the user.

Images