Mail transmission method, electronic device, storage medium and program product

Abstract

This application provides an email transmission method, electronic device, storage medium, and program product. The method includes: receiving an email request sent by an external terminal; processing the email request according to a pre-set business strategy to obtain a processed email request; returning response information to the external terminal based on the processed email request, and sending an email file corresponding to the processed email request to an internal terminal. An email receiving server is added as a backend server for an Nginx email proxy, providing only email protocol interaction with Nginx. That is, it processes the email request according to a pre-set business strategy to obtain a processed email request, and returns response information to the external terminal based on the processed email request. In this way, bidirectional transmission is achieved through a one-way gateway. For the external terminal, the received response information allows for timely understanding of the email transmission status.

Description

Technical Field

[0001] This application relates to the field of communication technology, and more specifically, to an email transmission method, electronic device, storage medium, and program product. Background Technology

[0002] One-way optical gateways (also known as one-way network gateways) serve as physical isolation devices between different networks and security domains, allowing only one-way, feedback-free data transmission. To prevent the leakage of important information, data from the external network can only be transmitted unidirectionally to the internal network. The hardware architecture of a one-way optical gateway is a 2+1 architecture, consisting of an external terminal, an internal terminal, and a one-way isolation component. The one-way isolation component comprises two one-way isolation cards connected by a one-way fiber optic cable. The external and internal terminals provide services externally as a whole, each running proxy software, and physical one-way communication exists between them. However, this method does not allow the external terminal to track email delivery status. Therefore, how to obtain timely information about email delivery is a pressing issue that needs to be addressed. Summary of the Invention

[0003] The purpose of some embodiments of this application is to provide an email transmission method, electronic device, storage medium, and program product. Through the technical solutions of the embodiments of this application, an email request sent by an external terminal is received; the email request is processed according to a pre-set business strategy to obtain a processed email request; response information is returned to the external terminal based on the processed email request, and an email file corresponding to the processed email request is sent to an internal terminal. In this application embodiment, an email receiving server is added, running as an independent process as a backend server for the Nginx email proxy. It only provides email protocol interaction with Nginx, that is, it processes the email request according to a pre-set business strategy to obtain a processed email request, and returns response information to the external terminal based on the processed email request. In this way, bidirectional transmission is achieved through a one-way network gateway. For the external terminal, the received response information allows for timely understanding of the email sending status.

[0004] Firstly, some embodiments of this application provide an email transmission method, including:

[0005] Receive email requests sent from external terminals;

[0006] The email request is processed according to a pre-set business strategy to obtain a processed email request.

[0007] Based on the processed email request, a response is returned to the external terminal, and the email file corresponding to the processed email request is sent to the internal terminal.

[0008] Some embodiments of this application add an email receiving server, which runs as an independent process and acts as the backend server for the Nginx email proxy. It only provides interaction with the Nginx email protocol, that is, it processes email requests according to a pre-set business strategy, obtains the processed email requests, and returns response information to external terminals based on the processed email requests. In this way, bidirectional transmission function is realized through a one-way network gateway. For external terminals, the received response information can help them understand the email sending status in a timely manner.

[0009] Optionally, the method further includes:

[0010] The email request sent by the external terminal is parsed to obtain authentication information;

[0011] The authentication information is compared with the preset authentication information;

[0012] Based on the comparison results, determine whether the external terminal has passed the verification.

[0013] Optionally, determining whether the external terminal passes verification based on the comparison result includes:

[0014] If the authentication information matches the preset authentication information, then the external terminal is determined to have passed the verification.

[0015] Optionally, the authentication information includes at least email account information and password information.

[0016] Some embodiments of this application create a local email authentication server using the SMTPD library. By reading authentication information configured on the web interface, the username and password of the email are verified without any further processing. This reduces implementation complexity, debugging difficulty, and the number of erroneous emails, thus improving system stability. Optionally, sending the email file corresponding to the processed email request to the internal terminal includes:

[0017] The external machine uses the UDP protocol to send the email file corresponding to the processed email request to the internal machine through the isolation card, so that the internal machine can send the email file to the internal terminal.

