KR20020048276A - Web application service method for transmitting multiple e-mails by using a massive e-mail sending system in common - Google Patents

Abstract

PURPOSE: A web application service method for sending lots of e-mails is provided to carry out a business sending a lot of e-mails as a high speed without constructing a separate e-mail sending infra by reducing the data processing time for a lot of e-mail data through indexing and grouping. CONSTITUTION: The web application service method comprises the steps of carrying out a log-on process when a client connects to a network(S401), setting an object sending e-mail according to a selection of the client, judging a success of a payment process after carrying out a calculation for a charge according to a service of the client(S405), and transferring the e-mail information to an SMTP(Simple Mail Transfer Protocol) server after confirming the payment. The SMTP server executes the e-mail sending job and monitors a sending state.

Description

WEB APPLICATION SERVICE METHOD FOR TRANSMITTING MULTIPLE E-MAILS BY USING A MASSIVE E-MAIL SENDING SYSTEM IN COMMON}

The present invention relates to an email forwarding agent service technology, and more particularly, a web application service providing method for allowing a large number of clients to share a large amount of email transmission system while enabling a large amount of email transmission, and a computer recording a program for realizing the same. The present invention relates to a recording medium which can be read.

Email marketing is an interactive network marketing where suppliers and customers communicate in both directions directly and directly through email. They get more active and real-time feedback than traditional passive and expensive offline marketing. Says marketing techniques that can. Although many companies are attempting to implement internet marketing, they are still at the beginning level such as recruiting members from the company's homepage.As a more advanced marketing technique, two-way communication with consumers is possible. Email marketing is known that can easily perform the above.

When emails sent from such email marketing are classified by their contents, they can be largely divided into broadcast mails and individual mails. Broadcast mail refers to an email that is identical in content to multiple email recipients, and individual mail refers to an email that is different in content to multiple email recipients. For example, if a department store customer manager wants to email a customer with information about a new product for this month, the same new product information for the same month will be sent to all customers. On the other hand, the department store customer manager manages the product or brand preference for each customer, and when the information about the brand and the product information is sent by e-mail, a separate content must be configured for each customer to be sent. Email corresponds to individual mail. Customer management through broadcast mail and individual mail has become an essential element in today's enterprise, and in almost all fields, such email marketing techniques are spreading.

On the other hand, recently, due to the limitation that banner advertising using a website is inefficient and passive, banner advertising using email is widely used. This allows you to connect to an advertising site by selecting a banner included in an email written in Hyper Text Markup Language (HTML) format, which allows you to provide active advertising, but if you send email to a large number of customers, your provider will be expensive. The cost of building an e-mail server equipment is not only huge, but the amount of e-mail sent for e-mail marketing is variable for each session. As a result, the mail server has a large load on the sender side with a relatively large amount of email transmission, and the use efficiency of mail server resources is significantly reduced at the sender side with a large amount of email transmission.

On the other hand, the conventional e-mail transmission and reception technology that the e-mail sending server receives the e-mail data generated by the mail user agent in a first-in, first-out manner, and one e-mail sending agent is connected to the e-mail receiving server in the order of the received e-mail data to send Is organized in such a way. Therefore, if a user wants to send a large amount of emails for email marketing according to the related art, an email sending agent must connect to a receiving server for each email data, so that the more time the email data attempts to access the receiving server, There was an increasing disadvantage.

In addition, even though there are many e-mails to be sent to the same e-mail receiving server in one session, the e-mail is sent on a first-in, first-out basis. Since the connection and transmission to the server several times, it takes a lot of time, the real-time processing of the client request is impossible and the transmission efficiency is also reduced.

Moreover, in the data process for sending an email, there is a disadvantage in that the time for searching the stored file is long because the email data received from the mail user agent is stored and read out of alignment. This disadvantage becomes worse as more emails need to be sent.

The reason is that despite a large number of return mails and undeliverable e-mails due to the absence of a recipient mail account, no domain, a syntax error in the outgoing e-mail, a network problem, etc. There was a problem that can not be analyzed and reported accurately email marketing can not be efficient.

Accordingly, the present invention has been proposed to solve the above-mentioned conventional problems, and shortens the data processing time by indexing and grouping a large amount of email data, activates a plurality of email sending agents in parallel, and dynamically sends emails. A large number of clients (corporate or individual) share a mass email transmission system that sends a large amount of emails at high speed by performing a task, and access the mass email transmission system through each client terminal with an account assigned thereto. By sending emails according to the sending target group and contents set by the members of the web, the web application providing method which can perform a large amount of email sending services without a separate email sending infrastructure at high speed, and to realize the same In a computer storing a program providing a recording medium which can be read out it is aimed.

1 is a block diagram showing a system for providing a mass email sending web application service according to an embodiment of the present invention;

Figure 2 is a schematic diagram showing a large-capacity email transmission proxy system of Figure 1;

3 is a schematic diagram showing an email sending server of FIG. 2;

4 is an overall flowchart of an email transmission web application service according to an embodiment of the present invention;

5 is a screen showing a web page displayed on a sending client connected to a mass email sending agent system according to the present invention;

6 is a flow chart showing the charging electronic payment step of FIG.

7 is a flowchart showing an e-mail data generation step of FIG. 4;

8 and 9 are flowcharts showing the dispatch execution step of FIG. 4;

10 is a screen showing a web page displayed on the transmitting client in the monitoring step of FIG.

11 is a diagram illustrating an account adding menu screen.

* Explanation of symbols for main parts of the drawings

100: large capacity email sending agency system

101: email receiving server 103: email sending client

105: email receiving client 210: web server

230: email sending server 240: reporting agent

250: monitoring agent 260: integrated database

In order to achieve the above object, the present invention provides a web application service method for allowing a plurality of email sending clients to send a large amount of email to a plurality of recipients through a network while sharing a mass email sending system, respectively. A first step of performing a logon process, as the e-mail sending client is connected through the network; Setting a sending target email according to selection of the at least one email sending client; A third step of performing a billing calculation to be processed on the basis of the service type for the corresponding email sending client and determining whether the payment processing is successful; A fourth step of transmitting the corresponding email information to the SMTP server when the charging process of the third step is confirmed; And a fifth step of executing an email sending task in the SMTP server and monitoring a sending status. The method may further include scheduling an email transmission at a specific date and time when the email transmission is requested from the at least one email sending client, and generating and databaseting an email sending result report. It provides a web application service method that allows a large number of clients to include a large number of email transmission system while sharing a large amount of email transmission system.

On the other hand, at least one email in a web application service system equipped with a microprocessor to allow a plurality of email sending clients to send a large amount of email to a large number of recipients over the network, each sharing a large email sending system A function of performing logon processing as a sending client connects through the network; Setting a sending target email according to the selection of the at least one email sending client; A function of performing a billing calculation to be processed based on a service type for the corresponding email sending client and determining whether the payment processing is successful; Transmitting the e-mail information to an SMTP server when the charging process is confirmed; And a computer-readable recording medium having recorded thereon a program for executing an e-mail sending operation in the SMTP server and monitoring a sending status. When the email is requested from the at least one email sending client at a specific date and time, a program for further realizing a function of scheduling an email to be sent at a specific date or a database for generating and sending an email sending result report. The present invention provides a recording medium that can be read by a computer that records a program for further realizing the above.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art can easily implement the present invention. Other features and operational advantages will be clarified by the preferred embodiment, including the object, construction and effects of the present invention.

1 is a block diagram showing a system for providing an email sending web application service according to the present invention. As shown in the drawing, the present invention provides a mass email sending agent system 100 and an email according to the present invention in a network such as the Internet. The receiving servers 101a to 101n, the email sending clients 103a to 103n, and the email receiving clients 105a to 105n are implemented under the environment in which they are connected. The transmitting clients 103a to 103n used herein are not limited to PCs, but various wireless terminals equipped with a web browser, a laptop equipped with a wireless modem, a PDA, or the like can be used. Typically, email is sent by an email sending server using the SMTP protocol, received and stored on an email receiving server using the POP3 protocol over a network, such as the Internet, and then sent to an email recipient client with an account on the email receiving server. Done.

As shown in Fig. 1, the mass email sending agent system 100 according to the present invention provides a mass mail sending system to the email sending clients 103a to 103n via the Internet. That is, the web application service according to the present invention installs a large-capacity email sending system 100 required by several users only on a specific server, and allows a user to send a large-capacity email through a network connection. Therefore, the web application service according to the present invention can reduce the manpower and cost on the user side, can use the high-quality service, is not restricted by the place, and develops a fast business to compete with large companies It will be possible.

