JP2012199717A - Mail server, mail processing program, mail processing method, and mail system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To alleviate a burden on a mail sender.SOLUTION: A mail server 200 has a communication controller 210, an authentication DB 220, a response DB 230, a mail DB 240, a mail management DB 250, a setting DB 260, and a controller 270. The controller 270 has a specification unit 271, a first acquisition unit 272, a second acquisition unit 273, a transmission unit 274, a creation screen generation unit 275, and a browsing screen generation unit 276. The transmission unit 274 generates such a mail display screen that a mail acquired by the first acquisition unit 272 among mails acquired by the second acquisition unit 273 is displayed in a different form from the other mails.

Description

  The technology disclosed in the present application relates to a mail server, a mail processing program, a mail processing method, and a mail system.

  Currently, e-mail is actively used, but an e-mail requesting an answer from a mail recipient may be transmitted for a predetermined case. In such a case, the sender of the mail often sets a reply deadline for the reply to the receiver of the mail in the electronic mail. Therefore, the sender of an e-mail requesting an answer informs the receiver that the answer deadline is approaching by telephone or e-mail, etc. in order to obtain the answer as much as possible by the deadline for answering, or the answer deadline has passed. Or to inform the recipient that they are

  In addition, in relation to the technology for requesting and obtaining responses, there is a technology for managing the user who made the response by managing the request email requesting the response and the response email corresponding to the request email in association with each other. is there. There is also a technique for reminding an unread reader of an electronic bulletin board by managing a viewing time limit of the electronic bulletin board and outputting a browse reminder message to an unread reader of the electronic bulletin board.

JP 2009-199273 A JP 2006-252270 A

  However, as described above, there is a problem that a sender of an e-mail requesting an answer has a work load such as telling the receiver that the answer deadline is imminent by telephone or e-mail. In addition, in order to reduce the work burden of the sender of the e-mail requesting an answer, it is also conceivable to use the above-described management technology or dunning technology. For example, the response of the recipient is managed, and when a response from the recipient is not obtained at a certain time, a message for prompting the response is transmitted. However, in this case, there is a problem that a new storage area for storing the dunning message is required for the recipient of the dunning message.

  The disclosed technology has been made in view of the above, and an object thereof is to provide a mail server, a mail processing program, a mail processing method, and a mail system that can reduce the burden on the mail sender.

  In one aspect, the mail server disclosed in the present application includes a first storage unit, a second storage unit, a specifying unit, a first acquisition unit, a second acquisition unit, and a transmission unit. . The first storage unit includes inquiry mail identification information for uniquely identifying an inquiry mail requesting an answer; user identification information for uniquely identifying a user who is the destination of the inquiry mail; and a response to the inquiry mail by the user Is stored in association with an answer status indicating whether or not The second storage unit stores the user identification information and a plurality of pieces of mail information including the inquiry mail transmitted to the user in association with each other. The specifying unit specifies the user identification information of the user when receiving a mail acquisition request for requesting at least a part of the plurality of mail information from a terminal operated by the user. The first acquisition unit is configured to obtain the inquiry mail identification information that is the inquiry mail identification information associated with the identified user identification information and that has not yet been answered from the first storage unit. get. The second acquisition unit is a mail information including at least a part of the plurality of mail information associated with the identified user identification information and including mail information corresponding to the acquired inquiry mail identification information. Obtained from the second storage unit. The transmission unit has acquired, by the second acquisition unit, mail information corresponding to the inquiry mail identification information acquired by the first acquisition unit among the mail information acquired by the second acquisition unit. Information to be displayed in a form different from other mail information is transmitted.

  According to one aspect of the technology disclosed in the present application, the burden on the mail sender can be reduced.

FIG. 1 is a block diagram showing the configuration of the mail server. FIG. 2 is a diagram illustrating an example of data in the authentication DB. FIG. 3 is a diagram illustrating an example of data in the answer DB. FIG. 4 is a diagram illustrating an example of mail DB data. FIG. 5 is a diagram illustrating an example of data in the mail management DB. FIG. 6 is a diagram illustrating an example of data in the setting DB. FIG. 7 is a diagram showing the overall flow of processing by the client device. FIG. 8 is a diagram showing the flow of message transmission processing. FIG. 9 is a diagram showing a flow of the reply mail browsing process. FIG. 10 is a diagram showing the overall flow of processing by the mail server. FIG. 11 is a diagram showing the flow of the message creation screen generation process. FIG. 12 is a diagram illustrating an example of an answer required message creation screen. FIG. 13 is a diagram illustrating an example of a header structure of a mail. FIG. 14 is a diagram illustrating an example of a general message creation screen. FIG. 15 is a diagram illustrating the flow of the reply mail browsing screen generation process. FIG. 16 is a diagram illustrating an example of a reply mail browsing screen. FIG. 17 is a diagram showing the flow of the mail display screen creation process (1). FIG. 18 is a diagram illustrating an example of a mail display screen. FIG. 19 is a diagram showing the flow of the mail display screen creation process (2). FIG. 20 is a diagram illustrating an example of a mail display screen. FIG. 21 is a diagram showing the flow of the mail display screen creation process (3). FIG. 22 is a diagram illustrating an example of a mail display screen. FIG. 23 is a diagram showing the flow of the mail display screen creation process (4). FIG. 24 is a diagram illustrating an example of a mail display screen. FIG. 25 is a diagram illustrating an example of a display form of an email requiring reply. FIG. 26 is a diagram illustrating an example of a computer that executes a mail processing program.

  Hereinafter, embodiments of a mail server, a mail processing program, a mail processing method, and a mail system disclosed in the present application will be described with reference to the drawings. An example described later is merely an embodiment, and does not limit the mail server, the mail processing program, the mail processing method, and the mail system disclosed in the present application. In addition, the embodiments described later can be appropriately combined within a range that does not cause a contradiction in the processing contents.

  In the following embodiment, each process performed by the mail server disclosed in the present application when the client device accesses the mail server using a web browser or the like and exchanges mail will be described. However, the disclosed technology is not limited to this, and can be applied to a case where the client device uses electronic mail software to communicate with the mail server and download the mail to the client device, as will be described later.