[0018] Some embodiments of this application utilize the Python language and the SMTPLIB library to create a lightweight email sending server, which runs as an independent process and sends the already stored email files to the intranet server. This reduces the complexity of implementation, the difficulty of debugging, the number of erroneous emails, and the stability of the system.

[0019] Optionally, the pre-set business strategy includes at least one or more control strategies for the protocol type, sender, recipient, attachments, or email content of external emails.

[0020] Optionally, processing the email request according to a pre-set business strategy to obtain a processed email request includes:

[0021] The email requests are filtered according to a pre-set business strategy to obtain filtered email data.

[0022] Based on the filtered email data, an email file corresponding to the email data is generated.

[0023] Some embodiments of this application configure a reverse email proxy function to proxy email requests from external networks to a local pseudo-mail server, thereby completing the email proxy forwarding function.

[0024] Secondly, some embodiments of this application provide an email transmission device, including:

[0025] The receiving module is used to receive email requests sent by external terminals;

[0026] The processing module is used to process the email request according to the preset business strategy to obtain the processed email request.

[0027] The sending module is used to return response information to the external terminal based on the processed email request, and to send the email file corresponding to the processed email request to the internal terminal.

[0028] Some embodiments of this application add an email receiving server, which runs as an independent process and acts as the backend server for the Nginx email proxy. It only provides interaction with the Nginx email protocol, that is, it processes email requests according to a pre-set business strategy, obtains the processed email requests, and returns response information to external terminals based on the processed email requests. In this way, bidirectional transmission function is realized through a one-way network gateway. For external terminals, the received response information can help them understand the email sending status in a timely manner.

[0029] Optionally, the processing module is configured to:

[0030] The email request sent by the external terminal is parsed to obtain authentication information;

[0031] The authentication information is compared with the preset authentication information;

[0032] Based on the comparison results, determine whether the external terminal has passed the verification.

[0033] Optionally, the processing module is configured to:

[0034] If the authentication information matches the preset authentication information, then the external terminal is determined to have passed the verification.

[0035] Optionally, the authentication information includes at least email account information and password information.

[0036] Some embodiments of this application create a local email authentication server using the SMTPD library. By reading authentication information configured on the web interface, the username and password of the email are verified without any further processing. This reduces implementation complexity, debugging difficulty, and the number of erroneous emails, thus improving system stability. Optionally, sending the email file corresponding to the processed email request to the internal terminal includes:

[0037] The external machine uses the UDP protocol to send the email file corresponding to the processed email request to the internal machine through the isolation card, so that the internal machine can send the email file to the internal terminal.

[0038] Some embodiments of this application utilize the Python language and the SMTPLIB library to create a lightweight email sending server, which runs as an independent process and sends the already stored email files to the intranet server. This reduces the complexity of implementation, the difficulty of debugging, the number of erroneous emails, and the stability of the system.

[0039] Optionally, the pre-set business strategy includes at least one or more control strategies for the protocol type, sender, recipient, attachments, or email content of external emails.

[0040] Optionally, the processing module is configured to:

[0041] The email requests are filtered according to a pre-set business strategy to obtain filtered email data.

[0042] Based on the filtered email data, an email file corresponding to the email data is generated.

[0043] Some embodiments of this application configure a reverse email proxy function to proxy email requests from external networks to a local pseudo-mail server, thereby completing the email proxy forwarding function.

[0044] Thirdly, some embodiments of this application provide an electronic device including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, can implement the email transmission method as described in any embodiment of the first aspect.

[0045] Fourthly, some embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, can implement the email transmission method as described in any embodiment of the first aspect.

[0046] Fifthly, some embodiments of this application provide a computer program product, the computer program product including a computer program, wherein the computer program, when executed by a processor, can implement the email transmission method as described in any embodiment of the first aspect. Attached Figure Description

[0047] To more clearly illustrate the technical solutions of some embodiments of this application, the accompanying drawings used in some embodiments of this application will be briefly described below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0048] Figure 1 A flowchart illustrating an email transmission method provided in an embodiment of this application;

[0049] Figure 2 A flowchart illustrating yet another email transmission method provided in an embodiment of this application;

[0050] Figure 3 This is a schematic diagram of the structure of an email transmission device provided in an embodiment of this application;

