KR100614866B1 - System and Method for Determining Possibility of Mail Receipt Before Sending Mail - Google Patents

Abstract

The present invention relates to a system and method for determining a reception possible state before sending a mail. The present invention relates to a mail writing page having an interface for requesting a user input as a recipient to check whether a mail can be received. It is provided to the sender, and when the mail sender requests a reception check, it determines whether the entered recipient is a registered user or a dormant account user, and calculates the capacity information of the mail to be sent, and the remaining mail capacity of the input recipient. It is determined whether the mail to be sent can be received by comparing with the information. According to the present invention, it is possible to provide a reliable e-mail service by allowing a mail sender to determine whether a user inputted as a recipient can receive a mail before sending the mail.

Mail, confirm, send, receive

Description

System and Method for Determining Possibility of Mail Receipt Before Sending Mail}             

1 is a diagram showing the configuration of a system for determining a reception possible state before sending a mail according to an embodiment of the present invention.

2 is a diagram illustrating a system configuration for checking whether reception is possible before sending a mail according to another embodiment of the present invention.

3 to 6 illustrate an example of a mail writing page and a message displayed when a receiver cannot receive a message according to an exemplary embodiment of the present invention.

7 is a block diagram showing a detailed configuration of a mail web server according to an embodiment of the present invention.

8 illustrates user data fields managed by an account server according to an embodiment of the present invention.

9 is a flowchart illustrating a process of checking whether a receiver exists and whether a user is a dormant account according to an embodiment of the present invention.

10 is a flowchart illustrating a method for providing remaining mail capacity information of an input recipient according to an exemplary embodiment of the present invention.

FIG. 11 is a flowchart illustrating a method for providing a user with information on whether or not reception is possible by comparing a capacity of a mail to be transmitted with a remaining mail capacity of an input recipient according to an exemplary embodiment of the present invention.

The present invention relates to a mail system and a mail service providing method, and more particularly, to a mail system and a mail service providing method capable of determining whether a recipient can receive mail.

The e-mail service is one of the most used Internet services by users, and is one of services that can quickly deliver text and files to other users.

In such an e-mail service, mail is delivered to the recipient based on the recipient's mail address information. Since the mail address information is a complex combination of alphabets and numbers, a typo occurs frequently when the mail address is entered. This often happens.

In addition, in the case of a webmail service, it is common to provide a limited mail space to a user, and mail transmission fails when a sender transmits mail data exceeding a mail space of a specific user.

Furthermore, most users have multiple webmail accounts, most of which are dormant except for some. When a sender sends mail to such a dormant account, the receiver often fails to check the mail sent for a long time or cannot check the mail sent.

As described above, due to a typo, limited capacity, and dormant account problems in writing an e-mail address, e-mail has been difficult to use as a reliable communication service.

In order to solve this problem, a method of providing information on whether or not the recipient checks the mail after the mail has been used has been used. However, this method is a hassle that the mail sender must continuously check whether the mail recipient has read the mail. There was a feeling.

In order to solve the problems of the prior art as described above, the present invention provides a mail system and a mail service method capable of determining whether a user inputted as a recipient can receive mail before the mail sender sends the mail. I would like to suggest.

Another object of the present invention is to propose a mail system and a mail service method capable of checking whether a user input as a recipient is a registered user and a dormant accounting user before sending mail.

It is still another object of the present invention to propose a mail system and a mail service method capable of determining whether a receiver is in a state of being able to be received by checking the amount of mail to be transmitted and the amount of mail remaining by a user input as a recipient.

In order to achieve the above object, according to an aspect of the present invention, an account server for managing user information, including user identification information including a user ID, log information of the user, mail capacity information given to the user; A mail writing page having an interface button for requesting a check of whether a recipient can receive mail before sending mail to a user client is provided, and the mail writing page entered as a recipient on a mail writing page through communication with the account server. A mail web server for determining whether the user is a registered user and a dormant account user; Receives mail data from the mail web server, determines whether the received mail data is mail data to be stored in its own mailbox or mail data to be sent to an external mail server, and sends the received mail data to an external mail server. Or a mail server for storing in a mailbox, wherein the mail web server reads folder information of the mailbox, checks the remaining mail capacity of the user entered as a recipient on the mail writing page, and checks the user registration information and dormancy. Provided is a mail system capable of checking whether a user inputted as a recipient can receive a mail by using the user information of the account and the remaining mail capacity information before sending the mail.

