CN117041200A - Private cloud multi-mailbox sending system and method - Google Patents

Abstract

The application relates to the technical field of electronic mailboxes, in particular to a private cloud multi-mailbox sending system and a private cloud multi-mailbox sending method, wherein the system can carry out mailbox account management operation according to user instructions through an email management module and update mailbox account information in a preset database according to the carried out mailbox account management operation; storing a load balancing algorithm through a load balancing algorithm module; when receiving a mail sending instruction, the email management module reads the information of a mailbox account, and invokes a load balancing algorithm to select one mailbox account for mail sending; and the E-mail sending monitoring module is used for monitoring whether the E-mail is successfully sent after the E-mail is sent, and triggering an alarm if the E-mail is failed to be sent. According to the technical scheme, a plurality of mailbox accounts can be configured, the mail dispersion risk is sent through the mailbox accounts, the mail sending failure condition is timely obtained through monitoring the mail sending condition, and the stability and the reliability of the system are improved.

Description

Private cloud multi-mailbox sending system and method

Technical Field

The application relates to the technical field of electronic mailboxes, in particular to a private cloud multi-mailbox sending system and method.

Background

Currently, when sending mail using private cloud services, only a single fixed mailbox account is typically configured. The private cloud has the problem of poor stability, so that when the existing single fixed mailbox account using the private cloud service is used for sending mails, the problem of unstable mail sending easily occurs, and the reliability and usability of the mail service are reduced.

Private clouds have the following problems: private cloud systems are commonly used by multiple users and require periodic maintenance and updating, which may result in delays or misses in information delivery if mail services cannot accommodate the different needs of these users; the network environment inside the private cloud is complex and various, and there may be network problems that obstruct mail transmission, such as firewall restrictions, network congestion, and the like. While a single fixed mailbox also has the problem of instability: at present, most private cloud systems only support a single fixed mailbox account to send mails, and once the account has a problem, the reliability of mail notification is threatened; the use of a single mail service provider may result in too high a dependency and the entire mail notification system may be paralyzed once the vendor has a problem.

Therefore, the current private cloud service is not enough in stability and reliability in a manner of configuring a single fixed mailbox account.

Disclosure of Invention

In view of the above, the present application aims to provide a private cloud multi-mailbox sending system and method, so as to solve the problem of insufficient stability and reliability in the prior art that a private cloud service configures a single fixed mailbox account.

According to a first aspect of an embodiment of the present application, there is provided a private cloud multi-mailbox sending system, applied to a private cloud service, including:

the email management module is used for carrying out email account management operation according to the user instruction and updating the email account information in a preset database according to the carried out email account management operation;

the load balancing algorithm module is used for storing a load balancing algorithm;

the email management module is also used for reading email account information when receiving an email sending instruction, and calling the load balancing algorithm to select one email account for email sending;

and the E-mail sending monitoring module is used for monitoring whether the E-mail is sent successfully or not after the E-mail is sent, and triggering an alarm if the E-mail is sent successfully.

Preferably, the email management module is further configured to read the mailbox account information when receiving an important email sending instruction, and select all the stored mailbox accounts to send the email.

Preferably, the email sending monitoring module is further configured to record and store email related information after the email is sent.

Preferably, the private cloud multi-mailbox sending system further comprises:

the mail sending failure alarm module is used for being integrated with the nailing communication robot to acquire an interface address and a secret key of a nailing sending group notice; when the email sending monitoring module is detected to trigger an alarm, the email related information is sent to the corresponding group by using the interface address and the key of the group sending notification.

Preferably, the email sending monitoring module is further configured to obtain a reason for email sending failure when detecting that email sending fails;

the mail sending failure alarm module is further capable of sending the mail sending failure reason to the corresponding group when the mail related information is sent to the corresponding group.

Preferably, the load balancing algorithm stored by the load balancing algorithm module includes: a polling algorithm, a weighted polling algorithm, a minimum number of connections algorithm, and/or an IP hashing algorithm.

