JP2014167767A - Mail system, control method thereof, and program; and mail server, control method thereof, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a mechanism in which when a plurality of information processors receive an electronic mail, they can receive an appropriate electronic mail according to account information including an electronic mail reception method.SOLUTION: A client device 101 transmits an electronic mail acquisition request together with account information containing a reception method that is set in a mailer of the client device 101. A mail server 102 receives the electronic mail acquisition request from the client device 101, obtains the mail from a mail box according to the reception method contained in the account information which is transmitted together with the acquisition request, and transmits it to the client device 101.

Description

  The present invention relates to e-mail management, and in particular, when receiving e-mails with a plurality of information processing apparatuses, a mail system capable of receiving appropriate e-mails according to account information set in a mailer, and The present invention relates to a control method, a program, a mail server, a control method thereof, and a program.

  2. Description of the Related Art Conventionally, information is transmitted between users by transmitting and receiving electronic mail (hereinafter, mail) using a mailer installed in an information processing apparatus (hereinafter, client apparatus). As a mechanism of such a mail system, the following is common. First, mail transmitted from the client device is stored in a mail server. The client device makes a mail acquisition request to the mail server. When receiving a mail acquisition request from the client device, the mail server transmits the stored mail to the client device. When the reception of the mail is completed, the client device transmits a received mail deletion request to the mail server, and the mail server receives the deletion request and deletes the mail. This structure prevents a large amount of mail from being stored in the mail server.

  However, when the mail stored in the mail server is to be received by a plurality of client devices, the above mechanism causes a problem. For example, when the first client device receives mail, the client device makes a deletion request to the mail server, so that the second and subsequent client devices cannot receive the mail. In other words, since the mail is stored only in the client device that first receives the mail, the same mail cannot be browsed by a plurality of client devices.

  In order to solve such a problem, a mechanism that prevents a deletion request from being sent from the client device to the mail server can be considered. However, if a deletion request is not made from the client device to the mail server, mail continues to be accumulated in the mail server, which puts pressure on the storage capacity of the mail server. Therefore, when such a mechanism is employed, the user manually deletes the mail on the mail server when reception is completed in all the client devices used by the user.

  In order to solve this problem, in Patent Document 1 below, an e-mail based on log information including which e-mail terminal has received which e-mail is sent to the e-mail, and the e-mail is received. Then, based on the log information included in the e-mail, it is determined whether or not the e-mail has been received by all e-mail terminals, and if received, a mechanism for sending the e-mail deletion request to the mail server Is disclosed.

  In Patent Document 2 below, the mail management device stores and manages information indicating the unread / read status of mail for each mail delivery destination terminal, and the mail management device receives a mail delivery request from the terminal. Then, when the unread status of the mail of the terminal that requested the delivery is changed to the read status, and the information indicating the unread / read status of all the terminals becomes the read status, the mail is sent from the mail management device. A mechanism for deletion is disclosed.

JP 2007-26268 A JP 2004-48391 A

  As described above, when a plurality of client devices wants to receive mail, it is necessary to store the mail in the mail server. However, the storage capacity of the mail server is determined by a mechanism such as Patent Document 1 or Patent Document 2. It is possible to construct a mail system that can receive mails with a plurality of client devices without pressure.

  However, although Patent Document 1 and Patent Document 2 reduce the capacity of mail stored in the mail server, there is a problem that all mail stored in the mail server must be received.

  There are also types of client devices that receive mail. For example, a general PC that is a fixed terminal, a mobile phone that is a mobile terminal, a tablet terminal, and the like. A fixed terminal can perform high-speed communication by LAN (Local Area Network) connection, but a mobile terminal must use a low-speed mobile communication system. Therefore, there is a problem that it takes a very long time to receive all the mails stored in the mail server.

  Furthermore, the storage capacity of the hard disk or the like provided in the mobile terminal is smaller than that of the fixed terminal. This is because as a result of obtaining the portability of the mobile terminal, the size of the mobile terminal must be reduced, and a hard disk or the like having a large storage area cannot be provided. For this reason, if all the mails stored in the mail server are received, there is a problem that the storage capacity of the mobile terminal is compressed.

  Further, in mail systems such as Patent Document 1 and Patent Document 2, even if the mail is received by the first client device, if the mail is stored in the mail server, the second and subsequent client devices can be used. A problem occurs in which the mail must be received. Since the mail received by the first client device is highly likely to be confirmed by the user, it is often unnecessary to receive it by the second and subsequent client devices. For this reason, in order not to reduce the storage capacity of the mobile terminal and not to take a long time for communication, a mechanism for receiving only mail that has not been received by any device (hereinafter, new mail) is required.

  In addition, because there is a difference in communication speed and storage capacity between fixed terminals and mobile terminals, client devices such as fixed terminals may receive all mail, and client devices such as mobile terminals may only receive new mail. is there. In this case, if the mail is deleted from the mail server immediately after receiving the mail as in the prior art, there arises a problem that the client device that wants to receive all the mail cannot receive the mail. This is because when a new mail is received by the mobile terminal, the mail is deleted from the mail server, and the fixed terminal cannot receive the mail. In other words, even if multiple client devices that receive mail specify different reception methods (receive all mail, receive only new mail), there must be a mechanism to establish that reception method. is there.

  The present invention has been made in view of the above problems, and an object of the present invention is to select an appropriate electronic device according to account information including an electronic mail receiving method when an electronic mail is received by a plurality of information processing apparatuses. To provide a mechanism that can receive mail.

  In order to achieve the above object, a mail system according to the present invention is a mail system including an information processing apparatus that transmits and receives electronic mail and a mail server that stores electronic mail. A setting accepting unit that accepts settings of account information including a mail receiving method, and an e-mail acquisition request sent to a destination related to the account information accepted by the setting accepting unit, including the account information. An e-mail acquisition requesting means for sending to the server; and a receiving means for receiving the e-mail requested by the e-mail acquisition requesting means, wherein the mail server stores the e-mail sent to the destination; When an e-mail acquisition request is received from the information processing apparatus, the account transmitted together with the acquisition request According to the reception method included in the report, an e-mail acquisition unit that acquires an e-mail transmitted to the destination related to the account information from the storage unit, and an e-mail acquired by the e-mail acquisition unit is sent to the information processing apparatus. And e-mail transmitting means for transmitting.

  According to the present invention, it is possible to cause the information processing apparatus to receive an e-mail according to the receiving method simply by setting account information including the e-mail receiving method in the information processing apparatus. It is possible to receive an appropriate mail while reducing labor.