Figure 2 is a block diagram showing the internal structure of a large-capacity email transmission proxy system according to an embodiment of the present invention, as shown in the web server 210, email sending server 230, reporting agent 240 ), A monitoring agent 250 and a unified database 260.

When the e-mail sending clients 103a to 103n log in to the web server 210 and transmit e-mail creation information, the web server 210 constructs an e-mail using data stored in the integrated database 260. The configured email is transmitted to the email sending server 230 to perform mass email sending, and in the process, the reporting agent 240 and the monitoring agent 250 integrate the email sending status and the sending result into the integrated database 260. In the meantime, the result is transmitted to the e-mail sending clients 103a to 103n.

The web server 210 has a transceiver 211, a body component 214, a dispatch manager 220, and a billing processor 221. The web server 210 is connected to the integrated database 260 to transmit and receive data. Here, the dispatch management unit 220 is connected to the email sending server 230 to transmit the email data generated by the body configuration unit 214 to the email sending server 230. The transceiver 211 is connected to the transmitting clients 103a to 103n, extracts authentication grade information from the e-mail creation information transmitted from the transmitting clients 103a to 103n, and stores the authentication grade information in the integrated database 260 and the scheduling queue described later. It has an authentication management agent 212 that performs an authentication operation that allows reading, writing, and deleting of the data, and a scheduler 213 that determines an email sending mode and an email sending order from email writing information. In addition, the transmission and reception unit 211 receives the e-mail composition information by sending a web page including a prompt page for receiving the body and header information of the e-mail from the logged-in transmission client (103a to 103n) and accordingly the body configuration unit ( 214 will generate an email. Since the large-capacity email transmission proxy system 100 according to the present invention is a web application providing service system, a plurality of sending clients 103a to 103n connect to the system 100.

The scheduler 213 will be described in detail as follows. First, the e-mail creation information transmitted from the sending clients 103a to 103n is stored in the mail message file system 260d in the integrated database 260, and index data for the file is generated. The generated index data is expressed as an identification ID for identifying a user account and corresponding email creation information, and indicates a storage path of the corresponding email creation information file stored in the mail message file system 260d.

On the other hand, in the process of storing the e-mail preparation information in the mail message file system 260d, the scheduler 213 determines the sending mode and the sending order of the e-mail. The scheduler 213 may determine a sending mode, that is, whether the corresponding email is immediately sent, scheduled sent, or regularly sent, based on an e-mail sending time and a sending period included in the e-mail preparation information.

Also, even in the same sending mode of the same sending time, the email to be sent first is determined according to the sending priority information included in the email writing information. When the sending mode and the sending priority are determined as described above, the generated index data is stored in the scheduling queue provided in the transmitting and receiving unit 211 for each sending order. The index data stored in the scheduling queue is transmitted to the main body 214 according to the sending time of the corresponding email.

The body component 214 includes an email recipient extractor 215, a merge agent 216, a database agent 217, and a web agent 218. The email receiver extractor 215 extracts a query statement included in the extended header of the email composition information based on the index data transmitted by the scheduler 213 for each email sending order, and the merge agent 216 and the data. The base agent 217 and the web agent 218 may include recipient related data, email content data, and web content of a web page, which are stored in the integrated database 260 according to a tag type among execution statements included in the body of the email. Reads data and replaces the read data with the corresponding tag in the place where the corresponding tag is located. Here, the query statement and the tag are information generated and transmitted by the sender through a web page transmitted to the transmitting clients 103a to 103n currently connected to the system 100 according to the present invention through the transceiver 211.

The sending management unit 220 inserts the email body generated by the body constructing unit 214 into a place where the body constituting the body of the email creation information is located, and completely generates the email, and then transmits the email body to the email sending server 230. It will perform the function.

Here, the charging processing unit 221 calculates the fee required for transmitting the corresponding email from the email creation data created by the sending clients 103a to 103n logged in to the system 100, and sends it to the sending clients 103a to 103n. After that, the e-mail sending process is paused until the billing processing is completed. That is, the email composition information received from the sending clients 103a to 103n after the payment is allowed is allowed to be transmitted to the body constructing unit 214 to proceed with the process.

The integrated database 260 includes a member information database 260a that can access the system 100, a recipient information database 260c, which may be referred to as the customer information of the member, and a template for creating email content. Refers to a file registered and stored as a 'letter' to compose an e-mail, from a content database 260g and sending clients 103a to 103n in which data such as image / video / audio files and newsletters are stored. A mail message file system 260d in which the sent e-mail creation information is stored, a billing information database 260b in which billing history data of a member is stored, and a dispatch queue information database in which e-mail information data scheduled for shipment by a member is stored ( 260e) and the sending status information of the bulk mail previously sent and the sending status information of the bulk mail currently being sent Reporting is stored emitter / monitoring information includes a database (260f).

In the member database 260a, a member's name, e-mail address, and social security number are basically stored, and in addition, member-related data (ID, password, etc.) set as required by the administrator of the system 100 is stored. .

In addition, the recipient information database 260c stores recipient information data necessary for the member management as a sender for customer management, including the recipient's name, email address, and social security number. For example, if the member is a financial company, the member's name is stored as a field value in a field named NM in the table PSA_CUST_MAIL, and the member's email address is stored as a field value in a field called COM_ID in the table PSA_CUST_MAIL. The member's social security number is stored in the SSNO field of the table PSA_CUST_MAIL2. The member's late fee data is also stored in the DELAY_FEE field of the LCF_CUST_SEND_EMAIL table.

On the other hand, as described above, the mail message file system 260d stores the e-mail creation information transmitted from the transmitting clients 103a to 103n. That is, the transmitting clients 103a to 103n transmit the email writing request and the email writing information to the web server 210 through the web page received from the transmitting and receiving unit 211, and the email writing information thus transmitted is a mail message file. Stored in system 260d.

Email composing information consists of extended header ([ExtHeader]), body ([BODY]), and content ([Content]) data, and extended header ([ExtHeader]) contains a group of recipients whose members can identify the email information. Name, a query statement requiring e-mail recipient extraction, e-mail sending time and sending cycle and sending priority by defining conditions for selecting e-mail recipients from sending clients 103a to 103n among data stored in the recipient database 260c. Contains information. In addition, the extension header [ExtHeader] includes authentication class information of the transmitting clients 103a to 103n.

The body [BODY] contains data defining contents constituting the actual content of the email. For reference, the [BODY] data is written as a html (hypertext markup language) document as a dispatch template.

Finally, the content [Content] includes syntax data specifying the header data of the email required for sending the email and the location of the above-mentioned body [BODY] data. In this case, when there is an attachment in the e-mail to be sent, the attachment is transmitted together after the content data.

The billing information database 260b stores billing information charged according to whether a member is a company or an individual and a type of service used.

FIG. 3 is a schematic diagram illustrating an exemplary configuration of the email sending server 230 of FIG. 1. As shown in the drawing, the email sending server 230 may include a web server for generating a broadcast mail and an individual mail ( 210 is connected. If necessary, a remote email sending server 330 may be further provided. The remote email sending server 330 divides the load on the email sending server 230 when the amount of emails to be sent is so great that the email sending server 230 takes a large amount of time to process alone. In this case, you will be in charge of sending e-mail in parallel.

The e-mail sending server 230 is a receiving unit 231, the receiving unit 231 responsible for receiving, storing and sorting the e-mail data constituting the actual information of the e-mail and the recipient information of the e-mail generated from the web server 210, the receiving unit 231 The broadcast mail unit 232 and the individual mail unit 233, which receive data stored and sorted in the Internet and perform data processing for high-speed transmission, are arranged in the broadcast mail unit 232 and the individual mail unit 233. Agent information sent from the web server 210 and the agent manager 235 which dynamically manages the email sending agents 237a to 237n which process the email data in parallel in order to send email at high speed based on the information and email data. Data stored in the file database 234 and the file database 234 for storing the e-mail data and data processed by the e-mail sending server 230 It consists of a remote email delivery server 330 and the file transfer portion 236 for transmitting and receiving.

Although not shown, the receiving unit 231 includes a buffer memory and a main index queue, and the broadcast mail unit 232 and the individual mail unit 233 are provided with sub index queues. The email sending agents 237a to 237n perform a function of connecting to the email receiving server of the called party and sending email.

The remote e-mail sending server 330 performs data communication with the receiving unit 231 of the e-mail sending server 230 to store the broadcast data stored in the index data and file database 234 stored and sorted by the receiving unit 231. The remote broadcast mail unit 332 and the remote individual mail unit 333 which perform data processing for high speed shipment by receiving content data and individual mail data, and the remote broadcast mail unit 332 and the remote individual mail unit 333. The agent management unit 335 dynamically manages the email sending agents 337a to 337n which process the email data in parallel in order to send email at a high speed based on the recipient information and the email data processed in the above. The remote broadcast mail unit 332 and the remote individual mail unit 333 communicate data with the receiver 231 and the file transmitter 236 to read the recipient information and the email content stored in the file database 234. Do this.

On the other hand, the mass email sending agent system 100 according to the present invention is for the information and the cause of the failure to send the e-mail failed to send and send at the email sending agent (237a to 237n) and remote email sending agent (337a to 337n) Information-The sending result information, such as the total number of emails you attempted to send, the number of emails that were sent successfully, and the list of emails that failed to send, and the reason for the failure, the recipient email address is no longer valid, or the email receiving server responds. A reporting agent 240 that monitors and records the reason for the failure to send an email, such as not doing it, and monitors to analyze and record the status of the current email sending server 230 and the remote email sending server 330 in real time. Agent 250. The result data generated by the reporting agent 240 and the monitoring agent 250 is transmitted to the transmitting clients 103a to 103n through the transceiver 211 of the web server 210.

FIG. 4 is a flow chart of an embodiment of a method for providing a web application service for allowing a large number of clients to send a large amount of email while sharing a large amount of email transmission system, according to the present invention. The present invention provides a web application service method that allows a plurality of email sending clients to send a large amount of emails to a plurality of recipients through a network while sharing a large email sending system, each of which includes at least one sending client 103a to 103n. Performs a logon process as the user connects through the network (S401), and creates and sends outgoing e-mail data to the system according to selection of the at least one transmitting client (103a to 103n) (S403). And a service type for the corresponding transmitting clients 103a to 103n. Performing a billing calculation to be processed as a condition and determining whether payment processing is successful (S405), and when the success of the billing process is confirmed, transmits the corresponding e-mail creation data to the main body 214 to form an e-mail. And transmitting to the sending server 230 (S407) and executing the sending email task at the email sending server 230 and monitoring the sending status (S409), and optionally generating an email sending result report. And databaseting the data (S411). The method may further include scheduling an email transmission at a specific date and time when the email transmission is requested from the at least one transmitting client 103a to 103n.

5A to 5H are diagrams showing web pages that can be displayed on sending clients 103a to 103n connected to the system 100 according to the present invention so that email creation information data can be input. A process (S403) of creating / sending email data at 103a to 103n will be described.

Fig. 5A is a diagram showing a menu screen displayed on the sending clients 103a to 103n. [Email sending] 501 is a button selected when generating e-mail data to be sent, and " reservation management " As a button selected when managing an e-mail scheduling, using the scheduler function menu 523 provided on the web page of FIG. 5H displayed when selecting "Schedule Management" 503, details of a scheduled date are also checked. This is possible. "Shipping management" (505) is a menu that provides a function that can check for the current e-mail sent or completed sending. In addition, the scheduler function menu 523 may be used to check the corresponding details, and provides a function of displaying information provided by the reporting agent 240 and the monitoring agent 250. "Template Management" 507 provides a function for checking / modifying / deleting a template previously created and stored in the mail content database 260g. Group management 509, which manages the address book to which mail is to be sent, divides the recipient information data for each member stored in the recipient information database 260c into a plurality of groups according to the sending destination, thereby providing an efficient mail address book management function. do. `` Account Management '' (511) provides a function for granting new authority to the dispatched part by the corporate member applicant (all managers), and the overall account management is overseen by the corporate manager. can do. This account management function can be disabled for individual members. Finally, in the "personal user information" 513, the date of sending the latest e-mail, the date of scheduling the mail sending, the latest reservation date, and the like are displayed.

5B and 5C are diagrams illustrating a process of selecting a group management menu in FIG. 5A to select recipients to upload recipient information from the transmitting clients 103a to 103n or to receive a current email from among the uploaded receiver data.

If the [Group management] menu 509 is selected, the group list stored by the current user in the recipient information database 260c is displayed, and the [Add Group] and [Delete Group] menus are displayed as detailed menus. When the "Add Group" menu is selected, a pop-up window with two tabs, "DB Tool" and "Address Book Upload", appears as shown in Fig. 5B. First, select the "Address Book Upload" tab 515, specify a group name, find a file to upload, and execute the upload. The uploaded recipient data is stored in the recipient information database 260c as data related to the corresponding sender member. 5C is a screen displaying contents of an uploaded file in a process of uploading an address book group file. Although not shown in the drawing, the "DB Tool" tab 517 is intended to select and send only e-mails to recipients that meet specific conditions by using the entire recipient data uploaded and stored from the transmitting clients 103a to 103n. In this case, it provides a function of extracting / selecting a specific e-mail recipient matching a desired condition from among the recipient data previously stored in the recipient information database 260c. This function is used when you need to send mail only to people. When the target recipient of the email is selected using the [DB tool] function, as described above, a query for requesting the recipient of the email is generated in the extension header [ExtHeader] as the email writing information transmitted to the web server 210.

FIG. 5D is a diagram showing a mail composing web page displayed when a user wants to create a body of an email to be sent by selecting the [send mail] menu 501 in FIG. 5A. In the drawing, when the [Web Agent] menu 519 is selected, a pop-up window for inputting a URL appears. When the user inputs a URL, the corresponding web page is displayed on the transmission clients 103a to 103n. When the sending clients 103a to 103n make a request to insert the web page into the body of the email, a syntax for inserting the URL into the body is generated. If you select 'Name' in 'Merge Function' (521), the phrase% merge.name% is created on the mail composing web page, and the name of each individual of the group of recipients to be sent is displayed in each mail. When selected, the phrase% merge.email% is created on the mail composing web page, displaying the email of each individual in the group of recipients you wish to send. This syntax is a kind of query tag, and is a function used when a recipient's name or email address is to be inserted into the body of an email from recipient data stored in the integrated database 260. That is, if the recipient group 'Hong Gil-dong' is marked as '% merge.name% Member' and the group of recipients to be sent is sent to the recipient 'Hong Gil-dong', an email marked 'Hong Gil-dong Member' is automatically sent. will be. As described above, the function of inserting the web page into the body of the email or inserting the recipient's name into the body of the email includes the merge agent 216 of the body component 214 in the web server 210, which will be described later. The web agent 218 analyzes each tag and replaces the corresponding data with each tag. If the web agent 218 wants to insert data such as an email template in the integrated database 260 into the body of the email in a similar manner. The base agent 217 is activated to replace the tag.

5E and 5F show a template management window displaying a list of templates stored by the user in the mail content database 260g so far when a user wants to create an email to be sent by selecting the [Template Management] menu 507 in FIG. 5A. And an upload popup window when the current user wants to upload a template. The [Template Management] function allows the sender to reuse or edit an e-mail template that has already been used, and also upload and save an e-mail template that has not yet been saved / sent in the current edit state. This functionality is the responsibility of the database agent 217 as described above.

Through the sending clients 103a through 103n, the sender creates an HTML document to be used as a template in the email creation web page of FIG. 5D. If you want to create an email data by editing a previously created email template, select one of the template list displayed in FIG. 5E to import the template file from the mail contents database 260g as shown in FIG. The document is displayed on the web page. When the e-mail body data is completed, the e-mail header information is generated by inputting the e-mail subject, sender name, recipient group name, and reservation setting data. When the reservation setting data is input, as described above, the scheduler 213 stores the e-mail creation information transmitted from the sending clients 103a to 103n in the mail message file system 260d and generates index data for the corresponding file. The e-mail sending time and the sending cycle included in the e-mail preparation information determine the sending mode, that is, whether the e-mail is sent immediately, scheduled sending or regular sending. When the sending mode and the sending priority are determined as described above, the generated index data is stored in the scheduling queue provided in the transmitting and receiving unit 211 for each sending order. The index data stored in the scheduling queue is transmitted to the main body 214 according to the sending time of the corresponding email. On the other hand, the e-mail information scheduled for shipment is stored in the dispatch queue information database 260e.

5H is a diagram illustrating a reservation status based on data stored in a scheduling queue. In FIG. 5A, it is displayed on the transmitting clients 103a to 103n via the " reservation management " menu 503. FIG. The displayed information is read out from the dispatch queue information database 260e. In this figure, the 'reserved name' indicates the name of the template, 'the corresponding group' indicates the group name of the address book to which the mail is to be sent, and the 'sending status' indicates the current mail sending status (sending / completed sending).

6 is a flowchart showing the charging electronic payment step after the email body data creation step of FIG. 4 shown in FIGS. 5A to 5H is completed.

The billing processing unit 221 checks whether the user who created the e-mail body data is a corporate member or an individual member, checks the type of service to be used at present (S601), calculates billing information in consideration of the amount of mail sent, and then sends the corresponding information. The transmission / display is performed to the clients 103a to 103n (S603). The sending clients 103a to 103n check the displayed contents, input the payment method and the necessary information (bank name, account number or card number, card password, etc.) and transmit them to the billing processing unit 221 ( S605). The billing processing unit 221 performs the payment based on the payment information received from the transmitting clients 103a to 103n (S607), saves the billing information (S609), and stores the email data created by the user in the mail message file system ( 260d, the e-mail creation information received from the sending clients 103a to 103n is allowed to be sent to the body constructing unit 214 to proceed with the process (S611).

7A to 7C are flow charts illustrating the step of generating email data in the text constructing unit 214 in the web server 210 after the billing electronic payment of FIG. 4 shown in FIG. 6 is completed, and in the text constructing unit 214. The following shows the operation of automatically generating an e-mail.

When the body configuration unit 214 receives the index data stored in the scheduling queue from the scheduler 213 according to the sending time of the corresponding email (S701), the email receiver extractor 215 receives the index message based on the received index data. The e-mail preparation information file stored in the read e-mail preparation information is read (S703) and the query statement included in the read e-mail preparation information is extracted (S705). In addition, the e-mail recipient extractor 215 extracts a tag from execution statements included in the body [BODY] included in the read e-mail preparation information (S707) and stores the tag in a data structure such as a hash table (S709). The data structure is created separately according to the tag type. That is, data structures are generated for each merge tag, database tag, and web tag, and each tag is stored in the corresponding data structure. Such tag extraction and data structure storage are performed for all tags included in the body [BODY] (S711).

After performing all the tags included in the body [BODY], the main body 214 analyzes the types of tags stored in each data structure and applies them to the tags contained in the body [BODY]. By activating which agent to determine the data to replace (S713). First, if a data structure for the merge tag exists, the merge agent 216 reconstructs the query statement included in the extension header [ExtHeader] (S715).

The process of reconstructing the query is as follows. In the body [BODY], data tables and fields not defined in the query statement included in the extension header [ExtHeader] may be defined. Therefore, the mail merge field is inserted into the query included in the extension header ([ExtHeader]). As described above, the merge agent 216 inserts a table and fields not defined in the extension header into the query statement and defines what relationships there are between the tables. By doing so, the basic query statement which extracts only the e-mail and name included in the extension header [[ExtHeader]) transmitted to the main body 214 is reconstructed into a query statement that can extract merge data. After that, by executing the reconstructed query statement (S717), it is possible to read the e-mail address, name and merge data of the intended e-mail recipient from the member data stored in the integrated database 260 at once.

The merge agent 216 generates a data table based on the read data as fields of the email address, name, and merge data of the email recipient of the email recipient (S719). For example, each column is a field described above, and a row is a data table created for each email recipient. Note that the order of the columns, or fields, of the generated data table corresponds to the order in which the merge tags described above are stored in the data structure. Next, the merge agent 216 sequentially extracts data for each row from the generated data table (S721), and sequentially includes a kit value corresponding to a field of the corresponding row in the body [BODY]. Substituted with and inserted (S723). If you replace and insert the kit values of all fields in one row, one email body ([BODY]) is completed. The completed e-mail body [BODY] is sent to the dispatch management unit S725 along with the remaining e-mail creation information. This operation is repeatedly performed on the generated data table (S727).

In the step S723 where the merge agent 25 described above replaces the kit value of the field and the merge tag, the operation is performed only on the merge tag. Therefore, separately, the database tag or the web tag is stored in the data structure. If there is a description as follows. First, the tag stored in the data structure is extracted (S729) to determine the type of the extracted tag (S731), and if the extracted tag is a database tag, the database agent 217 is activated and included in the corresponding database tag. The executed query statement is executed (S733) and the database content stored in the database is extracted (S735). here

%% DBAGENT: select * from psa_cust_email %%

In the case of a tag without a conditional statement, the database agent 217 replaces and inserts the same database content with the corresponding tag for all email recipients (S737).

%% DBAGENT: select * from psa_cust_email where juminno = '% $ DBOBJ: PSA_CUST_MAIL2.SSNO $%' %%

For a tag with a conditional statement (where juminno = '% $ DBOBJ: PSA_CUST_MAIL2.SSNO%'), different database contents are stored in the unified database (260) by indexing the kit value of the PSA_CUST_MAIL2.SSNO field for each email recipient. In this case, the database agent 217 extracts the database content according to the kit value and inserts the tag and the substitution in the body (S737). Therefore, the transmitting clients 103a to 103n can automatically create different e-mail contents for each e-mail recipient only with a predetermined condition without creating individual contents for each recipient. In the case of the database tag, unlike the merge tag, the database agent 217 is executed for each tag and inserted into the tag.

On the other hand, if the extracted tag is a web tag, the web agent 218 is activated and accesses a website included in the web tag (S739) and extracts web content in the corresponding website (S741). here

$$ HTTPAGENT: http: //www.yahoo.com/$$

In the case of a tag without a conditional statement, the web agent 218 replaces and inserts the same web content with the corresponding tag for all email recipients (S743).

$$ HTTPAGENT: http: //www.neocast.com/read.asp? Juminno =% $ DBOBJ: PSA_CUST_MAIL2.SSNO $% $$

For a tag with a conditional statement (read.asp? Juminno =% $ DBOBJ: PSA_CUST_MAIL2.SSNO $%), for example, different web content for each email recipient is stored in the website with the kit value of the PSA_CUST_MAIL2.SSNO field as an index As a result, the web agent 218 extracts the web content according to the kit value and inserts the tag and the substitution in the body (S743). Therefore, the transmitting clients 103a to 103n can automatically create different e-mail contents for each e-mail recipient only with a predetermined condition without creating individual contents for each recipient. In the case of the web tag, unlike the merge tag, the web agent 218 is executed for each tag and inserted into the tag.

Substitution insertion of the database tag, the web tag, and the corresponding content described above is repeatedly performed for all tags stored in the data structure (S745).

The e-mail body [BODY] generated as described above is transmitted to the shipment management unit 220 along with the remaining e-mail creation information, and the e-mail management unit 220 writes the entire e-mail body [BODY]. After inserting the syntax data (% Body%) in the content ([Content]) of the information, the e-mail is sent to the e-mail sending server 230 according to an appropriate protocol.

8 is an operation flowchart of the receiving unit 231 in the email sending server 230. The receiver 231 stores the receiver information and the e-mail content transmitted from the web server 210, and performs the grouping and sorting operations described below for high speed sending.

When the receiver 231 receives the receiver information and the email data from the web server 210 (S801), the receiver 231 determines whether the received email is a broadcast mail or an individual mail (S803). The format of the data received from the web server 210 is that, in the case of broadcast mail, the contents of the e-mails sent are the same, so that only one e-mail content may be received in the recipient e-mail address list. Recipient c@C.com; Recipient b@B.com; Recipient aaa@A.com; ...; E-mail contents ”, and in case of individual mails, since the contents of the e-mails sent are all different, the recipient e-mail address and the corresponding e-mail contents must be received. Email content, recipient c@C.com; Email content, recipient b@B.com; Email content, recipient aaa@A.com; Email content, ... '. Accordingly, the reception unit 231 can determine whether the email to be sent is a broadcast mail or an individual mail only by the format of the received data.

When the format of the received e-mail is a broadcast mail, the receiving unit 231 stores the e-mail contents in a file format in a file database, and stores recipient information in a buffer memory (S805). Recipient information stored in the buffer memory is sorted and grouped by domains of the email receiving servers 101a to 101n (S807). Subsequently, if it is possible to further store the recipient e-mail address by determining whether the recipient e-mail address is full in the buffer memory (S809), and performing the steps S805 and S807, when the recipient e-mail address is full in the buffer memory, The recipient email address stored in the buffer memory is stored in the file database 234 in the form of a file (S811), and information about the file is stored in the main index queue and indexed (S813). The index stored in the main index queue indicates the storage path of the file database 234 including the session ID identifying the session sending the email and the file ID stored in the file database 234. The index of the main index queue is used in the broadcast mail unit 232 as described later.

After step S813, the recipient e-mail address stored in the buffer memory is erased (S815), and it is determined whether all the broadcast mails to be sent are received from the web server 210 (S817). The determination of whether the reception is completed is performed by determining whether the email content is received from the data stream received from the web server 210. As described above, in the case of the broadcast mail, since only one email content is transmitted after the recipient email address list is completed, it can be determined that all the data of the broadcast mail has been received.

If all the broadcast mail data is not received, steps S805 to S815 are repeatedly performed. If all the broadcast mail data is received, the received email content is stored in the file database 234 in the form of a file (S819). ). Here, the session ID is used as storage information of the email content of the broadcast mail. In the case of the broadcast mail, since one email content is used in one session, the session ID may include the storage information of the file database 234 of the email content.

Hereinafter, the case of an individual mail will be described.

From the web server 210, 'receiver a@A.com; Email content, recipient c@C.com; Email content, recipient b@B.com; Email content, recipient aaa@A.com; If it is determined that the individual mail is to be transmitted by being received in the form of e-mail content, ... ', the receiving unit 231 stores in the file database 234 in the form of a file for each transmitted mail data (S821). Namely 'Recipient a@A.com; Email content ”,“ recipient c@C.com; Email content ”,“ recipient b@B.com; Email content ”,“ recipients aaa@A.com; 'E-mail contents' will be saved in a file format.

Subsequently, mail information is generated for each of the stored mail data (S823), and the generated mail information is stored in the buffer memory (S825). The mail information stored in the buffer indicates a storage path of the file database 234 including a session ID for identifying a session for sending an email and a file ID of mail data stored in the file database 234.

Here, unlike the broadcast mail, the number of mail information stored in the buffer memory is determined by a user's selection. For example, the mail information stored in the buffer memory may be set in advance such that 600 mail information is stored in one buffer memory. This is to shorten the time required for the individual mail unit 233 to search and read data stored in the file database 234, so that an e-mail can be sent at high speed.

As described above, by comparing the number of mail information stored in the buffer memory with a preset number N (S827), when the number of mail information stored in the buffer memory is smaller than N, steps S821 to S825 are repeatedly performed, and the buffer If the number of mail information stored in the memory is N, the mail information stored in the buffer is stored in the file database 234 in the form of a file, and the information about the file is stored and indexed in the main index queue (S831). The index stored in the main index queue is the file data including the session ID identifying the session sending the email, the folder ID identifying the file stored in the file database 234 and the range of mail information stored in the folder. The storage path of the base 234 is shown. The index of this main index queue is used in the individual mail unit 233 as described later.

After step S831, the mail information stored in the buffer memory is erased (S833), and it is determined whether all individual mails to be sent are received from the web server 210 (S835). The determination of whether the reception is completed is made by simply determining whether the transmission of data from the web server 210 is completed.

If all the individual mail data has not been received, steps S821 to S833 are repeatedly performed, and if all the individual mail data have been received, the procedure at the receiving unit 231 is terminated.

9A to 9B are flowcharts illustrating operations of the broadcast mail unit 232, the individual mail unit 233, the agent manager 235, and the agents 237a to 237n of FIG.

First, in the case of the broadcast mail, the broadcast mail unit 232 determines whether the index data exists in the main index queue (S901). If the index data exists, a space for storing the index data exists in the sub index queue. In operation S903, if space exists in the sub index queue, the index data is sequentially received through the index data stored in the main index queue (S905). The recipient email address stored in the file database 234 is read out based on the received index data (S907). In other words, the recipient email address is read by the file storage path of the index data. Here, the read recipient e-mail addresses are grouped by the domains of the e-mail receiving servers 101a to 101n, and the broadcast mail unit 232 stores and indexes these domains in the sub-index queue as index units (S909). ). Therefore, the recipient index addresses are stored in the sub index queue by domain. Based on the index data stored in the sub index queue as described below, the email sending agents 237a to 237n send an email, and after the sending is completed, the queue is deleted so that the index data is continuously present in the main index queue. The e-mail sending agent 237a to 237n performs the e-mail sending operation without interruption by constantly determining whether the sub-index queue is empty and whether the sub-index queue is empty so that the index data always exists in the sub-index queue. It will be able to ship in bulk.

As described above, the agent manager 235 determines whether there is an email sending agent in an idle state among the plurality of email sending agents 237a to 237n whenever index data exists in the sub-index queue (S911) (S913). If there are idle e-mail sending agents 237a to 237n, e-mail contents stored in the file database 234 are read out based on the message ID extracted from the index data read from the main index queue (S915). ), The read email content is combined with the recipient email address stored in the sub index queue (S917). Then, by activating the idle email sending agent (S919), the email sending agent connects to the email receiving server based on the recipient email address stored in the sub index queue (S921) and transmits the email (S923).