According to another aspect of the invention, the client communication unit for receiving the webmail-related request information from the user client, and transmits the webmail-related data requested by the user to the user client; A control unit controlling the overall operation to execute a predetermined process according to the webmail related request information of the user client; Edit the web page requested from the user client under the control of the controller, edit the mail writing page including an interface button for requesting a check of whether the recipient can receive the mail before sending the mail. Web page editing unit provided to; A user information checker for determining whether the input recipient is a registered user and a dormant account user when the user requests a reception check before sending the mail; When the user requests the reception check before sending the mail, the folder information of the input recipient is read from the mailbox to determine the mail space usage capacity of the input recipient, and the mail capacity information and the input given to the input recipient are determined. A mail capacity checker which calculates the remaining mail capacity of the input receiver using the mail space usage information of the received recipient; A MIME generation unit for converting mail data transmitted from the user client into mail data in a MIME format; And a mail server communication unit which transmits the mail data of the MIME format to the mail server.

According to still another aspect of the present invention, there is provided a method of providing a mail writing page including an interface button for requesting a user client to check whether a recipient can receive mail before sending the mail; (B) determining whether the received mail receiver is a registered user and a dormant account user when the user receives a request to receive a check before sending the mail; (C) determining a mail space usage capacity of the input receiver by reading folder information in the input receiver's mailbox when a user receives a request to receive a mail before sending the mail; Checking the amount of mail given to the input recipient and calculating a remaining amount of mail of the input recipient; And (e) determining whether the received recipient is able to receive mail using the user registration information, the dormant account user information, and the remaining mail capacity information. Is provided.

Hereinafter, with reference to the accompanying drawings will be described in detail a preferred embodiment of the system and method for determining the reception possible state before the mail transmission according to the present invention.

1 is a diagram showing the configuration of a system for determining a reception possible state before sending a mail according to an embodiment of the present invention.

Referring to FIG. 1, according to a preferred embodiment of the present invention, a mail system for determining a reception possible state before sending mail includes a mail web server 102, a mail account server 104, a mail server 106, and a mail box ( 108). Although FIG. 1 shows a mail box provided separately from a mail server, it will be apparent to those skilled in the art that a mail box may be provided in the mail server.

The user client 100 is connected to the mail system according to the present invention through a network. The network may include a wired network such as an internet network or a private network, as well as a wireless network such as a wireless internet network and a mobile communication network.

The user client 100 may include all terminals capable of communicating digital data processing through a network such as a general PC, laptop, mobile communication terminal, PDA, and the like.

The user client 100 is provided with a mail user agent (MUA) for communication with a mail system. MUA is a client program used by a user to send and receive e-mail. MUAs can include Microsoft's Outlook Express, Netscape's Netscape, and Unix-like / usr / ucb / mail. The present invention mainly applies to webmail, in which case the web browser plays the role of MUA. However, since the web browser alone cannot perform the MIME format generation and the SMTP protocol communication for the communication with the mail server 106, the web browser and the mail web server 102 together serve as MUAs.

The mail web server 102 transmits a web page related to mail to the user client 100 so that the user can use the webmail service, and communicates with the mail server 104 when the user requests to send or view the mail. Process the user's request information.

The mail web server 102 of the present invention provides the user client 100 with a mail writing page including an interface button that allows the user to check whether the mail recipient is in a state capable of receiving mail before sending the mail.

The web browser, which is the MUA of the user client 100, displays the mail writing page provided by the mail web server, and receives check request information on whether mail can be received from the user.

3 is a diagram illustrating an example of a mail writing page including an interface button for checking whether a mail receiver is in a state capable of receiving mail according to an exemplary embodiment of the present invention.

Referring to FIG. 3, a button for checking whether a mail receiver is in a state capable of receiving mail may be provided next to an item for inputting the receiver. The sender inputs the mail address of the mail receiver in the receiver input item and clicks the check button to check whether the receiver corresponding to the mail address entered in the receiver item can receive the mail.

The receivable check request information is transmitted to the mail web server 102, and the mail web server 102 determines whether or not the recipient can receive the mail.