[Configuration of Mail Server (Example 1)]
FIG. 1 is a block diagram showing the configuration of the mail server. As illustrated in FIG. 1, the mail server 200 according to the first embodiment is connected to a plurality of client devices 100 via a network 10. For convenience of explanation, FIG. 1 shows three client devices, that is, the client device 100A, the client device 100B, and the client device 100C, but the number is not limited to this.

  The client device 100 is a computer such as a personal computer, a mobile phone device, a PHS (Personal Handy-phone System) terminal, a smartphone, or a PDA (Personal Digital Assistant) having at least a web browser function. In addition, the client device 100 includes an input unit such as a keyboard and a display unit such as a liquid crystal display, and communicates with a web mail server by a web browser function to send and receive mail. The network 10 is a communication network such as the Internet, a LAN (Local Area Network), a WAN (Wide Area Network), and a mobile phone network.

  1, the mail server 200 includes a communication control unit 210, an authentication DB (Date Base) 220, an answer DB 230, a mail DB 240, a mail management DB 250, a setting DB 260, and a control unit 270. Have The communication control unit 210 controls communication regarding various information exchanged with the client device 100.

  The authentication DB 220 stores information used for authentication of the user of the client device that accesses the mail server 200. FIG. 2 is a diagram illustrating an example of data in the authentication DB. As shown in FIG. 2, the authentication DB 220 stores a user ID for identifying a user and a password unique to the user in association with each user of each client device 100 that is a user of the mail server 200. To do. The user ID (Identity) is identification information for uniquely identifying a mail user, and for example, a mail address is used. The password is authentication information for authenticating the user. For example, as shown in FIG. 2, the authentication DB 220 stores “user ID: aaa@xxx.ww” and “password: jjleriuth” in association with each other.

  The answer DB 230 stores the answer status with respect to an email requesting an answer (hereinafter referred to as an answer required email). FIG. 3 is a diagram illustrating an example of data in the answer DB. As shown in FIG. 3, the answer DB 230 stores the answerer ID, the answer flag, and the answer date and time in association with each other. The respondent ID is the user ID of the user who is the respondent of the reply required mail. The reply flag indicates the reply status to the reply required mail. For example, if it is “0”, it is not answered, and if it is “1”, it is answered. The reply date and time is the date and time when the mail server 200 confirms the reply, for example, the date and time when the reply mail is received. For example, as shown in FIG. 3, the answer DB 230 stores “answer ID: aaa@xxx.ww” and “answer flag: 0 (unanswered)” in association with each other. Alternatively, the answer DB 230 associates “answer ID: bbb@xxx.ww”, “answer flag: 1 (answered)”, and “answer date / time: 2011/12/20 12:45:34”. Remember. Here, the respondent ID is a user ID that is a respondent of the reply required mail. The reply flag indicates the reply status to the reply required mail. For example, if it is “0”, it is not answered, and if it is “1”, it is answered. The reply date / time is the date / time when the mail server 200 confirmed the reply. In this embodiment, since the answer DB is present for each mail requesting an answer, an answerer ID, an answer flag, and an answer date are described in association with each other. However, as an answer DB, one answer DB is prepared in the mail server 200, and an identifier (message ID) of an email requesting an answer, an answerer ID, an answer flag, and an answer date / time are associated with each other. May be described.

  The mail DB 240 stores information related to mail sent and received by the client device 100. FIG. 4 is a diagram illustrating an example of mail DB data. As shown in FIG. 4, the mail DB 240 includes a user ID, a mail type for each mail, a message ID for identifying the mail, a sender that is a mail transmission source, and a destination that is a mail reception destination. The transmission date and time and the mail information are stored in association with each other. The user ID corresponds to the user ID in the authentication DB 220. The type of mail indicates whether the mail is transmitted mail or received mail. The message ID is mail identification information that uniquely identifies a mail, and is created from, for example, a time or a mail address. The sender indicates the sender of the mail, and for example, a user ID is used. The destination indicates a mail receiving destination, and for example, a user ID is used. The transmission date / time indicates the date / time when the mail was transmitted. The mail information includes a title and a text. The title is the title of the mail (Subject), and the text is the text data of the mail. For example, as shown in FIG. 4, the mail DB 240 uses “Title: (Respondence Required) Adjustment of Health Examination Date” as information on the received mail of the user with “User ID: ddd@xxx.ww”. And mail information including “text: This is Taro Patent ...”. Similarly, as shown in FIG. 4, the mail DB 240 stores “title: (response required) adjustment of health checkup date” and “adjustment of health checkup date” as information on the received mail of the user with “user ID: sss@xxx.ww”. Mail information including "Body: Taro Patent ..." The mail DB 240 is expressed in a table format in FIG. 4, but may be stored in a folder format as an information storage format. For example, a form in which a subfolder is formed for each user ID, transmission and reception are prepared as lower folders, a folder corresponding to the message ID is prepared in the lower folder, and other information is inserted in the lower folder. It doesn't matter.

  The mail management DB 250 stores the reply deadline of the reply required mail and the reminder status regarding the reply required mail. FIG. 5 is a diagram illustrating an example of data in the mail management DB. As shown in FIG. 5, the mail management DB 250 stores, for each reply required mail, a message ID for identifying the reply required mail, a transmission date and time, a time limit, and a reminder flag in association with each other. The message ID and the transmission date / time correspond to the message ID and the transmission date / time in the mail DB 240. The deadline indicates the deadline date and time of the reply to the reply required mail. The dunning flag indicates whether or not a response has been dampened by the sender of the reply required mail. If “ON”, the dunning has been completed, and if “OFF”, the dunning has not been performed. For example, as shown in FIG. 5, the mail management DB 250 stores “reminder flag: ON” for the reply required mail of “message ID: syokuba@xxx.yy”. Therefore, referring to the information stored in the mail management DB 250, the reply required mail of “message ID: syokuba@xxx.yy” is in a state where a response is requested from the sender of the reply required mail. I understand.

  The setting DB 260 stores setting information for displaying an answer-required mail for which a response has been prompted in a form different from other mails. FIG. 6 is a diagram illustrating an example of data in the setting DB. As shown in FIG. 6, the setting DB 260 stores font and background color setting methods in association with “general” and “remind”. Here, “general” represents a setting relating to an email other than an email requiring reply for which an answer is requested. The “reminder” represents a setting related to an email requiring reply for which a reply is prompted. According to the setting information DB 260, as shown in FIG. 6, the font for displaying mail is set to “Gothic” for “General” and “Bold Gothic” for “Reminder”. Further, according to the setting information DB 260, as shown in FIG. 6, the background color when displaying the mail is set to “white” for “general” and set to “blue” for “reminding”. . These settings are only examples.

  The above-described user ID, password, and message ID data are merely examples, and any data may be used as long as it is unique data that can uniquely identify the target. Further, the authentication DB 220, the answer DB 230, the mail DB 240, the mail management DB 250, and the setting DB 260 described above can be implemented by general-purpose hardware such as a server, a storage, and a personal computer. Further, the authentication DB 220, the answer DB 230, the mail DB 240, the mail management DB 250, and the setting DB 260 described above can be implemented by a storage medium such as a large-capacity hard disk instead of the general-purpose hardware described above.

  As illustrated in FIG. 1, the control unit 270 includes a specifying unit 271, a first acquisition unit 272, a second acquisition unit 273, a transmission unit 274, a creation screen generation unit 275, and a browsing screen generation unit 276. And have. Note that the control unit 270 can be implemented by, for example, an electronic circuit or an integrated circuit. Examples of the electronic circuit include a CPU (Central Processing Unit) and an MPU (Micro Processing Unit). Examples of integrated circuits include ASIC (Application Specific Integrated Circuit) and FPGA (Field Programmable Gate Array).

  When receiving the mail display request (login request) from the client apparatus 100, the specifying unit 271 refers to the authentication DB 220 and authenticates the user of the client apparatus 100 that is the transmission source of the mail display request. For example, the specifying unit 271 requests a user ID and a password from the client device 100 that is a transmission source of the mail display request. Then, the specifying unit 271 determines that the authentication is successful when the pair of the user ID and the password acquired from the client device 100 that is the transmission source of the mail display request is in the authentication DB 220. On the other hand, the specifying unit 271 determines that the authentication fails when the pair of the user ID and the password acquired from the client device 100 that is the transmission source of the mail display request is not in the authentication DB 220. Note that the identification unit 271 may accept a mail display request only by the user ID and identify the user for a predetermined period after successful authentication using the password.

  When the first acquisition unit 272 refers to the mail management DB 250 and there is an unanswered reply-needed mail that has not been answered in the received mail of the user who has succeeded in the login authentication by the specifying unit 271, Get the message ID of the reply required email. An example of processing by the first acquisition unit 272 will be described later with reference to FIGS. 17, 19, 21, and 23.

  The second obtaining unit 273 obtains, from the mail DB 240, transmission / reception mails of users who have succeeded in login authentication by the specifying unit 271. Note that an example of processing by the second acquisition unit 273 will be described later with reference to FIGS. 17, 19, 21, and 23.

  The transmission unit 274 generates a mail display screen that displays the mail acquired by the first acquisition unit 272 among the mails acquired by the second acquisition unit 273 in a form different from other mails. . Note that an example of processing performed by the transmission unit 274 will be described later with reference to FIGS.

  Upon receiving a mail creation screen acquisition request from the client device 100, the creation screen generation unit 275 executes a mail creation screen generation process. Note that an example of processing performed by the creation screen generation unit 275 will be described later with reference to FIGS.

  When the browsing screen generation unit 276 receives a display request for a reply-needed email browsing screen from the client device 100, the browsing-screen creation unit 276 executes a reply-needed email browsing screen generation process. An example of processing by the browsing screen generation unit 276 will be described later with reference to FIGS.

[Processing in Example 1]
Hereinafter, the process according to the first embodiment will be described with reference to the drawings. 7, 8, and 9 are used to describe processing by the client device 100 </ b> A, the client device 100 </ b> B, the client device 100 </ b> C, and the like. 9 to 24 are used for explaining processing by the mail server 200. FIG.