Here, the recipient email addresses in the index data stored in the sub index queue are grouped by the domains of the email receiving servers 101a through 101n, and the email sending agents 237a through 237n are activated for each index data to send emails. Therefore, the e-mail receiving servers 101a to 101n are connected only once and all the e-mails existing in one index data are sent out. Therefore, the e-mail can be sent at a high speed by significantly reducing the access time to the receiving server.

In addition, the agent manager 235 manages the plurality of email sending agents 237a to 237n. Whenever the index data exists in the sub index queue, the agent manager 235 activates the email sending agents 237a to 237n in the idle state for each index data. When the email sending agent 237a to 237n completes an email sending task for a particular index data, another index data is provided as long as there is other index data than the index data currently being processed by another email sending agent. Dynamic processing that can perform email sending for data is possible, and in this way, multiple email sending agents 237a to 237n perform email sending for each index data, thereby implementing load balancing according to parallel processing. To send email quickly Will be.

Hereinafter, the case of an individual mail will be described.

In the case of individual mails, the individual mail unit 233 determines whether index data exists in the main index queue (S901), and if there is index data, determines whether there is space for storing index data in the sub index queue (S903). When space exists in the sub index queue, the index data is sequentially received through the index data stored in the main index queue (S905). The mail information stored in the file database 234 is read out based on the received index data (S907). That is, the mail information is read by accessing the file in which the mail information is stored based on the session ID and the folder ID of the index data. The read mail information indicates a storage path of the file database 234 including a session ID for identifying a session for sending an email and a file ID of mail data stored in the file database 234. In operation 909, the mail information is stored in the sub index queue of the individual mail unit 233 in the unit of index and indexed (S909). That is, unlike in the case of the broadcast mail, one piece of mail information is included in the index data stored in the sub index queue. Based on the index data stored in the sub-index queue, the e-mail sending agents 273a to 237n send an e-mail as described below, and after the sending is completed, the queue is deleted so that the index data is continuously present in the main index queue. The e-mail sending agent 273a to 237n performs the e-mail sending operation without interruption by constantly determining whether the sub-index queue is empty and whether the sub-index queue is empty so that the index data always exists in the sub-index queue. It will be able to ship in bulk.