According to an embodiment of the present invention, the mail web server 102 determines whether the mail address entered in the recipient input item is a mail address and whether the recipient corresponding to the mail address is a dormant account user.

In addition, the mail web server 102 determines the remaining capacity information of the mail recipient corresponding to the input mail address and provides the information to the user client 100 so that the mail sender adjusts the capacity of the sent mail so that the recipient receives the mail. To be received.

Furthermore, the mail web server 102 may check the capacity of the mail to be sent and the remaining mail capacity information of the mail receiver, and provide information on whether the receiver can receive the mail to be sent.

The account server 104 manages the information of the user and, when requested for information about the user, serves to provide the information. The account server 104 may be a mail account server that manages only information on a mail user, or may be an integrated account server 104 that manages all user information such as mail, communities, and blogs in a portal site.

When the mail web server 102 receives the mail reception check request information from the user client 100, the mail server 102 determines whether the receiver corresponding to the input mail address exists or is a dormant account user. Request information about the recipient at 104.

When the account server 104 receives the user information from the mail web server 102, the account server 104 determines whether the mail address input in the recipient field is an existing mail address. In the case of an existing mail address, the account server 104 checks the last login time information of the user using the log information of the user corresponding to the mail address.

According to an embodiment of the present invention, the account server 104 determines that the user is a dormant account user when the last login time information of the user is earlier than the preset time. That is, if the time for determining whether the account is dormant is one month, and the user's last login time is one month before, the user is determined to be the dormant account user. The account server 104 provides the mail web server 102 with judgment information on whether or not it is a dormant account user.

According to another embodiment of the present invention, the account server 104 transmits only the last login time information of the user to the mail web server 102, and the determination as to whether the user is a dormant account user is performed in the mail web server 102. It may be.

When the mail web server is confirmed whether the user is an existing user and a dormant account user, the mail web server provides the corresponding information to the user client.

If the recipient entered by the user does not exist, the message as shown in Fig. 4 is output to the web browser. If the recipient is a dormant account user, the message as shown in Fig. 5 is output to the web browser. In this case, a message as shown in FIG. 6 is output to the web browser.

The mail server 106 receives the user's request information from the mail web server and processes the user's request information related to the mail. Communication between the mail web server 102 and the mail server 106 is performed using the SMTP protocol.

The SMTP protocol is a type of TCP / IP protocol used to send and receive e-mail. It is defined in IETF's RFC 821. The SMTP protocol generally operates on TCP port 25.

Although not shown in FIG. 1, a mail server generally includes a mail transfer agent (MTA) and a mail delivery agent (MDA).

The MTA functions to receive e-mail from a web server via the SMTP communication protocol and to invoke the MDA to deliver the received e-mail to the MTA of another mail server or to the mailbox 108 of the mail server 106. As the MTA, send mail and qmail are generally used.

The MTA looks at the recipient's address information in the forwarded mail and, if the recipient is in charge, causes the MDA to store the email in the mailbox 108 via a system call.

If the recipient's address is not the recipient of the MTA's address, the MTA delivers the email through the SMTP protocol to the MTA of the external mail server corresponding to the recipient's address.

The MDA is an agent program module that delivers the e-mail received by the MTA to the actual user. The MDA is generally divided into an external delivery and an internal delivery. In case of external transmission, each MDA exists according to channel (TCP, uucp, etc.). In case of Unix, it can be driven by / bin / sh.

In the case of internal delivery, the MTA stores the mail received by the MTA in the user's mailbox, and the MDA which performs such a function is called a local MDA. Typically, a local MDA stores e-mails in mailboxes on the local file system, using a filtering program that can process e-mails. The local MDA performs MIME (Multipurpose Internet Mail Extension) parsing when storing e-mail in a mailbox. This means parsing data to be stored in a mailbox from MIME type mail data.

MIME is a protocol that extends the capabilities to send and receive audio, video, images, applications, and many other types of data files.

The mailbox 108 is a database that stores electronic mail. The standard format for storing mail is not specifically defined, but generally the mbox method of continuously appending to a file and the MH and Maildir methods of storing each e-mail as each file in one directory are mainly used.

As described above, the recipient may check the remaining capacity of the mail recipient to determine whether the mail can be received. In this case, the mail web server 102 accesses the mailbox 108 and checks the remaining capacity information. .