Preferably, the email management module is further configured to set whether the stored mailbox accounts are used for receiving emails according to the user instruction respectively;

if yes, the mailbox account can normally receive mails.

According to a second aspect of the embodiment of the present application, there is provided a private cloud multi-mailbox sending method, including:

receiving a user instruction, performing mailbox account management operation according to the user instruction, and updating mailbox account information in a preset database according to the performed mailbox account management operation;

when receiving a mail sending instruction, reading mail account information, and calling a pre-stored load balancing algorithm to select a mail account for mail sending;

after the mail is sent, whether the mail is sent successfully or not is monitored, and if the mail is sent successfully, an alarm is triggered.

The technical scheme provided by the embodiment of the application can comprise the following beneficial effects:

it can be understood that the technical scheme provided by the application can carry out mailbox account management operation according to the user instruction through the email management module, and update mailbox account information in a preset database according to the carried out mailbox account management operation; storing a load balancing algorithm through a load balancing algorithm module; when receiving a mail sending instruction, the email management module reads the information of a mailbox account, and invokes a load balancing algorithm to select one mailbox account for mail sending; and the E-mail sending monitoring module is used for monitoring whether the E-mail is successfully sent after the E-mail is sent, and triggering an alarm if the E-mail is failed to be sent. According to the technical scheme, a plurality of mailbox accounts can be configured, the mail dispersion risk is sent through the mailbox accounts, the mail sending failure condition is timely obtained through monitoring the mail sending condition, and the stability and the reliability of the system are improved.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.

FIG. 1 is a schematic block diagram of a private cloud multi-mailbox delivery system shown in accordance with one exemplary embodiment;

fig. 2 is a schematic diagram illustrating steps of a private cloud multi-mailbox transmission method according to one example embodiment.

Detailed Description

Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.

Example 1

Fig. 1 is a schematic block diagram of a private cloud multi-mailbox transmission system, referring to fig. 1, according to an exemplary embodiment, a private cloud multi-mailbox transmission system is provided, applied to a private cloud service, including:

the email management module 101 is configured to perform a mailbox account management operation according to a user instruction, and update mailbox account information in a preset database according to the performed mailbox account management operation;

in particular practice, it is preferred that the email management module may provide an email account management interface: the system is provided with a management interface, and an administrator can perform mailbox account management operation by sending user instructions, wherein the mailbox account management operation comprises adding, deleting and modifying different mailbox accounts on the interface. These operations update mailbox account information in the database in real-time.

Regarding the storage of the database, it is preferable that a specific database table is designed to store the related information of each mailbox account, such as account name, password, SMTP server, and the like.

In practical application, the added mailbox accounts can be mailboxes of different server manufacturers, for example, can be messenger mailboxes, internet easy mailboxes, google mailboxes and the like, and the risk can be dispersed by configuring a plurality of mailbox accounts of different manufacturers to send mail notifications, so that the stability and the reliability of the system are improved.

Preferably, the email management module may further have a test email sending function: an administrator can test the newly added mailbox account through the management interface, so that the account can be ensured to send mails normally.

The load balancing algorithm module 102 is configured to store a load balancing algorithm;

the email management module is also used for reading email account information when receiving an email sending instruction, and calling the load balancing algorithm to select one email account for email sending; the system adopts a load balancing algorithm to automatically balance the sending quantity of mails among a plurality of accounts, so that overload of a single account is avoided;

and the email sending monitoring module 103 is configured to monitor whether the email sending is successful after the email sending, and trigger an alarm if the email sending fails.

In particular practice, the alert message may be sent to the sender of the mail to inform the sender of the failure of sending the email, so that the sender of the mail may timely communicate the message via other mailboxes or other means, avoiding message delays. The alert information may also be sent to a system administrator so that the administrator may quickly view the error information to troubleshoot the problem.

Preferably, after the alarm is triggered, the email management module can also automatically switch to other mailbox accounts according to the load balancing algorithm to send the email, so that the email is ensured to be sent successfully, and the system stability is improved.