As described above, the agent manager 235 determines whether there is an email sending agent in an idle state among the plurality of email sending agents 273a to 237n whenever index data exists in the sub-index queue (S911) (S913). If there is an idle email sending agent, mail data stored in the file database 234 is read based on the file storage path of the mail data extracted from the index data read from the sub-index queue (S915). . However, since the mail data file stored in the file database 234 includes the recipient email address and the email content in the case of individual mails, unlike the case of the broadcast mail, the recipient email address is combined with the email content (S917). Is not necessary. Then, by activating the idle email sending agent (S919), the email sending agents 273a to 237n connect to the email receiving server based on the recipient email address in the mail data received from the agent manager 235 (S921), The e-mail is transmitted (S923).

Here, the agent manager 235 manages a plurality of email sending agents 273a to 237n, and whenever an index data exists in a sub-index queue, an agent sends an email by activating an idle email sending agent for each index data. When the email sending agent 273a to 237n completes an email sending task for a particular index data, the email sending agent is immediately sent to the other index data as long as there is index data other than the index data currently being processed by another email sending agent. Dynamic processing to perform the operation is possible, and in this way, a plurality of email sending agents (273a to 237n) are sent to each email data for each index data, so that load balancing based on parallel processing can be implemented to deliver email at high speed. Being able to ship The.