(Client device processing)
First, the overall flow of processing by the client device 100A, the client device 100B, the client device 100C, and the like will be described with reference to FIG. FIG. 7 is a diagram showing the overall flow of processing by the client device. The following processing is executed when the client device 100 accesses the mail server 200 using the function of the web browser.

  As illustrated in FIG. 7, when the client apparatus 100 receives a mail display request from the user via the input unit (S101 “Yes”), the client apparatus 100 transmits a mail display request to the mail server 200 (S102). ). When the client apparatus 100 does not accept the mail display request (S101 “No”), the client apparatus 100 repeatedly performs the same determination.

  Subsequently, the client device 100 determines whether or not a user ID and password input screen has been received from the mail server 200 (S103). When the client device 100 receives the user ID and password input screen from the mail server 200 (S103 “Yes”), the client device 100 displays the user ID and password input screen on the display unit (S104). When the client device 100 does not receive the user ID and password input screen from the mail server 200 (S103 “No”), the client device 100 repeatedly performs the same determination.

  Subsequently, the client device 100 determines whether or not an input of a user ID and a password has been received from the user via the input unit (S105). When the client device 100 receives the input of the user ID and password (S105 “Yes”), the client device 100 transmits the user ID and password to the mail server 200 (S106). Note that if the client apparatus 100 does not accept the input of the user ID and password from the mail server 200 (S105 “No”), the client apparatus 100 repeatedly performs the same determination.

  Subsequently, the client device 100 determines whether or not an authentication error screen has been received (S107). When the client apparatus 100 receives the authentication error screen (S107 “Yes”), the client apparatus 100 displays the authentication error screen on the display unit (S108) and ends the process.

  On the other hand, when the client apparatus 100 has not received the authentication error screen (“No” in S107), the client apparatus 100 subsequently determines whether or not the mail display screen has been received from the mail server 200 (S109). When the client apparatus 100 does not receive the mail display screen from the mail server 200 (S109 “No”), the client apparatus 100 repeatedly performs the same determination. When the client device 100 receives the mail display screen from the mail server 200 (S109 “Yes”), the client device 100 displays the mail display screen on the display unit (S110).

  Here, the mail display screen displays, for example, a list of mails received by the user. Then, on the mail display screen, the mail that is an answer-needed mail and that has not been answered is generated in a higher rank. Therefore, in the client device 100, unanswered mail is displayed at the top.

  Subsequently, the client device 100 determines whether a message creation request has been received from the user via the input unit (S111). When the client device 100 accepts the message creation request (S111 “Yes”), the client device 100 executes message transmission processing (S112). The message transmission process will be described later with reference to FIG. In S111 described above, when the client apparatus 100 does not accept the message creation request (S111 “No”), the client apparatus 100 proceeds to the process of step S113 described later.

  Subsequently, the client device 100 determines whether or not a request to display the reply mail browsing screen has been received from the user via the input unit (S113). When the client apparatus 100 receives a display request for the reply mail browsing screen (S113 “Yes”), the client apparatus 100 executes reply mail browsing processing (S114). The reply mail browsing process will be described later with reference to FIG.

  Subsequently, the client device 100 determines whether a mail display request has been received from the user via the input unit (S115). If the client apparatus 100 does not accept the reply request mail browsing screen display request in S113 described above (S113 “No”), the client apparatus 100 proceeds to the determination in S115 described above.

  When the client apparatus 100 receives a mail display request (S115 “Yes”), the client apparatus 100 transmits a mail display request to the mail server 200 (S116). Subsequently, the client device 100 determines whether or not there is a logout request (S117). If the client apparatus 100 does not accept the mail display request (S115 “No”), the client apparatus 100 proceeds to the determination of S117 described above.

  If there is a logout request from the user via the input unit (S117 “Yes”), the client device 100 transmits the logout request to the mail server 200 (S118) and ends the process. On the other hand, if there is no logout request (S117 “No”), the client device 100 returns to S111 described above and determines whether a message creation request has been accepted.

(Message transmission processing)
Next, the flow of the message transmission process of S112 shown in FIG. 7 described above will be described with reference to FIG. FIG. 8 is a diagram showing the flow of message transmission processing. Note that the user creates an email requiring a reply or a general email through the following processing.

  As shown in FIG. 8, the client device 100 determines whether or not the mail type is a reply required mail (S201). If the client apparatus determines that the mail type is a reply-needed mail (S201 “Yes”), it sends the mail type (answer-required mail) and a message creation request to the mail server (S202).

  Subsequently, the client apparatus 100 determines whether or not an answer required message creation screen has been received (S203). If the client device 100 has not received the reply required message creation screen (S203 “No”), the client device 100 repeatedly performs the same determination. When the client apparatus 100 receives the reply required message creation screen (S203 “Yes”), the client apparatus 100 displays the reply required message creation screen on the display unit (S204). Subsequently, the client device 100 accepts input of a destination, a title, an article text, and a time limit (S205). This deadline is a reply deadline for the created message.

  Subsequently, the client device 100 determines whether a message transmission request has been received from the user via the input unit (S206). When the client apparatus 100 has not received the message transmission request (S206 “No”), the client apparatus 100 repeatedly performs the same determination. When the client apparatus 100 accepts the message transmission request (S206 “Yes”), the client apparatus 100 transmits the destination, title, article text, and time limit to the mail server 200 (S207), and ends the process.

  If the client apparatus 100 determines in S201 described above that the mail type is not a reply-needed mail (S201 “No”), it sends the mail type (normal mail) and a message creation request to the mail server. (S208). Note that the normal mail is mail other than the reply required mail.

  Subsequently, the client device 100 determines whether or not a general message creation screen has been received (S209). The general message creation screen is a screen for creating the above-described normal mail. When the client apparatus 100 has not received the general message creation screen (S209 “No”), the client apparatus 100 repeatedly performs the same determination. When receiving the general message creation screen (S209 “Yes”), the client device 100 displays the general message creation screen on the display unit (S210). Subsequently, the client device 100 accepts input of a destination, a title, and an article text (S211).

  Subsequently, the client device 100 determines whether a message transmission request has been received from the user via the input unit (S212). If the client apparatus 100 has not received the message transmission request (S212 “No”), the client apparatus 100 repeatedly performs the same determination. When the client device 100 accepts the message transmission request (S212 “Yes”), the client device 100 transmits the destination, title, article text, and time limit to the mail server 200 (S213), and ends the processing.

(Reply email viewing process)
Next, with reference to FIG. 9, the flow of the reply mail browsing process in S114 shown in FIG. 7 described above will be described. FIG. 9 is a diagram showing a flow of the reply mail browsing process. Note that the user requests a reminder for the reply required email transmitted by the user through the following processing.

  As illustrated in FIG. 9, the client device 100 transmits a user ID and an acquisition request for a reply mail browsing screen to the mail server 200 (S301).

  Subsequently, the client device 100 determines whether or not a notification indicating that the dunning target mail does not exist has been received (S302). If the client device 100 has not received a notification that the dunning target mail does not exist (S302 “No”), the client device 100 subsequently determines whether or not a reply mail browsing screen has been received (S303). . If the client apparatus 100 has not received the reply mail browsing screen (S303 “No”), the client apparatus 100 returns to S302 described above.

  When the client apparatus 100 receives the reply mail browsing screen (S303 “Yes”), the client apparatus 100 displays the reply mail browsing screen on the display unit (S304). Subsequently, the client device 100 determines whether or not a mail is selected from the user via the input unit and a dunning request is accepted (S305). When the mail is selected and the dunning request is not accepted (S305 “No”), the client device 100 repeatedly performs the same determination.

  When the mail is selected and the dunning request is accepted (S305 “Yes”), the client device 100 acquires the message ID from the header of the selected mail (S306). Then, the client device 100 transmits the user ID, the message ID of the selected mail, and the dunning request to the mail server 200 (S307), and ends the process.

  In S302 described above, when the client apparatus 100 receives a notification that there is no reminder mail (S302 “Yes”), the reply mail does not exist or all the answers have arrived. (S308), and the process ends.