[0051] Figure 4 This is a schematic diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0052] The technical solutions of some embodiments of this application will now be described with reference to the accompanying drawings.

[0053] It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures. Furthermore, in the description of this application, terms such as "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0054] A one-way optical gateway (also known as a one-way network gateway) serves as a physical isolation device between different networks and security domains. It only allows one-way data transmission without feedback. To prevent the leakage of important information, data in the external network can only be transmitted unidirectionally to the internal network. The hardware architecture of the one-way optical gateway is a 2+1 architecture, consisting of an external terminal, an internal terminal, and a one-way isolation component. The one-way isolation component is composed of two one-way isolation cards connected by a one-way optical fiber. The external terminal and the internal terminal provide services to the outside world as a whole, each running agent software. The external terminal and the internal terminal communicate physically in one direction. However, this method does not allow external devices to know the email sending status. Therefore, how to promptly understand the email sending status is an urgent problem to be solved. In view of this, some embodiments of this application provide an email transmission method. The method includes receiving an email request sent by an external terminal; processing the email request according to a pre-set business strategy to obtain a processed email request; returning response information to the external terminal based on the processed email request; and sending an email file corresponding to the processed email request to an internal terminal. In this embodiment, an email receiving server is added, which runs as an independent process and acts as the backend server of the Nginx email proxy. It only provides email protocol interaction with Nginx, that is, it processes the email request according to a pre-set business strategy to obtain a processed email request, and returns response information to the external terminal based on the processed email request. In this way, bidirectional transmission is achieved through a one-way gateway. For the external terminal, the received response information allows for timely understanding of the email sending status.

[0055] like Figure 1 As shown, an embodiment of this application provides an email transmission method, the method comprising:

[0056] S101, Receive email requests sent by external terminals;

[0057] Specifically, external terminals and internal terminals are connected through a one-way gateway. The one-way gateway includes an external terminal, an internal terminal, and a one-way isolation component. External terminals communicate with the external terminal, and internal terminals communicate with the internal terminal. The external terminal of the one-way gateway receives email requests sent by external terminals.

[0058] S102. Process the email request according to the pre-set business strategy to obtain the processed email request;

[0059] Specifically, the external machine has pre-configured business policies, which include at least one or more control policies for the protocol type, sender, recipient, attachments, or email content of external emails. These business policies are used to filter received email requests, resulting in filtered email requests.

[0060] For example, the business policy set on the external terminal is based on the recipient's address information. Therefore, when an email request is received, it is filtered, meaning that only emails with recipient address information specified in the business policy are received.

[0061] S103. Based on the processed email request, return response information to the external terminal and send the email file corresponding to the processed email request to the internal terminal.

[0062] Specifically, after receiving the processed email request, the external server returns a response to the external terminal. Simultaneously, it sends the email file corresponding to the request to the internal server, which then forwards the email file to the internal terminal. This way, the external terminal receives the response and can promptly understand the email delivery status, while the internal terminal maintains a one-way transmission, ensuring data security. On the external server of the one-way gateway, Nginx's native email proxy functionality is used, and the backend server is configured as an SMTPD email receiving server created in Python. Nginx stores received emails as email files, performs content filtering and virus scanning on these files, and retains Nginx's high-performance processing and stability.

[0063] Some embodiments of this application add an email receiving server, which runs as an independent process and acts as the backend server for the Nginx email proxy. It only provides interaction with the Nginx email protocol, that is, it processes email requests according to a pre-set business strategy, obtains the processed email requests, and returns response information to external terminals based on the processed email requests. In this way, bidirectional transmission function is realized through a one-way network gateway. For external terminals, the received response information can help them understand the email sending status in a timely manner.

[0064] Another embodiment of this application further supplements the description of the email transmission method provided in the above embodiments.

[0065] Optionally, the method further includes:

[0066] Parse email requests sent from external terminals to obtain authentication information;

[0067] Compare the authentication information with the preset authentication information;

[0068] Based on the comparison results, determine whether the external terminal has passed the verification.

[0069] Optionally, based on the comparison result, determine whether the external terminal passes the verification, including:

[0070] If the authentication information matches the preset authentication information, the external terminal is deemed to have passed authentication.

