JP2004005120A - Automatic mail address database maintenance system - Google Patents

Abstract

Provided is an automatic mail address database maintenance system that can be updated automatically and reliably to a mail address.
A user recognized as a genuine user by an authentication process inputs a mail address, generates an HTTP argument including a session code of a series of processes including the authentication process, and generates the HTTP argument and the input mail address. When there is access from a user having the HTTP argument, the processing request is permitted as an authenticated user, and the input mail address is used as the mail address of the user. A maintenance server 3 for registering in a database was provided.
[Selection diagram] Fig. 1

Description

[0001]
TECHNICAL FIELD OF THE INVENTION
The present invention relates to a large-scale mail address database automatic maintenance system for storing and managing a large number of mail addresses.
[0002]
Although the term "database" is not generally unambiguously defined, it is used herein to refer to a collection of data that is systematically stored and managed. An aggregate of data managed in a table format is also referred to as a database. It should be noted that performing the update process on the hardware storing the data aggregate is also included in the automatic database maintenance according to the present invention.
[0003]
[Prior art]
With the recent development of computers and communication technologies, there are WEB sites for registering users and providing various services to the registered users.
[0004]
On the WEB site, e-mail is often used as a means of contacting a registered user. This is because the electronic mail can quickly send various notifications or information from the web site to the registered user without the registered user accessing the web site.
[0005]
Normally, each WEB site independently manages the e-mail addresses of registered users in order to perform the above-mentioned notification by e-mail. At present, the registered user's e-mail address is entered in the database at the time of registration, and thereafter, when the e-mail address is changed, the e-mail address is updated by contact from the registered user.
[0006]
[Problems to be solved by the invention]
However, nowadays, with the spread of e-mail, one user has more opportunities to change their e-mail address.
[0007]
As described above, in the management of the current mail address of the Web site, in such a case, the mail address database is updated based on a report from the registered user.
[0008]
For this reason, if there is no report from the registered user, there is a problem that data of the old mail address remains in the mail address database, and it becomes impossible to notify the registered user by e-mail or send information. .
[0009]
Also, now a single user often has multiple email addresses. For example, a case where a work mail address and a private mail address are separately provided.
[0010]
In this case, the e-mail addresses that the user mainly checks for the presence or absence of the received e-mail are often concentrated on a specific e-mail address among a plurality of e-mail addresses.
[0011]
Even in such a case, if there is no declaration of an e-mail address from a registered user to mainly check for the presence or absence of an incoming e-mail, there is a problem that notification and transmission of information by e-mail from the WEB site do not actually reach the registered user. Was.
[0012]
In particular, in the current WEB site where the number of registered users is often enormous, it is actually difficult to make all registered users declare each time their e-mail address is changed.
[0013]
For this reason, there has been a problem that the database of e-mail addresses that was initially useful becomes a database with low reliability over time.
[0014]
In order to overcome such an adverse effect, it is conceivable to periodically check a registered user with an e-mail address. However, checking a mail address regularly for a large number of registered users requires a lot of effort and is not practical.
[0015]
In addition, even if the email address is confirmed for all registered users in this way, there is no guarantee that a reliable reply will be received from all the registered users, and it is impossible to maintain a database of accurate email addresses after all. Was.
[0016]
Therefore, the problem to be solved by the present invention is to automatically and surely update a mail address database of a WEB site having a large number of registered users with a reliable mail address. Automatic maintenance system ".
[0017]
[Means for Solving the Problems]
An automatic maintenance system for a mail address database according to the present invention allows a user who is recognized as a genuine user to enter an email address by an authentication process, and generates an HTTP argument including a session code of a series of processes including the authentication process. Storing the HTTP argument and the input mail address, and when there is access from a user having the HTTP argument, permits the processing of the processing request as an authenticated user, and stores the input mail. A maintenance server for registering the address as a mail address of the user in a mail address database.
[0018]
According to the system of the present invention, a user recognized as a genuine user inputs a mail address, and stores the mail address and the processing session code. Next, the maintenance server sends a confirmation mail having an HTTP argument including the processing session code to the mail address. If the user receives the confirmation e-mail and clicks the confirmation button, an access request containing an HTTP argument is sent, thereby ensuring that the e-mail address entered by the user is the e-mail address that is received by the user. It is confirmed. By updating the e-mail address database according to the e-mail address that the user can surely receive, it is possible to maintain only a truly useful e-mail address in the e-mail address database. In addition, the updating process of the e-mail address database is performed every time the user accesses, and the user himself / herself inputs the correct e-mail address. Therefore, from the viewpoint of the WEB site, the e-mail address database can be automatically updated. .
[0019]
The HTTP argument includes time information, and when there is an access from a user having the HTTP argument, the maintenance server compares the time when the HTTP argument was first generated with the time when the next access was made, and a predetermined time. If the mail address is open for more than the time interval, the processing of the user's processing request is not permitted, and the input e-mail address can be deleted.
[0020]
According to the present invention, the reliability of the same processing session of the same user is improved by comparing the time when the HTTP argument is generated and the time when the next access is received with the HTTP argument including time information. Can be.
[0021]
The maintenance server may encrypt or decrypt data including a session code of the processing according to a predetermined algorithm.
[0022]
Also, the maintenance server can change the algorithm with time.
[0023]
According to the present invention, the possibility that the processing session code is read from the HTTP argument is reduced, and misuse can be prevented.
[0024]
The maintenance server deletes the e-mail address when receiving an access message having the HTTP argument and a request to delete the previously input e-mail address or receiving an error message of a user unknown. Is preferred.
[0025]
According to the present invention, it is possible to prevent an incorrect mail address from being registered. Moreover, since only the deletion request having the HTTP argument is permitted, it is possible to prevent the genuine mail address from being deleted.
[0026]
The maintenance server may be configured to output a command for transmitting a notification mail indicating that an e-mail address input by the user is incorrect to a user who is recognized as a genuine user by the authentication processing. .
[0027]
According to the present invention, a user can recognize an erroneous mail address and can know that the mail address has been deleted.
[0028]
Another automatic mail address database maintenance system of the present invention allows a user who is recognized as a genuine user to input an email address in the first authentication process, generates a unique confirmation code, and stores it together with the email address. ,
A maintenance server that allows a user who has been recognized as a genuine user to enter a confirmation code in the second authentication process, and updates a database of e-mail addresses in accordance with the entered confirmation code and the corresponding e-mail address. It is.
[0029]
According to the present invention, by performing the second authentication process, it is possible to confirm again that the user is a genuine registered user before actually processing the user's processing request. Thereby, it is possible to prevent an important process from being erroneously processed.
[0030]
The maintenance server deletes the e-mail address when the access has the confirmation code and has a request to delete the previously input e-mail address or receives an error message of a user unknown. Can be.
[0031]
The maintenance server may be configured to output a command for transmitting a notification mail indicating that an e-mail address input by the user is incorrect to a user who is recognized as a genuine user by the authentication processing. .
[0032]
Another automatic mail address database maintenance system of the present invention displays an e-mail address incorporated in a user ID, and allows the user to confirm whether or not the e-mail address is correct. Allow the processing of the processing request, if the user enters the e-mail address, update the e-mail address database according to the input e-mail address, encrypt the correct e-mail address with a predetermined algorithm and incorporate it into part of the user ID It is characterized by having a maintenance server that allows the user to download.
[0033]
According to the present invention, when a user accesses a WEB site, the registered mail address of the user can be displayed, and the user can confirm the correctness. In addition, when it is not correct, the user is required to input a correct e-mail address, so that the user can update to the correct e-mail address. Since the present invention does not transmit a confirmation mail, it can be used for a WEB site where it is important that the user's operation is easy.
[0034]
The maintenance server may confirm and update the e-mail address and update the user ID at predetermined times or at random times.
[0035]
According to the present invention, the process of confirming / updating the registered mail address is performed at a predetermined number of times or at a random number of times, so that the user's operation is further facilitated.
[0036]
The maintenance server holds an update log for each e-mail address in the e-mail database, and automatically sends a confirmation e-mail to a user whose e-mail address has been updated less than a predetermined number of times or has not been updated for a predetermined period of time. To be transmitted.
[0037]
According to the present invention, it is possible to confirm whether or not a user who is not accessing the WEB site needs an e-mail address, and to arrange the e-mail address database to reduce the required data capacity to a minimum.
[0038]
BEST MODE FOR CARRYING OUT THE INVENTION
Next, an embodiment of the "automatic maintenance system for a mail address database" according to the present invention will be described below.
[0039]
FIG. 1 shows the configuration of an embodiment of an "automatic maintenance system for a mail address database" according to the present invention.
[0040]
In the example of FIG. 1, the WEB site has an automatic maintenance system 1 (hereinafter referred to as "automatic maintenance system 1") for a mail address database and a service server 6 for providing services to registered users.
[0041]
The automatic maintenance system 1 has an authentication server 2, a maintenance server 3, a mail address database 4, and a mail server 5.
[0042]
In addition to the WEB site, there are a client 7, a mail address PC8, and a communication network 9 for communicably connecting the WEB site and the client 7.
[0043]
The authentication server 2 is a server for confirming that a person attempting access is a registered user. As the authentication method of the authentication server 2, any known method such as a password and an electronic certificate can be used. The following describes an example of performing authentication using a user ID and a password.
[0044]
The maintenance server 3 is a server for keeping the e-mail address of the e-mail address database 4 always authentic.
[0045]
The maintenance server 3 performs a preliminary process for updating the mail address database 4 and automatically determines the data in the mail address database 4 when it determines that the mail address database 4 can be updated. Update. This maintenance server 3 plays a central role in the automatic maintenance system 1.
[0046]
A system configuration in which the maintenance server 3 performs an authentication process is also conceivable. In this case, the authentication server 2 forms a part of the maintenance server 3. That is, in this case, the authentication server 2 and the maintenance server 3 become one maintenance server.
[0047]
The mail address database 4 manages the mail addresses of registered users so that they can be searched and updated systematically. As described above, the mail address database 4 may be in any form (a relational database, a table form, or the like).
[0048]
The mail server 5 is a server that sends an electronic mail to a specified mail address.
[0049]
In this embodiment, the mail server 5 transmits a confirmation mail for confirming the mail address. In addition, the mail server 5 receives various requests and various information to the registered user upon receiving a request from the service server 6 or the like. Preferably, the offer can be sent.
[0050]
The client 7 is a computer on the user side that requests the WEB site for various processes. Although only one client 7 is shown in FIG. 1, there are actually many clients 7.
[0051]
The e-mail address PC8 is a computer that receives an e-mail transmitted to the e-mail address specified by the registered user as described later.
[0052]
The email address PC8 matches the computer of the client 7 if the email address specified by the registered user can be received by the computer in use. If the mail address specified by the registered user is a mail address of a third party (a person other than the registered user), the mail address PC8 is a computer different from the client 7.
[0053]
The communication network 9 is a network that connects the client 7 and the WEB site in a communicable manner. The communication network 9 need not be the Internet, but is often the Internet.
[0054]
Next, the flow of processing of the automatic maintenance system 1 will be described. The flow of the process is shown in FIG. 2, and the flow of the process will be more apparent by referring to FIG. 1 as necessary in the following description.
[0055]
First, the user (registered user) accesses the WEB site by the client 7, so that the automatic maintenance of the mail address database 4 according to the present invention is started (FIG. 2; step S100).
[0056]
When the user accesses the WEB site, an authentication process by the authentication server 2 is started to determine whether the user is a genuine registered user (FIG. 2: step S110). In this authentication process, for example, a user ID and a password may be input.
[0057]
If it is recognized that the person attempting access by the authentication processing is a genuine user (registered user), the processing shifts to processing by the maintenance server 3 (see FIG. 1).
[0058]
The maintenance server 3 allows the genuine user (registered user) to input the mail address currently in use (FIG. 2; step S120).
[0059]
In the above description, the maintenance server 3 allows the user to input an e-mail address, but the authentication server 2 allows a genuine user (registered user) to input an e-mail address after authentication, and passes the data of the e-mail address to the maintenance server 3. Are also within the scope of the present invention.
[0060]
Next, the maintenance server 3 generates an HTTP argument including a session code (a code for specifying a processing process, hereinafter referred to as a processing session code) of a series of processing up to and including the authentication processing (FIG. 2; step S130).
[0061]
"Include session code" is because useful information such as time and user type can be included in the HTTP argument in addition to the processing session code. Here, the “HTTP argument” is transmitted and received in order to establish a communication protocol between the WEB server and the client when accessing the WEB site, and information (information such as attributes) added to the end of data representing the communication protocol ). When such an HTTP argument is provided, the information described in the HTTP argument can be extracted from the data of the communication protocol when communication with the client is started by the program on the server side.
[0062]
In the automatic maintenance system 1 of the present invention, it is preferable to encrypt the HTTP argument.
[0063]
In this case, the maintenance server 3 preferably includes information such as time in the processing session code to form a series of data, encrypts the data by a predetermined algorithm, and generates an HTTP argument. When the maintenance server 3 receives the access having the HTTP argument, the maintenance server 3 can decode the HTTP argument by the above algorithm and extract the processing session code or the time information.
[0064]
More preferably, the maintenance server 3 changes the encryption / decryption algorithm at predetermined time intervals.
[0065]
In this case, since the method of encrypting the HTTP argument changes with time, there is an advantage that it becomes extremely difficult for information included in the HTTP argument to leak out.
[0066]
The maintenance server 3 generates the HTTP argument and temporarily stores the processing session code in correspondence with the mail address input by the user (FIG. 2; step S130). Here, "temporarily store" means temporarily storing in a storage unit such as a memory of the maintenance server 3 without writing in the mail address database 4.
[0067]
Subsequently, the maintenance server 3 issues a request to the mail server 5 to transmit a confirmation e-mail to the e-mail address entered by the user (see FIG. 1).
[0068]
The confirmation e-mail of the e-mail address may be an e-mail in which "Your e-mail address is the following e-mail address" is described and the e-mail address entered by the user is described.
[0069]
The confirmation mail of the e-mail address includes a "confirmation button" to be clicked when confirming that the e-mail address is correct, and a button for deleting the e-mail address stored in the maintenance server 3 when confirming that the e-mail address is incorrect. It has a “delete button”.
[0070]
In response to the request from the maintenance server 3, the mail server 5 sends a confirmation mail of the above mail address to the specified mail address (FIG. 2: step S140).
[0071]
The e-mail confirmation mail is sent to the e-mail address PC8 (see FIG. 1). If the mail address is correct, the mail address PC8 matches the client 7, so that the user can receive the confirmation mail within a short time. In particular, when the user is constantly connected to the Internet, the user can access the confirmation mail within a very short time while keeping the screen of the browser accessing the WEB site open.
[0072]
The user opens the e-mail confirmation e-mail and clicks the confirmation button.
[0073]
By clicking the confirmation button, a request to directly access the maintenance server 3 is transmitted from the client 7 (FIG. 2: step S150). This access request is based on the HTTP protocol, and the HTTP session argument includes the processing session code.
[0074]
Upon receiving the access request having the HTTP argument, the maintenance server 3 decrypts the HTTP argument and checks the HTTP argument against the processing session code stored in the maintenance server 3 (FIG. 2; step S160).
[0075]
If there is a matching processing session code, the maintenance server 3 updates the mail address in the mail address database 4 according to the corresponding mail address stored (FIG. 2; step S170).
[0076]
At the same time, processing of the processing request of the user (authentic user and authenticated user) is permitted, and the processing of the processing request is requested to the service server 6 (FIG. 2; step S180).
[0077]
As is clear from the above description of the processing, according to the automatic maintenance system 1 of the present embodiment, when a user accesses a WEB site and can be authenticated as a genuine registered user, the user is regularly used by the user. Enter your email address. A confirmation e-mail is transmitted to the input e-mail address by a different route (e-mail) from the communication by the WEB site. By replying from the confirmation e-mail (access to the WEB site having the HTTP argument), it is possible to confirm that the e-mail address input by the user is the e-mail address used by the user. After confirming that the mail address is the mail address used by the user, the mail address database 4 can be updated according to the mail address.
[0078]
According to the present invention, it is possible to maintain a mail address that reaches a user.
[0079]
In the past, even if a registered user was asked for an email address, the answer was up to the user, and it was not possible to maintain an email address that would ensure that the email would reach the user completely. On the other hand, according to the present invention, the user can cause the processing request to be processed on condition that the e-mail address entered by the user himself is correct. It can be confirmed.
[0080]
In the above description, the case where each registered user registers one e-mail address has been described in mind, but a plurality of e-mail addresses can be registered if necessary.
[0081]
Further, according to the automatic maintenance system of the present invention, the information of the mail address database can be automatically updated every time the user accesses the web site.
[0082]
In particular, in a WEB site having a large-scale mail address database, there is no need to regularly check all registered users, and the mail address database is constantly updated continuously, and the effort on the WEB site side Can be achieved.
[0083]
Next, processing of the embodiment in which time information is included in the HTTP argument will be described with reference to FIG.
[0084]
FIG. 3 shows the flow of processing according to an embodiment of the present invention when time information is included in the HTTP argument.
[0085]
The flowchart of FIG. 3 is the same as the flowchart of FIG. 2 except that steps S162 and S164 are provided. Steps S100 to S180 are exactly the same as the processes denoted by the same reference numerals in FIG. 2, and thus redundant description will be omitted.
[0086]
In this embodiment, information on the time at which the HTTP argument was generated is included in the HTTP argument in addition to the processing session code.
[0087]
When the access having the HTTP argument is received, the maintenance server 3 decrypts the HTTP argument and checks the HTTP argument against the processing session code stored in the maintenance server 3 (FIG. 3; step S160). At the same time, the time at which the HTTP argument was generated and the time at which the access was received are compared, and it is determined whether or not the time is within the time for maintaining the processing session (FIG. 3; step S162). If the process session can be maintained, the process returns to step S160 to update the mail address database and process the process request (FIG. 3; steps S170 and S180).
[0088]
On the other hand, if it is determined in step S162 that the time period during which the processing session can be maintained is exceeded, the processing is stopped, and the previously input mail address is deleted (FIG. 3; step S164). It is preferable to notify the user that the processing has been stopped.
[0089]
This embodiment is preferable for maintaining the continuity of the processing session.
[0090]
That is, if the first access and the second access to the WEB site are opened for a certain time interval or more, the processing is stopped to improve the reliability of security and increase the number of sessions being processed. It can be prevented from becoming too much. Other functions and effects are the same as those in FIG.
[0091]
Next, an embodiment will be described which has a process in a case where there is an error in the mail address input by the registered user.
[0092]
FIG. 4 shows the flow of processing when there is an error in the mail address input by the registered user.
[0093]
In FIG. 4, steps S100 to S140 are completely the same as the processes denoted by the same reference numerals in FIG. 2, and thus redundant description will be omitted.
[0094]
In step S140 of FIG. 4, a confirmation mail is transmitted to the wrong mail address. That is, in FIG. 1, the client 7 and the mail address PC8 are computers of different persons. In this case, a person other than the registered user (hereinafter referred to as “third party”) will see the confirmation email.
[0095]
As described above, the confirmation mail is provided with a "delete button" for requesting deletion of the displayed mail address. When the third party clicks the delete button, a request for deletion is sent to the maintenance server 3 together with the HTTP argument (FIG. 4; step S200).
[0096]
The maintenance server 3 that has received the deletion request decrypts the HTTP argument and compares it with the processing session code stored in the maintenance server 3 (FIG. 4; step S210).
[0097]
When the processing session code of the deletion request matches the processing session code stored in the maintenance server 3, the confirmation e-mail sent to the e-mail address entered by the user is certainly received by the third party, and Confirm that the deletion was requested.
[0098]
Therefore, the maintenance server 3 deletes the e-mail address temporarily stored in the maintenance server 3 and searches the e-mail address database 4, and when the same e-mail address is incorrectly registered as the e-mail address of the user, Deletes the mail address (FIG. 4; step S220).
[0099]
Next, the maintenance server 3 notifies the registered user who has input an incorrect e-mail address that the input e-mail address is incorrect (FIG. 4; step S230).
[0100]
If multiple e-mail addresses are registered, e-mail is sent to the remaining e-mail addresses, a message is displayed on the screen when the subsequent processing is stopped, or a separate mail etc. Can be notified.
[0101]
According to the present embodiment, erroneous data can be deleted from the mail address database, and only the correct mail address can be maintained. Maintaining only correct e-mail addresses can prevent various e-mails from being sent, especially to third parties. The operation and effect in the case of FIG. 2 are the same in this embodiment.
[0102]
The notification allows the registered user to confirm that the e-mail address entered by the user is incorrect, and to delete the incorrect e-mail address if he or she is using it elsewhere.
[0103]
Next, a description will be given of an embodiment having another process when there is an error in the mail address input by the registered user.
[0104]
FIG. 5 shows a process in a case where a confirmation mail transmitted when there is an error in the mail address input by the registered user is returned as a user unknown (destination unknown) error message.
[0105]
In FIG. 5, steps S100 to S140 are completely the same as the processes denoted by the same reference numerals in FIGS. 2 and 4, and thus the duplicate description will be omitted.
[0106]
In step S140 of FIG. 5, a confirmation e-mail is transmitted to an incorrect e-mail address. If the e-mail address does not exist, an error message of user unknown is received (FIG. 5; step S240).
[0107]
Upon receiving the error message, the maintenance server 3 deletes the mail address temporarily stored in the maintenance server 3 and searches the mail address database 4, and registers the same wrong mail address as the mail address of the user. If so, the mail address is deleted (FIG. 5; step S250).
[0108]
Next, the maintenance server 3 notifies the registered user who has input an incorrect e-mail address that the input e-mail address is incorrect (FIG. 5; step S260).
[0109]
According to the present embodiment, erroneous data can be deleted from the mail address database, and only the correct mail address can be maintained.
[0110]
In particular, according to the present embodiment, a mail address whose destination is unknown can be deleted, and the mail address database can be maintained at a minimum data amount. The operation and effect in the case of FIG. 2 are the same in this embodiment.
[0111]
The automatic maintenance system 1 for the mail address database of the present invention can automatically maintain the mail address database 4 without any user access. Next, an embodiment having these processes will be described.
[0112]
FIG. 6 shows a process for automatically deleting a mail address whose access count is equal to or less than a certain value.
[0113]
In the present embodiment, the maintenance server 3 updates the mail address database 4 every time a user accesses, and automatically organizes the mail address database 4 at a predetermined timing.
[0114]
As shown in FIG. 6, the mail address database 4 is updated every time a user accesses the device through the processing of steps S100 to S170 in FIG.
[0115]
While performing the above processing, the maintenance server 3 holds an update log (update record) of the mail address (FIG. 6; step S300). The update log preferably records the update date and time of each mail address.
[0116]
In the present embodiment, the maintenance server 3 checks each mail address stored in the mail address database 4 at a predetermined timing, for example, periodically based on an update log.
[0117]
At this time, a confirmation e-mail is automatically transmitted to the registered user for an e-mail address whose number of updates is below a certain number (FIG. 6; step S310).
[0118]
When the registered user confirms that the e-mail address is not used, or when there is no reply to the confirmation e-mail more than a certain number of times, the e-mail address is deleted (FIG. 6; step S320).
[0119]
Next, a process for automatically deleting a mail address that has not been updated for a certain period will be described.
[0120]
FIG. 7 shows a process for automatically deleting a mail address that has not been updated for a certain period of time.
[0121]
As shown in FIG. 7, the mail address database 4 is updated every time a user accesses the computer through the processing of steps S100 to S170 in FIG.
[0122]
While performing the above processing, the maintenance server 3 holds an update log of the mail address (FIG. 7; step S330). The update log preferably records the update date and time of each mail address.
[0123]
In the present embodiment, the maintenance server 3 checks each mail address stored in the mail address database 4 at a predetermined timing, for example, periodically based on an update log.
[0124]
In the present embodiment, a confirmation e-mail is automatically sent to the registered user for an e-mail address that has not been updated for a certain period of time (FIG. 7; step S340).
[0125]
When the registered user confirms that the e-mail address is not used, or when there is no reply to the confirmation e-mail more than a certain number of times, the e-mail address is deleted (FIG. 7; step S350).
[0126]
In the embodiment of FIG. 6, it is conceivable that too many e-mail addresses are deleted because the number of updates has not reached the predetermined number of times. On the other hand, in the present embodiment, e-mail addresses that have not been updated for a certain period I do. The processing in FIG. 6 is effective when there are too many mail addresses to be deleted. Of course, the embodiment of FIG. 6 and the embodiment of FIG. 7 may be combined.
[0127]
According to the embodiment of FIGS. 6 and 7, in combination with the automatic update of the mail address database by the user's access, not only the mail address updated by the user's access but also the mail without the user's access As for the address, only a truly useful e-mail address can be maintained.
[0128]
As a result, unnecessary mail addresses can be eliminated, and the mail address database 4 can always be maintained at the minimum necessary size.
[0129]
Next, an embodiment will be described in which, when a particularly important processing request is made, the user authentication processing is performed again before making the processing request.
[0130]
FIG. 8 shows a flow of processing when the above-mentioned double user authentication is performed.
[0131]
As shown in FIG. 8, after authenticating that the user is a genuine registered user (FIG. 8; step S110), the user is required to input a mail address (FIG. 8; step S120).
[0132]
In the present embodiment, next, the maintenance server 3 randomly generates data as a confirmation code, outputs a command to be described in the confirmation mail, and stores the confirmation code in correspondence with the mail address input by the user ( FIG. 8: Step S400).
[0133]
Note that the confirmation code may be information indicating that the user has passed the first authentication process, and may preferably be several digits.
[0134]
Next, the mail server 5 transmits a confirmation mail describing the confirmation code to the mail address input by the user (FIG. 8; step S410).
[0135]
If the e-mail address entered by the user is correct, the confirmation e-mail is received by the user, and when the user clicks the confirmation button of the confirmation e-mail, the user accesses the WEB site again and performs the second authentication processing (FIG. 8; Step S420).
[0136]
When the user is confirmed to be a genuine registered user by the second authentication process, the maintenance server 3 causes the user to input a confirmation code (FIG. 8; step S430).
[0137]
The order of steps S420 and S430 may be changed so that the confirmation code is input first, and the second authentication process may be performed before shifting to important processing.
[0138]
When the confirmation code is inputted by the user, the maintenance server 3 checks the inputted confirmation code against the confirmation code temporarily stored in the maintenance server 3 (FIG. 8; step S440).
[0139]
If there is a matching confirmation code, the maintenance server 3 can confirm that the confirmation e-mail has been read by the user, and the e-mail of the e-mail address database 4 can be obtained according to the e-mail address stored corresponding to the confirmation code. The address is updated (FIG. 8; step S450).
[0140]
At the same time, the processing of the processing request of the user is permitted, and the service server 6 is requested to process the processing request (FIG. 8; step S460).
[0141]
According to the automatic maintenance system 1 for the mail address database of the above embodiment, the authentication process is performed again immediately before starting the important process. Thereby, it is possible to strictly prevent an important process from being performed erroneously. The other operation and effect, that is, only a completely correct e-mail address can be maintained, and the e-mail address is automatically confirmed by the WEB site are the same as those in FIG.
[0142]
It goes without saying that the embodiment of FIG. 8 and the embodiments of FIGS. 3 to 7 can be combined. In that case, the operation and effect of each embodiment of FIGS. 3 to 7 can be further achieved.
[0143]
Next, still another embodiment of the present invention will be described. FIG. 9 shows the configuration of this embodiment, and FIG. 10 shows the flow of the processing.
[0144]
The automatic maintenance system of the mail address database according to the present embodiment includes the information of the mail address in the user ID, omits the confirmation mail by the mail server, checks the mail address of the user ID between the maintenance server and the client, and checks the mail. It updates the address database and rewrites the user ID.
[0145]
As shown in FIG. 9, the configuration of the present embodiment is obtained by omitting the mail server 5 from the configuration of the embodiment of FIG. The authentication server 2, the maintenance server 3, the mail address database 4, and the service server 6 are the same as those in FIG. 1, and thus redundant description of these components will be omitted.
[0146]
The processing flow according to the present embodiment will be described below with reference to FIG.
[0147]
As shown in FIG. 10, also in the present embodiment, the user accesses the WEB site by the client 7, so that the automatic maintenance of the mail address database is started (FIG. 10; step S500).
[0148]
When the user accesses the WEB site, authentication processing by the authentication server 2 is performed (FIG. 10; step S510).
[0149]
When the authentication server 2 confirms that the accessed user is a genuine registered user, the processing shifts to the maintenance server 3, and the maintenance server 3 registers the mail address (registered in the mail address database 4) incorporated in the user ID. Is extracted and displayed (FIG. 10; step S520).
[0150]
Step S520 may be performed by the authentication server 2. In this case, the confirmation of the e-mail address is conveniently performed as part of the authentication process.
[0151]
In the present embodiment, the mail address incorporated in the user ID is preferably encrypted and incorporated.
[0152]
In this case, the maintenance server 3 holds the encryption / decryption algorithm, decrypts the mail address from the user ID of the user who has completed the authentication processing, and indicates the decrypted mail address to the user.
[0153]
The user confirms whether the displayed registered mail address is correct (FIG. 10; step S530).
[0154]
When the user confirms that the registered e-mail address is correct and transmits information that the registered e-mail address is correct to the maintenance server 3, the maintenance server 3 causes the service server 6 to process the user's processing request (FIG. 10; step S540).
[0155]
On the other hand, when the user sends information to the maintenance server 3 that the registered e-mail address is incorrect, the maintenance server 3 receives the information and causes the user to input a correct e-mail address (FIG. 10; step S550).
[0156]
When the user inputs a correct e-mail address and receives a correct e-mail address from the user, the maintenance server 3 updates the e-mail address database 4 according to the input e-mail address (FIG. 10; step S560).
[0157]
Further, the maintenance server 3 encrypts the input e-mail address according to the stored encryption / decryption algorithm and incorporates the user ID (FIG. 10; step S570).
[0158]
The maintenance server 3 allows the user to download the encrypted user ID incorporating the correct mail address, and rewrites the user ID stored in the client 7 (FIG. 10; step S580).
[0159]
When the above processing in the case where the registered mail address is incorrect is completed, the maintenance server 3 causes the service server 6 to process the processing request of the user (FIG. 10; step S540).
[0160]
According to the automatic maintenance of the mail address database according to the present embodiment, when the user accesses the WEB site, the user can automatically check his / her registered mail address. As a result, it is possible to save labor for periodically checking the registered mail addresses of a large number of registered users.
[0161]
The processing steps of steps S520 and S530 for displaying the registered e-mail address to the user and confirming the user can be performed every fixed number of accesses to the WEB site or every random number of accesses.
[0162]
By doing so, there is no need to confirm each time the user accesses the WEB site, but the registered mail address can be confirmed at regular intervals.
[0163]
This embodiment can of course be combined with the embodiment of FIGS. 6 and 7. That is, in addition to the user's access, an update log of the e-mail address database is retained, and a confirmation e-mail can be transmitted to a user whose e-mail address has been updated less than a predetermined number of times or has not been updated for a predetermined period of time. .
[0164]
According to such an embodiment, it is possible to further exert an operational effect that the mail address database 4 can be arranged at predetermined intervals other than the user's access.
[0165]
【The invention's effect】
As is apparent from the above description, according to the present invention, when the user accesses the web site, the user inputs or confirms the mail address, so that the web site automatically updates the mail address database. It can be carried out. Therefore, there is no need to periodically check with all registered users whether the registered e-mail address is correct as in the related art.
[0166]
Further, according to the automatic maintenance system of the mail address database for transmitting the confirmation mail of the present invention, the processing and the automatic maintenance of the mail address are performed on condition that the information described in the confirmation mail is sent to the WEB site again. To ensure that the confirmation email was received, i.e., that the email address entered by the user is indeed receivable, thus updating the email address database to a completely correct email address be able to.
[0167]
This completely eliminates the uncertainty of not receiving a response from all users, not confirming the user correctly, etc., as in the conventional method of confirming the registered e-mail address to the user, and completely accurate You can update to your email address.
[0168]
Also, by maintaining an update log of the e-mail address at the time of user's access, the e-mail address can be automatically checked for e-mail addresses that have been updated less than a predetermined number of times or have not been updated for a predetermined period of time. The data in the database can be organized and a mail address database with a minimum required data volume can be maintained at all times.
[Brief description of the drawings]
FIG. 1 is a block diagram showing a configuration of an automatic mail address database maintenance system according to an embodiment of the present invention.
FIG. 2 is a flowchart showing a flow of processing for automatic maintenance of a mail address database according to an embodiment of the present invention.
FIG. 3 is a flowchart showing a flow of automatic maintenance processing of a mail address database according to an embodiment of the present invention when time information is included in an HTTP argument.
FIG. 4 is a flowchart showing a flow of a process of automatic maintenance of a mail address database according to an embodiment of the present invention for deleting a mail address inputted by a user in response to a deletion request of a third party.
FIG. 5 is a flowchart showing a flow of a process of automatic maintenance of a mail address database according to an embodiment of the present invention for deleting a mail address input by a user in response to an error message indicating a user unknown.
FIG. 6 is a flowchart showing a flow of a process of automatic maintenance of a mail address database according to an embodiment of the present invention for deleting a mail address below a certain number of updates.
FIG. 7 is a flowchart illustrating a flow of a process of automatic maintenance of a mail address database according to an embodiment of the present invention for deleting a mail address that has not been updated for a predetermined period.
FIG. 8 is a flowchart showing a flow of a process of automatic maintenance of a mail address database according to an embodiment of the present invention in which an authentication process is performed again before processing a processing request of a user.
FIG. 9 is a block diagram showing a configuration of an automatic maintenance system for a mail address database according to an embodiment of the present invention in which a user confirms a user by incorporating a mail address into a user ID.
FIG. 10 is a flowchart showing a flow of a process of automatic maintenance of a mail address database according to an embodiment of the present invention in which a user confirms a user by incorporating a mail address into a user ID.
[Explanation of symbols]
1 E-mail address database automatic maintenance system
2 Authentication server 2
3 Maintenance server
4 Email address database
5 mail server
6 service server
7 Client
8 Email address PC