(Processing by mail server 200)
Next, the overall flow of processing by the mail server 200 will be described with reference to FIG. FIG. 10 is a diagram showing the overall flow of processing by the mail server. The following processing is executed by the mail server 200 communicating with the client device 100 using the function of the web browser.

  As illustrated in FIG. 10, the control unit 270 of the mail server 200 repeatedly performs the same determination when the mail display request is not received (S401 “No”). When receiving a mail display request from the client device 100 (S401 “Yes”), the control unit 270 of the mail server 200 subsequently determines whether or not the user has been authenticated to the client device 100 ( S402). When the control unit 270 determines that the authentication has not been completed (S402 “No”), the specifying unit 271 transmits a user ID and password input screen to the client device 100 (S403).

  Subsequently, the specifying unit 271 determines whether a user ID and a password are received (S404). When the identification unit 271 has not received the user ID and password (S404 “No”), the determination is repeated. When receiving the user ID and password (S404 “Yes”), the specifying unit 271 performs authentication using the authentication DB 220 (S405).

  If the authentication has failed (in the case of authentication NG) (S406 “No”), the specifying unit 271 creates an authentication error screen and transmits it to the client device 100 (S407), and ends the process. On the other hand, when the authentication by the specifying unit 271 is successful (in the case of authentication OK) (S406 “Yes”), the transmission unit 274 executes a mail display screen creation process (S408) and transmits a mail transmission screen. (S409). The mail display screen creation process will be described later with reference to FIGS.

  Subsequently, the control unit 270 determines whether a message creation request and a mail type have been received (S410). When the control unit 270 determines that the message creation request and the mail type are received (S410 “Yes”), the creation screen generation unit 275 executes a message creation screen generation process (S411). The message creation screen generation process will be described later with reference to FIGS.

  Subsequently, the control unit 270 determines whether or not an acquisition request for the reply mail browsing screen has been received (S412). When the control unit 270 determines to receive an acquisition request mail viewing screen acquisition request (S412 “Yes”), the browsing screen generation unit 276 executes an answer request mail browsing screen generation process (S413). The reply mail browsing screen generation process will be described later with reference to FIGS. 15 and 16.

  Then, the control unit 270 determines whether or not a logout request has been received from the client device 100 (S414). When the control unit 270 receives a logout request from the client device 100 (S414 “Yes”), the process ends. On the other hand, when the logout request has not been received from the client device 100 (S414 “No”), the control unit 270 returns to S410 described above and determines whether the message creation request and the mail type have been received. Do.

  In S402 described above, if the control unit 270 has been authenticated (S402 “Yes”), the control unit 270 proceeds to the process in step S408 described above.

  If the message creation request and the mail type have not been received in S410 described above (S410 “No”), the control unit 270 proceeds to the determination in S414 described above.

  In S412, the control unit 270 proceeds to the determination of S414 as described above when the response request mail browsing screen acquisition request is not received (S412 “No”).

(Message creation screen generation process)
Next, the flow of message creation screen generation processing will be described with reference to FIGS. FIG. 11 is a diagram showing the flow of the message creation screen generation process. FIG. 12 is a diagram illustrating an example of an answer required message creation screen. FIG. 13 is a diagram illustrating an example of a header structure of a mail. FIG. 14 is a diagram illustrating an example of a general message creation screen. Note that the mail server 200 receives a reply required mail or a general mail from the client apparatus 100 through the following processing.

  When the message creation request and the mail type are received from the client device 100, the creation screen generation unit 275 generates a message ID and a header as shown in FIG. 11 (S501), and whether or not the mail type is a reply required mail. (S502).

  If the mail type is reply required mail (S502 “Yes”), the creation screen generation unit 275 generates a reply required message creation screen (S503) and transmits the reply required message creation screen to the client device 100. (S504). FIG. 12 shows an example of an answer required message creation screen. For example, at the top of the reply required message creation screen, operation buttons for designating "send", "save" and "logout" processes and a link for displaying a mail display screen to be described later are provided. . In addition, at the bottom of the reply required message creation screen, “To” and “CC (Carbon Copy)” to enter the address, “Subject” to enter the title of the mail, “Time limit” to enter the reply deadline, An input area such as an “article input screen” for inputting the text is provided. For example, when the user inputs an e-mail article, an answer deadline, or the like in the corresponding part on the reply message creation screen shown in FIG. 12 and operates the “Send” operation button, the deadline, destination, title, and article body are changed to the mail server 200. Will be sent to.

  Subsequently, the creation screen generation unit 275 determines whether a time limit, a destination, a title, and an article body have been received (S505). If the deadline, destination, title, and article text have not been received (S505 “No”), the creation screen generation unit 275 repeatedly performs the same determination. When the creation screen generation unit 275 receives the time limit, the destination, the title, and the article body (S505 “Yes”), the creation screen generation unit 275 adds the time limit to the mail header (S506). FIG. 13 shows an example of the header. For example, the creation screen generation unit 275 provides an area “Deadline (time limit)” for describing the time limit in the header of the mail. Then, the creation screen generation unit 275 adds, for example, a 2011/2/5 time limit to the “Deadline (time limit)”.

  Subsequently, the creation screen generation unit 275 generates a unique message ID, and records this message ID, transmission date, deadline, and reminder flag (OFF) in the mail management DB 250 (S507). Subsequently, the creation screen generation unit 275 generates an answer DB 230 in association with the message ID, records the address in the answerer ID of the answer DB 230, and records 0 in the answerer flag of the answer DB 230 (S508).

  Subsequently, the creation screen generation unit 275 transmits the header, the title, and the article to a destination (folder, directory, etc.) (S509). Subsequently, the creation screen generation unit 275 records the message ID, title, and article text in the transmission field of the user ID corresponding to the mail transmission source and destination and the reception field of the address in the mail DB 240 (S510). The process ends.

  In S502 described above, the creation screen generation unit 275 generates a general message creation screen assuming that the mail type is a general mail when the mail type is not a reply-needed mail (S502 “No”). S511). Then, the creation screen generation unit 275 transmits a general message creation screen to the client device 100 (S512). FIG. 14 shows an example of a general message creation screen. For example, at the top of the general message creation screen, operation buttons for designating “send”, “save”, and “logout” processes and a link for displaying a mail display screen to be described later are provided. Also, at the bottom of the general message creation screen, there are “Destination” and “CC (Carbon Copy)” for entering the recipient, “Subject” for entering the title of the email, and “Article entry screen” for entering the text of the email article Input areas are provided. For example, when the user inputs a mail article or the like in the corresponding part on the general message creation screen shown in FIG. 14 and operates the “Send” operation button, the destination, title, and article body are transmitted to the mail server 200. Become.

  Subsequently, the creation screen generation unit 275 determines whether a destination, a title, and an article body have been received (S513). If the destination, title, and article text have not been received (S513 “No”), the creation screen generation unit 275 repeatedly performs the same determination. On the other hand, when receiving the destination, title, and article body (S513 “Yes”), the creation screen generation unit 275 determines whether this mail is a reply mail for another mail (S514).

  When the other mail is a reply mail (S514 “Yes”), the creation screen generation unit 275 determines whether the message ID of the original article exists in the mail management DB 250 (S515). That is, if the message ID of the original article included in the reply mail in S514 can be acquired from the mail management DB 250, the creation screen generation unit 275 can determine that the reply mail describes the reply to the reply required mail. When the message ID of the original article exists in the mail management DB 250 (S515 “Yes”), the creation screen generation unit 275 acquires the sender ID (respondent ID) from the mail header (S516). Then, the creation screen generation unit 275 sets the answer flag corresponding to the respondent ID of the answer DB 230 corresponding to the message ID of the original article to ON (that is, 1), and records the answer date (S517).

  Then, the creation screen generation unit 275 performs the processes of S509 and S510 described above, and ends the process. In S514 described above, the creation screen generation unit 275 proceeds to the above-described processing of S509 when the other mail is not a reply mail (S514 “No”). In S515 described above, when the message ID of the original article is not in the mail management DB 250 (S515 “No”), the creation screen generation unit 275 proceeds to the process of S509 described above.