[0071] Optionally, the authentication information may include at least email account information and password information.

[0072] On the external machine of the one-way gateway, a local email authentication server is created using the SMTPD library in Python. By reading the authentication information configured on the web, the username and password of the email are verified without any other processing. This reduces the complexity of implementation, the difficulty of debugging, the number of errors sent, and the stability of the system.

[0073] Some embodiments of this application create a local email authentication server using the SMTPD library. By reading authentication information configured on the web interface, the username and password of the email are verified without any further processing. This reduces implementation complexity, debugging difficulty, and the number of erroneous emails, thus improving system stability. Optionally, the email file corresponding to the processed email request is sent to the internal terminal, including:

[0074] The external machine uses the UDP protocol to send the email file corresponding to the processed email request to the internal machine through the isolation card, so that the internal machine can send the email file to the internal terminal.

[0075] Some embodiments of this application utilize the Python language and the SMTPLIB library to create a lightweight email sending server, which runs as an independent process and sends the already stored email files to the intranet server. This reduces the complexity of implementation, the difficulty of debugging, the number of erroneous emails, and the stability of the system.

[0076] Optionally, the pre-set business policies include at least one or more control policies for the protocol type, sender, recipient, attachments, or email content of external emails.

[0077] Optionally, the email request is processed according to a pre-set business strategy to obtain a processed email request, including:

[0078] Based on pre-set business strategies, email requests are filtered to obtain filtered email data.

[0079] Based on the filtered email data, generate an email file corresponding to the email data.

[0080] Some embodiments of this application configure a reverse email proxy function to proxy email requests from external networks to a local pseudo-mail server, thereby completing the email proxy forwarding function.

[0081] Figure 2This is a schematic diagram of the email proxy design for a one-way gateway. In this embodiment, key modules are added to the one-way gateway, including an Nginx email proxy module, an SMTPD email authentication server module, an SMTPD email receiving server module, and an SMTPLIB sending client module. These modules together constitute a solution combining an Nginx email proxy and an email server to realize the email proxy function of the one-way gateway.

[0082] The external machine uses Nginx's native email proxy function, combined with the SMTPD email receiving server and SMTPD email authentication server, to receive emails from the external network, complete email persistence, and filter email content according to business policies. The synchronization module sends legitimate email files to the internal machine via the isolation card using the UDP protocol. On the internal machine, the SMTPLIB sending client sends the emails to the internal network, realizing a one-way network gateway email proxy, that is, a one-way email data transmission without feedback.

[0083] Among them, 1) Nginx mail proxy module. As a high-performance reverse proxy server, Nginx can handle a large number of concurrent connections, with high throughput and low latency, and is easy to expand and maintain.

[0084] By configuring the email reverse proxy function, email requests from the external network are proxied to the local pseudo-mail server, thus completing the email proxy forwarding function.

[0085] By configuring email authentication, authentication requests are forwarded to the local authentication server, which verifies and authenticates the username and password information configured in the web application.

[0086] By configuring the email backup function, emails can be stored as files.

[0087] 2) The SMTPD authentication server module is located on the external machine of the one-way gateway. It uses Python and the SMTPD library to create a lightweight mail receiving server. It runs as an independent process and acts as the backend server for the Nginx mail agent. It only provides mail protocol interaction with Nginx and discards all received emails without processing them. This reduces the complexity of implementation, the difficulty of debugging, the number of erroneous emails sent, and the stability of the system.

[0088] Use Python's SMTPD library to create a local mail authentication server that runs as a standalone process and initializes the mail authentication information in the web configuration when the system starts.

[0089] The system configures email authentication information, such as username and password, via the web, saves the authentication information to a file, and sends an update signal for the authentication information to the local email authentication server.

[0090] After receiving the update signal, the local authentication server reads the web configuration email authentication information and caches the username and password.

[0091] It receives authentication requests from the Nginx email proxy module, verifies the username and password for the email, and does not perform any other processing.

[0092] 3) SMTPD receiving server module: Uses Python's SMTPD library to create a local pseudo mail receiving server, which runs as a separate process during system initialization.

[0093] The SMTPD mail receiving server acts as the backend receiving server for the Nginx mail agent. It agrees on the IP address and port number of the mail agent with the Nginx mail agent and configures them in the Nginx mail agent configuration file.