Claims (12)

A user recognized as a genuine user by the authentication process inputs an email address, generates an HTTP argument including a session code of a series of processes including the authentication process, and stores the HTTP argument and the input email address. When there is access from a user having the HTTP argument, the processing of the processing request is permitted as an authenticated user, and the input mail address is registered in the mail address database as the mail address of the user. An automatic maintenance system for a database of e-mail addresses, comprising a maintenance server. The HTTP argument includes time information, and when there is an access from a user having the HTTP argument, the maintenance server compares the time when the HTTP argument was first generated with the time when the next access was made, and a predetermined time. 2. The automatic maintenance system for a mail address database according to claim 1, wherein, if the mail address is open for more than a predetermined time interval, the processing of the user's processing request is not permitted, and the input mail address is deleted. . The automatic maintenance system for a mail address database according to claim 1 or 2, wherein the maintenance server encrypts or decrypts data including a session code of the processing according to a predetermined algorithm. 4. The system according to claim 3, wherein the maintenance server changes the algorithm according to time. The maintenance server deletes the e-mail address when the access has the HTTP argument and has a request to delete the previously input e-mail address or receives an error message of a user unknown. The automatic maintenance system for a database of a mail address according to claim 1. The said maintenance server outputs the instruction | indication which transmits the notification mail to the effect that the e-mail address input by the said user was incorrect to the user recognized as the genuine user by the said authentication process. 5. An automatic maintenance system for the mail address database described in 5. A user recognized as a genuine user by the first authentication process is caused to input an e-mail address, a unique confirmation code is generated and stored together with the e-mail address,
An email characterized by having a maintenance server that allows a user who is recognized as a genuine user to enter a confirmation code in the second authentication process, and updates a database of email addresses according to the email address corresponding to the entered confirmation code. Automatic maintenance system of address database. The maintenance server deletes the e-mail address when receiving the access having the confirmation code and a request to delete the previously input e-mail address or receiving an error message of a user unknown. An automatic maintenance system for a mail address database according to claim 7. The said maintenance server outputs the instruction | indication which transmits the notification mail to the effect that the e-mail address input by the said user was incorrect to the user recognized as the genuine user by the said authentication process. 8. An automatic maintenance system for the database of the e-mail addresses described in 8. Displays the e-mail address embedded in the user ID, asks the user to confirm that it is the correct e-mail address, and if the user confirms that the e-mail is correct, allows the processing of the user's processing request, and the user enters the e-mail address In the case, the mail has a maintenance server that updates a mail address database according to the input mail address, encrypts the correct mail address by a predetermined algorithm, incorporates the correct mail address into a part of the user ID, and causes the user to download the mail. Automatic maintenance system of address database. 11. The system according to claim 10, wherein the maintenance server checks and updates the e-mail address and updates the user ID at predetermined times or at random times. . The maintenance server holds an update log for each e-mail address in the e-mail database, and automatically sends a confirmation e-mail to a user whose e-mail address has been updated less than a predetermined number of times or has not been updated for a predetermined period of time. The automatic mail address database maintenance system according to any one of claims 1 to 11, wherein the mail address database is transmitted.

Images