(Answer mail required screen generation process)
Next, referring to FIGS. 15 and 16, the flow of the reply mail browsing screen generation process will be described. FIG. 15 is a diagram illustrating the flow of the reply mail browsing screen generation process. FIG. 16 is a diagram illustrating an example of a reply mail browsing screen. Note that the mail server 200 accepts a reminder request for a reply-needed mail from the client device 100 through the following processing.

  As illustrated in FIG. 15, the browsing screen generation unit 276 acquires the message ID of the outgoing mail corresponding to the user ID from the mail DB 240 (S601). Note that the user ID in S601 is the user ID received in S404 shown in FIG. 10 described above. Subsequently, the browsing screen generation unit 276 determines whether or not the message ID is included in the mail management DB 250 (S602). When the message ID is included in the mail management DB 250 (S602 “Yes”), the browsing screen generation unit 276 acquires the time limit corresponding to the message ID from the mail management DB 250 (S603).

  Subsequently, the browsing screen generation unit 276 acquires the destination of the client device 100 whose answer flag is 0 (unanswered) in the answer DB 230 corresponding to the message ID (S604). Then, the browsing screen generation unit 276 determines whether or not there is a destination whose answer flag is 0 (S605). In other words, the browsing screen generation unit 276 determines whether or not a destination whose answer flag is 0 can be acquired from the answer DB 230. When there is a destination whose answer flag is 0 (S605 “Yes”), the browsing screen generation unit 276 acquires the transmission date / time and title of the message ID from the mail DB 240 (S606).

  Subsequently, the browsing screen generation unit 276 generates a response list mail browsing screen including a message list with a selection button for each message, the number of unanswered persons of each message, and a deadline, and the client device 100 (viewing display person) ) (S607). FIG. 16 shows an example of the reply mail browsing screen. In the upper part of the reply mail browsing screen, an operation button for designating “request for reminder” and “logout” and a link for displaying a mail display screen to be described later are provided. In addition, a display area for displaying a user ID as a destination, a transmission date and time, a subject, a reply time limit, and the number of unanswered persons is provided for each reply required mail message at the bottom of the reply required mail browsing screen. For example, when the user browsing the browsing screen operates the dunning request button on the reply-requested mail browsing screen shown in FIG. 16, a dunning request for a message in which a check is inserted in the check box on the left side of the destination is sent to the mail server 200. Will be sent to.

  Subsequently, the browsing screen generation unit 276 determines whether a user ID, a message ID, and a reminder request have been received (S608). When the user ID, the message ID, and the dunning request are not received (S608 “No”), the browsing screen generation unit 276 repeats the same determination. On the other hand, when receiving the user ID, the message ID, and the dunning request (S608 “Yes”), the browsing screen generating unit 276 turns on the dunning flag of the mail management DB 250 for the message ID ( S609), the process ends.

  In S602 described above, when the message ID is not included in the mail management DB 250 (S602 “No”), the browsing screen generation unit 276 transmits a notification that the dunning target mail does not exist to the client device 100 ( S610). And the browsing screen production | generation part 276 complete | finishes a process. Further, in S605 described above, when there is no destination whose answer flag is 0 (S605 “No”), the browsing screen generation unit 276 performs the process of S610 described above and ends the process.

(Message display screen creation process)
Next, the flow of message display screen creation processing will be described with reference to FIGS. Note that the mail server 200 transmits mail to the client device 100 through any of the following processes. FIG. 17 is a diagram showing the flow of the mail display screen creation process (1). FIG. 18 is a diagram illustrating an example of a mail display screen. FIG. 19 is a diagram showing the flow of the mail display screen creation process (2). FIG. 20 is a diagram illustrating an example of a mail display screen. FIG. 21 is a diagram showing the flow of the mail display screen creation process (3). FIG. 22 is a diagram illustrating an example of a mail display screen. FIG. 23 is a diagram showing the flow of the mail display screen creation process (4). FIG. 24 is a diagram illustrating an example of a mail display screen. Note that which of the mail display screen creation processes (1) to (4) the mail server 200 executes is left to, for example, an administrator setting or a user setting. Either a single operation may be used, or a plurality of operations may be mixed, such as for each user, for each time zone, or for each time limit for reply required mail.

(Mail display screen creation process (1))
First, the flow of the mail display screen creation process (1) will be described with reference to FIGS. In the mail display screen creation process (1), an example is shown in which a reply required mail for which a reply is requested is displayed in a font different from that of other mails.

  As shown in FIG. 17, the second acquisition unit 273 acquires a mail corresponding to the user ID from the mail DB 240 (S701). For example, the second acquisition unit 273 acquires a predetermined number of emails from the latest emails received by the user. This predetermined number is determined by an administrator setting or a user setting (for example, a display font size of the display unit). Note that the user ID in S701 is the user ID received in S404 shown in FIG. 10 described above.

  Subsequently, the first acquisition unit 272 determines whether the message ID of the acquired mail is included in the mail management DB 250 (S702). When the message ID is included in the mail management DB 250 (S702 “Yes”), the first acquisition unit 272 determines whether there is a reminder flag ON among mails included in the mail management DB 250. It is determined whether or not (S703). The first acquisition unit 272, when there is a message with the dunning flag turned ON (S703 “Yes”), among the mails with the dunning flag ON, the respondent ID (recipient) whose answer flag is 0 answers It is determined whether or not it exists in the DB 230 (S704). When the answerer ID (recipient) whose answer flag is 0 is in the answer DB 230 (S704 “Yes”), the first obtaining unit 272 obtains the dunning mail font from the setting DB 260 (S705). Subsequently, the transmission unit 274 generates a mail display screen using the font acquired in S705 as the font of the mail whose answer flag is 0 (S706), and ends the process. For example, the transmission unit 274 generates a mail display screen in which only the font of mail with an answer flag of 0 is set to bold gothic, mails are sorted in order of due date, and mails with an answer flag of 0 are sorted in order of close to deadline. .

  In S702 described above, the first acquisition unit 272 sets the determination result in S702 to “No” when the message ID is not included in the mail management DB 250. Then, the transmission unit 274 sorts the mails acquired from the mail DB 240 in order of date to generate a mail display screen (S707), and ends the process. In S703 described above, when the first acquisition unit 272 determines that there is no reminder flag ON (S703 “No”), the transmission unit 274 performs the process of S707 described above. The process ends. In S704 described above, if the first acquisition unit 272 determines that the answerer ID (recipient) whose answer flag is 0 is not in the answer DB 230 (S704 “No”), the sending unit 274 Then, the process of S707 described above is performed and the process is terminated.

  FIG. 18 shows an example of a mail display screen generated by the processing of FIG. 17 described above. A mail display area is provided at the bottom of the mail display screen generated by the processing of FIG. In this mail display area, received mail corresponding to the screen size is displayed as shown in FIG. The answer-required mail for which the response is prompted is displayed in a font different from that of the other mails and is displayed above the other mails. As a result, it is possible to make the user recognize a reply-needed email that is prompting a reply at first glance by simply performing a simple process of changing the font. In the mail display area, for example, when the user selects any received mail, the text of the selected mail is displayed on the entire surface of the mail display area.

  In the upper part of the mail display screen generated by the processing of FIG. 17, as shown in FIG. 18, “normal message creation”, “answer required message creation”, “response required email browsing”, and “logout” processing are performed. An operation button for designating is provided. For example, when a “normal message creation” button is operated on the mail display screen, a normal message creation request is transmitted to the mail server 200. Further, when the “Create response required message” button is operated on the mail display screen, a response request message generation request is transmitted to the mail server 200. When the message creation request is received, the mail server 200 executes the above-described message creation screen generation process shown in FIG. In addition, when the “browse reply mail” button is operated on the mail creation screen, a reply mail browsing request is transmitted to the mail server 200. When the reply mail browsing request is received, the mail server 200 executes the reply mail browsing screen generation process shown in FIG. When a “logout” button is operated on the mail creation screen, a logout request is transmitted to the mail server 200. When the logout request is received, the mail server 200 executes logout processing.