[0094] The SMTPD mail receiving server receives protocol interactions and email data conversion requests from the Nginx mail agent module, discards all received email data, maintains the communication connection with the Nginx agent, and provides support for the Nginx mail agent to receive emails completely.

[0095] 4) Synchronization module: On the external machine, after Nginx receives emails and saves them as email files, the synchronization module uses the UDP protocol to send the email files to the internal machine via the isolation card and saves them in the internal machine's email proxy directory.

[0096] 5) SMTPLIB Sending Client Module: On the internal machine, the SMTPLIB sending client module is an independent process that accesses the internal machine's mail agent directory, reads email files, and sends the email files to the internal network's mail receiving server.

[0097] The SMTPLIB sending client configures the internal mail receiving server's configuration information via the web interface and saves it in a file. Before sending, the sending module reads the mail server's configuration information, sets the address, username, and password of the internal network mail receiving server, and uses the SMTPLIB library to communicate with the mail receiving server via the SMTP protocol to send the email to the internal network's mail receiving server.

[0098] For example:

[0099] This application describes the process of sending an email from an external network to an internal network through a one-way gateway, as shown below:

[0100] 1. Initialize all modules of the email agent;

[0101] On the external machine, the Nginx mail agent process starts, and the configuration file is configured with the default addresses and ports of the SMTPD authentication server and SMTPD receiving server.

[0102] On the external machine, the SMTPD authentication server is started as a separate process.

[0103] On the external machine, the SMTPD mail receiving server is started as a separate process.

[0104] 2. Configure email proxy policies via the web;

[0105] The external machine is configured with email proxy policies that include access control based on blacklists and whitelists for handling external emails, such as protocol type, sender, recipient, attachments, and email content.

[0106] The internal terminal is configured to receive mail server information from both internal and external servers.

[0107] 3. The external machine receives email requests and performs email authentication;

[0108] On the external machine, the Nginx mail proxy module receives email requests from the external network, parses the email requests, and sends authentication requests to the SMTPD authentication server.

[0109] On the external machine, after the SMTPD authentication server receives the email authentication request from Nginx, it reads the email authentication information configured in the web configuration, performs authentication verification, and responds to the Nginx email agent with the authentication result.

[0110] On the external machine, the Nginx proxy receives the authentication result from the SMTPD authentication server. If authentication fails, the connection is closed, ending the current transmission.

[0111] On the external machine, the Nginx proxy receives the authentication result from the SMTPD authentication server. If the authentication is successful, it proxies the email request to the local mail receiving server and begins email data transmission.

[0112] 4. The external machine receives email data and filters the content;

[0113] The Nginx email proxy module filters and controls access to email data, such as by using blacklists and whitelists for protocol type, sender, recipient, attachments, and email content.

[0114] The Nginx mail proxy module forwards email data to the SMTPD receiving server and simultaneously stores the email data as an email file in the external machine's email file directory.

[0115] The SMTPD receiving server only interacts with the Nginx mail agent and discards all received email data without processing it.

[0116] 5. Synchronize email files from the external machine to the internal machine via the isolation card;

[0117] The external machine sends email files to the internal machine via the isolation card using the UDP protocol. The internal machine receives the emails and saves them to the email file directory.

[0118] 6. Send email files from the internal terminal;

[0119] The SMTPLIB client polls the internal machine's email file directory and sends email files to the internal network.

[0120] This application embodiment maximizes the reuse of the mail proxy function in Nginx reverse proxy, capable of handling a large number of concurrent connections, with high throughput and low latency, improving the system's scalability and maintainability. It effectively combines Nginx mail proxy functionality with the SMTPD mail server, reusing many of Nginx's advantages. It features high performance, the ability to handle a large number of concurrent connections, high throughput and low latency, easy scalability and maintainability, and provides SSL / TLS encryption support to help protect the security of email transmission. It also offers good stability and resource utilization efficiency.

[0121] This project utilizes the SMTPD library in Python to create a lightweight mail receiving server. Running as a standalone process, it acts as a backend server for the Nginx mail agent, only interacting with Nginx's mail protocol. It discards all received emails without processing them, reducing implementation complexity, simplifying debugging, minimizing errors, and improving system stability.