In addition, the mail web server 102 compares the capacity of the mail created by the mail sender with the remaining mail capacity of the receiver, determines whether the receiver can receive the mail to be transmitted, and provides the determination result to the user client 100. A method of checking the remaining mail capacity of the receiver and a method of checking the capacity of the mail to be transmitted will be described later through separate drawings.

2 is a diagram illustrating a system configuration for checking whether reception is possible before sending a mail according to another embodiment of the present invention.

1 illustrates a system capable of checking whether a sender and a receiver input by a sender belong to the same mail domain. For example, if a mail sender also uses a mail domain named 'naver.com' and a recipient uses a mail domain named 'naver.com', as shown in FIG. Can be.

However, when the sender's mail address and the receiver's mail address belong to different domains, as shown in FIG. 1, the sender's mail system cannot determine whether the receiver can receive the mail.

In this case, the sender's mail system should request information about the receiver from the mail system corresponding to the receiver.

In FIG. 2, the first mail system 130 is the sender's mail system and the second mail system 150 is the recipient's mail system.

If the receiver is a user of another mail system, and the client 100 of the mail sender transmits the reception check request information to the mail web server 102 of the first mail system 130, the mail web server 102 receives the receiver. Confirms that the user is not a user belonging to the domain, and transmits the receivable check request information to the mail web server 152 of the mail system 150 corresponding to the recipient. At this time, the address information of the mail web server 150 belonging to the mail system 152 of the receiver may be stored in the sender mail system 130 in advance, and a separate intermediary server (not shown) may receive a check request message. It may also be delivered to the recipient's mail system 150.

The mail web server 152 of the second mail system 150 determines whether the recipient is a user who exists and is a dormant account user through communication with the account server 154, and determines the determination information on the first mail system 130. Mail web server 102, the mail web server 102 of the first mail system 130 provides the received information to the user client (100).

In addition, the mail web server 152 of the second mail system 150 checks the remaining mail capacity information of the recipient by accessing the mailbox 158 and provides it from the mail web server 102 of the first mail system 130. The mail volume to be transmitted is checked to determine whether the recipient is in a state capable of receiving mail, and the determination information is transmitted to the mail web server 102 of the first mail system 130.

Through the system as shown in FIG. 2, it is possible to determine whether the receiver can receive mail even if the receiver does not have a mail address of the same domain as the sender.

7 is a block diagram showing a detailed configuration of a mail web server according to an embodiment of the present invention.

Referring to FIG. 7, a mail web server according to an exemplary embodiment of the present invention includes a client communication unit 700, a control unit 702, a web page editing unit 704, a receiver information check unit 706, and a capacity check unit 708. ), A MIME generator 710, and a mail server communication unit 712.

The client communication unit 700 receives the request information from the user client and provides the information requested by the client. When the user requests a receivable check using an interface button, the user receives the information and transmits the information to the controller 702. When the receiver inputted by the sender is a user belonging to a mail system different from the sender, the client communication unit 700 may receive the receivable check request information from the mail web server of the mail system to which the sender belongs.

The control unit 702 receives the user request information from the client communication unit 700 and controls the overall operation of the mail web server so that the user request information is executed. The control unit 702 executes the receiver information check unit 706 and the capacity check unit 708 when the receivable check request information is transmitted from the user client or the external mail web server.

The web page editing unit 704 functions to edit a corresponding web page when a user requests a web page such as reading a mail or writing a mail, and the edited web page is transmitted to the user client through the client communication unit 700.

In particular, the web page editing unit 704 generates and provides a mail writing page including an interface button for requesting a check that the receiver inputted by the sender before receiving the mail is ready to receive mail.

The receiver information checker 706 performs an operation for checking whether the input receiver is a user who exists and whether the user is a dormant account user.

The recipient information checker 706 transmits the recipient confirmation request information to the account server, and the account server determines whether the corresponding recipient exists and checks the last login time of the recipient using the log information. As described above, the account server may provide only the last login information to the receiver information checker 706, and whether the account holder is a dormant account user may be determined by the receiver information checker 706, and the account server uses the last login time information. It may be determined whether the user is a dormant account, and may provide the determination information to the reception checker 706.