(Mail display screen creation process (2))
Next, the flow of the mail display screen creation process (2) will be described using FIG. 19 and FIG. In the mail display screen creation process (2), an example is shown in which an answer-required mail for which an answer is prompted is displayed with a background color different from other mails. Note that the processing of S801 to S804 shown in FIG. 19 is the same as the processing of S701 to S704 shown in FIG.

  That is, as shown in FIG. 19, the second acquisition unit 273 acquires a mail corresponding to the user ID from the mail DB 240 (S801). Subsequently, the first acquisition unit 272 determines whether or not the message ID of the acquired mail is included in the mail management DB 250 (S802). If the first acquisition unit 272 determines that the message ID is not included in the mail management DB 250 (S802 “No”), the transmission unit 274 sorts the mails acquired from the mail DB 240 in order of date. A mail display screen is generated (S807). And the transmission part 274 complete | finishes a process.

  On the other hand, when the message ID is included in the mail management DB 250 (S802 “Yes”), the first acquisition unit 272 selects the mail with the dunning flag ON among the mails included in the mail management DB 250. It is determined whether or not there is (S803). If the first acquisition unit 272 determines that there is no reminder flag ON (S803 “No”), the transmission unit 274 performs the above-described processing of S807 and ends the processing.

  On the other hand, the first acquisition unit 272, when there is a message with the dunning flag ON (S803 “Yes”), among the mails with the dunning flag ON, the respondent ID (recipient) whose answer flag is 0 Is determined in the answer DB 230 (S804). When the first acquisition unit 272 determines that the answerer ID (recipient) whose answer flag is 0 is not in the answer DB 230 (S804 “No”), the transmission unit 274 performs the process of S807 described above. To finish the process.

  And the process of S805 and S806 shown in FIG. 19 differs from the process shown in FIG. 17 mentioned above.

  That is, when the answerer ID (recipient) whose answer flag is 0 is in the answer DB 230 (S804 “Yes”), the first obtaining unit 272 obtains the background color of the reminder mail from the setting DB 260 (S805). ). Subsequently, the transmission unit 274 generates a mail display screen in which the background color acquired in S805 is the background color of the mail whose answer flag is 0 (S806), and ends the process. For example, the transmission unit 274 generates a mail display screen in which only the background color of emails with an answer flag of 0 is blue, the emails are sorted in order of due date, and the emails with an answer flag of 0 are sorted in order from the nearest due date. .

  FIG. 20 shows an example of a mail display screen generated by the process of FIG. 19 described above. In the upper part of the mail display screen generated by the process of FIG. 19, "normal message creation", "answer required message creation", "response required mail browsing" and "logout" processes are specified as shown in FIG. An operation button is provided. This point is the same as that of FIG. 18 described above, but is different from that described below. In the mail display area provided in the lower part of the mail display screen, as shown in FIG. 20, the reply-required mail for which the reply is requested is displayed with a background color different from other mails. Yes. Thereby, rather than changing the font, it is possible to make the user recognize an answer-needed email that is prompted for an answer at first glance.

(Mail display screen creation process (3))
Next, the flow of the mail display screen creation process (3) will be described using FIG. 21 and FIG. In the mail display screen creation process (3), an example is shown in which the title of the reply required mail is displayed in another area. Note that the processing of S901 to S904 shown in FIG. 21 is the same as the processing shown in FIG. 17 and FIG.

  That is, as shown in FIG. 21, the second acquisition unit 273 acquires a mail corresponding to the user ID from the mail DB 240 (S901). Subsequently, the first acquisition unit 272 determines whether or not the message ID of the acquired mail is included in the mail management DB 250 (S902). When the first acquisition unit 272 determines that the message ID is not included in the mail management DB 250 (S902 “No”), the transmission unit 274 sorts the mails acquired from the mail DB 240 in order of date. The mail display screen is generated (S908). And the transmission part 274 complete | finishes a process.

  On the other hand, when the message ID is included in the mail management DB 250 (S902 “Yes”), the first acquisition unit 272 selects the mail with the dunning flag ON among the mails included in the mail management DB 250. It is determined whether or not there is (S903). If the first acquisition unit 272 determines that there is no reminder flag ON (S903 “No”), the transmission unit 274 performs the above-described processing of S908 and ends the processing.

On the other hand, the first acquisition unit 272, when there is a message with the dunning flag ON (S903 “Yes”), among the mails with the dunning flag ON, the respondent ID (recipient) whose answer flag is 0 Is determined in the answer DB 230 (S904). If the first acquisition unit 272 determines that the answerer ID (recipient) whose answer flag is 0 is not in the answer DB 230 (S904 “No”), the sending unit 274 performs the process of S908 described above. To finish the process.

  And the process of S905-S907 shown in FIG. 21 differs from the process shown in FIG.17 and FIG.18 mentioned above.

  That is, when the answerer ID (recipient) whose answer flag is 0 is in the answer DB 230 (S904 “Yes”), the first acquisition unit 272 selects the title of the mail whose answer flag is 0 from the mail DB 240. Obtain (S905). Subsequently, the transmission unit 274 creates an answer required mail display area (S906). Then, the transmission unit 274 generates a mail display screen in which the title (link) of the mail whose answer flag is 0 is created in the reply required mail display area created in S906 (S907), and ends the process.

  FIG. 22 shows an example of a mail display screen generated by the processing of FIG. 21 described above. In the upper part of the mail display screen generated in the process of FIG. 21, the processes of “Generate normal message”, “Create reply message”, “View reply mail” and “Logout” are specified as shown in FIG. An operation button is provided. This is the same as FIG. 18 and FIG. 20 described above, except for the points described below. In the mail display area provided at the lower part of the mail display screen, an answer required mail display area is created as shown in FIG. Furthermore, as shown in FIG. 22, in the answer required mail display area, the title of the answer required mail for which the response is prompted is displayed. As a result, it is possible to make the user recognize the reply-needed mail for which the user is prompted for a reply more reliably than when the font is changed or the background color is applied. In FIG. 22, only one reply-needed mail is displayed, but when there are a plurality of mails, it is preferable to sort them by time limit and display them in order.

(Mail display screen creation process (4))
Next, the flow of the mail display screen creation process (4) will be described with reference to FIGS. In the mail display screen creation process (4), an example is shown in which the title and text of the reply required mail are displayed in separate areas. Note that the processing of S1001 to S1004 shown in FIG. 23 is the same as the processing shown in FIG. 17, FIG. 19, or FIG.

  That is, as shown in FIG. 23, the second acquisition unit 273 acquires a mail corresponding to the user ID from the mail DB 240 (S1001). Subsequently, the first acquisition unit 272 determines whether the message ID of the acquired mail is included in the mail management DB 250 (S1002). When the first acquisition unit 272 determines that the message ID is not included in the mail management DB 250 (S1002 “No”), the transmission unit 274 sorts the mails acquired from the mail DB 240 in order of date. The mail display screen is generated (S1009). And the transmission part 274 complete | finishes a process.

  On the other hand, when the message ID is included in the mail management DB 250 (S1002 “Yes”), the first acquisition unit 272 selects the mail whose dunning flag is ON among the mails included in the mail management DB 250. It is determined whether or not there is (S1003). If the first acquisition unit 272 determines that there is no reminder flag ON (S1003 “No”), the transmission unit 274 performs the process of S1009 described above and ends the process.

  On the other hand, the first acquisition unit 272, when there is a reminder flag ON (S1003 "Yes"), among the mail whose reminder flag is ON, the respondent ID (recipient) whose answer flag is 0 Is determined in the answer DB 230 (S1004). When the first acquisition unit 272 determines that the answerer ID (recipient) whose answer flag is 0 is not in the answer DB 230 (“No” in S1004), the transmission unit 274 performs the process of S1009 described above. To finish the process.

  And the process of S1005-S1008 shown in FIG. 23 differs from the process shown in FIG.17, FIG.19 or FIG.21 mentioned above.

  That is, when the answerer ID (recipient) whose answer flag is 0 is in the answer DB 230 (S1004 “Yes”), the first acquisition unit 272 has the shortest deadline among the mails whose answer flag is 0. A thing is acquired (S1005). Subsequently, the first acquisition unit 272 acquires, from the mail DB 240, the title and text of the e-mail that has the closest expiration date acquired in S1005 (S1006). Subsequently, the transmission unit 274 creates an answer required mail display area (S1007). Then, the transmission unit 274 generates a mail display screen describing the title (link) and the text of the mail with the shortest deadline among the mails with the reply flag set to 0 in the reply required mail display area created in S1007 ( S1008), the process is terminated.

  FIG. 24 shows an example of a mail display screen generated by the process of FIG. 23 described above. In the upper part of the mail display screen generated by the process of FIG. 23, as shown in FIG. 24, “normal message creation”, “answer required message creation”, “response required email viewing”, and “logout” processing are specified. An operation button is provided. This is the same as FIG. 18, FIG. 20, or FIG. Also, as shown in FIG. 24, an answer required mail display area is created in the mail display area provided at the bottom of the mail display screen. This is the same as FIG. 22 described above. On the other hand, as shown in FIG. 24, not only the title of the reply required mail for which the reply is requested but also the contents of the mail are displayed in the reply required mail display area. Thereby, not only can the user be surely recognized the reply-required mail for which the response is prompted, but also the user can easily confirm the content of the reply-required mail for which the response is prompted. This eliminates the need for selecting an answer required mail.