[0122] By using the SMTPD library in Python, a local email authentication server is created. It reads the authentication information configured on the web server to verify the username and password of emails without performing any other processing. This reduces the complexity of implementation, the difficulty of debugging, the number of errors sent, and the stability of the system.

[0123] Using Python and the SMTPD library to write an SMTPD mail authentication server and an SMTPD mail receiving server is a lightweight process that only performs simple authentication and SMTP protocol interaction, without handling complex business logic. This simplifies the implementation, reduces the error rate, and improves system stability.

[0124] This email client, written in Python using SMTPLIB, is a lightweight process that runs as a standalone process. It sends archived email files to an internal network server without handling complex business logic, simplifying implementation, reducing error rates, lowering complexity, simplifying debugging, and improving system stability.

[0125] It should be noted that each of the implementable methods in this embodiment can be implemented individually or in any combination without conflict. This application does not limit this.

[0126] Another embodiment of this application provides an email transmission apparatus for performing the email transmission method provided in the above embodiments.

[0127] like Figure 3 The diagram shown is a structural schematic of an email transmission device provided in an embodiment of this application. The email transmission device includes a receiving module 301, a processing module 302, and a sending module 303, wherein:

[0128] The receiving module 301 is used to receive email requests sent by an external terminal;

[0129] The processing module 302 is used to process email requests according to a pre-set business strategy to obtain processed email requests.

[0130] The sending module 303 is used to return response information to the external terminal based on the processed email request, and to send the email file corresponding to the processed email request to the internal terminal.

[0131] Regarding the apparatus in this embodiment, the specific manner in which each module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0132] Some embodiments of this application add an email receiving server, which runs as an independent process and acts as the backend server for the Nginx email proxy. It only provides interaction with the Nginx email protocol, that is, it processes email requests according to a pre-set business strategy, obtains the processed email requests, and returns response information to external terminals based on the processed email requests. In this way, bidirectional transmission function is realized through a one-way network gateway. For external terminals, the received response information can help them understand the email sending status in a timely manner.

[0133] Another embodiment of this application further supplements the description of the email transmission device provided in the above embodiments.

[0134] Optionally, the processing module is used for:

[0135] Parse email requests sent from external terminals to obtain authentication information;

[0136] Compare the authentication information with the preset authentication information;

[0137] Based on the comparison results, determine whether the external terminal has passed the verification.

[0138] Optionally, the processing module is used for:

[0139] If the authentication information matches the preset authentication information, the external terminal is deemed to have passed authentication.

[0140] Optionally, the authentication information may include at least email account information and password information.

[0141] Some embodiments of this application create a local email authentication server using the SMTPD library. By reading authentication information configured on the web interface, the username and password of the email are verified without any further processing. This reduces implementation complexity, debugging difficulty, and the number of erroneous emails, thus improving system stability. Optionally, the email file corresponding to the processed email request is sent to the internal terminal, including:

[0142] The external machine uses the UDP protocol to send the email file corresponding to the processed email request to the internal machine through the isolation card, so that the internal machine can send the email file to the internal terminal.

[0143] Some embodiments of this application utilize the Python language and the SMTPLIB library to create a lightweight email sending server, which runs as an independent process and sends the already stored email files to the intranet server. This reduces the complexity of implementation, the difficulty of debugging, the number of erroneous emails, and the stability of the system.

[0144] Optionally, the pre-set business policies include at least one or more control policies for the protocol type, sender, recipient, attachments, or email content of external emails.

[0145] Optionally, the processing module is used for:

[0146] Based on pre-set business strategies, email requests are filtered to obtain filtered email data.

[0147] Based on the filtered email data, generate an email file corresponding to the email data.

[0148] Some embodiments of this application configure a reverse email proxy function to proxy email requests from external networks to a local pseudo-mail server, thereby completing the email proxy forwarding function.

[0149] Regarding the apparatus in this embodiment, the specific manner in which each module performs its operations has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0150] It should be noted that each of the implementable methods in this embodiment can be implemented individually or in any combination without conflict. This application does not limit this.