The capacity checker 708 determines the remaining mail capacity of the user who will receive the mail, and compares the mail capacity information of the determined recipient with the determined mail capacity information when receiving the capacity information of the mail to be sent from the user client or an external mail web server. It is determined whether the mail can be received.

The capacity checker 708 requests the account server's folder location information from the account server to access the recipient folder of the mailbox, and receives the requested information from the account server. In addition, the capacity checker 708 requests the account server for mail capacity information given to the recipient, and also receives information on the mail capacity of the recipient from the account server. Receiving the folder location information of the recipient, the capacity checker 708 accesses the mailbox using the location information, reads the recipient folder information, and checks the mail capacity stored in each folder. For example, the recipient's folder may include a folder such as an inbox, a sent box, spam mail, and the like, and the capacity checker 708 checks the amount of mail stored in each folder. When the mail storage capacity information of all folders is read, the capacity checker 708 calculates the mail space used by the recipient by summing the mail storage capacity of each folder, and the mail space assigned to the user received from the account server. Compute the remaining capacity by comparison. In addition, when the capacity information of the mail to be transmitted is received, it is compared with the remaining capacity to determine whether the recipient can receive the mail.

The MIME generator 710 converts the transmitted electronic mail data into MIME format data when the user requests mail transmission. Since the MIME data format is already known, a detailed description thereof will be omitted.

The mail server communication unit 712 transmits mail data of the MIME format generated by the MIME generating unit 710 to the MTA of the mail server. The mail server communication unit transmits the data of the MIME format through the SMTP protocol.

8 illustrates user data fields managed by an account server according to an exemplary embodiment of the present invention.

Referring to FIG. 8, according to a preferred embodiment of the present invention, a data field managed by an account server includes a user ID field 800, a log information field 802, a mail capacity field 804, and a mail folder location information field. 806 may include.

The user ID field 800 is a field in which ID information of a mail user is recorded. When the mail web server requests the account server to check whether the mail recipient ID exists, the account server checks whether the requested recipient ID exists in the user ID field.

The log information field 802 is a field in which log information about access and termination of each user is recorded. When the mail web server inquires whether the recipient is a dormant account user, the account server checks the last login time of the user in the log information field and sends the last login time information to the mail web server or by using the last login time information. Determine if you are a dormant account user.

In the mail capacity field 804, mail capacity information assigned to each user is recorded. In general, mail volume varies depending on whether the user is a paid user or a free user, and the mail volume may be adjusted according to the degree of use. When the mail web server requests the mail capacity assigned to the recipient, the account server provides the mail web server with information in the mail capacity field.

In the mail folder location information field 806, folder location information in each user's mailbox is recorded. When the mail web server requests the account server for folder location information to confirm the mail occupancy capacity of the recipient, the account server provides the mail web server with data in the mail folder location information field.

9 is a flowchart illustrating a process of confirming whether a receiver exists and whether a user is a dormant account user according to an exemplary embodiment of the present invention.

Referring to FIG. 9, a user inputs a mail address of a mail recipient in a web page displayed on the client (step 900), and receives mail check request information for the input recipient using an interface button provided in the web page. Send to web server (step 902). If the recipient's mail domain is different from the sender, the sender's mail web server may send the receivable check request information to the recipient's mail web server.

Upon receiving the receivable check request information, the mail web server transmits confirmation request information about the recipient to the account server (step 904).

The account server examines the user field to determine whether the entered recipient is a registered user (step 906).

If the entered recipient is a registered user, the account server checks the log information field to confirm the last login time information of the recipient (step 908).

If the last login time is later than the preset time, the account server determines that the recipient is not a dormant account user, and if the last login time is earlier than the preset time, the account server determines that the recipient is a dormant account user (step 910).

After determining whether the receiver input in steps 906 to 910 is a registered user and a dormant account user, the account server transmits the recipient confirmation response information to the ME web server (step 912).

As described above, the determination as to whether the input recipient is a dormant account user may be performed in the mail web server, in which case the account server provides the last login time information to the receiver entered in the mail web server.

The mail web server transmits the receivable check response information to the user client using the information received from the account server (step 914).

9 illustrates a case in which the user client transmits the receivable check response information. However, when the input receiver is a user belonging to a mail domain different from the sender, the receivable check request information may be transmitted from the sender's mail web server. There will be.