[Effects of Example 1]
As described above, the mail server 200 manages the reply status of reply-needed mail in the mail management DB 250, for example. When the mail server 200 receives a mail display request (login request) from the client device 100, the mail server 200 generates and returns a mail display screen of the user of the client device 100 that is the transmission source of the mail display request. At this time, the mail server 200, when there is an unanswered mail for which a response is prompted in the received mail of the user who is the transmission source of the mail display request, An e-mail display screen is generated so that it is displayed in a form different from e-mail. For example, an e-mail display screen is generated for changing the font and background color of the e-mail and displaying the e-mail title and e-mail text. In other words, the mail server 200 corresponds to the case where there is an unanswered reply-required mail that is being prompted for a reply at the timing when a login for referring to the received mail is received from the user. Encourage email recognition. As described above, since the sender of the reply-needed mail does not need to send the reminder mail to the unanswered user, according to the first embodiment, the burden on the sender of the reply-needed mail can be reduced as much as possible. it can.

  In addition, for example, when there is an unanswered mail requiring reply for which an answer is requested, the mail server 200 is higher than other mails on the user interface such as a browser screen. Generate information to be displayed. This makes it possible for the user to easily recognize unanswered emails that need to be answered.

  In the above-described first embodiment, the mail server 200 has been explained as a case where the sender of the reply required mail is prompted and the reply required mail that has not been answered is displayed in a form different from other mails. The following processing may be performed. For example, when the mail server 200 receives a login for referring to the received mail from the user and there is an unanswered reply-requested mail, the other mail is sent even if there is no prompt for the reply-requested mail. It may be displayed in a different form. In this case, the mail server 200 extracts unanswered reply-needed mail received by the user. In this case, it is not necessary to store the “reminder flag” in the mail management DB 250. As a result, it is possible to reduce the burden on the sender of the reply required mail and to prompt the reply of the reply required mail recipient.

  In addition, if there is an answer-needed mail that has not been answered and the reply deadline has been exceeded at the timing when the login is received from the user, the mail server 200 can identify other mails without prompting the reply-needed mail. You may make it display in a different form. In this case, the mail server 200 refers to the mail DB 240 and the mail management DB 250, and extracts the reply-necessary mails received by the user that are not answered and have exceeded the reply deadline regardless of the “Dunning flag”. To do. As a result, if there are unanswered ones, the responses of the recipients of the emails that need to be answered are suppressed while suppressing the annoyance of the recipients of the emails requiring the answer, compared to the case where they are always displayed in a different form from other emails. Can be urged.

  Note that the mail server 200 differs from other mails even if there is no response to the reply-required mail if there is a reply-needed mail that is unanswered and the reply deadline is approaching at the timing when the login is received from the user. You may make it display in a form. For example, if there is an unanswered e-mail requiring an answer three days before or before the deadline for answering at the timing of accepting login from the user, the corresponding e-mail is displayed in a form different from other e-mails. In this case, the mail server 200 refers to the mail DB 240 and the mail management DB 250 and extracts, among the reply-necessary mails received by the user, unanswered and three days before the reply deadline regardless of the “Dunning flag”. . As a result, if there are unanswered responses that have exceeded the response deadline, the response by the recipient of the email that requires the response will be made within the response deadline as much as possible, rather than displaying it in a different form than other emails. Can be.

  In addition, for example, when there is an unanswered mail requiring reply for which an answer is requested, the mail server 200 is higher than other mails on the user interface such as a browser screen. Generate information to be displayed. This makes it possible for the user to easily recognize unanswered emails that need to be answered.

  Hereinafter, other embodiments of the mail server, mail processing program, mail processing method, and mail system disclosed in the present application will be described.

(1) Processing Using E-mail Software of Client Device In the above-described first embodiment, the case where the client device 100 such as the client device 100A accesses the mail server 200 using a web browser has been described. That is, the mail server 200 has been described with respect to the case where, when the user accepts login, the mail server generates a mail display screen and transmits the mail display screen to the accessing client device 100. However, e-mail software (mailer) implemented in the client device 100 has been described. It is also possible to use. For example, information for identifying a user is transmitted to the mail server 200 at the timing when the mailer is activated on the client device 100 or at a predetermined interval. Then, the mail server 200 replies to the client device 100 in which the mailer has been activated with information such as information that can identify an unanswered reply-required mail that has been urged for a reply together with the received mail. . The mailer of the client device 100 identifies and displays the corresponding mail from the mail in the local folder based on the information that can identify the unanswered mail requiring reply that is being prompted for a reply.

  For example, FIG. 25 shows an example of a display form of an email requiring reply. FIG. 25 is a diagram illustrating an example of a display form of an email requiring reply. As shown in FIG. 25, when the client device 100 receives the information identifying the unanswered reply-needed mail together with the received mail, the client apparatus 100 already separates from the mailer screen 2 displayed as the user interface on the display 1. Opens the reply mail that has been received, and the screen 3 showing the contents of the reply mail is displayed. For example, the contents of the reply required email are displayed in a separate window. This makes it possible for the user to easily recognize unanswered e-mails that require an answer. Although an example in which the window is displayed behind the already displayed window has been described here in consideration of user convenience, the present invention is not limited to this.

(2) Device Configuration, etc. For example, the functional block configuration of the mail server 200 shown in FIG. 1 is conceptual and does not necessarily need to be physically configured as illustrated. For example, the specifying unit 271, the first acquisition unit 272, the second acquisition unit 273, and the transmission unit 274 of the control unit 270 illustrated in FIG. 1 may be integrated functionally or physically. Further, the answer DB 230 and the mail management DB 250 shown in FIG. 1 may be integrated. In this way, for example, all or part of the functional blocks of the mail server 200 shown in FIG. 1 are functionally or physically distributed or integrated in arbitrary units according to various loads or usage conditions. Can be configured.