It can be understood that, according to the technical scheme provided by the embodiment, the email account management operation can be performed by the email management module according to the user instruction, and the email account information in the preset database is updated according to the performed email account management operation; storing a load balancing algorithm through a load balancing algorithm module; when receiving a mail sending instruction, the email management module reads the information of a mailbox account, and invokes a load balancing algorithm to select one mailbox account for mail sending; and the E-mail sending monitoring module is used for monitoring whether the E-mail is successfully sent after the E-mail is sent, and triggering an alarm if the E-mail is failed to be sent. According to the technical scheme, a plurality of mailbox accounts can be configured, the mail dispersion risk is sent through the mailbox accounts, the mail sending failure condition is timely obtained through monitoring the mail sending condition, and the stability and reliability of the system are improved.

It should be noted that, the load balancing algorithm stored by the load balancing algorithm module includes: a polling algorithm, a weighted polling algorithm, a minimum number of connections algorithm, and/or an IP hashing algorithm.

Round Robin (Round Robin) algorithm: this is a simple and widely used load balancing algorithm. In practical application, when a polling algorithm is used, the system distributes mails to each mailbox account in sequence, so that each account is ensured to have an opportunity to participate in mail transmission. The realization logic is that mailbox accounts are sequentially selected according to the polling sequence to send mails, and the mail is circularly reciprocated.

Weight polling (Weighted Round Robin) algorithm: the weight is increased based on the polling algorithm. In practical applications, different mailbox accounts may be assigned different weights to more finely regulate the load of each account. Higher weighted accounts receive more mail sending tasks.

Minimum number of connections (Least Connections) algorithm: the algorithm will select the mailbox account with the least number of current connections to send the mail, thereby avoiding overload. This requires the system to maintain the current number of connections per mailbox account and to dynamically adjust.

IP Hash (IP Hash) algorithm: the algorithm performs hash calculation according to the source IP address of the sent mail, and then sends the mail to the corresponding mailbox account. Therefore, the mails with the same IP address can be ensured to be sent to the same account, and the method is suitable for scenes in which session consistency needs to be maintained.

In practical application, the proper load balancing algorithm can be selected according to the characteristics and requirements of different services, so that the performance and efficiency of the system can be improved. For example:

if the performance difference of each mailbox account is smaller, a polling algorithm can be selected, and the method is simple in average load and suitable for the condition of relatively balanced load. If the performance of some accounts is higher, a weighted round robin algorithm may be used to load the higher performing accounts more. If dynamic adjustment is needed, a minimum connection number algorithm can be considered, so that the connection number of each account is ensured to be relatively balanced, and the method is suitable for a long connection scene. If session consistency for a particular user needs to be maintained, an IP hashing algorithm may be selected.

And finally, selecting according to actual conditions, comprehensively considering factors such as system performance, server configuration, service requirements and the like, so as to find the most suitable load balancing algorithm scheme.

The email management module is further configured to read the email account information when receiving an important email sending instruction, and select all the stored email accounts to send the email.

In specific practice, the email management module of the system has a multi-mailbox redundancy sending function, and a user or a system administrator can set an important email sending instruction for important emails so that the system can perform multi-mailbox redundancy sending, and the email sending mode is as follows: when the system needs to send important mails, all the stored mailbox accounts are used for simultaneously sending the same email. For example, mailbox a, mailbox B, and mailbox C are configured, and when an important mail transmission instruction is received, mailbox a, mailbox B, and mailbox C are used to transmit once, respectively. It can be understood that, in the technical scheme shown in this embodiment, even if one account fails to send, the system can still successfully send the mail through other accounts, so as to improve the sending reliability.

The email sending monitoring module is also used for recording and storing email related information after the email is sent.