10 is a flowchart illustrating a method of providing remaining mail capacity information of an input recipient according to an exemplary embodiment of the present invention.

Referring to FIG. 10, a user inputs a recipient in a mail writing page (step 1000), and when a user clicks a receiveable check request button, mail capacity check request information is transmitted from a user client to a mail web server (step 1002). Of course, when the receiver is a user belonging to a different mail domain from the sender, the mail capacity check request information may be transmitted from the sender's mail web server to the receiver's mail web server.

Receiving the mail capacity check request information, the mail web server requests the mail capacity given to the recipient entered in the account server and the folder location information in the mailbox (step 1004).

The accounting server examines the user capacity information field and the mail folder location information field and transmits the mail capacity and mail folder location information given to the input recipient to the mail web server (step 1006).

The mail web server reads the folder information of the input recipient in the mailbox received from the account server to check the mail space used by the user input in each folder (step 1008). For example, if a recipient's mail folder consists of an Inbox, Sent Mail, and Spam Mail folder, the mail web server checks the space usage information of each folder.

Upon checking each folder usage space of the input recipient, the mail web server adds up each folder usage space to calculate the total mail space used by the user (step 1010).

The mail web server calculates the amount of mail remaining in the input recipient using the mail capacity information given to the input recipient and the mail space information used by the input recipient (step 1012).

The mail web server sends the calculated remaining mail capacity information to the user client (step 1014).

As such, when the user requests a reception check, the mail web server provides the user with the remaining mail capacity information of the input recipient, so that the user can adjust the capacity of the mail to be sent.

FIG. 11 is a flowchart illustrating a method for providing a user with information on whether or not reception is possible by comparing a capacity of a mail to be transmitted with a remaining mail capacity of an input receiver according to an exemplary embodiment of the present invention.

According to the present invention, not only the remaining mail capacity information can be provided to the user as shown in FIG. 10 but also information on whether the recipient can receive the mail created by checking the capacity of the mail to be transmitted. In this case, however, the sender must prepare a mail to be transmitted in advance and then click the reception check button to accurately calculate the amount of mail to be sent.

Referring to FIG. 11, the mail web server provides a mail writing page including a script for calculating a text capacity to a user client (step 1100). Since inserting a script for calculating text capacity information into a mail writing page is a known technique, a detailed description thereof will be omitted.

The user enters a recipient in the provided mail writing page, composes a mail to be sent, and clicks a receiveable check button (step 1102).

When the user clicks the receivable check button, the text capacity information is calculated by the script, and the receivable check request information including the input recipient information and the text capacity information is transmitted to the mail web server (step 1104). Since the attached file is registered in the mail web server when the user attaches the file, it is not necessary to transmit the capacity information of the attached file from the user client to the mail web server, and the mail web server can check the capacity of the registered file.

According to another embodiment of the present invention, unlike FIG. 11, a script for transmitting mail text information written by the user to the mail web server when the user clicks the checkable check button may be included in the mail writing page. In this case, the mail web server calculates the text capacity of the mail created by the user using the transmitted text capacity information.

Receiving the receivable check request information, the mail web server requests the account server for the mail capacity information given to the input recipient of the account server and the folder location information in the input recipient's mailbox (step 1106).

The accounting server examines the mail capacity field and the mail folder location information field, and provides the mail web server with the mail capacity information given to the entered recipient and the folder location information in the entered recipient's mailbox (step 1108).

The mail web server reads the folder information in the input recipient's mailbox using the information received from the account server (step 1100), and calculates the total mail space used by the input recipient using the read information. (Step 1112).

When the total mail space used by the input recipient is calculated, the mail web server calculates the remaining mail capacity of the input receiver using the mail capacity information given to the input receiver (step 1114).

The mail web server calculates the amount of mail sent through the text capacity of the mail to be sent and the file size of the mail to be sent and compares it with the remaining mail capacity of the input user to determine whether or not the received recipient can receive the mail to be sent. Determine (step 1116).

The mail web server transmits the receivable check response information to the user client according to the determination result in step 1116. Of course, if a request for mail reception is made by the mail web server, the check receipt information of the reception is transmitted to the mail web server, and the mail web server transmits it back to the user client.