(3) Mail processing program The various processes executed by the mail server 200 described in the above embodiment can be realized by executing a predetermined program on a computer having an electronic circuit, an integrated circuit, or the like, for example. . In the following, an example of a computer that executes a mail processing program that realizes the same function as the processing executed by the mail server 200 described in the above embodiment will be described with reference to FIG. FIG. 26 is a diagram illustrating an example of a computer that executes a mail processing program.

  As illustrated in FIG. 26, the computer 300 includes, for example, a memory 301 and a CPU (Central Processing Unit) 302. Further, the computer 300 includes a hard disk drive interface 303 and an optical disk drive interface 304 as shown in FIG. As shown in FIG. 26, the computer 300 includes a serial port interface 305, a video adapter 306, and a network interface 307. The computer 300 connects these units 301 to 307 via a bus 308.

  As shown in FIG. 26, the memory 301 includes a ROM (Read Only Memory) and a RAM (Random Access Memory). The ROM stores a boot program such as BIOS (Basic Input Output System). The hard disk drive interface 303 is connected to the hard disk drive 309 as shown in FIG. The optical disk drive interface 304 is connected to the optical disk drive 310 as shown in FIG. For example, a removable storage medium such as an optical disk is inserted into the optical disk drive 310. As shown in FIG. 26, the serial port interface 305 is connected to a mouse 400 and a keyboard 500, for example. As shown in FIG. 26, the video adapter 306 is connected to a display 600, for example.

  Here, as shown in FIG. 26, the hard disk drive 309 stores, for example, an OS (Operating System), application programs, program modules, and program data.

  That is, the mail processing program according to the disclosed technology is stored in, for example, the hard disk drive 309 as a program module in which a command to be executed by the computer 300 is described. That is, a program module describing a procedure for executing the same processing as that of the control unit 270 described in the above-described embodiment is stored in the hard disk drive 309. For example, this program module describes a procedure for executing the same processing as the processing shown in FIGS.

  Data used for processing by the mail processing program is stored as program data in, for example, the hard disk drive 309. For example, this program data corresponds to various types of information stored in the authentication DB 220, the answer DB 230, the mail DB 240, the mail management DB 250, and the setting DB 260 described in the above embodiment.

  Then, the CPU 302 reads out the program modules and program data stored in the hard disk drive 309 to the RAM as necessary, and executes the same processing (FIGS. 10 to 24) as described in the above-described embodiment. Execute.

  Note that the program module and program data related to the mail processing program are not limited to being stored in the hard disk drive 309, and may be stored in, for example, the optical disk drive 310, which is a removable storage medium. In this case, the CPU 302 reads program modules and program data related to the mail processing program via the optical disc drive 310. Alternatively, the program module and program data relating to the mail processing program may be stored in another computer connected via a network (LAN (Local Area Network), WAN (Wide Area Network), etc.). In this case, the CPU 302 reads the program module and program data related to the mail processing program via the network interface 307.

  Instead of the CPU 302, for example, an electronic circuit such as an MPU (Micro Processing Unit) or an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array) can be used. Further, instead of the memory 301, a semiconductor memory device such as a flash memory can be used.

10 network 100A, 100B, 100C client device 200 mail server 210 communication control unit 220 authentication DB
230 Answer DB
240 Mail DB
250 Mail management DB
260 Setting DB
300 Computer 301 Memory 302 CPU
303 Hard Disk Drive Interface 304 Optical Disk Drive Interface 305 Serial Port Interface 306 Video Adapter 307 Network Interface 308 Bus 309 Hard Disk Drive 400 Mouse 500 Keyboard 600 Display

Claims (7)

Inquiry mail identification information for uniquely identifying an inquiry mail requesting an answer, user identification information for uniquely identifying a user who is the destination of the inquiry mail, and an answer indicating whether the user is replying to the inquiry mail A first storage unit for storing the situation in association with each other;
A second storage unit for storing the user identification information in association with a plurality of pieces of mail information including the inquiry mail transmitted to the user;
A specifying unit for specifying the user identification information of the user when receiving a mail acquisition request for requesting at least part of the plurality of mail information from a terminal operated by the user;
A first acquisition unit that acquires, from the first storage unit, inquiry mail identification information that is the inquiry mail identification information associated with the identified user identification information and that has not yet been answered. When,
Mail information including mail information corresponding to the acquired inquiry mail identification information is at least part of the plurality of mail information associated with the identified user identification information from the second storage unit. A second acquisition unit to acquire;
Of the mail information acquired by the second acquisition unit, the mail information corresponding to the inquiry mail identification information acquired by the first acquisition unit is acquired by the second acquisition unit. A mail server, comprising: a transmission unit that transmits information to be displayed in a form different from other mail information. The first storage unit further stores a reply deadline for the inquiry mail in association with the inquiry mail identification information,
The first acquisition unit is the unanswered inquiry mail identification information associated with the user identification information of the user specified by the specifying unit, the answer status is unanswered, and the The mail server according to claim 1, wherein inquiry mail identification information that exceeds a reply deadline is acquired from the first storage unit. The first storage unit further stores a reminder status of an answer to the inquiry mail in association with the inquiry mail identification information;
The first acquisition unit is the unanswered inquiry mail identification information associated with the user identification information of the user specified by the specifying unit, the answer status is unanswered, and the The mail server according to claim 1 or 2, wherein inquiry mail identification information whose dunning status is dunning is obtained from the first storage unit.   The transmission unit transmits information for displaying mail information corresponding to the inquiry mail identifier acquired by the first acquisition unit in a display area higher than the other mail information. The mail server described in. On the computer,
When a mail acquisition request for requesting at least part of a plurality of mail information is received from a terminal operated by the user, the user who is the transmission source of the mail acquisition request is identified,
Inquiry mail identification information for uniquely identifying an inquiry mail requesting an answer, user identification information for uniquely identifying a user who is the destination of the inquiry mail, and an answer indicating whether the user is replying to the inquiry mail The inquiry mail identification information associated with the user identification information of the user who has performed the identification, with reference to the first storage unit that associates and stores the situation, and the answer situation is Obtain unanswered inquiry mail identification information from the first storage unit,
Corresponding to the user identification information of the specified user from the second storage unit that stores the user identification information and a plurality of mail information including the inquiry mail transmitted to the user in association with each other The mail information including at least a part of the plurality of attached mail information and including the mail information corresponding to the acquired inquiry mail identification information is acquired from the second storage unit,
Among the mail information acquired from the second storage unit, the mail information corresponding to the inquiry mail identification information acquired from the first storage unit is included in the mail information acquired from the second storage unit. A mail processing program for executing each processing to display in a form different from the mail information. Computer
When a mail acquisition request for requesting at least part of a plurality of mail information is received from a terminal operated by the user, the user who is the transmission source of the mail acquisition request is identified,
Inquiry mail identification information for uniquely identifying an inquiry mail requesting an answer, user identification information for uniquely identifying a user who is the destination of the inquiry mail, and an answer indicating whether the user is replying to the inquiry mail The inquiry mail identification information associated with the user identification information of the user who has performed the identification, with reference to the first storage unit that associates and stores the situation, and the answer situation is Obtain unanswered inquiry mail identification information from the first storage unit,
Corresponding to the user identification information of the specified user from the second storage unit that stores the user identification information and a plurality of mail information including the inquiry mail transmitted to the user in association with each other The mail information including at least a part of the plurality of attached mail information and including the mail information corresponding to the acquired inquiry mail identification information is acquired from the second storage unit,
Among the mail information acquired from the second storage unit, the mail information corresponding to the inquiry mail identification information acquired from the first storage unit is included in the mail information acquired from the second storage unit. A mail processing method characterized by executing each processing to display the mail information in a form different from the mail information. A mail system having a client device and a mail server,
The mail server is
Inquiry mail identification information for uniquely identifying an inquiry mail requesting an answer, user identification information for uniquely identifying a user who is the destination of the inquiry mail, and an answer indicating whether the user is replying to the inquiry mail A first storage unit for storing the situation in association with each other;
A second storage unit for storing the user identification information in association with a plurality of pieces of mail information including the inquiry mail transmitted to the user;
A specifying unit for specifying the user identification information of the user when receiving a mail acquisition request for requesting at least part of the plurality of mail information from a terminal operated by the user;
A first acquisition unit that acquires, from the first storage unit, inquiry mail identification information that is the inquiry mail identification information associated with the identified user identification information and that has not yet been answered. When,
Mail information including mail information corresponding to the acquired inquiry mail identification information is at least part of the plurality of mail information associated with the identified user identification information from the second storage unit. A second acquisition unit to acquire;
Of the mail information acquired by the second acquisition unit, the mail information corresponding to the inquiry mail identification information acquired by the first acquisition unit is acquired by the second acquisition unit. A transmission unit that transmits information to be displayed in a form different from other mail information,
The client device is
A mail system comprising: a receiving unit that receives the information transmitted from the mail server; and a display unit that displays the information received by the receiving unit.

Images