Preferably, a database mail sending log may be set: the system designs a database table as a mail sending log for recording the sending time, account, receiver address, sending result and other mail related information of each mail. A monitoring interface may be provided: the manager can check the mail sending log in the database through the monitoring interface and display the sending state of each mail in a list form, so that the mail sending condition is known in real time. Search and filter functions: the monitoring interface provides searching and filtering functions, so that an administrator can conveniently and quickly find out the sending log of the specific mail.

It should be noted that the private cloud multi-mailbox sending system further includes:

the mail sending failure alarm module is used for being integrated with the nailing communication robot to acquire an interface address and a secret key of a nailing sending group notice; when the email sending monitoring module is detected to trigger an alarm, the email related information is sent to the corresponding group by using the interface address and the key of the group sending notification.

In practical application, the system is integrated with the nailing communication robot first, and obtains an interface address and a key of a group notification of a group capable of transmitting information. When the mail sending module detects that the sending fails, an alarm is triggered. And the mail sending failure warning module is used for sending a mail sending failure notification to a designated warning group through a nail interface according to the related information of the failed mail. The notification content comprises the failed time, the information related to mails such as a sender, a receiver, a title and the like, so that an administrator can conveniently and quickly know the situation.

After receiving the nail notice, the administrator can log in the system to check the detailed log information so as to check the problem and take proper measures.

The email sending monitoring module is further configured to obtain a reason for email sending failure when email sending failure is detected;

the mail sending failure alarm module is further capable of sending the mail sending failure reason to the corresponding group when the mail related information is sent to the corresponding group.

In specific practice, if the reason of the sending failure is obtained, the reason of the sending failure of the mail can be sent to the corresponding group when the related information of the mail is sent to the corresponding group, so that an administrator can grasp the reason of the sending failure more quickly, and further, the problem can be quickly checked.

It will be appreciated that various problems may occur during the mail sending process, such as mailbox server failures, network connection problems, etc. The technical scheme shown in the embodiment can help an administrator to discover and locate the problems in time, accelerate the fault checking flow and reduce the unavailable time of the system.

Preferably, the email management module is further configured to set whether the stored mailbox accounts are used for receiving emails according to the user instruction respectively;

if yes, the mailbox account can normally receive mails.

In practical application, in the system shown in this embodiment, since each user configures multiple mailboxes, such as mailbox a, mailbox B, and mailbox C, the user can select which mailboxes can receive the mail and which mailboxes do not receive the mail, so that repeated sending of some mails is avoided. For example, the user may select whether to open an option of receiving a mail notification corresponding to the mailbox on the profile setting page, and if the option is closed, the mailbox may only send the mail and may not receive the mail.

Preferably, the forward mail function may be set when some mailboxes are not used for receiving mail. For example, the user sets only mailbox a, mailbox B and mailbox C corresponding to the user, and the user can normally receive the mail, and when mailbox B or mailbox C receives the mail, the mail can be automatically forwarded to mailbox a, so as to avoid missing mail information.

It can be understood that the system of the embodiment can dynamically configure a plurality of different mailbox accounts, monitor mail sending states, realize redundant sending of multiple mailboxes, personalized user receiving setting, alarm notification of mail sending failure and the like, comprehensively solve the problems existing in the prior art, and improve the stability, reliability and maintainability of mail service in a private cloud environment. Compared with the prior art, the application has the innovation point that the technical means cooperate, so that a complete and efficient mail service system is formed.

The technical scheme of the embodiment has the following obvious technical effects:

improving mail service reliability and availability: by dynamically configuring a plurality of different mailbox accounts, the system can automatically switch to other available accounts for mail transmission when one or more accounts fail, so that the problem that the mail cannot be transmitted due to the failure of a single account is avoided. The multi-mailbox redundant sending function further increases the reliability of mail sending, and even if sending of one account fails, the system can still guarantee mail sending through other accounts.

The mail monitoring and fault detection capability of an administrator is enhanced: through the E-mail sending monitoring module, an administrator can monitor the mail sending state in real time, check the sending log and quickly check the reason of the sending failure. The mail sending failure alarm module timely informs an administrator of failure information, is beneficial to quickly finding and solving problems, and reduces the time of unavailable systems.