Hereinafter, a mass email sending process in the remote email sending server 330 will be described.

As described above, the remote email sending server 330 performs data communication with the email sending server 230 to determine whether there is index data stored in the main index queue of the receiving unit 231 in the email sending server 230. (S901), it is determined whether there is space for storing index data in the sub-index queues of the remote broadcasting mail unit 332 and the remote individual mail unit 333 (S903), and receives the index data from the main index queue ( S905), the indexing operation according to the broadcast mail and the individual mail as described above is stored in each sub-index queue (S909).

In addition, the agent manager 335 and the email sending agents 337a to 337n in the remote email sending server 330 are the agent manager 235 and the email sending agent 237a to 237n of the email sending server 230 described above. Will perform the same operation as The content data of the broadcast mail and the mail data of the individual mail are read from the file database 234 by the file transfer unit 236 and received. Then, by activating the idle email sending agents 337a to 337n (S919), the email sending agents 337a to 337n access the email receiving server based on the recipient email address stored in the sub index queue (S921). In step S923, the e-mail is transmitted.

Furthermore, by creating a main index queue in the receiving unit 231 and connecting the remote email sending server 330 to the email sending server 230, the broadcast mailing unit 232 and the individual mailing unit of the email sending server 230 ( The e-mail sending server 230 allows the remote broadcasting mail unit 332 and the remote individual mail unit 333 to process the queue stored in the main index queue without processing the system while the process 233 is in progress. ) Dynamically load-balances the email sending processing process, which is incurred by), so that a large amount of email can be processed and sent at high speed. That is, the plurality of email sending agents 237a to 237n in the email sending server 230 speeds up the email sending processing by dynamically paralleling the load on the email sending that one machine needs to process. The plurality of remote e-mail sending servers 330 connected to 230 may speed up the e-mail sending process by dynamically paralleling the load for data processing for sending the e-mail.