As described above, according to the method and system for determining a reception possible state before mail transmission according to the present invention, it is possible to determine whether a user input as a recipient can receive a mail before the mail sender sends the mail. In this way, it is possible to provide a reliable e-mail service.

Claims (16)

An account server for managing user information including user identification information including a user ID, log information of the user, and mail capacity information assigned to the user; A mail writing page having an interface button for requesting a check of whether a recipient can receive mail before sending mail to a user client is provided, and the mail writing page entered as a recipient on a mail writing page through communication with the account server. A mail web server for determining whether the user is a registered user and a dormant account user; Receives mail data from the mail web server, determines whether the received mail data is mail data to be stored in its own mailbox or mail data to be sent to an external mail server, and sends the received mail data to an external mail server. Mail servers that store or store in mailboxes, The mail web server reads the folder information of the mailbox, checks the remaining mail capacity of the user entered as the recipient on the mail writing page, and uses the user registration information, dormant accounting user information, and the remaining mail capacity information. And a mail system capable of checking whether or not the user inputted with the mail can receive the mail. The method of claim 1, The account server determines whether the user is a registered user by using the mail receiver information provided from the mail web server, and if the user is a registered user, checks the last login time information of the corresponding receiver by using log information, and last login time. A mail system capable of checking whether or not reception is possible before sending mail, wherein the information is determined whether the user is a dormant account using information. The method of claim 1, The account server determines whether the user is a registered user by using mail receiver information provided from the mail web server, and checks the last login time information of the corresponding recipient by using log information when the registered user is the mail web server. The mail system of claim 1, wherein the mail web server determines whether the user is a dormant account user by using last login time information. The method of claim 1, The mail web server requests the mail capacity information given to the user inputted as the recipient to the account server and the folder location information in the mailbox, and is inputted to the recipient of the mailbox via the folder location information provided from the account server. Reads the folder information of the user, calculates the mail usage space of the user entered as the recipient based on the read folder information, and uses the mail capacity information and the mail usage space information given to the user entered as the recipient to display the remaining mail. A mail system capable of checking whether or not reception is possible before sending mail, characterized in that the capacity is calculated. The method of claim 4, wherein The mail writing page includes a script for checking the text data size of the mail input by the mail sender, and when the user clicks the interface button, the mail text size information input by the mail sender is transmitted to the mail web server. , The mail web server calculates the data size of the mail to be transmitted using the text size information and the attached file size information when the attached file is attached, A mail system capable of checking whether or not a user input as the recipient can receive a mail by using the remaining mail capacity information and data size information of the mail to be sent; . The method of claim 4, wherein The mail writing page includes a script for transmitting the mail text input by the mail sender to the mail web server when the user clicks the interface button. The mail web server calculates text size information using the transmitted mail text information, checks the size information of an attached file when an attached file is attached, and uses the text size information and the attached file size information. Calculate the data size of the mail to be sent A mail system capable of checking whether or not a user input as the recipient can receive a mail by using the remaining mail capacity information and data size information of the mail to be sent; . The method of claim 1, The mail web server, A client communication unit which receives the webmail related request information from the user client and transmits the webmail related data requested by the user to the user client; A control unit controlling the overall operation of the mail web server to execute a predetermined process according to the webmail related request information of a user client; Edit the web page requested from the user client under the control of the controller, edit the mail writing page including an interface button for requesting a check of whether the recipient can receive the mail before sending the mail. Web page editing unit provided to; A user information checker which determines, via communication with the account server, whether the input recipient is a registered user and a dormant account user when the user requests a reception check before sending the mail; When the user requests a reception check before sending the mail, the size of the mail data to be sent is calculated, the folder information of the input recipient is read from the mailbox, and the mail usage capacity of the input receiver is determined, and the account server A mail capacity checker configured to receive mail capacity information given to the input recipient through communication with and calculate a remaining mail capacity of the input recipient; A MIME generation unit for converting mail data transmitted from the user client into mail data in a MIME format; And And a mail server communication unit for transmitting the mail data of the MIME format to the mail server. A client communication unit which receives the webmail related request information from the user client and transmits the webmail related data requested by the user to the user client; A control unit controlling the overall operation to execute a predetermined process according to the webmail related request information of the user client; Edit the web page requested from the user client under the control of the controller, edit the mail writing page including an interface button for requesting a check of whether the recipient can receive the mail before sending the mail. Web page editing unit provided to; A user information check unit for determining whether an input recipient is a registered user and a dormant account user when the user requests a reception check before sending a mail; When the user requests the reception check before sending the mail, the folder information of the input recipient is read from the mailbox to determine the mail space usage capacity of the input recipient, and the mail capacity information and the input given to the input recipient are determined. A mail capacity checker which calculates the remaining mail capacity of the input receiver using the mail space usage information of the received recipient; A MIME generation unit for converting mail data transmitted from the user client into mail data in a MIME format; And And a mail server communication unit for transmitting the mail data of the MIME format to the mail server. The method of claim 8, The user information check unit determines whether the user is a registered user and a dormant account user through communication with the account server, And the mail capacity checker receives the mail capacity information assigned to the input recipient from the account server. The method of claim 9, The mail capacity checker requests and receives folder location information from the input recipient's mailbox from the account server, and reads the input folder information of the input recipient using the received information. A mail web server that can check the availability of mail. The method of claim 8, The mail writing page includes a script for checking the text data size of the mail input by the mail sender, and when the user clicks the interface button, the mail text size information input by the mail sender is transmitted to the mail web server. , The mail capacity checker calculates the data size of the mail to be sent using the text size information and the size information of the attached file when the attached file is attached, and stores the remaining mail capacity information and the data size information of the mail to be sent. And a mail web server capable of checking whether the user inputted as the receiver can receive the mail before sending the mail. The method of claim 8, The mail writing page includes a script for transmitting the mail text input by the mail sender to the mail web server when the user clicks the interface button. The mail capacity checker calculates text size information using the transmitted mail text information, checks the size information of an attached file when an attached file is attached, and transmits using the text size information and the attached file size information. And calculating the data size of the mail to be received, and determining whether the user input to the recipient can receive the mail by using the remaining mail capacity information and the data size information of the mail to be sent. Mail web server that can check availability. (A) providing a mail writing page having an interface button for requesting a check of whether a recipient can receive mail before sending mail to the user client; (B) determining whether the received mail receiver is a registered user and a dormant account user when the user receives a request to receive a check before sending the mail; (C) determining a mail space usage capacity of the inputted recipient by reading folder information in the inputted recipient's mailbox when a user is requested to receive a check before sending the mail; Checking the amount of mail given to the input recipient and calculating a remaining amount of mail of the input recipient; And (E) determining whether the received recipient can receive mail by using the user registration information, the dormant account user information, and the remaining mail capacity information. How to. The method of claim 13, The mail writing page includes a script for checking the text data size of the mail input by the mail sender, and when the user clicks the interface button, the mail text size information input by the mail sender is transmitted. Step (e), Calculating a data size of an e-mail to be transmitted using the text size information and the attached file size information; And Determining whether a user input as the recipient can receive mail by using the remaining mail capacity information and data size information of the mail to be transmitted. Way. The method of claim 13, The mail writing page includes a script for transmitting the mail text input by the mail sender when the user clicks the interface button. Step (e), Calculate text size information using the transmitted mail text information, check the size information of an attached file when an attached file is attached, and use the text size information and the attached file size information to determine the data size of the mail to be sent. Calculating; And  Determining whether a user input as the recipient can receive mail by using the remaining mail capacity information and data size information of the mail to be transmitted. Way. An account server for managing user information including user identification information including a user ID, log information of the user, and mail capacity information assigned to the user; Provides a mail compose page with an interface button that allows the user client to check whether the recipient is ready to receive mail before sending it, and whether or not a specific recipient can receive mail from an external mail web server. A mail web server that receives request information for and determines whether the recipient is a registered user and a dormant account user through communication with the account server; Receives mail data from the mail web server, determines whether the received mail data is mail data to be stored in its own mailbox or mail data to be sent to an external mail server, and sends the received mail data to an external mail server. Mail servers that store or store in mailboxes, The mail web server reads folder information of the mailbox to check the remaining mail capacity of the recipient, and whether the recipient can receive mail using the user registration information, dormant accounting user information, and remaining mail capacity information. And a mail system capable of checking whether or not reception is possible before transmission of the mail, characterized in that the transmission is determined.

Images