Personalized user experience: the user receiving setting function is introduced, so that the user is allowed to autonomously select whether to receive the mail notification, and therefore irrelevant mails are prevented from being received, and user experience is improved. The user can freely open or close the mail receiving function of a certain mailbox according to the actual demand.

Solves the problem of single manufacturer dependence: by integrating mailbox accounts of a plurality of different manufacturers, the system reduces the dependence on a single manufacturer, thereby reducing the risk of mail service interruption caused by manufacturer faults and improving the stability of the whole system.

Optimizing resource utilization and load balancing: through a mailbox account load balancing algorithm, the system realizes mail sending balance among a plurality of accounts and avoids overload of a single account. This helps to improve system performance, ensuring that each account is fully involved in the mail sending task.

Facilitating maintainability of private cloud environments: through a timely mail message monitoring and alarming mechanism, an administrator can rapidly take measures when problems occur, and stable operation of the whole private cloud environment is ensured. This helps to reduce maintenance costs and improve maintainability of the private cloud.

Compared with the prior art, the scheme of the application has the following technical advantages:

multi-account dynamic configuration: while the prior art generally only configures a single fixed mailbox account, the present embodiment allows an administrator to dynamically configure mailbox accounts for a plurality of different vendors, thereby improving the reliability and flexibility of mail delivery.

Mail sending monitoring and alarming: the embodiment introduces a system integrating mail message monitoring and alarming, so that an administrator can monitor the mail sending state in real time and discover and solve the problems in time, thereby improving the stability and maintainability of the system.

Redundant transmission of multiple mailboxes: and a multi-mailbox redundant sending function is introduced, so that even if one account fails or fails to send, other accounts can send mails, and the reliability of mail sending is improved.

User individualization experience: through the user receiving setting function, a user can choose whether to receive mail notification according to personal requirements, so that interference of irrelevant mails is avoided, and user experience is improved.

Solving the single manufacturer dependence: by integrating mailbox accounts of a plurality of different manufacturers, the dependence on a single manufacturer is reduced, and the service interruption risk caused by manufacturer faults is reduced.

In practical applications, for example: in a private cloud environment of an enterprise, the private cloud multi-mailbox sending system is deployed and is used for managing and sending mail notification:

an administrator operates:

the system administrator logs into the email sending management interface of the system.

The administrator adds three different mailbox accounts for the enterprise (mailer): a mailbox, a B mailbox and a C mailbox.

The administrator sets the weight for the A mailbox to be 2, and the weights of the B mailbox and the C mailbox are both 1.

E, mail sending:

when the enterprise needs to send important mails, the system sends the same mail to the same addressee mailbox by utilizing the A mailbox, the B mailbox and the C mailbox according to the multi-mailbox redundant sending function.

Mailbox account load balancing:

and according to the set weight, the system adopts a polling algorithm to send the mail. First, the a mailbox sends a mail, then the B mailbox and finally the C mailbox.

When the system detects that the sending quantity of the A mailbox is overlarge, the weight is automatically adjusted, so that the B mailbox and the C mailbox receive more mail sending tasks.

Mail sending monitoring:

an administrator can query the mail sending log in the database through the monitoring interface to check the sending state and related information of each mail.

The user receives the settings:

the employee logs into the system and closes the mail receiving function on the profile settings page because he does not want the mailbox to receive mail notifications.

Mail sending failure alarm:

when the system detects that a certain mail fails to send, the mail sending failure alarm module is triggered.

The system automatically sends alarm notification to a preset alarm group, wherein the alarm notification comprises failure time, mail related information and failure reasons.