10A to 10C are diagrams illustrating screens in which result data received from the reporting agent 240 and the monitoring agent 250 is displayed on the transmitting clients 103a to 103n, wherein the reporting agent 240 is an email sending agent 235. , 335) information about the e-mails that failed to be sent and sent and information about the reason for the failure, such as the total number of e-mails to be sent, the number of e-mails that sent successfully, and the list of e-mails that failed to send, The reason for the failure is that the recipient e-mail address is no longer valid, or the e-mail sending failure reason such as the e-mail receiving servers 101a to 101n does not respond, is recorded, displayed on the sending clients 103a to 103n, and monitored. Agent 250 informs the sending clients 103a to 103n of the transmission status of the email currently being sent. This makes it easier to analyze sender's e-mail sending result and customer management by managing the report, and to manage marketing information that is no longer valid among member's recipient data as sender, as well as to establish marketing strategy more efficiently. .

Fig. 10A shows the progress of the session when the sending client completes the e-mail creation and requests the mass e-mail sending agent system 100 to send, and then selects the "Send Management" menu 505 in Fig. 5A. This is the figure that is displayed. The "Shipping Management" window is displayed with the scheduler 523 in the upper right corner and the details in the center of the screen. The details of the e-mail currently being sent are displayed in the details, and the 'number' and 'reservation status' 'title' 'sending time' 'appropriate group' A menu called 'Shipping Status' and 'Delete' is located at the top of the screen, 'Shipping Time' indicates the time at which the sending is started, and 'Shipping Status' indicates whether it is currently being sent or finished. If the shipment has been completed, the "Complete Shipment" indication is displayed in the "Shipping Status". When the transmitting client 103a to 103n transmits a signal requesting the display of the result report relating to the dispatch, it is switched to the "delivery result report" screen in FIG. 10B.

As shown in FIG. 10B, the [Send Result Report] screen displays 'Mail Title', 'Send Start Time', 'Send End Time', 'Total Sends', 'Send Mails', and 'Total Send Mails'. The results so far are displayed in the center. As shown in FIG. 10B, 'successful delivery' indicates a successful number of e-mails requested by the sender, and 'Network Error' indicates that a sending error occurs due to network problems (system load / network bottleneck, etc.) when sending an e-mail. Represents a generated number, and 'Domain Error' indicates a case in which the recipient email server names 101a to 101n have a wrong or missing recipient email server name. For example, you should write '****@hanmail.net' incorrectly as '****@hanmail.com' or '****@yy.cc.kr'. This could be the case with the recipient's email server name. 'Unknown User' indicates when the recipient ID does not exist in the corresponding recipient email server 101a through 101n. If the recipient is 'qwer@hanmail.net', the recipient email server named 'hanmail.net' qwer 'means that the account does not exist or the account is written incorrectly. Also, 'Syntax Error' indicates an email address grammar error, and the format of server domain name such as '*** @ dsfsf' or '******. Co.kr' is not correct or '@' This is the part that displays an error that occurs when the sender creates an e-mail address that does not conform to the e-mail address grammar, such as when the recipient's e-mail address is entered without the information. On the other hand, when the transmitting client 103a to 103n transmits a signal requesting a result report to a file such as a spreadsheet, the system 100 transmits a signal to the transmitting client 103a to 103n to the corresponding file (for example, Microsoft Corporation). Excel file). In this figure, by selecting an icon representing an Excel file on the left side, the sending clients 103a to 103n download the result report files. If the system 100 is sending an e-mail, the message 'Sending mail' is displayed. If the message is completed, the message 'Send is completed' is displayed. If the mail is being sent, the monitoring agent 250 displays the current sending progress. It monitors at predetermined intervals, and transmits and displays them to the transmitting clients 103a to 103n. At the top right of this screen, there are detailed menus of [Receipt Confirmation], [Send Result by E-mail] and [Email List by Result]. [Receipt Confirmation] is a menu to stop the system of mass mails to be. In addition, [Email Result for Each E-mail] is a menu of a function for displaying the e-mail sending result for each e-mail in the group, as shown in FIG. 10C. For example, in the sending client 103a to 103n, select the [Send Result by E-mail] menu, and among the recipients to send, A@castmail.com, B@castmail.com, C@castmail.com, and D @ castmail. If the mail addresses are .com and E@castmail.com, then each of these five mail addresses will be displayed as to whether the sending was successful or failed.

[E-mail List for Each Result] is a screen in which each e-mail list is reprocessed and displayed according to the success of sending, failure to send, and the cause of failure.