It is a lineblock diagram showing an example of mail system 100 in an embodiment of the present invention. It is a block diagram which shows an example of the hardware constitutions of the client apparatus 101 and the mail server 102 which are shown in FIG. It is a block diagram which shows an example of the module structure of the client apparatus 101 and the mail server 102 which are shown in FIG. It is a flowchart which shows the flow of the process of the account registration in embodiment of this invention. 5 is a configuration diagram showing an example of an account registration screen 500. FIG. 4 is a configuration diagram showing an example of a configuration of an account table 600 stored in a mail server 102. FIG. It is a flowchart which shows the flow of a series of processes of the mailer in embodiment of this invention. 5 is a configuration diagram showing an example of an account setting screen 800. FIG. It is a flowchart which shows the detail of the mail reception process shown in FIG. FIG. 11 is a continuation flowchart of the mail reception process of FIG. 10. FIG. It is a schematic diagram which shows an example of the mail header at the time of giving Receiving-Count to the mail without Receiving-Count. It is a schematic diagram which shows an example of the mail header at the time of incrementing the value of Receiving-Count with the mail with Receiving-Count. It is a flowchart which shows the detail of the mail list acquisition process shown in FIG. FIG. 5 is a configuration diagram showing an example of a mail list 1400 and a schematic diagram showing an example when a mail list of new mail is generated from the mail list 1400. It is a flowchart which shows the detail of the received mail count-up process shown in FIG. It is a schematic diagram which shows the outline | summary of this invention. It is a schematic diagram which shows the outline | summary of this invention.

  Hereinafter, an example of an embodiment of the present invention will be described with reference to the drawings.

  FIG. 1 is a diagram showing an example of a system configuration of a mail system 100 according to the present invention. A mail system 100 according to the present invention includes a client device 101 (client device 101a, client device 101b, client device 101c) and a mail server 102, which are connected via a network 103 such as a LAN (Local Area Network). They are connected so that they can communicate with each other. The configuration of various terminals or servers connected on the network 103 in FIG. 1 is an example, and it goes without saying that there are various configuration examples depending on the application and purpose.

  The client device 101 (information processing device) is a device that communicates with the mail server 102 and transmits and receives electronic mail (hereinafter, mail) through a mailer. The client device 101 may be a personal computer or a mobile terminal such as a smartphone or a mobile phone. The mailer is stored in the ROM 202 or the external memory 211 shown in FIG. 2 described later, and the CPU 201 reads out to the RAM 203 and performs various operations in accordance with instructions from the user.

  The mailer performs creation, transmission / reception, display, and the like of mail according to operations from the user. In this embodiment, the client apparatus 101a, the client apparatus 101b, and the client apparatus 101c are assumed to be the client apparatus 101 used by one user. Therefore, each client device 101 is set to receive mail stored in a mailbox related to the user account.

  The mail server 102 is a device that stores and manages the mail transmitted from the client apparatus 101 for each destination, and transmits the mail in response to a request from the client apparatus 101. In the mail server 102, a mailbox is prepared for each user account, and the mail is stored in the account mailbox indicated by the mail destination. Then, the mail of the mailbox corresponding to the account set in the client apparatus 101 is transmitted to the client apparatus 101. In communication with the client apparatus 101, transmission and reception are performed using protocols such as SMTP (Simple Mail Transfer Protocol) and POP (Post Office Protocol). The communication protocol is not limited to this. It suffices if mail can be transmitted and received between the client apparatus 101 and the mail server 102.

  The client device 101 may include the configuration of the mail server 102, or the mail server 102 may include the configuration of the client device 101.

  FIG. 2 is a diagram illustrating a hardware configuration of various terminals according to the embodiment of the present invention.

  The CPU 201 comprehensively controls each device and controller connected to the system bus 204.

  Further, the ROM 202 or the external memory 211 (storage means) realizes a BIOS (Basic Input / Output System) or an operating system program (hereinafter referred to as OS) that is a control program of the CPU 201 and functions executed by each server or each PC. For this purpose, various programs described later are stored. The RAM 203 functions as a main memory, work area, and the like for the CPU 201.

  The CPU 201 implements various operations by loading a program necessary for execution of processing into the RAM 203 and executing the program.

  An input controller (input C) 205 controls input from a pointing device such as a keyboard 209 or a mouse (not shown).

  A video controller (VC) 206 controls display on a display device such as a CRT display (CRT) 210. The display device may be a liquid crystal display as well as a CRT. These are used by the administrator as needed.

  The memory controller (MC) 207 is an adapter to a hard disk (HD), flexible disk (FD) or PCMCIA card slot for storing boot programs, browser software, various applications, font data, user files, editing files, various data, and the like. Controls access to an external memory 211 such as a card-type memory connected via the.

  A communication I / F controller (communication I / FC) 208 is connected to and communicates with an external device via a network, and executes communication control processing in the network. For example, Internet communication using TCP / IP is possible.

  For example, the CPU 201 can perform display on the CRT 210 by executing outline font rasterization processing on a display information area in the RAM 203. In addition, the CPU 201 enables a user instruction with a mouse cursor (not shown) on the CRT 210.

  Various programs used by the client apparatus 101 and the mail server 102 of the present invention to execute various processes to be described later are recorded in the external memory 211 and are executed by the CPU 201 by being loaded into the RAM 203 as necessary. Is. Furthermore, definition files and various information tables used by the program according to the present invention are stored in the external memory 211.

  Next, a functional configuration diagram showing module configurations of the client apparatus 101 and the mail server 102 will be described with reference to FIG. Note that the module configurations of the various terminals or servers in FIG. 3 are merely examples, and it goes without saying that there are various configuration examples depending on applications and purposes.

  The client apparatus 101 includes a storage module 301, a screen display module 302, a transmission / reception module 303, a mail deletion request module 304, a web browser module 305, and an account setting module 306.

  The storage module 301 is a module that stores mail created, transmitted and received by the mailer. The mail stored by the storage module 301 is stored in the external memory 211 or the like of the client device 101, and is read by the storage module 301 as necessary.

  The screen display module 302 is a module for displaying various information such as mail and screen on the CRT 210 of the client apparatus 101. In particular, in the present embodiment, the account registration screen 500 shown in FIG. 5 is displayed and inputs and operations from the user are accepted.

  The transmission / reception module 303 is a module for transmitting mail generated by the client apparatus 101 to the mail server 102 and receiving mail stored in the mail server 102. In addition, when transmitting / receiving information to / from the mail server 102 via the Web browser module 305 described later, the transmitting / receiving module 303 is operated to exchange information.

  The mail deletion request module 304 is a module for transmitting a mail deletion request received from the mail server 102 to the mail server 102.

  The web browser module 305 is a module for displaying the web page generated by the screen generation module 318 provided in the mail server 102.

  The account setting module 306 is a module for setting an account for the mailer of the client apparatus 101. By setting an account in the mailer of the client apparatus 101, it becomes possible to receive mail transmitted to the mail address related to the account. The account includes a user ID and a password. Based on this information, user authentication is performed by the mail server 102 and a corresponding account is specified. In particular, in the present embodiment, it is possible to register a plurality of user IDs indicating mail reception methods for one account. The reception method indicates acquisition conditions for received mail. For example, there are a reception method in which only a mail that has not been received by the client device 101 other than the client device 101 that receives mail (hereinafter, new mail), a reception method in which all mails are received as usual, and the like. The user can receive an appropriate mail only by setting the user ID indicating this reception method in the mailer account.

  The mail server 102 includes a storage module 311, a mailbox management module 312, a user authentication module 313, a transmission / reception module 314, a mail deletion module 315, a mail header update module 316, a mail deletion determination module 317, a screen generation module 318, and a mail list generation module. 319, a reception method determination module 320, and a table management module 321.

  The storage module 311 (storage means) is the same as the storage module 301 of the client apparatus 101 described above. The mail received by the transmission / reception module 314 described later, the mail updated by the mail header update module 316, and the like are stored.

  The mailbox management module 312 is a module for storing and managing the mail stored in the storage module 311 for each account. When a mail reception request is received by a later-described transmission / reception module 314, an account from which mail is acquired is specified, the mail is acquired from the mailbox of the account, and passed to the transmission / reception module 314.

  The user authentication module 313 is a module for authenticating whether or not the user of the mail system 100 is based on the user ID and password transmitted from the client apparatus 101.

  The transmission / reception module 314 is a module for performing transmission / reception of mail with the client apparatus 101. A screen generated by a screen generation module 318 to be described later is transmitted, and information input by a Web browser module 305 provided in the client apparatus 101 is received.

  The mail deletion module 315 is a module that deletes a mail that is determined to be deleted by a mail deletion determination module 317 described later when a mail deletion request is received from the mail deletion request module 304 of the client apparatus 101.

  The mail header update module 316 is a module for updating the mail header of the mail to be transmitted when the mail is transmitted in response to the mail acquisition request from the client apparatus 101. The mail header includes information (transmitted information) indicating the number of times the mail is transmitted from the mail server 102 to the client apparatus 101, that is, the number of client apparatuses 101 that have received the mail. Added or incremented. As another embodiment, the mail header includes information indicating the remaining number of times to be transmitted to the client apparatus 101, and these may be added or decremented when the mail is transmitted.

  When the mail deletion determination module 317 receives a mail deletion request transmitted from the mail deletion request module 304 of the client apparatus 101, information indicating the number of mails to be received associated with the account and the number of times transmitted to the client apparatus 101. Based on the above, it is a module that determines whether or not to delete. If the remaining number of times to be transmitted to the client apparatus 101 is set in the mail header, it may be determined whether or not to delete depending on whether or not the remaining number has expired.

  The screen generation module 318 is a module that generates the account registration screen 500 shown in FIG. 5 in response to a request from the client apparatus 101. The generated screen is a Web page written in HTML or the like and can be displayed by the Web browser module 305 of the client apparatus 101.

  The mail list generation module 319 is a module that generates a list of mails (hereinafter, mail list) that the mail server 102 transmits to the client apparatus 101 when a mail acquisition request is received from the client apparatus 101. The mail list includes “Message-id” that is a mail header for identifying the mail. The client apparatus 101 compares the “Message-id” of the mail list with the “Message-id” of the received mail to determine whether there is a new mail to be received. Since the mail list generation module 319 generates a list of mails to be transmitted, if only new mails are transmitted, a mail list including only new mails is generated.

  The reception method determination module 320 is a module that determines a mail reception method from the user ID transmitted from the client apparatus 101. As described above, a reception method is set for each user ID. Therefore, it is determined based on an account table 600 described later which reception method is used. Based on the determination result, an appropriate mail is transmitted to the client apparatus 101.

  The table management module 321 is a module for storing and updating an account table 600 of FIG. Various tables are stored in the external memory 211 and read out to the RAM 203 as necessary.

  Next, account registration processing according to the embodiment of the present invention will be described with reference to the flowchart shown in FIG. A program for causing the client apparatus 101 and the mail server 102 to execute this processing may be prepared as a mailer or a part of an application installed in the client apparatus 101 and the mail server 102, or as an add-on program. The program may be prepared separately from the mailer or application.

  The process shown in FIG. 4 is a process for registering an account of a user who uses the mail system 100. In the present embodiment, the description will be made as a mode in which the user registers the account himself, but the administrator may register or another user may register.

  First, in step S <b> 101, the client apparatus 101 transmits an account registration screen acquisition request to the mail server 102 in order to register an account.

  In step S102, the mail server 102 receives an account registration screen acquisition request from the client apparatus 101. In step S103, the mail server 102 generates an account registration screen 500 as shown in FIG. 5 in the form of a Web page. In the present embodiment, since the account registration screen 500 is displayed by the Web browser provided in the client apparatus 101, the account registration screen 500 is generated in the Web page format, but the present invention is not limited to this. In step S <b> 104, the mail server 102 transmits the generated account registration screen 500 to the client device 101.

  In step S <b> 105, the client apparatus 101 receives the account registration screen 500 transmitted from the mail server 102. In step S106, the client apparatus 101 displays the received account registration screen 500 on the Web browser and accepts an input from the user.

  In the account registration screen 500, an input of an account of a user who uses the mail system 100 is accepted. The account is information indicating one record of the account table 600 to be described later, and includes an email address, a password, a user ID for each reception method, and the number of received emails.

  In the mail address input field 501 and the password input field 502, the input of the mail address and password to be used is accepted. The user ID input field 507 accepts input of a user ID for each reception method. The user ID (normal) input field 503 in the user ID input field 507 accepts an input of a user ID indicating a reception method for receiving all mails stored in the account mailbox. The received number input field 506 accepts an input of the number of client apparatuses 101 that wants to receive mail.

  In the user ID input field 507, the user ID (new arrival 1) input field 504 receives mail (new mail) that has not been sent to any client device 101 among mails stored in the account mailbox. An input of a user ID indicating a method is accepted. In the user ID input field 507, the user ID (new arrival 2) input field 505 is similar to the user ID (new arrival 1) input field 504, and any of the client devices 101 among the mails stored in the account mailbox. An input of a user ID indicating a reception method for receiving a mail that has not been transmitted (new mail) is accepted. However, the user ID (new arrival 2), unlike the user ID (new arrival 1), also updates information indicating the number of received mails (hereinafter, received mail) other than the new mail. The information indicating the number of received units is “Receiving-Count” (transmitted information) included in the mail header of the mail. By counting up “Receiving-Count”, it is possible to identify the number of times that the client apparatus 101 has received the mail, that is, the number of times the mail has been transmitted from the mail server to the client apparatus 101. When sending mail, this “Receiving-Count” is incremented and sent. However, when only new mail is sent, “Receiving-Count” of mail other than new mail is not incremented. This is to allow a user to switch from a user ID (new arrival 1) to a user ID (normal), and to receive received mail that has not been received even when switching. The user ID (new arrival 2) is a reception method in which “Receiving-Count” is incremented assuming that only new mail is received and other mail is received. There is such a difference between the user ID (new arrival 1) and the user ID (new arrival 2).

  In step S107, the client apparatus 101 determines whether or not the registration button 508 on the account registration screen 500 has been pressed to register information regarding the input account. If it is determined that the registration button 508 has been pressed, the process proceeds to step S108. If it is not determined that the registration button 508 has been pressed, that is, if the registration button 508 has not been pressed, the process waits until the registration button 508 is pressed.

  In step S <b> 108, the client apparatus 101 transmits various information input on the account registration screen 500 to the mail server 102. In step S109, the mail server 102 receives various information transmitted from the client apparatus 101. In step S110, the received information is registered in the account table 600 shown in FIG.

  The account table 600 (see FIG. 6) stores information on accounts of users who can use the mail system 100. The account table 600 includes a mail address 601, a password 602, a user ID (normal) 603, a user ID (new arrival 1) 604, a user ID (new arrival 2) 605, and the number of received items 606. Each item constituting the account table 600 is the same as each entry field provided in the account registration screen 500.

  In step S <b> 111, the mail server 102 transmits the account registration result to the client apparatus 101. In step S112, the client apparatus 101 receives the account registration result transmitted from the mail server 102, displays a message or the like according to the registration result, and ends the series of processes.

  Next, a series of processing performed by the client apparatus 101 according to the embodiment of the present invention will be described using the flowchart shown in FIG. Note that a program for causing the client device 101 to execute this processing may be prepared as a part of a mailer or application installed in the client device 101, or as an add-on program, or installed separately from the mailer or application. It may be prepared as a prepared program.

  First, in step S <b> 201, the client apparatus 101 activates a mailer program stored in the external memory 211 of the client apparatus 101. In step S202, the client apparatus 101 receives an operation from the user with respect to the mailer.

  In step S203, the client apparatus 101 determines whether or not the operation accepted in step S102 is an account setting instruction. For example, it may be determined whether an account setting button (not shown) is pressed from the mailer menu. If it is an account setting instruction, the process proceeds to step S204. If it is not an account setting instruction, the process proceeds to step S205.

  In step S204, the client apparatus 101 displays an account setting screen 800 as shown in FIG. 8, and receives input from the user (setting receiving means). The account setting screen 800 is a screen for performing various settings for receiving mail from the mail server 102. A user setting field 801 that accepts input of a user name and mail address, a mail server setting field 802 that accepts settings of the mail server 102, and an account setting field 803 that accepts user account settings are provided. In particular, the account setting field 803 includes a user ID field 804 and a password field 805. The user ID column 804 accepts input of a registered user ID according to the receiving method for receiving mail, and the password column 805 accepts input of a registered password. That is, even an existing mailer that has existed in the past can select a mail to be received simply by inputting a user ID registered for each reception method. In order to receive a mail by selecting a reception method, conventionally, it has been necessary to provide a selection column for a reception method in a mailer. However, as in the present invention, if a plurality of user IDs are provided in one account and the reception method is determined for each user ID, the user can change the user ID of the mailer and the user's desired reception method. You will be able to receive emails. When the registration button 806 is pressed, the input content is confirmed and set in the mailer. Then, the process returns to step S202.

  In step S205, the client apparatus 101 determines whether the operation received in step S102 is a mail reception instruction. For example, it may be determined whether or not a mail reception button (not shown) is pressed from the mailer menu. If it is a mail reception instruction, the process proceeds to step S206; otherwise, the process proceeds to step S207.

  In step S <b> 206, the client apparatus 101 executes processing for receiving mail stored in the mail server 102. Details of the mail receiving process are shown in FIGS. When the process ends, the process returns to step S202.

  In step S207, the client apparatus 101 determines whether the operation received in step S202 is a mailer end instruction. For example, it may be determined whether or not an end button (not shown) is pressed from the mailer menu. If it is an end instruction, the process proceeds to step S208; otherwise, the process returns to step S202.

  In step S208, since the client apparatus 101 has received the mailer termination instruction, the client apparatus 101 terminates the mailer and terminates the series of processes.

  Next, mail reception processing performed by the client device 101 and the mail server 102 according to the embodiment of the present invention will be described with reference to FIGS. A program for causing the client apparatus 101 and the mail server 102 to execute this processing may be prepared as a mailer or a part of an application installed in the client apparatus 101 and the mail server 102, or as an add-on program. The program may be prepared separately from the mailer or application.

  The mail reception process is a process of receiving an appropriate mail according to the user ID indicating the reception method set in the mailer of the client apparatus 101.

  First, with reference to FIG. 16 and FIG. 17, the difference in the reception method in the mail reception process will be described.

  16 indicates a case where the user ID (normal) is set in the mailer of the client apparatus 101. A mail acquisition request is made including the account information (user ID, password) set in the mailer of the client apparatus 101 in step S204 described above. When the mail server 102 receives the acquisition request and the user ID included in the account information is a user ID (normal) 603, all mail sent to the destination (mail address) related to the account information is sent to the client. Send to device 101. In the example shown in 1600, the user ID set in the client apparatus 101 is “aaa1@xxxx.co.jp”. It can be seen that the user ID that matches this is the user ID (normal). Therefore, all mails are acquired from the mail box having the mail address “aaa@xxxx.co.jp” corresponding to the user ID, and transmitted to the client apparatus 101. At the time of transmission, “Receiving-Count” in the mail header of all the mails to be transmitted is incremented. Since there is no “Receiving-Count” in new mail, it is added to the mail header. The above is a case where the reception method is normal reception.

  16 indicates a case where the user ID (new arrival 1) is set in the mailer of the client apparatus 101. Similarly to 1600, a mail acquisition request is made including the account information (user ID, password) set in the mailer of the client apparatus 101 in step S204 described above. When the mail server 102 receives the acquisition request and the user ID included in the account information is the user ID (new arrival 1) 604, among the emails sent to the destination (email address) related to the account information, The client apparatus 101 other than the client apparatus 101 that has issued the mail acquisition request acquires mail that has not been received (that is, mail that has not been transmitted to any client apparatus 101) and transmits it to the client apparatus 101. In the example shown in 1610, the user ID set in the client apparatus 101 is “aaa2@xxxx.co.jp”. It can be seen that the user ID that matches this is the user ID (new arrival 1). Therefore, a new mail is acquired from the mail box of the mail address “aaa@xxxx.co.jp” corresponding to this user ID, and is transmitted to the client apparatus 101. At the time of transmission, “Receiving-Count” is added to the mail header of the new mail to be transmitted and incremented. On the other hand, “Receiving-Count” is not updated for received mail other than new mail. The above is the case where the reception method is new arrival 1 reception.

  17 indicates a case where the user ID (new arrival 2) is set in the mailer of the client apparatus 101. Similarly to 1600, a mail acquisition request is made including the account information (user ID, password) set in the mailer of the client apparatus 101 in step S204 described above. When the mail server 102 receives the acquisition request and the user ID included in the account information is the user ID (new arrival 2) 605, among the emails sent to the destination (email address) related to the account information, The client apparatus 101 other than the client apparatus 101 that has issued the mail acquisition request acquires mail that has not been received (that is, mail that has not been transmitted to any client apparatus 101) and transmits it to the client apparatus 101. In the example shown in 1700, the user ID set in the client apparatus 101 is “aaa3@xxxx.co.jp”. It can be seen that the user ID that matches this is the user ID (new arrival 2). Therefore, a new mail is acquired from the mail box of the mail address “aaa@xxxx.co.jp” corresponding to this user ID, and is transmitted to the client apparatus 101. At the time of transmission, “Receiving-Count” is added to the mail header of the new mail to be transmitted and incremented. Also, “Receiving-Count” is incremented for received mail other than new mail. The above is a case where the reception method is new arrival 2 reception.

  As described above, according to the reception method included in the account information set in the client apparatus 101, the mail transmitted to the destination related to the account information can be acquired. Mail can be received by multiple receiving methods without any modification. In this embodiment, there are three types of reception methods: normal reception, new arrival 1 reception, and new arrival 2 reception, but other reception methods may exist. For example, a reception method that receives only emails with attachments attached, a reception method that receives only emails sent to the mailing list, a reception method that receives only emails that are flagged to indicate important emails, etc. Various reception methods can be considered. Hereinafter, this outline will be described in detail.

  First, in step S301, the client apparatus 101 transmits a user ID and password (account information) set in advance to the mailer to the mail server 102 in order to perform user authentication. The user ID and password may be received from the user every time they are received, and the input user ID and password may be transmitted to the mail server 102.

  In step S302, the mail server 102 receives the user ID and password transmitted from the client device 101. In step S303, the received user ID and password, and the account table 600 stored in the external memory 211 of the mail server 102 are displayed. User authentication is performed based on the above. If the combination of the received user ID and password exists in the account table 600, the authentication is OK. Otherwise, the authentication is NG.

  In step S304, the mail server 102 returns the result authenticated in step S203 to the client apparatus 101.

  In step S <b> 305, the client apparatus 101 receives the user authentication result transmitted from the mail server 102. In step S306, the client apparatus 101 determines whether the reception result is authentication OK. If the authentication is OK, the process proceeds to step S308. If the authentication is NG, the process proceeds to step S307.

  In step S307, the client apparatus 101 notifies the user of a connection error because it is authentication NG, ends the mail reception process, and returns the process to the caller.

  In step S308, the client apparatus 101 requests the mail server 102 to acquire a mail list of mails stored in the mail box of the mail server 102 (e-mail acquisition request unit). The mail list is a list of mails including “Message-id” which is a mail header for identifying the mail. Based on this, a mail that has not been received by the client apparatus 101 is specified, and an acquisition request for the mail is transmitted. When requesting acquisition of the mail list, it is transmitted including the account information including the user ID and password set in the mailer of the client apparatus 101.

  In step S <b> 309, the mail server 102 receives the mail list acquisition request transmitted from the client apparatus 101. In step S310, the mail server 102 executes processing for acquiring a mail list corresponding to the reception method indicated by the user ID received in step S302 (e-mail acquisition unit). Details of the mail list acquisition processing are shown in FIG.

  In step S311, the mail server 102 transmits the mail list acquired in step S310 to the client apparatus 101.

  In step S312, the client apparatus 101 receives the mail list transmitted from the mail server 102. In step S313, the client apparatus 101 compares the received mail list with the mail header of the mail received by the client apparatus 101. And check whether there is a new mail to be received. Specifically, a mail having “Message-id” included in the received mail list may be searched from the mailer of the client apparatus 101. If there is a mail having “Message-id” included in the received mail list in the client apparatus 101, it can be determined that the mail has already been received. However, if there is no mail having “Message-id” included in the received mail list, the mail having the “Message-id” is a new mail to be received from the mail server 102. Can be determined.

  In step S314, the client apparatus 101 determines whether there is a new mail to be received as a result of the confirmation in step S313. If it is determined that there is a new mail to be received, the process proceeds to step S316 in FIG. 10, and if it is determined that there is no new mail to be received, the process proceeds to step S315.

  In step S315, the client apparatus 101 notifies the user that there is no new mail to be received. Then, the mail reception process is terminated, and the process is returned to the caller.

  Following FIG. 9, description will be made with reference to FIG. In step S316, the client apparatus 101 repeats the processing of steps S317 to S331 described later for the number of received mails. When the loop for the number of mails to be received is completed, the process exits the loop and proceeds to step S332.

  In step S <b> 317, the client apparatus 101 transmits a mail reception request to be newly received to the mail server 102. Here, a reception request for one mail among the mails to be newly received is transmitted. The order of mail reception is not limited.

  In step S318, the mail server 102 receives a mail reception request transmitted from the client apparatus 101. In step S319, the mail server 102 acquires the mail requested from the client apparatus 101 from the user's mailbox.

  In step S320, the mail server 102 determines whether “Receiving-Count” exists in the mail header of the mail acquired in step S319. If “Receiving-Count” exists, the process proceeds to step S322. If “Receiving-Count” does not exist, the process proceeds to step S321.

  In step S321, since “Receiving-Count” does not exist in the mail header of the mail acquired in step S319, the mail server 102 newly adds “Receiving-Count” to the mail header and sets the value to “1”. (Sent information update means) As shown in the outgoing mail header 1100 of FIG. 11, for a mail that originally does not have “Receiving-Count” in the mail header, “Receiving-Count” is newly added as shown in the mail header information 1101, and “ 1 ”is set. Here, the value of “Receiving-Count” is set to “1” because the mail is transmitted to the client apparatus 101 and is received by one apparatus.

  On the other hand, in step S322, the mail server 102 increments the value of “Receiving-Count” included in the mail header of the mail acquired in step S319 (sent information update unit). As shown in the mail header information 1201 of the outgoing mail header 1200 of FIG. 12, the value “1” is already set as “Receiving-Count” in the mail header of the mail acquired in step S319. That is, it indicates that the mail has already been transmitted to one client apparatus 101. In order to newly transmit a mail this time, “1” is further added to the value of “Receiving-Count”, and the value is changed to “2” as shown in the mail header information 1202. In this way, it is possible to record how many client apparatuses 101 have transmitted. Note that, as described above, the present embodiment will be described as a mechanism in which such information is included in the mail header. However, the information may be different from the mail, or may be generated as an attached file of the mail.

  In step S323, the mail server 102 transmits the mail acquired in step S319 and in which “Receiving-Count” is added or updated in step S321 or step S322 to the client apparatus 101 (e-mail transmission unit).

  In step S324, the client apparatus 101 receives the mail transmitted from the mail server 102 (electronic mail receiving means).

  In step S325, since the reception of the mail is completed in step S324, the client apparatus 101 transmits a deletion request for the mail to the mail server 102. When sending a deletion request, it is sent together with information that can identify the mail. For example, “Message-id” included in the mail header of the mail and account information such as a user ID and a password for specifying the user.

  In step S326, the mail server 102 receives the mail deletion request transmitted from the client apparatus 101.

  In step S327, the mail server 102 acquires the received number 606 set by the user from the account information included in the received deletion request. Specifically, an account is specified from the account table 600 and the user ID included in the received account information, and the received number 606 of the account may be acquired.

  In step S328, the mail server 102 determines whether or not the value of “Receiving-Count” included in the mail header of the mail for which the deletion request has been made is equal to or greater than the received number 606 acquired in step S327 (e-mail). Delete determination means). That is, it is determined whether or not the client apparatus 101 has received the set number of reception units. If the number of receptions set here is received, the deletion request is accepted and the mail is deleted. If not, the deletion request is ignored and the processing of the next mail is started. If the mail stored in the mailbox of the mail server 102 is deleted by such a mechanism, the user simply sets the number of received messages in the mail server 102, and does not press the capacity of the mail server. The same mail can be received by the client apparatus 101. When it is determined that the value of “Receiving-Count” is equal to or greater than the number of received signals 606, the process proceeds to step S329. The process proceeds to step S330.

  In step S329, the mail server 102 deletes the mail requested to be deleted from the mailbox (electronic mail deleting means). Specifically, the mail in the user's mailbox is identified from “Message-id” included in the deletion request received in step S326, and the mail is deleted from the mailbox.

  In step S330, the mail server 102 transmits an execution result corresponding to the deletion request received in step S326 to the client apparatus 101.

  In step S331, the client apparatus 101 receives the execution result transmitted from the mail server 102 and stores it in the RAM 203 as necessary. When the reception is completed, it is determined whether or not all the emails determined as the reception target emails have been received in step S314. If the reception of all the emails has been completed, the process proceeds to step S332. In order to receive unreceived mail, steps S317 to S331 are repeated.

  In step S332, the client apparatus 101 causes the CRT 210 to display the mail list received in step S324 so that the user can view it. When the display is completed, the mail reception process is terminated and the process is returned to the caller. Here, the execution result corresponding to the deletion request received in step S331 is notified to the user. For example, the user can be made aware of the processing contents by notifying the user of a message such as “The device has not been received yet, so it could not be deleted”. In particular, it is possible to grasp the mail that could not be deleted by notifying the subject of the mail that could not be deleted and the “Message-id”. In this case, it is only necessary to include the subject of the mail or “Message-id” in the execution result transmitted in step S330 and notify the information.

  Next, the mail list acquisition process performed by the mail server 102 in the embodiment of the present invention will be described with reference to FIG. The program for causing the mail server 102 to execute this processing may be prepared as a part of an application installed in the mail server 102 or as an add-on program, or as a program installed separately from the application. It may be prepared.

  In step S401, the mail server 102 acquires the user ID included in the account information transmitted in step S308. In step S <b> 402, the mail server 102 specifies an account based on the acquired user ID and the account table 600.

  In step S403, the mail server 102 generates a mail list that is a list of mails transmitted to the destination related to the account specified in step S402. The mail server 102 refers to the mailbox corresponding to the specified account, and acquires “Message-id” in the mail header of the mail stored in the mailbox and “Receiving-Count” in the mail header. To generate a list. For example, a mail list as shown in a mail list 1400 in FIG. 14 is generated. The mail list 1400 includes a message-id 1401 and a receiving-count 1402. If “Receiving-Count” does not exist in the mail header of the mail, “NULL” is stored in Receiving-Count 1402.

  In step S404, the mail server 102 specifies the reception method indicated by the user ID acquired in step S401. More specifically, it is specified whether or not the user ID that matches the user ID acquired in step S401 is in the account specified in step S402. The first record of the account table 600 shown in FIG. 6 will be described as an example. If the user ID acquired in step S401 is “aaa1@xxxx.co.jp”, it is the user ID (normal) 603. It turns out that it is normal reception. Further, if the user ID acquired in step S401 is “aaa2@xxxx.co.jp”, it is the user ID (new arrival 1) 604, and thus it is understood that the reception method is new arrival 1 reception. Further, if the user ID acquired in step S401 is “aaa3@xxxx.co.jp”, it is the user ID (new arrival 2) 605, and thus it is understood that the reception method is new arrival 2 reception.

  In step S405, the mail server 102 determines whether the reception method specified in step S404 is new arrival 1 reception or new arrival 2 reception. If it is determined that the reception method is new arrival 1 reception or new arrival 2 reception, the process proceeds to step S406. If it is determined that the reception method is not new arrival 1 reception or new arrival 2 reception, that is, normal reception, the mail list acquisition process is terminated and the process returns to the caller.

  In step S406, the mail server 102 generates a mail list including only new mail based on the mail list 1400 generated in step S403. More specifically, only a record in which “Receiving-Count 1402” of the mail list 1400 is “NULL” is extracted to generate a mail list of new mail. The mail list transmitted in step S311 described above is not the mail list generated in step S403 but the mail list generated in step S406 when the mail list of new mail is generated in step S406. To do.

  In step S <b> 407, the mail server 102 determines whether to count up “Receiving-Count” of received mail other than new mail. More specifically, it is determined whether or not the reception method specified in step S404 is new arrival 2 reception. If it is determined that the new arrival 2 is received, the process proceeds to step S408. If it is not determined that 2 new arrivals have been received, that is, if 1 new arrival has been received, the mail list acquisition process is terminated and the process returns to the caller.

  In step S <b> 408, the mail server 102 executes a process of counting up “Receiving-Count” of the received mail that has been received by any one of the client apparatuses 101. Details of the received mail count-up process are shown in FIG. When the received mail count-up process ends, the mail list acquisition process ends, and the process returns to the caller.

  Next, received mail count-up processing performed by the mail server 102 in the embodiment of the present invention will be described with reference to FIG. The program for causing the mail server 102 to execute this processing may be prepared as a part of an application installed in the mail server 102 or as an add-on program, or as a program installed separately from the application. It may be prepared.

  First, in step S501, the mail server 102 repeats steps S502 to S506, which will be described later, for the number of received mails in the mail list 1400 generated in step S403. When processing is completed for the number of received mails, the process exits the loop and ends.

  In step S502, the mail server 102 identifies a record whose Receiving-Count 1402 of the mail list 1400 generated in step S403 is not “NULL”, and refers to a mail having a Message-id 1401 of the record from the mailbox.

  In step S503, the mail server 102 increments “Receiving-Count” in the mail header of the mail referred to in step S502. If “Receiving-Count” is “1”, it is incremented to “2”, and if “Receiving-Count” is “2”, it is incremented to “3”.

  In step S504, the mail server 102 acquires the number of received accounts 606 of the account specified in step S402. In step S505, the mail server 102 determines whether or not the value of “Receiving Count” updated in step S503 is equal to or greater than the number of received units 606 acquired in step S504. That is, it is determined whether or not all client apparatuses 101 that the user wants to receive mail have received. If it is determined that the value of “Receiving-Count” is equal to or greater than the number of received units 606, the process proceeds to step S506. If it is determined that the value of “Receiving-Count” is not greater than or equal to the number of received units 606, the process returns to step S501.

  In step S505, the mail server 102 deletes the mail referred to in step S502 from the mailbox because reception has been completed in all the client apparatuses 101. This way, you can keep only the mail you need in your mailbox.

  As described above, according to the present embodiment, only by setting account information including an e-mail reception method in the information processing apparatus, the information processing apparatus receives an e-mail according to the reception method. Therefore, it is possible to receive an appropriate mail while reducing the user's trouble.

  The present invention can be implemented as a system, apparatus, method, program, storage medium, or the like, and can be applied to a system including a plurality of devices. You may apply to the apparatus which consists of one apparatus.

  Note that the present invention includes a software program that implements the functions of the above-described embodiments directly or remotely from a system or apparatus. The present invention also includes a case where the system or the computer of the apparatus is achieved by reading and executing the supplied program code.

  Accordingly, since the functions of the present invention are implemented by computer, the program code installed in the computer also implements the present invention. In other words, the present invention includes a computer program itself for realizing the functional processing of the present invention.

  In that case, as long as it has the function of a program, it may be in the form of object code, a program executed by an interpreter, script data supplied to the OS, and the like.

  Examples of the recording medium for supplying the program include a flexible disk, hard disk, optical disk, magneto-optical disk, MO, CD-ROM, CD-R, and CD-RW. In addition, there are magnetic tape, nonvolatile memory card, ROM, DVD (DVD-ROM, DVD-R), and the like.

  As another program supply method, a browser on a client computer is used to connect to an Internet home page. The computer program itself of the present invention or a compressed file including an automatic installation function can be downloaded from the homepage by downloading it to a recording medium such as a hard disk.

  It can also be realized by dividing the program code constituting the program of the present invention into a plurality of files and downloading each file from a different homepage. That is, a WWW server that allows a plurality of users to download a program file for realizing the functional processing of the present invention on a computer is also included in the present invention.

  In addition, the program of the present invention is encrypted, stored in a storage medium such as a CD-ROM, distributed to users, and key information for decryption is downloaded from a homepage via the Internet to users who have cleared predetermined conditions. Let It is also possible to execute the encrypted program by using the downloaded key information and install the program on a computer.

  Further, the functions of the above-described embodiments are realized by the computer executing the read program. In addition, based on the instructions of the program, an OS or the like running on the computer performs part or all of the actual processing, and the functions of the above-described embodiments can also be realized by the processing.

  Further, the program read from the recording medium is written in a memory provided in a function expansion board inserted into the computer or a function expansion unit connected to the computer. Thereafter, the CPU of the function expansion board or function expansion unit performs part or all of the actual processing based on the instructions of the program, and the functions of the above-described embodiments are realized by the processing.

  The above-described embodiments are merely examples of implementation in carrying out the present invention, and the technical scope of the present invention should not be construed as being limited thereto. That is, the present invention can be implemented in various forms without departing from the technical idea or the main features thereof.