Through the above embodiments, the association and connection relationship between the respective technical modules can be clearly seen. An administrator can configure and manage a plurality of mailbox accounts on a management interface, the system realizes balanced distribution of mail sending according to a load balancing algorithm, simultaneously monitors mail sending states and carries out alarm notification, and a user can select whether to receive the mail notification according to requirements. The whole system works cooperatively, a scheme of sending mails and integrating mail message monitoring and alarming based on multiple mailboxes of private cloud is realized, and reliability, availability and maintainability of mail service are improved.

Example two

Fig. 2 is a schematic step diagram of a private cloud multi-mailbox sending method according to an exemplary embodiment, and provides a private cloud multi-mailbox sending method, which includes:

step S11, receiving a user instruction, performing mailbox account management operation according to the user instruction, and updating mailbox account information in a preset database according to the performed mailbox account management operation;

step S12, when receiving a mail sending instruction, reading mail account information, and calling a pre-stored load balancing algorithm to select a mail account for mail sending;

and step S13, after the mail is sent, monitoring whether the mail is sent successfully, and if the mail is sent successfully, triggering an alarm.

According to the technical scheme, a plurality of mailbox accounts can be configured, the mail dispersion risk is sent through the mailbox accounts, the mail sending failure condition is timely obtained through monitoring the mail sending condition, and the stability and reliability of the system are improved.

It is to be understood that the same or similar parts in the above embodiments may be referred to each other, and that in some embodiments, the same or similar parts in other embodiments may be referred to.

It should be noted that in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present application, unless otherwise indicated, the meaning of "plurality" means at least two.

Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.

It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.

Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.

The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.

In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.

While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.

Claims (8)

1. A private cloud multi-mailbox sending system applied to private cloud services, comprising:

the email management module is used for carrying out email account management operation according to the user instruction and updating the email account information in a preset database according to the carried out email account management operation;

the load balancing algorithm module is used for storing a load balancing algorithm;

the email management module is also used for reading email account information when receiving an email sending instruction, and calling the load balancing algorithm to select one email account for email sending;

and the E-mail sending monitoring module is used for monitoring whether the E-mail is sent successfully or not after the E-mail is sent, and triggering an alarm if the E-mail is sent successfully.

2. The private cloud multi-mailbox delivery system of claim 1 wherein,

the email management module is further configured to read the email account information when receiving an important email sending instruction, and select all the stored email accounts to send the email.

3. The private cloud multi-mailbox delivery system of claim 1 wherein,

the E-mail sending monitoring module is also used for recording and storing the related information of the E-mail after the E-mail is sent.

4. The private cloud multi-mailbox delivery system of claim 3 further comprising:

the mail sending failure alarm module is used for being integrated with the nailing communication robot to acquire an interface address and a secret key of a nailing sending group notice; when the email sending monitoring module is detected to trigger an alarm, the email related information is sent to the corresponding group by using the interface address and the key of the group sending notification.

5. The private cloud multi-mailbox delivery system of claim 4 wherein,

the E-mail sending monitoring module is also used for acquiring the reason of the mail sending failure when the mail sending failure is detected;

the mail sending failure alarm module is further capable of sending the mail sending failure reason to the corresponding group when the mail related information is sent to the corresponding group.

6. The private cloud multi-mailbox delivery system of claim 1 wherein,

the load balancing algorithm stored by the load balancing algorithm module comprises the following steps: a polling algorithm, a weighted polling algorithm, a minimum number of connections algorithm, and/or an IP hashing algorithm.

7. The private cloud multi-mailbox delivery system of claim 1 wherein,

the E-mail management module is also used for setting whether the stored mailbox accounts are used for receiving mails or not according to user instructions;

if yes, the mailbox account can normally receive mails.

8. The private cloud multi-mailbox sending method is characterized by comprising the following steps of:

receiving a user instruction, performing mailbox account management operation according to the user instruction, and updating mailbox account information in a preset database according to the performed mailbox account management operation;

when receiving a mail sending instruction, reading mail account information, and calling a pre-stored load balancing algorithm to select a mail account for mail sending;

after the mail is sent, whether the mail is sent successfully or not is monitored, and if the mail is sent successfully, an alarm is triggered.