11 is a view showing an account management menu screen, the "account management" menu 511 can be used only by corporate members according to the administrator selection of the system 100, the first applicant (hereinafter 'administrator' This is the menu used when creating a new account for this person when another person in charge of sending mail as a member of the company, not '). First, select the 'Add Account' detailed menu included in the screen displayed by selecting the 'Account Management' menu (511), and then select 'User Name' 'Login ID' 'Login PWD' 'Email Address'' Department Name '' If you define a restriction such as "Send Limit" (total number of times per month) and select the Register button, a new account is created. In the detailed menu of `` All Shipment History '', the administrator can check the details of how many times the mail sender actually sent the mail and which address book was created.

As described above, the implementation methods proposed to achieve the desired purpose in the present invention may be written in a program that can be executed in various types of devices having a microprocessor, and may be stored in various types of recording media. In this case, the recording medium may be a memory device such as a ROM or a RAM, a magnetic storage medium such as a floppy disk or a hard disk, or an optical recording medium such as an optical recording medium such as a CD-ROM or a DVD. It includes.

In addition, the present invention is not limited by the above-described embodiment and the accompanying drawings, the above-described embodiments and the accompanying drawings are merely provided to assist in understanding the technical idea of the present invention, and the technical spirit of the present invention It is apparent to those skilled in the art that various substitutions, modifications, and changes can be made without departing from the scope of the present invention.

As described above, according to the present invention, a plurality of email sending agents dynamically parallel email processing according to the processed data while simultaneously processing a large amount of email as data suitable for parallel processing according to broadcast mail and individual mail. Many email sending clients can share a large email delivery system that performs parallel processing with load balancing by allowing large amounts of email to be sent at high speed, as well as allowing for parallel installation without stopping the system. As a result, even an individual or a company that does not have a device for exclusive use of a large amount of e-mails has an effect of processing an e-mail transmission task in real time when a large amount of e-mail sending tasks are desired.

In addition, the present invention is a large-capacity email transmission system for sending a large amount of email at high speed while a large number of clients (corporate or individual) is shared, each client computer (PC) through the account (ID, password) assigned to each of the above By accessing a large-scale e-mail transmission system, users can set their own sending target groups and contents, so that they can carry out a large amount of e-mail sending tasks without establishing a separate e-mail sending infrastructure. In addition, in the present invention, by using a specific message of the SMTP protocol as described above, the present invention monitors transmission error conditions occurring in various forms and analyzes and provides a cause thereof. Thereby, each email Queries such as sending clients their incoming and outgoing email by returning the state to take countermeasures according to the cause has excellent effects that allow you to take advantage of such useful marketing.

Claims (74)

In the web application service method that allows a plurality of email sending clients to send a large amount of email to a large number of recipients over a network while sharing a large email sending system, respectively, A first step of performing logon processing as at least one sending client accesses through the network; A second step of generating e-mail composition information data according to selection of the logged-on sending client; A third step of performing a billing calculation to be processed based on a service type for the logged-on sending client and determining whether payment processing is successful; A fourth step of generating a mass e-mail based on the e-mail preparation information data of the second step if the charging process of the third step is confirmed; And A fifth step of sending the mass email generated in the fourth step and monitoring the sending status; Web application service method that allows a plurality of clients including a large number of email transmissions while sharing a large email transmission system. The method of claim 1, The second step is Uploading email recipient data from the logged on sending client to a database of the mass email sending system; A second step of generating an email body including a tag; Generating a query to extract an email address of a recipient from among email recipient data stored in the database; And Step 4 of setting up a schedule for sending email Web application service method that allows a plurality of clients including a large number of email transmission while sharing a large email transmission system. The method of claim 2, The tag of the second process is It is a merge tag including a query statement for extracting data related to a recipient from among email recipient data stored in the database. How to make web application service available. The method of claim 2, The tag of the second process is It is a database tag including a query statement for extracting data related to a recipient from among the email template data stored in the database. Web application service method that enables it. The method of claim 2, The tag of the second process is A web application service method that enables a large number of clients to send a large amount of email while sharing a large amount of email transmission systems, characterized in that it is a web tag including a URL (Uniform Resource Locator) of a web page related to a recipient. The method of claim 2, The query statement of the third step is Web application that allows a large number of clients to send a large amount of email while sharing a large amount of email transmission system, characterized in that the query statement composed of a condition for extracting a predetermined recipient from the email recipient data stored in the database Service method. The method of claim 2, The fourth process is A web application service method that enables a large number of clients to send a large amount of email while sharing a mass email sending system, characterized by generating data regarding email sending time, sending frequency, and sending priority. The method according to any one of claims 1 to 7, The fourth step, A first step of receiving the email composition information data; A second process of automatically generating an email content by replacing a tag included in the email preparation information data with data; Web application service method that allows a plurality of clients including a large number of email transmission while sharing a large email transmission system. The method of claim 8, A third step of storing the received email creation information data in a database; A fourth step of generating index data for the stored email preparation information data; And A fifth step of determining an order of sending an e-mail based on the e-mail creation information data and storing index data in a queue for each order A web application service method for allowing a plurality of clients including a further comprising a large number of email transmission system and a large amount of email transmission. The method of claim 8, Step 6 of displaying the result of automatic generation of email contents on the logged on sending client A web application service method for allowing a plurality of clients including a further comprising a large number of email transmission system and a large amount of email transmission. The method of claim 9 or 10, The second process is A seventh step of reading e-mail preparation information data stored in a database based on the index data read from the queue of the fifth step; An eighth step of extracting a query statement for extracting email recipient data from the read email creation information data; A ninth step of extracting a tag included in the read email preparation information data and storing the tag in the data structure; A tenth step of editing the query statement according to the merge tag when the tag of the ninth step is a merge tag; An eleventh step of generating a data table by executing a query on the database according to the query statement; And Step 12 of generating e-mail content by substituting data corresponding to the tag of step 9 Web application service method that allows a plurality of clients including a large number of email transmission while sharing a large email transmission system. The method of claim 11, The twelfth process Web application service method that allows a large number of clients to send a large amount of email while sharing a mass email transmission system, characterized in that for replacing the field value of the merge tag and the data table corresponding to the merge tag stored in the ninth step . The method of claim 12, If the tag stored in the ninth step is not a merge tag The twelfth process A thirteenth step of reading corresponding data based on the tag of the ninth step; And Step 14 of generating an email content by replacing the tag of step 9 with the data of step 13 A web application service method for allowing a plurality of clients including a further comprising a large number of email transmission system and a large amount of email transmission. The method of claim 13, The tag is a database tag, The thirteenth process is A web application service method for allowing a large number of clients to share a large amount of e-mail transmission systems while reading a content data stored in a database. The method of claim 14, And the content data is different for each e-mail recipient, and a plurality of clients can share a mass e-mail transmission system while allowing a large amount of e-mail transmission. The method of claim 13, The tag is a web tag, The thirteenth process is A web application service method for allowing a plurality of clients to access a web page and to read a web content, and to send a large amount of email while sharing a large email transmission system. The method of claim 16, The web content is a web application service method that allows a plurality of clients, characterized in that different for each email recipient to share a large amount of email transmission system while sending a large amount of email. The method according to any one of claims 12 to 17, The data table is And a field for at least a recipient email address, wherein a plurality of clients share a large email transmission system while enabling a mass email transmission. The method of claim 18, The second process is Step 15 of including e-mail header information in the e-mail content is further performed. A web application service method for allowing a plurality of clients to share a large amount of email transmission system and to send a large amount of email, further comprising a. The method of claim 19, The fifth step is A first step of indexing the mass email generated in the fourth step into recipient information; A second step of storing the mass email generated in the fourth step; And A third step of dynamically paralleling and sending the stored emails based on the indexed recipient information by at least one email sending agent Web application service method that allows a plurality of clients to a large amount of email transmission while sharing a large number of email transmission system comprising a. The method of claim 20, The first process A fourth step of grouping the recipient information by domain of the email receiving server; A fifth step of storing the grouped recipient information in a predetermined unit; A sixth step of storing the stored receiver information of the predetermined unit as one index unit in a main index queue; A seventh step of reading the stored receiver information based on the index stored in the main index queue; And An eighth process of storing the read recipient information in a sub-index queue using the domain of the grouped email receiving server as an index unit Web application service method that allows a plurality of clients to a large amount of email transmission while sharing a large number of email transmission system comprising a. The method of claim 20, The first process A ninth step of storing the receiver information in a predetermined number unit; A tenth step of storing the stored predetermined number of receiver information as one index unit in a main index queue; An eleventh step of reading the stored receiver information based on an index stored in the main index queue; And Step 12 of storing the read receiver information in an index unit and storing in the sub index queue Web application service method that allows a plurality of clients to a large amount of email transmission while sharing a large number of email transmission system comprising a. The method of claim 21 or 22, The first process Determining whether an index exists in the main index queue; And Determining whether the stored receiver information can be stored in the sub index queue when an index exists in the main index queue. A web application service method for allowing a plurality of clients to share a large amount of email transmission system and to send a large amount of email, further comprising a. The method of claim 21 or 22, The third process is A fifteenth step of activating an idle email sending agent among the at least one email sending agent; A sixteenth step of reading the stored email based on the index stored in the sub index queue for each activated email sending agent; A seventeenth step of accessing the e-mail receiving server and sending the read e-mail; And 18th process of repeating 15th to 17th process Web application service method that allows a plurality of clients to a large amount of email transmission while sharing a large number of email transmission system comprising a. The method of claim 24, The third process is 19th step of determining whether an index exists in the sub-index queue A web application service method for allowing a plurality of clients to share a large amount of email transmission system and to send a large amount of email, further comprising a. The method of claim 20, And the email is stored in a file system. The web application service method of the present invention enables a plurality of clients to share a large amount of email transmission systems and to send a large amount of emails. The method of claim 21, The predetermined unit is determined in consideration of the capacity of the buffer memory, The recipient information is temporarily stored in the buffer memory until the predetermined unit, and then stored in the file system. Service method. The method of claim 22, The recipient information is temporarily stored in the buffer memory until the predetermined number is stored in the file system, characterized in that the web application to enable a large number of email transmission while a large number of clients share a large email transmission system Service method. The method according to any one of claims 26 to 28, The recipient information is A web application service method for allowing a large number of clients to send a large amount of email while sharing a large email sending system, comprising a recipient's email address. The method according to any one of claims 26 to 28, The recipient information is And a storage path in the file system of the e-mail data stored in the file system. The method of claim 29, The index stored in the main index queue is And a storage path of the recipient information in the file system and identification information of the e-mail data. A plurality of clients can share a mass e-mail transmission system while allowing a mass e-mail transmission. The method of claim 30, The index stored in the main index queue is And a storage path in the file system of the recipient information, wherein a plurality of clients share a large email transmission system while allowing a large amount of email transmission. The method of claim 27 or 28, And at least one buffer memory, wherein a plurality of clients share a large volume of email transmission systems while allowing a large volume of emails to be transmitted. The method of claim 24, And a 20 th step of displaying the result of the e-mail sending after the 17 th step of the plurality of clients. The method according to any one of claims 1 to 7, and 34, Sixth step to create and database email sending result data Web application service method that allows a plurality of clients further comprising a large number of email transmission system while sharing a large number of email transmission. The method according to any one of claims 1 to 7, In the fifth step, the sending status monitoring is performed by using a specific message of the Simple Mail Transfer Protocol (SMTP) to recognize a transmission error state and analyze the cause thereof. Web application service method that allows to send a large amount of email while sending. The method according to any one of claims 1 to 7, The third step of billing processing and payment calculation is processed for each client according to individual / company classification, service type, billing condition, and set payment method. Web application service method that enables the sending of email. In a large email sending system that allows multiple email sending clients to send large amounts of email to multiple recipients over a network, A memory in which a mass e-mail transmission program is stored; An email sending means coupled to said memory and having a processor for executing said mass email sending program, The processor is configured by the mass email sending program. A first step of performing logon processing as at least one sending client accesses through the network; A second step of generating e-mail composition information data according to selection of the logged-on sending client; A third step of performing a billing calculation to be processed based on a service type for the logged-on sending client and determining whether payment processing is successful; A fourth step of generating a mass e-mail based on the e-mail preparation information data of the second step if the charging process of the third step is confirmed; And A fifth step of sending the mass email generated in the fourth step and monitoring the sending status; Massive email transmission system, characterized in that for executing. The method of claim 38, The second step is Uploading email recipient data from the logged on sending client to a database of the mass email sending system; A second step of generating an email body including a tag; Generating a query to extract an email address of a recipient from among email recipient data stored in the database; And Step 4 of setting up a schedule for sending email Massive email sending system comprising a. The method of claim 39, The tag of the second process is And a merge tag including a query statement for extracting data related to a recipient from among email recipient data stored in the database. The method of claim 39, The tag of the second process is And a database tag including a query statement for extracting data related to a recipient from among email template data stored in the database. The method of claim 39, The tag of the second process is And a web tag including a Uniform Resource Locator (URL) of a web page related to a recipient. The method of claim 39, The query statement of the third step is And a query statement composed of conditions for extracting a predetermined recipient from among email recipient data stored in the database. The method of claim 39, The fourth process is A mass email sending system, characterized by generating data regarding email sending time, sending frequency, and sending priority. The method according to any one of claims 38 to 44, The fourth step, A first step of receiving the email composition information data; A second process of automatically generating an email content by replacing a tag included in the email preparation information data with data; Massive email sending system comprising a. The method of claim 45, A third step of storing the received email creation information data in a database; A fourth step of generating index data for the stored email preparation information data; And A fifth step of determining an order of sending an e-mail based on the e-mail creation information data and storing index data in a queue for each order Larger email sending system comprising more. The method of claim 45, Step 6 of displaying the result of automatic generation of email contents on the logged on sending client Larger email sending system comprising more. 48. The method of claim 46 or 47, The second process is A seventh step of reading e-mail preparation information data stored in a database based on the index data read from the queue of the fifth step; An eighth step of extracting a query statement for extracting email recipient data from the read email creation information data; A ninth step of extracting a tag included in the read email preparation information data and storing the tag in the data structure; A tenth step of editing the query statement according to the merge tag when the tag of the ninth step is a merge tag; An eleventh step of generating a data table by executing a query on the database according to the query statement; And Step 12 of generating e-mail content by substituting data corresponding to the tag of step 9 Massive email sending system comprising a. The method of claim 48, The twelfth process And a field value of a merge tag and a data table corresponding to the merge tag stored in the ninth step. The method of claim 49, If the tag stored in the ninth step is not a merge tag The twelfth process A thirteenth step of reading corresponding data based on the tag of the ninth step; And Step 14 of generating an email content by replacing the tag of step 9 with the data of step 13 Larger email sending system comprising more. 51. The method of claim 50, The tag is a database tag, The thirteenth process is A large capacity email transmission system characterized in that the content data stored in the database is read. The method of claim 51, And the content data is different for each email recipient. 51. The method of claim 50, The tag is a web tag, The thirteenth process is A large capacity email transmission system, characterized in that for reading the web content by accessing the web page. The method of claim 53, And the web content is different for each email recipient. The method of any one of claims 49-54, The data table is And a field for at least the recipient email address. The method of claim 55, The second process is Step 15 of including e-mail header information in the e-mail content is further performed. Massive email transmission system, characterized in that it further comprises. The method of claim 56, wherein The fifth step is A first step of indexing the mass email generated in the fourth step into recipient information; A second step of storing the mass email generated in the fourth step; And A third step of dynamically paralleling and sending the stored emails based on the indexed recipient information by at least one email sending agent Massive email transmission system comprising a. The method of claim 57, The first process A fourth step of grouping the recipient information by domain of the email receiving server; A fifth step of storing the grouped recipient information in a predetermined unit; A sixth step of storing the stored receiver information of the predetermined unit as one index unit in a main index queue; A seventh step of reading the stored receiver information based on the index stored in the main index queue; And An eighth process of storing the read recipient information in a sub-index queue using the domain of the grouped email receiving server as an index unit Massive email transmission system comprising a. The method of claim 57, The first process A ninth step of storing the receiver information in a predetermined number unit; A tenth step of storing the stored predetermined number of receiver information as one index unit in a main index queue; An eleventh step of reading the stored receiver information based on an index stored in the main index queue; And Step 12 of storing the read receiver information in an index unit and storing in the sub index queue Massive email transmission system comprising a. The method of claim 58 or 59, The first process Determining whether an index exists in the main index queue; And Determining whether the stored receiver information can be stored in the sub index queue when an index exists in the main index queue. Massive email transmission system, characterized in that it further comprises. The method of claim 58 or 59, The third process is A fifteenth step of activating an idle email sending agent among the at least one email sending agent; A sixteenth step of reading the stored email based on the index stored in the sub index queue for each activated email sending agent; A seventeenth step of accessing the e-mail receiving server and sending the read e-mail; And 18th process of repeating 15th to 17th process Massive email transmission system comprising a. 62. The method of claim 61, The third process is 19th step of determining whether an index exists in the sub-index queue Massive email transmission system, characterized in that it further comprises. The method of claim 57, And the email is stored in a file system. The method of claim 58, The predetermined unit is determined in consideration of the capacity of the buffer memory, And the recipient information is temporarily stored in the buffer memory until the predetermined unit is stored in the file system. The method of claim 59, And the recipient information is temporarily stored in a buffer memory until the predetermined number is stored in the file system. The method of any one of claims 63-65, The recipient information is A mass email sending system, comprising an email address of a recipient. The method of any one of claims 63-65, The recipient information is And a storage path in a file system of e-mail data stored in the file system. The method of claim 66, The index stored in the main index queue is And a storage path in said file system of said recipient information and identification information of said e-mail data. The method of claim 67, The index stored in the main index queue is And a storage path of said recipient information in said file system. 66. The method of claim 64 or 65, And at least one buffer memory. 65. The method of claim 64, And a twentieth step of displaying an e-mail sending result after the seventeenth step. The method of any one of claims 38 to 44 and 71, Sixth step to create and database email sending result data Massive email transmission system further comprising. The method according to any one of claims 38 to 44, The sending status monitoring in the fifth step is a large-capacity email transmission system, characterized in that it recognizes the transmission error status occurred using a specific message of the Simple Mail Transfer Protocol (SMTP) and analyzes the cause. The method according to any one of claims 38 to 44, The third-party billing processing and payment calculation is a large-scale email transmission system, characterized in that for each client, according to the individual / company classification, service type, billing conditions, and the set payment method.