[0151] This application also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, can perform the operation of any of the methods corresponding to the email transmission methods provided in the above embodiments.

[0152] This application also provides a computer program product, which includes a computer program, wherein when the computer program is executed by a processor, it can implement the operation of any of the methods corresponding to the email transmission methods provided in the above embodiments.

[0153] like Figure 4 As shown, some embodiments of this application provide an electronic device 400, which includes a memory 410, a processor 420, and a computer program stored in the memory 410 and executable on the processor 420. When the processor 420 reads the program from the memory 410 via a bus 430 and executes the program, it can implement the method of any embodiment of the above-described email transmission method.

[0154] Processor 420 can process digital signals and may include various computing architectures. For example, it may be a complex instruction set computer architecture, a reduced instruction set computer architecture, or an architecture that implements multiple instruction set combinations. In some examples, processor 420 may be a microprocessor.

[0155] Memory 410 can be used to store instructions executed by processor 420 or data related to the execution of instructions. These instructions and / or data may include code for implementing some or all of the functions of one or more modules described in the embodiments of this application. The processor 420 of this disclosure embodiment can be used to execute instructions in memory 410 to implement the methods shown above. Memory 410 includes dynamic random access memory, static random access memory, flash memory, optical memory, or other memories well known to those skilled in the art.

[0156] The above are merely embodiments of this application and are not intended to limit the scope of protection of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application. It should be noted that similar reference numerals and letters in the following figures indicate similar items; therefore, once an item is defined in one figure, it does not need to be further defined and explained in subsequent figures.

[0157] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

[0158] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply the existence of any such actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, an element defined by the phrase "comprising a ..." does not exclude the presence of other identical elements in the process, method, article, or device comprising the element.

Claims

1. A mail transmission method applied to a one-way isolation device connecting an external network and an internal network, the one-way isolation device comprising an external terminal, an internal terminal, and a one-way isolation component, wherein an external terminal communicates with the external terminal, and an internal terminal communicates with the internal terminal, characterized in that... The method for configuring an Nginx mail proxy module and an SMTPD mail receiving server on an external machine includes: The Nginx mail proxy module receives email requests sent from external terminals; The email request is processed according to a pre-set business strategy to obtain a processed email request. The Nginx mail proxy module forwards the processed email data to the SMTPD mail receiving server. The SMTPD mail receiving server only interacts with the Nginx mail proxy module to generate response information. The Nginx email proxy module returns the response information to the external terminal and sends the email file corresponding to the processed email request to the internal terminal through the one-way isolation device, and then the internal terminal sends it to the internal terminal.

2. The email transmission method according to claim 1, characterized in that, The method further includes: The external terminal parses the email request sent by the external terminal to obtain authentication information; The authentication information is compared with the preset authentication information; Based on the comparison results, determine whether the external terminal has passed the verification.

3. The email transmission method according to claim 2, characterized in that, The step of determining whether the external terminal passes verification based on the comparison result includes: If the authentication information matches the preset authentication information, then the external terminal is determined to have passed the verification.

4. The email transmission method according to claim 2, characterized in that, The authentication information includes at least email account information and password information.

5. The email transmission method according to claim 4, characterized in that, Sending the email file corresponding to the processed email request to the internal terminal, including: The external machine uses the UDP protocol to send the email file corresponding to the processed email request to the internal machine through the isolation card, so that the internal machine can send the email file to the internal terminal.

6. The email transmission method according to claim 1, characterized in that, The pre-set business strategy includes at least one or more control strategies for the protocol type, sender, recipient, attachments, or email content of external emails.

7. The email transmission method according to claim 6, characterized in that, The process of processing the email request according to a pre-set business strategy to obtain the processed email request includes: The email requests are filtered according to a pre-set business strategy to obtain filtered email data. Based on the filtered email data, an email file corresponding to the email data is generated.

8. An electronic device, characterized in that, The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the program, implements the email transmission method according to any one of claims 1-7.

9. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, characterized in that, when the program is executed by a processor, it can implement the email transmission method according to any one of claims 1-7.

10. A computer program product, said computer program product comprising a computer program, wherein, When the computer program is executed by a processor, it can implement the email transmission method according to any one of claims 1-7.

Images