100 mail system 101a client apparatus 101b client apparatus 101c client apparatus 102 mail server 103 network 201 CPU
202 RAM
203 ROM
204 System Bus 205 Input Controller 206 Video Controller 207 Memory Controller 208 Communication I / F (Interface) Controller 209 Input Device 210 Display Device 211 External Memory

Claims (10)

A mail system including an information processing device that transmits and receives electronic mail and a mail server that stores electronic mail,
The information processing apparatus includes:
A setting accepting means for accepting setting of account information including an e-mail receiving method;
An e-mail acquisition request unit that transmits an e-mail acquisition request sent to a destination related to the account information whose setting is received by the setting reception unit, including the account information, to the mail server;
E-mail receiving means for receiving the e-mail requested by the e-mail acquisition request means,
The mail server is
Storage means for storing an email sent to the destination;
Upon receiving an e-mail acquisition request from the information processing apparatus, the e-mail transmitted to the destination related to the account information is acquired from the storage unit according to the reception method included in the account information transmitted together with the acquisition request. Email retrieval means;
An e-mail system comprising: an e-mail transmission unit configured to transmit the e-mail acquired by the e-mail acquisition unit to the information processing apparatus. The storage means stores transmitted information indicating that an email has been transmitted to the information processing apparatus for each email.
The e-mail acquisition unit is not used by an information processing apparatus other than the information processing apparatus among e-mails transmitted to a destination related to the account information according to a reception method included in the account information transmitted together with the acquisition request. 2. The mail system according to claim 1, wherein a received electronic mail is acquired from the storage unit based on the transmitted information. The mail server is
E-mail deletion determination means for determining whether to delete the e-mail corresponding to the transmitted information based on the transmitted information;
The mail system according to claim 2, further comprising: an e-mail deleting unit that deletes the e-mail from the storage unit when the e-mail deletion determining unit determines to delete the e-mail. The transmitted information includes the number of times the electronic mail corresponding to the transmitted information has been transmitted to the information processing device,
The mail server is
Further comprising transmitted information update means for updating the number of transmissions of transmitted information corresponding to the email acquired by the email acquisition means,
The e-mail deletion determination means determines whether to delete an e-mail corresponding to the transmitted information based on the number of transmissions of the transmitted information,
4. The mail system according to claim 3, wherein the e-mail deleting unit deletes the e-mail from the storage unit when it is determined that the e-mail deletion determining unit determines to delete the e-mail.   5. The mail system according to claim 4, wherein the transmitted information update unit updates transmitted information corresponding to an e-mail not acquired by the e-mail acquisition unit according to the reception method. A method for controlling a mail system, comprising: an information processing device that transmits and receives electronic mail; and a storage unit that stores electronic mail transmitted from the information processing device, and a mail server that stores electronic mail,
A setting receiving step in which the setting receiving means of the information processing apparatus receives setting of account information including an e-mail receiving method;
The electronic mail acquisition request means of the information processing apparatus transmits an e-mail acquisition request transmitted to the destination related to the account information whose setting has been received in the setting reception step, including the account information, to the mail server. Email retrieval request step;
An e-mail receiving step in which the e-mail receiving means of the information processing apparatus receives the e-mail requested in the e-mail acquisition request step;
When the e-mail acquisition unit of the mail server receives an e-mail acquisition request from the information processing apparatus, the e-mail acquisition unit transmits the e-mail acquisition request to a destination related to the account information according to the reception method included in the account information transmitted together with the acquisition request. E-mail acquisition step of acquiring the e-mail from the storage means;
A mail system control method, comprising: an e-mail transmission unit of the e-mail server including an e-mail transmission step of transmitting the e-mail acquired in the e-mail acquisition step to the information processing apparatus. An information processing apparatus for sending and receiving electronic mail, and a storage means for storing electronic mail transmitted from the information processing apparatus, and a computer for executing a mail system control method including a mail server for storing electronic mail A program that can be read and executed by a computer,
The information processing apparatus;
A setting accepting means for accepting setting of account information including an e-mail receiving method;
An e-mail acquisition request unit that transmits an e-mail acquisition request sent to a destination related to the account information whose setting is received by the setting reception unit, including the account information, to the mail server;
Function as an email receiving means for receiving an email requested by the email acquisition requesting means;
The mail server,
Upon receiving an e-mail acquisition request from the information processing apparatus, the e-mail transmitted to the destination related to the account information is acquired from the storage unit according to the reception method included in the account information transmitted together with the acquisition request. Email retrieval means;
A computer-readable and executable program that functions as an e-mail transmission unit that transmits an e-mail acquired by the e-mail acquisition unit to the information processing apparatus. A mail server that is connected to an information processing apparatus that transmits and receives e-mails, and that accumulates e-mails.
Storage means for storing an email sent to a destination related to account information including an email reception method;
Upon receiving an e-mail acquisition request from the information processing apparatus, the e-mail transmitted to the destination related to the account information is acquired from the storage unit according to the reception method included in the account information transmitted together with the acquisition request. Email retrieval means;
A mail server comprising: an e-mail transmission unit configured to transmit the e-mail acquired by the e-mail acquisition unit to the information processing apparatus. A mail server for storing e-mail, comprising storage means for storing e-mail sent to a destination related to account information including e-mail reception method, and connected to an information processing apparatus for sending and receiving e-mail. A control method,
When the e-mail acquisition unit of the mail server receives an e-mail acquisition request from the information processing apparatus, the e-mail acquisition unit transmits the e-mail acquisition request to a destination related to the account information according to the reception method included in the account information transmitted together with the acquisition request. E-mail acquisition step of acquiring the e-mail from the storage means;
A mail server control method, comprising: an e-mail transmission unit that transmits an e-mail acquired in the e-mail acquisition step to the information processing apparatus. A mail server for storing e-mail, comprising storage means for storing e-mail sent to a destination related to account information including e-mail reception method, and connected to an information processing apparatus for sending and receiving e-mail. A computer-readable program for causing a computer to execute a control method,
The mail server,
Upon receiving an e-mail acquisition request from the information processing apparatus, the e-mail transmitted to the destination related to the account information is acquired from the storage unit according to the reception method included in the account information transmitted together with the acquisition request. Email retrieval means;
A computer-readable and executable program that functions as an e-mail transmission unit that transmits an e-mail acquired by the e-mail acquisition unit to the information processing apparatus.

Images