JP4704307B2 - Message delivery system, message transfer apparatus, message transfer method, and message transfer program - Google Patents

Description

  The present invention relates to a message delivery system, a message transfer device, a message transfer method, and a message transfer program that deliver a message based on caller information that is information related to a message sender. The present invention relates to a message delivery system, a message transfer device, a message transfer method, and a message transfer program capable of compressing and registering a certain permitted caller information and thereby reducing resources necessary for storing the permitted caller information. .

  In recent years, with the increase in spam mail, various techniques for preventing spam mail have been developed. For example, by registering the mail address of a sender who is allowed to receive mail as a permitted sender address in a mail transfer server that forwards mail, the mail transfer server transfers only mail having the registered address as the sender address. Technology has been developed.

  In addition, since it is a burden on the user to register all e-mail addresses that are permitted to be received, a technique for automatically registering e-mail addresses that the user permits to receive has been developed. For example, Patent Literature 1 describes a technique in which when a user replies to a received mail, the reply destination mail address is automatically registered as a mail address that the user permits to receive.

JP 2003-178008 A

  However, if all e-mail addresses permitted to be received are stored, there is a problem that a necessary storage area becomes large. Therefore, although the maximum number of permitted caller addresses that can be registered is limited, there is a problem that it is inconvenient for the user because the permitted caller addresses exceeding the maximum number cannot be registered.

  The present invention has been made to solve the above-described problems caused by the prior art, in order to compress and register authorized sender information such as authorized sender address, and to store authorized sender information. It is an object of the present invention to provide a message delivery system, a message transfer device, a message transfer method, and a message transfer program that can reduce necessary resources.

In order to solve the above-described problems and achieve the object, the invention according to claim 1 is a message delivery system that delivers a message based on sender information that is information about the sender of the message, and is received by the user. The permitted sender compressed information storage means storing the permitted sender compressed information, which is obtained by compressing the information related to the sender permitting the permission, and the rejected sender storing the rejected sender information which is information regarding the sender that the user refuses to receive Information storage means, rejection sender information determination necessity storage means for storing the necessity of transfer rejection determination based on the rejection sender information in correspondence with the permitted sender compression information, and transmission of an arrived message Sender information compression means for compressing sender information to generate sender compressed information, and permitted sender compressed information corresponding to the destination of the arrived message. Of the permitted sender compressed information which is read from the compressed person information storing means and compared with the compressed sender information generated by the sender information compressing means, and the rejected sender information determination necessity storage means When the necessity information corresponding to the matched permitted caller compression information is not required to be determined, it is determined that the message can be transferred, the matching permitted caller compression information is present, and the rejected caller information determination is performed. When the necessity information corresponding to the matching permitted sender compression information is necessary in the necessity storage means, the rejection sender information corresponding to the destination of the arrived message is sent from the rejection sender information storage means. A transfer permission determination means for determining that transfer of the message is impossible when there is matching rejected caller information that is read and compared with the caller information of the message; When new sender information is registered as rejected sender information, the new sender information is compressed to generate compressed sender information, and the generated compressed sender information is the registration target of rejected sender information. When it matches one of the permitted sender compressed information corresponding to a certain user, the necessity information corresponding to the matched permitted sender compressed information in the rejected sender information determination necessity storage means is determined as necessary. And a necessity information setting means for setting.

Further, the invention according to claim 2 is the communication history information stored in the communication history information stored in the communication history information storage unit, the communication history information stored in the communication history information storage unit. Based on the above, it is further characterized by further comprising permitted sender compressed information automatic deleting means for specifying and deleting permitted sender compressed information to be automatically deleted from the permitted sender compressed information storage means.

Further, in the invention according to claim 3, in the above invention, the communication history information storage means stores the last message communication time as communication history information, and the permitted sender compressed information automatic deletion means includes the communication history information. When the difference between the last message communication time stored in the storage means and the current time is greater than a predetermined value, the permitted sender compressed information corresponding to the user and the communication partner is stored in the permitted sender compressed information storage means. It is characterized by being automatically deleted from.

According to a fourth aspect of the present invention, in the above invention, the communication history information storage means stores the last message communication time as communication history information, and the permitted sender compressed information automatic deletion means is the permitted sender. The number of permitted sender compressed information stored in the permitted sender compressed information storage means for the user when the new permitted sender compressed information is registered in correspondence with the user in the compressed information storage means is a predetermined maximum. If the value is a value, the permitted sender compression information related to the communication partner whose oldest message communication time point stored in the communication history storage means is deleted from the permitted sender compression information stored for the user. It is characterized by.

According to a fifth aspect of the present invention, in the above invention, when the user transmits a message to a new communication partner, the information about the communication partner is compressed and automatically registered in the permitted sender compressed information storage means. It further comprises an authorized sender compressed information automatic registration means.

According to a sixth aspect of the present invention, in the above invention, the permitted caller uncompressed information storage means for storing the permitted caller information, which is information related to the caller permitted to be received by the user, without compression, and use Authorized sender information manual registration means for accepting a new authorized sender information registration request from the user and registering it in the authorized sender uncompressed information storage means, and a new authorized sender without receiving a registration request from the user And a permitted sender compressed information automatic registering means for automatically registering compressed information, wherein the transfer permission determining means reads the permitted sender compressed information corresponding to the destination of the arrived message from the permitted sender compressed information storage means. Compared to the caller compressed information generated by the caller information compressing means, and there is a matching permitted caller compressed information or the permitted caller information corresponding to the destination. The comparison with the caller information of the authorized caller uncompressed information message from the storage means and the arrival, and judging the allowed transfer of the message if there is a permission caller information match.

According to a seventh aspect of the present invention, in the above invention, the sender compressed information generated by the sender information compressing means is matched with any of the permitted sender compressed information corresponding to the destination of the arrived message. If the sender information of the arrived message does not match any of the rejected sender information corresponding to the destination of the message, a message address including a transfer condition generated based on the sender information of the message, When a message transmitted to the sender of the message is sent to the message address as a destination and a message sent to the message address is received, the sender information of the message is included in the message address. If the transfer condition is satisfied, it is determined that the message can be transferred and the message is transmitted. If the information is not satisfied transfer conditions included in the message address, and further comprising a disable and determining transfer possibility determination means for forwarding the message.

The invention according to claim 8 is the above-mentioned invention, wherein the permitted sender non-compressed information storage means stored without compressing the permitted sender information, which is information relating to the sender that the user permits reception, A part of the permitted sender information stored in the permitted sender uncompressed information storage means on the condition that the number of permitted sender information stored in the permitted sender uncompressed information storage means has reached a predetermined number The permitted sender compressed information is generated by compressing so that the storage area required for storing the permitted sender information is reduced, and the generated permitted sender compressed information is registered in the permitted sender compressed information storage means. It further comprises a partly permitted sender compressed information registration means.

The invention according to claim 9 is a message transfer device for transferring a message based on caller information which is information relating to the caller of the message, and compresses the caller information of the arrived message to compress the caller information. A sender information compressing unit that generates the permitted sender compressed information corresponding to the destination of the arrived message among the permitted sender compressed information obtained by compressing the information on the sender permitted to be received by the user, and the Transfer rejection judgment based on rejected caller information, which is information related to the caller that the user has rejected to receive when there is matching allowed caller compressed information compared with the caller compressed information generated by the caller information compression means If the necessity information registered in association with the permitted sender compression information is not required to be determined, it is determined that the message can be transferred. When there is matching permitted sender compressed information and the necessity information registered in association with the permitted sender compressed information is necessary for determination, rejected sender information corresponding to the destination of the arrived message Transfer permission determination means for determining that the message cannot be transferred when there is matching rejected caller information, and the new caller information is set as rejected caller information. When registering, the new sender information is compressed to generate sender compressed information, and the generated sender compressed information corresponds to the permitted sender compressed information corresponding to the user who is the registration target of the rejected sender information. And a necessity information setting unit that sets necessity information corresponding to the matched permitted sender compression information as a necessity for determination when it matches any one of the information.

According to a tenth aspect of the present invention, in the above invention, the caller compression information generated by the caller information compression means is matched with any of the permitted caller compression information corresponding to the destination of the arrived message. If the sender information of the arrived message does not match any of the rejected sender information corresponding to the destination of the message, a message address including a transfer condition generated based on the sender information of the message, When a message transmitted to the sender of the message is sent to the message address as a destination and a message sent to the message address is received, the sender information of the message is included in the message address. If the transfer condition is satisfied, it is determined that the message can be transferred and the message is issued. Who If the information does not satisfy the transfer condition included in the message address, and further comprising a disable and determining transfer possibility determination means for forwarding the message.

According to an eleventh aspect of the present invention, in the above invention, the number of permitted caller information registered without compression of the permitted caller information, which is information related to a caller permitted to receive by the user, is a predetermined number. On the condition that the authorized sender information is compressed, a part of the registered authorized sender information is compressed so that the storage area required for storing the authorized sender information is reduced, and the authorized sender compressed information is generated and generated. It further comprises partial permitted sender compressed information registration means for registering the permitted permitted sender compressed information.

According to a twelfth aspect of the present invention, there is provided a message transfer method by a message transfer device for transferring a message on the basis of caller information which is information relating to a message sender, wherein the caller information of an arrived message is compressed. Sender information compression step for generating sender compression information, and permitted sender compression information corresponding to the destination of the arrived message among the permitted sender compression information obtained by compressing information on the sender that the user permits reception. Rejected caller information that is acquired and compared with the caller compressed information generated by the caller information compressing means, and there is a matching permitted caller compressed information, and information on the caller that the user refuses to receive When the necessity information registered in association with the permitted caller compression information is information indicating the necessity of the transfer rejection determination by the If it is determined that message transfer is possible and there is matching permitted caller compression information and the necessity information registered in association with the permitted caller compression information is required to be determined, the received message A transfer permission determination step of acquiring rejected caller information corresponding to the destination and comparing it with the caller information of the message and determining that transfer of the message is impossible when there is a matching rejected caller information, and a new call When registering caller information as rejected caller information, new caller information is compressed to generate compressed caller information, and the generated caller compressed information is sent to a user who is a registration target of rejected caller information. And a necessity information setting step for setting necessity information corresponding to the matched permitted sender compression information to a determination necessity when it matches any of the corresponding permitted sender compression information. .

According to a thirteenth aspect of the present invention, in the above invention, the sender compression information generated by the sender information compression step is matched with any of the permitted sender compression information corresponding to the destination of the arrived message. If the sender information of the arrived message does not match any of the rejected sender information corresponding to the destination of the message, a message address including a transfer condition generated based on the sender information of the message, When a message transmitted to the sender of the message is sent to the message address as a destination and a message sent to the message address is received, the sender information of the message is included in the message address. If the transfer condition is satisfied, it is determined that the message can be transferred and the message is issued. Who If the information does not satisfy the transfer condition included in the message address, and further comprising a disable and determining transfer possibility determination step the transfer of the message. Further, in the invention according to claim 14, in the above invention, the number of permitted sender information registered without compression of the permitted sender information, which is information relating to the sender permitted to be received by the user, is a predetermined number. On the condition that the authorized sender information is compressed, a part of the registered authorized sender information is compressed so that the storage area required for storing the authorized sender information is reduced, and the authorized sender compressed information is generated and generated. The method further includes a partially permitted sender compressed information registration step of registering the permitted sender compressed information. The invention according to claim 15 causes a computer to execute the message transfer method described above.

According to the invention according to claim 1, 9 , 12, or 15 , in a message delivery system, a message transfer device, a message transfer method, or a message transfer program for delivering a message based on caller information that is information related to a message sender The message delivery system includes a permitted sender compressed information storage means storing permitted sender compressed information obtained by compressing information relating to a sender permitted to be received by a user, and information relating to a sender that the user refuses to receive. Rejected caller information storage means for storing rejected caller information, and rejected caller information for storing the necessity of transfer rejection determination by the rejected caller information as necessity information in correspondence with the permitted caller compressed information Judgment necessity storage means and sender information for compressing the sender information of the arrived message to generate the sender compressed information The compressed means and the permitted sender compressed information corresponding to the destination of the arrived message are read from the permitted sender compressed information storage means and compared with the sender compressed information generated by the sender information compressing means, and they match. When there is permitted sender compression information and the necessity information corresponding to the matching permitted sender compression information in the rejected sender information judgment necessity storage means does not need to be judged, the message can be transferred. And when there is matching permitted caller compression information and the necessity information corresponding to the matching permitted caller compression information in the rejected caller information determination necessity storage means needs to be determined, When rejected caller information corresponding to the destination of the arrived message is read from the rejected caller information storage means and compared with the caller information of the message, and there is matching rejected caller information Transfer permission determination means for determining that the message cannot be transferred, and new sender information is registered as rejected caller information in the rejected caller information storage means, and the new caller information is compressed and the caller is compressed. When the compressed caller information is generated and the generated caller compressed information matches any of the permitted caller compressed information corresponding to the user who is the registration target of the rejected caller information, the rejection caller information determination necessity Since it is configured to include necessity information setting means for setting necessity information corresponding to the matched permitted sender compressed information in the storage means to be required for determination, the permitted sender information can be compressed and registered. . Therefore, it is possible to reduce the resources necessary for storing permitted sender information. In addition, it is possible to prevent erroneous determination that occurs due to the compressed permitted sender information. Further, even when the permitted sender compressed information and the permitted sender / denied sender information are matched by the information compression, it is possible to prevent the occurrence of misdistribution in which the message from the rejected sender is transferred.

Further, according to the invention according to claim 2 , based on the communication history information storage means storing the communication history information with the communication partner for each user, and the communication history information stored in the communication history information storage means, The permitted sender compressed information is automatically deleted from the permitted sender compressed information storage means, and the permitted sender compressed information automatic deletion means for specifying and deleting the permitted sender compressed information is deleted. Can be prevented. The permitted sender compressed information may be difficult for the user to understand depending on the information compression method. In such a case, it is difficult for the user to delete the permitted sender compressed information, and it is particularly important to automatically delete unnecessary information.

According to a third aspect of the present invention, the communication history information storage means stores the last message communication time as communication history information, and the permitted sender compressed information automatic deletion means is stored in the communication history information storage means. When the stored last message communication time point and the current time point are compared and the difference is larger than a predetermined value, the permitted sender compressed information corresponding to the user and the communication partner is automatically deleted from the permitted sender compressed information storage means Since it comprised so, when communication is not performed for a predetermined period, permission caller compression information can be deleted automatically.

According to the invention of claim 4 , the communication history information storage means stores the last message communication time as communication history information, and the permitted sender compressed information automatic deletion means stores the permitted sender compressed information storage. The number of permitted sender compressed information stored in the authorized sender compressed information storage means for the user when registering new authorized sender compressed information corresponding to the user in the means is a predetermined maximum value. In this case, since the permitted sender compressed information stored in the communication history storage means is deleted from the permitted sender compressed information stored for the user, the permitted sender compressed information relating to the communication partner with the oldest communication time is deleted. , it is possible the elapsed period since last communication to automatically delete the authorized caller compression information of the longest communication partner.

According to the invention of claim 5 , when a user transmits a message to a new communication partner, the authorized sender who compresses information about the other party and automatically registers it in the authorized sender compressed information storage means Since the compressed information automatic registration means is further provided, it is possible to reduce the burden of the user registering permitted sender information.

According to the sixth aspect of the invention, the permitted sender uncompressed information storage means for storing the permitted sender information, which is the information related to the sender permitted to be received by the user without compression, and a new message from the user. Authorized sender information manual registration means for accepting a request for registration of authorized authorized sender information and registering it in the authorized sender uncompressed information storage means, and new authorized sender compressed information without receiving a registration request from the user An automatic permitted sender compression information registering means for automatically registering, wherein the transfer permission determining means reads out the permitted sender compressed information corresponding to the destination of the arrived message from the permitted sender compressed information storage means and Compared with the sender compressed information generated by the sender information compression means, there is a matching permitted sender compressed information or the permitted sender information corresponding to the destination is 'S uncompressed information from the storage unit compared with the caller information of the message described above arrives, because if there is a permission caller information matching with the transfer of the message configured to determine a variable, user authorization originating The advantage of the information compression included in the person compression information and the advantage of the ease of maintenance included in the permitted sender information can be used separately.

Further, according to the present invention, it is possible to perform a variety of information compressed by a hash function to use.

Further, according to the invention of claim 7 , the caller compression information generated by the caller information compression means does not match any of the permitted caller compression information corresponding to the destination of the arrived message, When the sender information of the arrived message does not match any of the rejected sender information corresponding to the destination of the message, the message address including the forwarding condition generated based on the sender information of the message is When a message transmitted to the transmission source is requested to send the message with the message address as the destination, and the message sent with the message address as the destination is received, the transfer condition in which the sender information of the message is included in the message address Is satisfied, it is determined that the message can be transferred, and the sender information of the message is If not satisfied transfer conditions included in the message address, since it is configured to further comprise a No and determining transfer possibility determination means for forwarding the message, can be used in combination reject caller information and authorization caller information .

  Exemplary embodiments of a message delivery system, a message transfer apparatus, a message transfer method, and a message transfer program according to the present invention will be described below in detail with reference to the accompanying drawings. Here, the case where the present invention is applied to a mail delivery system will be mainly described.

  In this embodiment, after describing the configuration of the mail delivery system according to this embodiment, the processing procedures such as the mail transfer processing of the mail delivery system and the registration deletion processing of various data used for mail filtering are explained. The effect of the present embodiment will be described.

[Configuration of mail delivery system]
First, the configuration of the mail delivery system according to the present embodiment will be described with reference to FIG. FIG. 1 is a diagram illustrating a configuration of a mail delivery system according to the present embodiment. The mail delivery system shown in the figure connects a service user A terminal 220 and a communication partner B terminal 320 via a service user A side IP network 240, the Internet 400, and a communication partner B side IP network 340. A service user A terminal 220 sends a mail addressed to the service user A 230 sent from the communication partner B terminal 320 to the communication partner B 330 via the communication partner B mail server 310 and the service user A mail server 210. This is a mail delivery system that delivers up to Here, it is assumed that the service user A230 is a user of the mail delivery service according to the present embodiment, and the communication partner B330 is a partner who exchanges mail with the service user A230.

  The service user A terminal 220 and the communication partner B terminal 320 are terminal devices that are used when the service user A 230 and the communication partner B 330 exchange mails via the Internet 400, respectively. WEB browser software and electronic mail software (mailer) are installed in the PC), and are connected to the service user A side IP network 240 and the communication partner B side IP network 340 via the router R, respectively. The service user A side IP network 240 and the communication partner B side IP network 340 are each connected to the Internet 400 via a router R.

  The service user A mail server 210 and the communication partner B mail server 310 are so-called existing mail servers. That is, the service user A mail server 210 accepts the mail transmitted from the service user A terminal 220 and transmits it to the mail destination, and receives the mail to the service user A terminal 220 to receive the service user A terminal 220. The communication partner B mail server 310 receives the mail transmitted from the communication partner B terminal 320 and transmits it to the destination of the mail, and receives the mail to the communication partner B terminal 320 to receive the communication partner B. Transmit to terminal 320. For convenience of explanation, only two terminal devices and a mail server are shown here, but this mail delivery system is composed of a large number of terminal devices and mail servers.

  In addition, in this mail delivery system, in addition to an email addressed to an actual email address held by a user (hereinafter referred to as “real address”), a public address composed of a user ID and a predetermined domain name is sent to Deliver the email. FIG. 2 is a diagram illustrating an example of a public address. As shown in the figure, this public address is composed of a user ID “suzuki” and a domain name “privango.net” of the mail transfer server 110 described later.

  The reason for using the public address is that the user may not want to disclose the real address to the communication partner. For example, if the communication partner is a mail order dealer on the Internet, if you disclose the real address unnecessarily, this real address will spread to other vendors through mailing lists, etc., and direct mail etc. that do not require users This is because there may be a situation where it is necessary to receive a call.

  As described above, in this mail delivery system, since a public address can be used, a mail transfer server 110 that receives a mail addressed to the public address and transfers it to a recipient, and a registration process of a compressed white list and a black list A compression whitelist / blacklist registration server 120 that performs the above, a data management server 130 that manages a compression whitelist, a blacklist, and the like, and an individual address issue server 140 that issues an individual address are provided.

  Here, the compressed whitelist is a hash value of a sender's mail address (hereinafter referred to as “reception permitted address”) or a domain name (hereinafter referred to as “reception permitted domain name”) that the user allows to receive mail. It is a list. In other words, the compressed white list is a list of hash values obtained by compressing the reception permitted address and the reception permitted domain in contrast to the normal white list which is a list of the reception permitted address and the reception permitted domain. Thus, by compressing the reception permitted address and the reception permitted domain into a hash value, it is possible to reduce the storage area required for storing the compressed white list. For example, when the mail address can be composed of a domain name of 255 characters and a user name of 64 characters, the storage area required to store one mail address is 255 + 64 + 1 = 320 characters including @. However, if a 128-bit (16 characters) hash value is used, the storage area required to store the mail address can be reduced to 16/320 = 1/20.

  The black list is a list of mail addresses (hereinafter referred to as “reception reject addresses”) and domain names (hereinafter referred to as “reception reject domain names”) of senders who refuse to receive mail.

  The mail transfer server 110 determines whether mail can be transferred using a compressed white list and a black list when transferring mail whose destination is a public address. That is, the mail transfer server 110 determines that the mail can be transferred when the hash value of the mail address of the sender is registered in the compressed white list corresponding to the mail destination, and the mail address of the sender Is registered in the black list corresponding to the mail address, it is determined that the mail cannot be transferred. The mail transfer server 110 does not register the hash value of the sender's mail address in the compressed white list corresponding to the mail destination, and the sender's mail address becomes a black list corresponding to the mail destination. If the address is not registered, the individual address issuing server 140 is requested to generate an individual address, and the mail sender is requested to retransmit the individual address generated by the individual address issuing server 140 as a destination.

  Here, the individual address is a conditional address in which mail transfer conditions such as a period (time limit), time, and sender address where mail transfer is permitted are incorporated, and the mail transfer server 110 receives the individual address as a destination. When the e-mail is received, the transfer condition is taken out, and the e-mail is transferred to the recipient when the transfer condition is satisfied.

  FIG. 3 is a diagram illustrating an example of an individual address. As shown in the figure, this individual address includes a user ID “suzuki”, a mail transfer condition “sbtwr3”, a falsification prevention code “gr5b”, and a domain name “privango.net” of the mail transfer server 110. Details of the processing related to the individual address will be described later.

  As described above, the mail delivery system according to the present embodiment filters mails using the compressed white list and the black list, and for the mail of the caller who is not registered in either the compressed white list or the black list. Allows filtering using both compressed whitelists and blacklists by filtering email using individual addresses.

  The mail transfer server 110, the compressed whitelist / blacklist registration server 120, the data management server 130, and the individual address issuing server 140 are connected to the LAN 100 connected to the Internet 400 via the router R and the firewall FW.

  The mail transfer server 110 is a server device that performs filtering processing and forwarding processing of mail whose destination is a public address, and includes a mail communication unit 111, a filter processing unit 112, a transfer processing unit 113, and a compressed whitelist automatic process. Unit 114 and black list automatic processing unit 115. Such a mail transfer server 110 can be realized by installing a program corresponding to these functional units in a commercially available PC or workstation (WS).

  The mail communication unit 111 is a processing unit that receives a mail whose destination is a public address or an individual address from a mail server on the transmission side, and transmits the filtered mail to the mail server on the reception side.

  The filter processing unit 112 is a processing unit that filters mail whose destination is a public address. Specifically, when the hash value of the mail source address is registered in the compressed white list, the mail is transferred. If it is passed to the processing unit 113 and the mail source address is registered in the black list, the mail is discarded.

  Further, the filter processing unit 112, when the hash value of the mail source address is not registered in the compressed white list and the mail source address is not registered in the black list, the individual address issuing server 140 requests the issuance of the individual address, notifies the sender of the issued individual address, and requests retransmission of the mail. Then, the transfer condition of the retransmitted mail is determined. If the transfer condition is satisfied, it is determined that the mail can be transferred. If the transfer condition is not satisfied, the mail is discarded.

  As described above, the filter processing unit 112 determines whether or not mail can be transferred using the compressed white list and the black list, and when the transmission source address is not registered in the compressed white list or the black list, By determining whether or not mail can be transferred using an individual address, it is possible to use a compressed white list and a black list together and to reliably eliminate junk mail. The details of the filter processing by the filter processing unit 112 will be described later.

  The transfer processing unit 113 is a processing unit that changes the address of the mail determined to be transferable by the filter processing unit 112 to a real address and transfers it. Specifically, the transfer processing unit 113 transfers the mail by changing the destination to the real address corresponding to the user ID.

  The compressed white list automatic processing unit 114 is a processing unit that performs automatic registration in the compressed white list, and the black list automatic processing unit 115 is a processing unit that performs automatic registration and automatic deletion in the black list. Details of the processing of the compressed white list automatic processing unit 114 and the black list automatic processing unit 115 will be described later. The compressed white list, black list, and real address are managed by the data management server 130.

  The compression whitelist / blacklist registration server 120 is a server device that performs processing for registering a hash value of a reception permission address, a reception rejection address, and the like in the data management server 130. The HTTP communication unit 121 and the compression whitelist registration processing Unit 122 and black list registration processing unit 123. The compressed whitelist / blacklist registration server 120 can be realized by installing programs corresponding to these functional units in a commercially available PC or WS, similarly to the mail transfer server 110.

  The HTTP communication unit 121 is a processing unit that performs communication in accordance with HTTP (Hyper Text Transfer Protocol). For example, a request for registering a mail address to a compressed white list or black list performed by a user using WEB browser software is performed. It is received and passed to the compressed whitelist registration processing unit 122 or the blacklist registration processing unit 123.

  The compressed whitelist registration processing unit 122 receives a registration request such as a reception permission address to the compressed whitelist performed by the user using the WEB browser software and a registration request from the compressed whitelist automatic processing unit 114 and receives the data management server 130. Is a processing unit that performs registration in the compressed white list managed by the.

  The compressed white list registration processing unit 122 calculates a hash value from a reception permission address or the like when registering in the compression white list managed by the data management server 130, and a hash value instead of the reception permission address or the like. Is requested to the data management server 130 to be registered in the compression white list.

  The compression white list registration processing unit 122 calculates a hash value from the reception permission address or the like, and requests the data management server 130 to register the hash value in the compression white list instead of the reception permission address or the like. The necessary storage area can be reduced as compared with the case of not.

  The black list registration processing unit 123 receives a registration request such as a reception rejection address to the black list or the registration request and the deletion request from the black list automatic processing unit 115 performed by the user using the WEB browser software, and the data management server 130. Is a processing unit that performs registration and deletion in the black list managed by the user, specifically, accepts a user ID, a reception rejection address, and the like, and requests the data management server 130 for registration and deletion.

  The data management server 130 is a server device that manages a compressed white list, a black list, and real addresses, and includes a real address table 131, a compressed white list table 132, and a black list table 133. The data management server 130 can be realized by installing a program for managing data in a commercially available PC or WS, like the mail transfer server 110 and the compressed whitelist / blacklist registration server 120.

  The real address table 131 is a table that stores user IDs and real addresses in association with each other. FIG. 4 is a diagram illustrating an example of the real address table 131. As shown in the figure, the real address table 131 stores the real address “suzuki1010@anywhere.ne.jp” corresponding to the user ID “suzuki” and the real address “sunaka” corresponding to the user ID “tanaka”. “taro@isp-A.ne.jp” is stored, and the real address “yamada-k@anywhere.ne.jp” is stored in association with the user ID “yamada”.

  The compressed white list table 132 is a table that stores a user ID and a compressed white list in association with each other. The compressed white list table 132 also stores a black list check flag in association with each hash value. FIG. 5 is a diagram illustrating an example of the compressed white list table 132. As shown in the figure, the compressed whitelist table 132 stores a hash value “0x8a1d742c” and a hash value “0x56ab129d” in association with the user ID “suzuki”, and a blacklist check corresponding to the hash value “0x8a1d742c”. “0” is stored as the flag value, and “1” is stored as the black list check flag value corresponding to the hash value “0x56ab129d”. “0x” represents a hexadecimal number, and here, a 32-bit hash value is used.

  Also, the black list check flag indicates whether the black list corresponding to the compressed white list needs to be checked when the hash value of the mail sender address or the domain part of the sender address matches the hash value of the compressed white list. It is a flag indicating whether or not. If the hash value is used, the user can always receive mail that the user wants to permit, but may receive mail that he / she wants to refuse. That is, a hash value such as a transmission source address to be rejected may match a hash value registered in the compressed white list.

  Therefore, in this embodiment, when registering an email address or the like in the black list, the black list registration processing unit 123 calculates a hash value from the email address or the like, and the calculated hash value is registered in the corresponding compressed white list. If so, the black list check flag corresponding to the hash value is set to “1”. The transfer processing unit 113 checks the black list check flag when the transmission source address is registered in the compressed white list, and transfers the mail when the black list check flag is “1”. Without permitting, it is determined whether transfer is rejected or transfer is not possible using the black list corresponding to the hash value.

  In this way, by using the black list check flag, mail from the source address registered in the black list is forwarded to the user because the hash value matches the hash value registered in the compressed white list. Can be prevented.

  The black list table 133 is a table that stores a user ID and a black list in association with each other. FIG. 6 is a diagram illustrating an example of the black list table 133. As shown in the figure, this black list table 133 stores a reception rejection address “spammer@black.com” in association with the user ID “suzuki”, and a reception rejection address “spammer@black.com” in association with the user ID “tanaka”. “advertise@shop.com” and “spam@mail.com” are stored, and the reception rejection address “black@spam.com” is stored in association with the user ID “yamada”.

  The individual address issuing server 140 is a server device that issues an individual address, and includes a communication unit 141 and an address generation unit 142. The individual address issuing server 140 can be realized by installing a program for managing data in a commercially available PC or WS like the mail transfer server 110 or the like.

  The communication unit 141 is a processing unit that communicates with the mail transfer server 110 or the like via the LAN 100. For example, the communication unit 141 receives an individual address generation request from the mail transfer server 110 and transmits the individual address to the mail transfer server 110.

  The address generation unit 142 is a processing unit that receives an individual address generation request from the communication unit 141, generates an individual address, and passes it to the communication unit 141. The details of the individual address generation process by the address generation unit 142 will be described later.

  Next, a processing procedure by the mail delivery system according to the present embodiment will be described with reference to FIGS. In the following description, a case where the communication partner B330 transmits a mail to the service user A230 will be described as an example. Further, as shown in FIG. 7, the service user A230 can publish the public address “suzuki@privango.net” in advance on the homepage, and the communication partner B330 can use the public address of the service user A230. Shall.

[Mail forwarding process]
FIG. 8 is a sequence diagram illustrating a processing procedure of mail transfer processing by the mail delivery system according to the present embodiment. As shown in the figure, in this mail transfer process, the communication partner B terminal 320 receives a mail transmission request addressed to the public address “suzuki@privango.net” from the communication partner B 330 and sends it to the communication partner B mail server 310. Transmit (step S110). Then, the communication partner B mail server 310 transmits the mail to the mail transfer server 110 because the transmission destination is the public address “suzuki@privango.net” (step S120).

  Then, the filter processing unit 112 of the mail transfer server 110 that has received the mail refers to the compression white list table 132 and the black list table 133 to perform filter processing, that is, whether to transfer mail (step S130). As a result, when the filter processing unit 112 determines that transfer is possible, the process shown in FIG. 9 is performed. When it is determined that transfer is not possible, the mail is discarded. When transferability is unknown, the process shown in FIG.

  That is, when the filter processing unit 112 determines that transfer is possible, the transfer processing unit 113 obtains a real address from the real address table 131 (step S140) and transmits a mail using the real address as the transfer destination, as shown in FIG. (Step S150). Then, the mail received by the service user A mail server 210 is temporarily stored.

  Thereafter, when the service user A terminal 220 requests the service user A mail server 210 to confirm the arrival mail based on an instruction from the service user A 230 (step S160), the service user A mail server 210 temporarily stores the mail. Is transmitted to the service user A terminal 220 (step S170).

  If the filter processing unit 112 determines that transfer is not possible, the filter processing unit 112 requests the address generation unit 142 of the individual address issuing server 140 to generate an individual address as shown in FIG. 10 (step S180). It responds to the communication partner B terminal 320 (step S190) and requests retransmission of the mail.

  Then, upon receiving the individual address, the communication partner B terminal 320 stores the individual address in the address book of the mail software based on the instruction of the communication partner B 330 (step S200), and retransmits the mail with the individual address as the destination. (Step S210). Then, the filter processing unit 112 of the mail transfer server 110 performs a filtering process based on the transfer condition of the individual address, that is, a delivery determination process for determining whether delivery is possible (step S220). If the transfer condition is satisfied, A delivery process for delivering the mail is performed (step S230). Details of the delivery determination process and the delivery process will be described later.

  As described above, the filter processing unit 112 of the mail transfer server 110 refers to the compressed white list table 132 and the black list table 133 to determine whether or not the mail addressed to the public address can be transferred. Since filtering emails based on individual addresses, users can use both the convenience provided by compressed whitelists and blacklists and the certainty provided by individual addresses to eliminate spam. Can be used.

[Filter processing]
Next, the process procedure of the filter process (process corresponding to step S130 shown in FIG. 8) by the filter processing unit 112 will be described. FIG. 11 is a flowchart showing the processing procedure of the filter processing by the filter processing unit 112. Here, a case where the destination address is “suzuki@privango.net” will be described as an example.

  As shown in the figure, in this filter processing, the filter processing unit 112 receives the transmission source address and the destination address, and acquires the user ID u from the destination address (step S131). Here, “suzuki” is acquired as u. Then, the filter processing unit 112 acquires the compressed white list WL corresponding to the user ID u from the compressed white list table 132 (step S132). Here, it is assumed that the compression white list WL = {(0x8a1d742c, 0), (0x56ab129d, 1)} corresponding to “suzuki”.

  Then, the filter processing unit 112 sets the element in the compressed white list WL as w, calculates the hash value of the source address and the domain part, and determines whether there is w that matches the calculated hash value (step) S133). As a result, when such w is in the compression white list, the filter processing unit 112 determines whether or not the black list check flag corresponding to w is “1” (step S133a), and “1 Otherwise, it is determined that the mail can be transferred because the source address or the like having the same hash value is not registered in the corresponding black list (step S136a).

  On the other hand, when the black list check flag is “1”, the filter processing unit 112 acquires the black list BL corresponding to the user ID u from the black list table 133 (step S134a). Here, it is assumed that the black list BL corresponding to “suzuki” = {spammer@black.com}.

  Then, the filter processing unit 112 sets b as an element in the black list BL, and determines whether there is b that matches the transmission source address or partially matches the domain part of the transmission source address (step S135a). As a result, if such b is in the black list, the filter processing unit 112 determines that mail transfer is not possible (step S136b), and if not, mail transfer is possible. Determination is made (step S136a).

  If w that matches the calculated hash value is not in the compressed white list, the filter processing unit 112 acquires the black list BL corresponding to the user ID u from the black list table 133 (step S134).

  Then, the filter processing unit 112 sets the element in the black list BL to b, and determines whether there is b that matches the source address or partially matches the domain part of the source address (step S135). As a result, if such b is in the black list, the filter processing unit 112 determines that the mail cannot be transferred (step S136b), and if not, determines that the transfer is unknown. (Step S136c).

  In this way, the filter processing unit 112 determines whether the element that matches the hash value of the source address or the domain part of the source address is in the compressed white list, and matches the source address or the domain of the source address. Judge whether or not to forward mail based on whether there is an element in the black list that partially matches the part, and if there is no such element in the compressed whitelist or blacklist, determine whether or not forwarding is unknown Thus, the compression white list and the black list can be used together.

  In this example, when the source address or the hash value of the domain part of the source address matches “0x8a1d742c”, it is determined that transfer is possible because the blacklist check flag is “0”, and the source address Is “spammer@black.com”, it is determined that transfer is not possible, and in other cases, it is determined that transfer is not possible.

  In this filter processing, the filter processing unit 112 checks the compression white list and checks the black list after checking the compression white list, but checks the compression white list after checking the black list. It can also be done.

[Address generation processing]
Next, a processing procedure of address generation processing by the address generation unit 142 of the individual address issuing server 140 will be described. FIG. 12 is a sequence diagram illustrating a processing procedure of address generation processing by the address generation unit 142. Here, a case where the caller is limited as a transfer condition will be described as an example.

  As shown in the figure, the address generation unit 142 inputs the user ID u of the service user A and the mail address S of the communication partner B, and generates the transfer condition C related to the caller limitation (step S181). Specifically, after the hash value of the mail address S is obtained, the lower 30 bits of this hash value are encoded with BASE32 to generate a 6-character string V_S (for example, “sbtwr3”).

  Subsequently, the address generation unit 142 generates a tampering prevention code for ensuring the validity of the individual address T (step S182). Specifically, a character string K is generated by concatenating the user ID u (for example, “suzuki”) and the six character string V_S (for example, “sbtwr3”) generated in step S181 above with the dot character “.”. Later, the keyed hash function value of the character string K is obtained using the issued key, and the lower 20 bits of this value are encoded with BASE32 to generate a four-character tamper-proof code V (for example, “gr5b”). To do.

  Then, the address generation unit 142 generates the individual address T using the character string K and the falsification preventing code V (step S183). Specifically, a character string in which a character string K (for example, “suzuki.sbtwr3”) and a falsification prevention code V (for example, “gr5b”) are concatenated is generated, and the domain name “@ privango.net” is added after the character string. Is added to generate and output the individual address T.

  As described above, the address generation unit 142 generates the transfer condition and the falsification prevention code to generate the individual address, so that the transfer condition can be incorporated into the mail address and the individual address can be prevented from being falsified.

[Delivery judgment processing]
Next, details of mail delivery determination processing (processing corresponding to step S220 shown in FIG. 10) by the filter processing unit 112 of the mail transfer server 110 will be described with reference to FIG. FIG. 13 is a flowchart showing details of mail delivery determination processing by the filter processing unit 112. Here, a case where the caller is limited as a transfer condition will be described as an example.

  As shown in FIG. 13, in this delivery determination process, the filter processing unit 112 receives the individual address T and the mail address S of the communication partner B as input, and verifies the validity of the individual address T (falsification prevention code) (step). S221).

  Specifically, the filter processing unit 112 acquires the first half of the user name portion of the incoming mail destination address (that is, the individual address T) from the end to the fifth character as a character string K, and four characters from the end. The second half after the first is acquired as a character string V. Then, the filter processing unit 112 obtains the value of the keyed hash function of the character string K using the verification key, encodes the lower 20 bits of this value with BASE32, obtains the character string T of 4 characters, and obtains the character string V And whether or not the character string T matches. If the two match in this determination, it is determined that the falsification prevention code is valid, and the process proceeds to the following step S222. If the two do not match, the individual address T is determined to be invalid. Is sent to the communication partner B terminal 320, and the delivery determination process is terminated.

  Following such verification of the falsification prevention code, the filter processing unit 112 verifies whether or not it is a legitimate caller (step S222). Specifically, the same algorithm as in the case of generating the individual address T using the hash value of the sender address of the incoming mail (that is, the mail address S of the communication partner) (the algorithm executed in step S181 in FIG. 12 described above) Then, the lower 30 bits of this hash value are encoded with BASE32 to generate a 6-character string T_S. Then, the filter processing unit 112 acquires a portion after the dot character “.” In the character string K acquired in step S221 as the character string V_S, and whether or not the character string V_S matches the character string T_S. Determine whether. If both match in this determination, it is determined that the caller is valid, and the process proceeds to the process of step S223 shown below. However, if both do not match, it is described that the caller is incorrect. The response mail (delivery impossible mail) is transmitted to the communication partner B terminal 320, and the delivery determination process is terminated.

  As a result, when both of the delivery determinations (steps S221 and S222) described above are satisfied, the filter processing unit 112 performs a character string (for example, “a” before the dot character “.” In the user name portion of the individual address T). suzuki ") is extracted as the user ID u (step S223), the user ID u and the delivery determination result are output, and the delivery determination process is terminated.

  As described above, the filter processing unit 112 verifies the falsification prevention code and the caller, and determines whether or not delivery is possible based on the verification result, thereby preventing unauthorized mail transfer.

[Compressed whitelist manual registration process]
Next, a processing procedure of registration processing of a reception permitted address and a reception permitted domain name to the compressed white list by the mail delivery system according to the present embodiment will be described. FIG. 14 is a sequence diagram illustrating a processing procedure for registering a reception-permitted address and a reception-permitted domain name in the compressed white list by the mail delivery system according to the present embodiment. Here, a case where the service user A230 registers the reception permission address in the compressed white list will be described.

  As shown in the figure, in the registration process to the compressed white list, the service user A terminal 220 receives an input of a registration address (reception permission address) registered in the compressed white list from the service user A 230 (step S310). The permitted address registration request is made to the compressed whitelist / blacklist registration server 120 together with the user ID and the registered address (step S320). For example, the service user A terminal 220 sends a permission address registration request to the compressed whitelist / blacklist registration server 120 together with the user ID “suzuki” and the registration address “taro@isp-A.ne.jp”.

  Then, the compression whitelist registration processing unit 122 of the compression whitelist / blacklist registration server 120 receives the user ID and the registration address, calculates the hash value of the registration address, and sends the hash value to the data management server 130. A compressed white list registration process for requesting registration to the compressed white list corresponding to the user ID is performed (step S330). When the registration in the compressed white list table 132 is completed, the compressed white list registration processing unit 122 transmits an address registration response to the service user A terminal 220 (step S340).

  As described above, the compression whitelist registration processing unit 122 of the compression whitelist / blacklist registration server 120 requests the data management server 130 to register to the compression whitelist based on the request from the service user A230. The hash value of the reception permitted address and the reception permitted domain name can be registered in the compressed white list table 132.

[Blacklist manual registration process]
Next, a processing procedure of registration processing of a reception refusal address to the black list and a reception refusal domain name by the mail delivery system according to the present embodiment will be described. FIG. 15 is a sequence diagram illustrating a processing procedure of registration processing of a reception refusal address and a reception refusal domain name to the black list by the mail delivery system according to the present embodiment. Here, the case where the service user A230 registers the reception refusal address in the black list will be described.

  As shown in the figure, in the blacklist registration process, the service user A terminal 220 accepts an input of a registration address (reception refusal address) registered in the blacklist from the service user A230 (step S410), and the user A rejection address registration request is sent to the compressed whitelist / blacklist registration server 120 together with the ID and registration address (step S420). For example, the service user A terminal 220 makes a rejection address registration request to the compressed whitelist / blacklist registration server 120 together with the user ID “suzuki” and the registration address “spammer@black.com”.

  Then, the blacklist registration processing unit 123 of the compressed whitelist / blacklist registration server 120 receives the user ID and the registration address, and registers the registration address in the blacklist corresponding to the user ID with respect to the data management server 130. The requested blacklist registration process is performed (step S430). When the registration in the black list table 133 is completed, the black list registration processing unit 123 transmits an address registration response to the service user A terminal 220 (step S440).

  In this way, the blacklist registration processing unit 123 of the compressed whitelist / blacklist registration server 120 requests the data management server 130 to register to the blacklist based on the request of the service user A230, thereby rejecting the reception. Addresses and reception refusal domain names can be registered in the black list table 133.

  14 and 15, the case where the service user A230 makes a registration request to the compressed whitelist and blacklist from the service user A terminal 220 has been described. However, registration and deletion to the compressed whitelist and blacklist are described. Can also be performed automatically. Therefore, automatic registration to the compressed white list and automatic registration / deletion processing to the black list will be described.

[Compressed whitelist automatic registration processing]
FIG. 16 is a sequence diagram illustrating a processing procedure in which the mail delivery system according to the present embodiment automatically registers the hash value of the destination address in the compressed white list when the service user A230 transmits mail to the new communication partner B330. is there. Here, it is assumed that all mails transmitted by the service user A230 are transferred to the mail transfer server 110. In addition, when the service user A230 sends a mail, it is considered that the service user A230 receives a mail from the communication partner B330. Therefore, the hash value of the destination address of the communication partner B330 is automatically registered in the compressed white list. .

  As shown in FIG. 16, in the automatic registration process to the compressed white list, the service user A terminal 220 transmits a mail to a new communication partner based on an instruction from the service user A 230 (step S510).

  Then, the compressed whitelist automatic processing unit 114 of the mail transfer server 110 registers the hash value of the destination address in the compressed whitelist corresponding to the user ID of the service user A230. The compressed whitelist registration processing unit 122 is requested (step S520). For example, it requests registration of the hash value of “taro@isp-A.ne.jp” to the compression white list corresponding to the user ID “suzuki”.

  When the registration in the compressed white list table 132 is completed, the compressed white list automatic processing unit 114 transmits a mail to the communication partner B mail server 310 (step S530), and the mail received by the communication partner B mail server 310 is transmitted. Store temporarily.

  Thereafter, when the communication partner B terminal 320 requests the communication partner B mail server 310 to confirm the arrival mail based on the instruction of the communication partner B 330 (step S540), the communication partner B mail server 310 transmits the temporarily stored mail to the communication partner B. It transmits to the terminal 320 (step S550).

  As described above, when the service user A 230 sends a mail to a new communication partner, the compressed white list automatic processing unit 114 automatically registers the hash value of the destination address in the compressed white list, so that the user can receive it. It is possible to reduce the burden of registering hash values such as permitted email addresses in the compressed white list.

  In addition, the communication partner B330 that is not registered in either the compressed white list or the black list transmits mail, and the mail transfer server 110 requests that the mail be resent with the individual address as a destination, and responds to the request individually. When the mail retransmitted with the address as the destination satisfies the transfer condition, the hash value of the mail address of the communication partner B330 can be automatically registered in the compressed white list. In other words, when the mail addressed to the individual address satisfies the transfer condition, it is considered that the communication partner B330 can be trusted, so the hash value of the mail address of the communication partner B330 can be registered in the compressed white list.

  A processing procedure for automatically registering the hash value of the sender address in the compressed white list when a mail addressed to the individual address satisfies the transfer condition will be described. FIG. 17 is a sequence diagram illustrating a processing procedure in which the mail delivery system according to the present embodiment automatically registers the hash value of the sender address in the compressed white list when the mail addressed to the individual address satisfies the transfer condition. .

  As shown in FIG. 17, in the automatic registration process to the compressed white list, when the communication partner B 330 transmits a mail from the communication partner B terminal 320 in response to a mail resend request addressed to the individual address (step S610). The communication partner B mail server 310 receives the mail and transmits it to the mail transfer server 110 (step S620). For example, the individual address “suzuki.sbtwr3gr5b@privango.net” is used as the destination address.

  Then, when the filter processing unit 112 of the mail transfer server 110 performs the delivery determination process shown in FIG. 13 (step S630) and determines that the delivery is possible, the sender to the compressed white list corresponding to the user ID included in the individual address is sent. The compression white list automatic processing unit 114 requests the compression white list registration processing unit 122 of the compression white list / black list registration server 120 to register the hash value of the address (step S640). For example, the hash value of the sender address “taro@isp-A.ne.jp” is registered in the compressed white list corresponding to the user ID “suzuki” included in the individual address. Thereafter, the transfer processing unit 113 replaces the destination address with the real address and transmits the mail to the service user A mail server 210 (step S650).

  In this way, when a mail addressed to an individual address satisfies the transfer conditions, the hash value of the sender address is automatically registered in the compressed white list, so that the mail address or the like that the user is allowed to receive is compressed in the compressed white list. Can reduce the burden of registering.

  Note that the hash value of the mail address of the reply destination is automatically registered in the compressed white list when a reply is made to the mail addressed to the individual address instead of when the mail addressed to the individual address satisfies the forwarding condition. You can also. FIG. 18 is a sequence diagram illustrating a processing procedure in which the mail delivery system according to the present embodiment automatically registers the hash value of the reply destination mail address in the compressed white list when a reply is made to the mail addressed to the individual address. is there.

  As shown in FIG. 18, in the automatic registration process to the compressed whitelist, when the service user A terminal 220 replies to the mail addressed to the individual address based on the instruction from the service user A230 (step S710), the mail transfer The server 110 receives the message via the service user A mail server 210.

  Here, when the mail addressed to the individual address is sent to the service user A230, since the destination address is converted to the real address, is the reply mail sent from the service user A230 a reply to the mail addressed to the individual address? It cannot be specified from the sender address of the reply mail, but by adding information indicating that it is mail addressed to the individual address to the forwarded mail and reply mail converted from the individual address to the real address The mail transfer server 110 can determine whether the reply mail is a mail addressed to an individual address.

  For example, as shown in FIG. 19, when the mail transfer server 110 receives a mail whose destination address is the public address “suzuki@privango.net” and receives a mail addressed to the individual address after a request for resending the mail addressed to the individual address, The transfer processing unit 113 rewrites the individual address to the real address “suzuki1010@anywhere.ne.jp” and transmits it to the service user A230. At this time, the transfer processing unit 113 converts the real address “taro@isp-A.ne.jp” of the mail source into the format of “taro/isp-A.ne.jp/suzuki@privango.net” (hereinafter, “ (Reply format) and send email.

  When the reply mail for the mail addressed to the individual address is received, the mail transfer server 110 extracts the user ID “suzuki” from the reply destination address “taro/isp-A.ne.jp/suzuki@privango.net”. , Rewrite the destination address to “taro@isp-A.ne.jp” and rewrite the source address to “suzuki@privango.net” and forward the mail.

  In this way, the mail transfer server 110 rewrites the destination address from the individual address to the real address, rewrites the real address of the transmission source in the reply format, and receives the reply mail in which the destination address is the reply format. You can know that it is a reply mail for. In addition, by rewriting the destination address in the reply format to the real address and rewriting the transmission source address to the public address, disclosure of the real address can be prevented even when the user directly replies to the mail of the public address.

  Returning to FIG. 18, when the mail transfer server 110 receives the reply mail whose reply is in the reply format, the compressed whitelist automatic processing unit 114 uses the user ID and the registered address (destination address) included in the reply address. The compression whitelist / blacklist registration server 120 requests the compression whitelist registration processing unit 122 to register (step S720). For example, it requests registration of the hash value of “taro@isp-A.ne.jp” to the compression white list corresponding to the user ID “suzuki”.

  Then, the mail transfer server 110 performs a source address rewriting process for rewriting the source address of the reply mail to the public address (step S730). For example, the sender address of the reply mail is rewritten as “suzuki@privango.net”. Then, the communication mail is transmitted to the communication partner B mail server 310 (step S740), and the mail received by the communication partner B mail server 310 is temporarily stored.

  Thereafter, when the communication partner B terminal 320 requests the communication partner B mail server 310 to confirm the arrival mail based on the instruction of the communication partner B 330 (step S750), the communication partner B mail server 310 transmits the temporarily stored mail to the communication partner B. It transmits to the terminal 320 (step S760).

  Thus, when a reply is made to a mail addressed to an individual address, the user ID and the mail address of the communication partner B330 are reproduced from the reply mail reply address and automatically registered in the compressed whitelist. The burden of registering e-mail addresses permitted to be received by the user in the compressed white list can be reduced.

[Compressed whitelist registration process]
FIG. 20 is a flowchart showing the processing procedure of the compressed whitelist registration processing by the compressed whitelist registration processing unit 122 of the compressed whitelist / blacklist registration server 120. As shown in the figure, in this compressed white list registration process, the compressed white list registration processing unit 122 receives the user ID u and the registered address a, and firstly, converts the compressed white list WL corresponding to the user ID u to the compressed white list. Obtained from the table 132 (step S331). Here, it is assumed that the user ID u = “suzuki”, the registered address a = “taro@isp-A.ne.jp”, and the compressed white list WL = {(0x8a1d742c, 0), (0x56ab129d, 1)}.

  Then, the compressed whitelist registration processing unit 122 sets w as an element in the compressed whitelist WL, and determines whether there is a w that matches the hash value of the registered address a (step S332). As a result, if there is no w that matches the hash value of the registered address a, the hash value of the registered address a is registered in the compressed white list WL corresponding to the user ID u in the compressed white list table 132 (step S333). If there is w that matches the hash value of the registered address a, step S333 is skipped. Here, since the compressed whitelist WL = {(0x8a1d742c, 0), (0x56ab129d, 1)} has the hash value “0x8a1d742c” of the registered address a = “taro@isp-A.ne.jp”, step S333 is executed. skip.

  Then, the compressed white list registration processing unit 122 acquires the black list BL corresponding to the user ID u from the black list table 133 (step S334). Here, the black list BL={spammer@black.com}. Then, the compressed white list registration processing unit 122 sets b as an element in the black list BL, and determines whether there is b that matches the registered address a (step S335). As a result, if there is b matching the registered address a, the registered address a is deleted from the black list BL corresponding to the user ID u in the black list table 133 (step S336), and b matching the registered address a is If not, step S336 is skipped. Here, since there is no b that matches the registered address a, step S336 is skipped.

  As described above, when the compressed white list registration processing unit 122 registers the hash value of the registered address in the compressed white list, by checking that the same registered address is not registered in the compressed white list and the black list, Consistency between the compressed whitelist and blacklist can be taken to ensure correct filtering.

[Blacklist automatic registration processing and automatic deletion processing]
FIG. 21 is a sequence diagram illustrating a processing procedure of blacklist automatic registration processing by the mail delivery system according to the present embodiment. Here, in the case where a mail is received from a communication partner B330 that is not registered in the compressed whitelist or the blacklist and an individual address is notified, the destination address of the communication partner B330 is assumed to be unreliable for the time being. To the blacklist.

  As shown in FIG. 21, in the blacklist automatic registration process, when the filter processing unit 112 requests the individual address issuing server 140 to issue an individual address (step S180), the blacklist automatic processing unit 115 The blacklist registration processing unit 123 of the compressed whitelist / blacklist registration server 120 is requested to register the mail sender address (the destination address of the individual address) in the blacklist corresponding to the user ID included in the individual address. (Step S185). Here, registration of “taro@isp-A.ne.jp” is requested to the black list corresponding to the user ID “suzuki”. When registration in the black list table 133 is completed, the filter processing unit 112 transmits the individual address to the communication partner B terminal 320 (step S190).

  In this way, the blacklist automatic processing unit 115 registers the communication partner B330 to which the individual address is transmitted to the blacklist for the time being, thereby reducing the burden of the user registering the email address to be rejected on the blacklist. Can do.

  However, when performing such automatic registration, it is necessary to delete the address automatically registered in the black list when it is determined that the communication partner B330 to which the individual address is transmitted can be trusted. A process for deleting an address automatically registered in the black list when it is determined that the communication partner B330 is reliable will be described.

  FIG. 22 shows that the mail delivery system according to the present embodiment automatically deletes the sender address from the black list when the communication partner B330 is found to be reliable, that is, when the mail addressed to the individual address satisfies the transfer condition. It is a sequence diagram which shows a processing procedure. As shown in FIG. 22, in this automatic deletion process from the black list, when the communication partner B 330 transmits a mail from the communication partner B terminal 320 in response to a mail resend request destined for an individual address (step S810), communication is performed. The partner B mail server 310 receives the mail and transmits it to the mail transfer server 110 (step S820). Here, the individual address “suzuki.sbtwr3gr5b@privango.net” is used as the destination address.

  Then, when the filter processing unit 112 of the mail transfer server 110 performs the delivery determination process shown in FIG. 13 (step S830) and determines that delivery is possible, the sender address from the black list corresponding to the user ID included in the individual address The blacklist automatic processing unit 115 requests the blacklist registration processing unit 123 of the compressed whitelist / blacklist registration server 120 to delete the data (step S840). For example, a request is made to delete the sender address “taro@isp-A.ne.jp” from the black list corresponding to the user ID “suzuki” included in the individual address. Thereafter, the transfer processing unit 113 replaces the destination address with a real address and transmits a mail to the service user A mail server 210 (step S850).

  As described above, when the mail addressed to the individual address satisfies the transfer condition, the sender address is automatically deleted from the black list, so that the mail address registered in the black list can be deleted from the black list for the time being.

[Blacklist registration processing]
FIG. 23 is a flowchart showing a processing procedure of blacklist registration processing by the blacklist registration processing unit 123 of the compressed whitelist / blacklist registration server 120. As shown in the figure, in this blacklist registration process, the blacklist registration processing unit 123 receives the user ID u and the registration address a, and first acquires the blacklist BL corresponding to the user ID u from the blacklist table 133. (Step S431). Here, it is assumed that the user ID u = “suzuki”, the registered address a = “spammer@black.com”, and the black list BL={spammer@black.com}.

  Then, the blacklist registration processing unit 123 sets b as an element in the blacklist BL, and determines whether there is b that matches the registered address a (step S432). As a result, if there is no b matching the registered address a, the registered address a is registered in the black list BL corresponding to the user ID u of the black list table 133 (step S433), and b matching the registered address a is If there is, step S433 is skipped. Here, since the registered address a = “spammer@black.com” is in the black list BL={spammer@black.com}, step S433 is skipped.

  Then, the black list registration processing unit 123 acquires the compressed white list WL corresponding to the user ID u from the compressed white list table 132 (step S434). Here, the compression white list WL = {(0x8a1d742c, 0), (0x56ab129d, 1)}. Then, the blacklist registration processing unit 123 calculates the hash value of the registered address a using w as the element in the compressed whitelist WL, and determines whether there is a w that matches the calculated hash value (step S435). ). As a result, when there is w that matches the hash value of the registered address a, the black list check flag corresponding to the matched hash value among the hash values of the user ID u in the compressed white list table 132 is set to “1” ( Step S436) If there is no w that matches the hash value of the registered address a, step S436 is skipped. Here, since there is no w that matches the hash value of the registered address a, step S436 is skipped.

  As described above, when the blacklist registration processing unit 123 registers a registered address in the blacklist, the blacklist registration processing unit 123 registers the blacklist by setting the blacklist check flag corresponding to the hash value of the registered address to “1”. When the hash value of the address that has been matched with the hash value registered in the compressed white list, it is possible to prevent an error that the mail is transferred.

[Effect of this embodiment]
As described above, according to the present embodiment, the hash value of the reception-permitted address or the reception-permitted domain name is stored in the compressed white list table 132 in correspondence with the user, and the mail sent by the filter processing unit 112 is transmitted. Since the hash value is calculated from the domain part of the original address and the source address, and the hash value matching the calculated hash value is in the compressed white list table 132, the mail transfer is permitted. The table size can be reduced as compared with the case where the reception permitted domain name is stored as it is, and the storage resource managed by the data management server 130 can be reduced. Alternatively, when the storage resources managed by the data management server 130 are not reduced, the number of reception-permitted addresses and reception-permitted domain names that can be registered by the user can be increased.

  Further, according to the present embodiment, when registering a reception rejection address or reception rejection domain name in the user's blacklist, the blacklist registration processing unit 123 calculates a hash value from the reception rejection address or reception rejection domain name. If there is a matching hash value in the compressed white list corresponding to the user in the compressed white list table 132, the black list check flag corresponding to the matching hash value is set to “1”, and the transfer process is performed. If the hash value that matches the hash value calculated from the sender address of the mail and the domain part of the sender address is in the compressed white list, the unit 113 checks the black list check flag corresponding to the matching hash value, When the value of the list check flag is "1", mail forwarding is permitted Instead, it is decided to refer to the black list to determine whether the mail is unforwardable or unclearable, so the hash value that matches the hash value of the reception rejection address or reception rejection domain name is the compressed whitelist. Can be prevented from being accidentally permitted to transfer emails.

  Further, according to the present embodiment, the data management server 130 stores the compressed white list and the black list in the compressed white list table 132 and the black list table 133 in association with the user ID, respectively, and generates the address of the individual address issuing server 140. When the unit 142 generates an individual address, the filter processing unit 112 of the mail transfer server 110 determines whether or not the mail addressed to the public address can be transferred using the compressed white list and the black list. Requests the sender of the mail to resend the mail using the individual address generated by the address generation unit 142, and forwards the mail to the recipient when the mail sent to the individual address satisfies the transfer condition. Compressed whitelist and black because we decided to The mail delivery system can be used together with the convenience provided by the compressed whitelist and blacklist for spam mail and the certainty provided by the mail delivery system using conditional individual addresses. be able to.

  Further, according to the present embodiment, when the user transmits mail to a new communication partner, the compressed white list automatic processing unit 114 of the mail transfer server 110 compresses the hash value of the mail address of the communication partner. When a mail is received from a communication partner that is registered in, and is not registered in the compressed whitelist or blacklist, when it is determined that the communication partner is reliable or when a reply is made to the communication partner, the communication partner Since the hash value of the e-mail address is registered in the compressed white list, the burden of maintaining the compressed white list by the user can be reduced.

  Further, according to the present embodiment, when the black list automatic processing unit 115 of the mail transfer server 110 receives mail from a communication partner that is not registered in the compressed white list or the black list, the mail address of the communication partner Once registered in the blacklist, and the email address once registered in the blacklist is deleted when the communication partner is found to be reliable, the burden on the user of maintaining the blacklist can be reduced. .

  Further, according to the present embodiment, when the compression whitelist registration processing unit 122 of the compression whitelist / blacklist registration server 120 registers the hash value of the email address or domain name that is permitted to be received in the compression whitelist, the registration is performed. Check whether the email address or domain name that matches the email address or domain name to be registered is in the blacklist, and the same email address or domain name is registered in the compressed whitelist and the blacklist, making it inconsistent It is possible to guarantee the correct mail transfer.

  In this embodiment, when the individual address is rewritten to the real address and transmitted to the service user A230, the transfer processing unit 113 rewrites the mail source address (mail address of the communication partner B330) in the reply format. When the mail transfer server 110 receives the reply mail addressed to the reply address, the mail transfer server 110 extracts the user ID from the reply address, rewrites the destination address to the mail address of the communication partner B330, and returns the reply mail. Since the mail source address is rewritten to the public address and the mail is transferred, it is possible to prevent the real address of the service user A230 from being disclosed in the reply mail.

[Other examples]
In this embodiment, if the hash value of the sender's email address is not registered in the compressed white list and the sender's email address is not registered in the black list, an individual address is generated. Although the three-layer control for requesting the sender to retransmit has been described, the black list can be used in combination with the compressed white list for the purpose of preventing erroneous determination by the compressed white list without using an individual address. In other words, due to the compression of the white list, the hash value of the email address that rejects incoming calls matches the hash value registered in the compressed white list, and an incoming email that rejects incoming calls is permitted. The black list can be used together with the compressed white list for the purpose of preventing the determination.

  FIG. 24 is a flowchart showing the processing procedure of the filter processing of the filter processing unit 112 when the black list is used together with the compressed white list for the purpose of preventing erroneous determination by the compressed white list.

  As shown in the figure, in this filter processing, the filter processing unit 112 receives the transmission source address and the destination address, and acquires the user ID u from the destination address (step S901). Then, the filter processing unit 112 acquires the compressed white list WL corresponding to the user ID u from the compressed white list table 132 (step S902).

  Then, the filter processing unit 112 sets the element in the compressed white list WL as w, calculates the hash value of the source address and the domain part, and determines whether there is w that matches the calculated hash value (step) S903). As a result, when such w is not in the compression white list, the filter processing unit 112 determines that the mail cannot be transferred (step S906b).

  On the other hand, if there is w that matches the calculated hash value, the filter processing unit 112 acquires the black list BL corresponding to the user ID u from the black list table 133 (step S904). Then, the element in the black list BL is set to b, and it is determined whether or not there is b that matches the source address or partially matches the domain part of the source address (step S905). If it is, the filter processing unit 112 determines that mail transfer is not possible (step S906b). If not, it determines that mail transfer is possible (step S906a).

  As described above, the filter processing unit 112 can prevent erroneous determination due to the compressed white list by using the compressed white list and the black list together. In the filter processing shown in FIG. 24, the case where the black list is always checked when the element matching the calculated hash value is in the compressed white list has been described. However, the black list is checked using the black list check flag. It is also possible to perform the check efficiently.

  FIG. 25 is a flowchart showing the processing procedure of the filter processing of the filter processing unit 112 when the black list is efficiently checked using the black list check flag. As shown in the figure, in this filter process, the filter processing unit 112 receives the transmission source address and the destination address, and acquires the user ID u from the destination address (step S911). Then, the filter processing unit 112 acquires the compressed white list WL corresponding to the user ID u from the compressed white list table 132 (step S912).

  Then, the filter processing unit 112 sets the element in the compressed white list WL as w, calculates the hash value of the source address and the domain part, and determines whether there is w that matches the calculated hash value (step) S913). As a result, when such w is not in the compression white list, the filter processing unit 112 determines that the mail cannot be transferred (step S917b).

  On the other hand, if there is w that matches the calculated hash value, the filter processing unit 112 determines whether or not the black list check flag corresponding to w is “1” (step S914), and “1”. If not, since the source address or the like having the same hash value is not registered in the corresponding black list, it is determined that the mail can be transferred (step S917a).

  On the other hand, when the black list check flag is “1”, the filter processing unit 112 acquires the black list BL corresponding to the user ID u from the black list table 133 (step S915). Then, the filter processing unit 112 sets the element in the black list BL to b, and determines whether there is b that matches the source address or partially matches the domain part of the source address (step S916). As a result, if such b is in the black list, the filter processing unit 112 determines that mail transfer is not possible (step S917b), and if not, mail transfer is possible. Determination is made (step S917a).

  As described above, by using the black list check flag, it is possible to efficiently perform the check even when the black list is checked in order to prevent erroneous determination by the compressed white list.

  In the present embodiment, a case has been described in which a hash value calculated from a mail address is registered in the compression white list. However, the present invention is not limited to this and can be obtained from the mail address by another information compression method. The same can be applied to the case where the compression information is registered in the compression white list. For example, only a predetermined number of characters in the mail address can be registered in the compressed white list.

  Further, in the present embodiment, the case where the hash value is registered in the compressed white list instead of the mail address has been described. However, the present invention is not limited to this, and the compressed information is substituted in the black list instead of the mail address. The same applies to registration. However, it should be noted that when a plurality of mail addresses are compressed into the same compressed information, a message that the user wants to receive may be rejected.

  In this embodiment, the automatic registration of the compressed whitelist has been described. However, for each user, the last mail transmission date, the last mail transmission time, the last mail reception date, the last mail reception time, etc. with each communication partner are described. When the last communication time is stored as communication history information, and when the communication history information is compared with the current time such as the current date or time and the difference between the two is greater than a predetermined value, mail is not sent or received for a predetermined period The hash value of the mail address corresponding to the communication partner can be automatically deleted from the compressed white list. Similarly, for the black list, the last reception time such as the last mail reception date and the last mail reception time from each sender is stored as communication history information for each user, and the communication history information and the current date and time are stored. If the difference between the current time and the current time is larger than a predetermined value, it is possible to automatically delete the corresponding mail address from the black list assuming that no mail has been received for a predetermined period.

  In addition, the maximum number of registrations is set for each user for the compressed white list and the black list, and when the maximum number of registrations has already been performed when registering in the compressed white list and the black list, respectively. Can refer to the communication history information and automatically delete the hash value and the mail address registered in the compressed white list and black list, respectively, with the oldest mail communication time or the last mail reception time. it can.

  Further, as the communication history information, the communication frequency can be stored instead of the last communication time point, and information with a low communication frequency can be automatically deleted from the compressed white list.

  Note that when registering compressed information in the compressed white list, depending on the compression method, it becomes difficult for the user to recognize the registered information, and thus it is difficult for the user to delete the registered information. Therefore, it is conceivable that the compressed white list is enlarged. For this reason, the automatic deletion function of the compressed white list that prevents the compressed white list from being enlarged is an extremely important function in practice. Also, if the compressed white list is automatically deleted, there is a possibility that an email to be received cannot be received. Therefore, when the compressed white list is simply used, there is a problem in automatically deleting the compressed white list. However, when the hash value corresponding to the communication partner permitted to receive is automatically deleted from the compressed white list by performing the three-layer control using the compressed white list, the black list, and the individual address as in this embodiment. However, since incoming calls can be made using individual addresses, the compressed white list can be automatically deleted.

  In this embodiment, the case where the compressed white list is used has been described. However, a normal white list that is not compressed and a compressed white list can be used in combination. For example, registration of the reception permission address based on the user's instruction is performed for a normal white list, and maintenance of the white list is performed by the user. On the other hand, it is assumed that the reception permission address that is automatically registered is registered in the compressed white list, and the deletion from the compressed white list is performed only by automatic deletion. Further, the transfer permission is determined to be transferable if it is registered in either the white list or the compressed white list. In this way, by using a compressed whitelist and a normal whitelist together, the user can use the advantages of the compression of the compressed whitelist and the advantages of the ease of maintaining the normal whitelist separately. Can do.

  In addition, a normal white list is initially used, and when the number of registrations reaches a predetermined number, some reception permission addresses and the like can be moved to the compressed white list. In this way, when the number of registrations reaches a predetermined number, by moving some reception-permitted addresses and the like to the compressed white list, the user can easily maintain and avoid erroneous transfer while the number of registrations is small. When the number of registrations is increased by using the list, it is possible to selectively use a compressed white list that is difficult to maintain and may be erroneously transferred. In addition to letting the user specify some reception-permitted addresses etc. to the compressed white list, for example, in addition to the order of the most frequent communication or the last communication time point closest to the current time, Can be moved.

  In addition, here, automatic whitelist registration / automatic deletion and blacklist automatic registration / automatic deletion of a three-layer mail delivery system that combines a compression whitelist, blacklist, and other filtering methods have been described. Automatic registration / deletion of whitelist and automatic registration / deletion of blacklist are mail delivery systems that use only compressed whitelists and blacklists, or two-layer mail delivery that combines compressed whitelists and other filtering methods. The present invention can also be applied to a two-layer mail delivery system that combines a system and a black list with other filtering methods.

  Conventionally, if you automatically delete a compressed whitelist or blacklist, emails from people who have been allowed to receive will not be delivered suddenly, or spam emails will suddenly arrive. It was impossible for the service to automatically delete the blacklist. However, two-layer transfer control that combines the compressed whitelist and other filtering methods, two-layer transfer control that combines the blacklist and other filtering methods, or a combination of compressed whitelist, blacklist, and other filtering By performing three-layer transfer control, it is possible to automatically delete the compressed white list and black list in terms of service.

  In the present embodiment, the case where the hash value of the email address or domain name is registered in the compressed white list and the email address or domain name is registered in the black list has been described. However, the present invention is not limited to this. The same applies to the case where other information related to the mail sender is compressed and registered in the compressed white list, and other information related to the mail sender is registered in the black list to determine whether the mail can be transferred. be able to.

  In this embodiment, the mail delivery system has been described from the functional aspect, but in reality, each device such as the mail transfer server 110 and the data management server 130 can be realized by a commercially available computer. It is sufficient to install a program on each of these computers. This program may be loaded not only from a secondary recording medium such as a hard disk device or a ROM but also from a recording medium such as a CD-R. For example, when loading a program from a CD-R, a mail transfer server 110 program, a data management server 130 program, etc. are stored in advance on a CD-R (may be a separate CD-R for each device). The CD-R is loaded into the CD-R reader of each device, and the program is loaded.

  In the present embodiment, the case where four server devices are used, that is, a mail transfer server, a compressed whitelist / blacklist registration server, a data management server, and an individual address issuing server, is described, but the present invention is limited to this. For example, when the functions provided by the compression whitelist / blacklist registration server and the data management server are provided by one server device, or when all the functions are provided by one server device, the same applies. Can be applied.

  Further, in the present embodiment, a case has been described in which a mail address used for an electronic mail message such as an Internet mail or a mobile mail is targeted, but the present invention is not limited to this, for example, a so-called instant message. It is also possible to target message addresses used for SIP messages such as presence exchange messages and IP telephone control messages. In other words, the present invention can be similarly applied not only when delivering e-mail messages between users, but also when delivering SIP messages such as instant messages, presence exchange messages, and IP phone control messages. it can.

  Further, in the present embodiment, a case has been described in which a mail destination address (TO address) is replaced with a real address for transfer, but it is not essential to replace the destination address at the time of transfer. In the transfer protocol for transferring mail data to the mail server without replacing the mail, the mail may be transferred by defining the real address of the mail transfer destination.

  In the present embodiment, the case where the mail transfer server transfers the mail to the mail server for the recipient has been described. However, the present invention is not limited to this. For example, the mail transfer server is for the recipient. As a mail server, the mail can be distributed and stored in the message box of the receiver of the mail transfer server (the box corresponding to the actual address of the receiver). It may be.

  As described above, the message delivery system, the message transfer device, the message transfer method, and the message transfer program according to the present invention are useful for message delivery that eliminates annoying messages, and particularly for storing white lists and black lists. This is suitable when it is necessary to reduce the required storage area or when it is desired to increase the number of registered white lists and black lists.

It is a figure which shows the structure of the mail delivery system which concerns on a present Example. It is a figure which shows an example of a public address. It is a figure which shows an example of an individual address. It is a figure which shows an example of a real address table. It is a figure which shows an example of a compression white list table. It is a figure which shows an example of a black list table. It is a figure which shows disclosure of a public address. It is a sequence diagram (1) which shows the process sequence of the mail transfer process by the mail delivery system concerning a present Example. It is a sequence diagram (2) which shows the process sequence of the mail transfer process by the mail delivery system concerning a present Example. It is a sequence diagram (3) which shows the process sequence of the mail transfer process by the mail delivery system concerning a present Example. It is a flowchart which shows the process sequence of the filter process by a filter process part. It is a sequence diagram which shows the process sequence of the address generation process by an address generation part. It is a flowchart which shows the detail of the mail delivery determination process by a filter process part. It is a sequence diagram which shows the process sequence of the registration process of the reception permission address and reception permission domain name to the compression white list by the mail delivery system which concerns on a present Example. It is a sequence diagram which shows the process sequence of the registration process of the reception refusal address and reception refusal domain name to a black list by the mail delivery system which concerns on a present Example. FIG. 10 is a sequence diagram illustrating a processing procedure in which the mail delivery system according to the present embodiment automatically registers the hash value of the destination address in the compressed white list when the service user A transmits mail to a new communication partner B. FIG. 10 is a sequence diagram illustrating a processing procedure in which a mail delivery system according to the present embodiment automatically registers a hash value of a sender address in a compressed white list when a mail addressed to an individual address satisfies a transfer condition. FIG. 10 is a sequence diagram illustrating a processing procedure in which the mail delivery system according to the embodiment automatically registers the hash value of the reply destination mail address in the compressed white list when a reply is made to the mail addressed to the individual address. It is explanatory drawing for demonstrating the address of a reply format used for identification of the reply mail with respect to mail addressed to an individual address. It is a flowchart which shows the process sequence of the compression white list registration process by the compression white list registration process part of a compression white list and black list registration server. It is a sequence diagram which shows the process sequence of the black list automatic registration process by the mail delivery system which concerns on a present Example. The processing procedure for automatically deleting the sender address from the black list by the mail delivery system according to the present embodiment when the communication partner B is found to be reliable, that is, when the mail addressed to the individual address satisfies the transfer condition is shown. It is a sequence diagram. It is a flowchart which shows the process sequence of the black list registration process by the black list registration process part of a compression white list and black list registration server. It is a flowchart which shows the process sequence of the filter process of the filter process part in the case of using a black list together with a compression white list for the purpose of preventing the misjudgment by a compression white list. It is a flowchart which shows the process sequence of the filter process of the filter process part in the case of performing a black list check efficiently using a black list check flag.

Explanation of symbols

100 LAN
110 mail transfer server 111 mail communication unit 112 filter processing unit 113 transfer processing unit 114 compression white list automatic processing unit 115 black list automatic processing unit 120 compression white list / black list registration server 121 HTTP communication unit 122 compression white list registration processing unit 123 Blacklist registration processing unit 130 Data management server 131 Real address table 132 Compressed whitelist table 133 Blacklist table 140 Individual address issuing server 141 Communication unit 142 Address generation unit 210 Service user A mail server 220 Service user A terminal 230 Service use Person A
240 service user A side IP network 310 communication partner B mail server 320 communication partner B terminal 330 communication partner B
340 Communication partner B side IP network 400 Internet

Claims (15)

A message delivery system for delivering a message based on caller information, which is information about a message sender,
And allow the caller compression information storage means the user has authorized caller compression information remembers obtained by compressing the information about the caller you allowed to receive,
Rejected caller information storage means that stores rejected caller information that is information about a caller that the user refuses to receive,
Rejected caller information determination necessity storage means for storing the necessity of transfer rejection determination by the rejected caller information corresponding to the permitted caller compression information as necessity information;
A sender information compression means for compressing the sender information of the arrived message and generating the sender compressed information;
Allow outgoing said arrived the allowed caller compression information that corresponds to the destination of the message is read from the authorized caller compression information storage unit compared with the caller compressed information generated by the caller information compression means, consistent The message can be transferred when it is determined that the necessity information corresponding to the matching permitted sender compression information in the rejected sender information determination necessity storage means is unnecessary. When there is matching permitted caller compression information and the necessity information corresponding to the matching permitted caller compression information in the rejected caller information determination necessity storage means needs to be determined, the arrival The rejected caller information corresponding to the address of the received message is read from the rejected caller information storage means and compared with the caller information of the message. A transfer permission determination unit disables the transfer and determines,
When new sender information is registered as rejected sender information in the rejected sender information storage means, new sender information is compressed to generate compressed sender information, and the generated compressed sender information is rejected. Corresponds to the matched permitted caller compressed information in the rejected caller information determination necessity storage means when it matches any of the permitted caller compressed information corresponding to the user who is the registration target of the caller information A message delivery system comprising: necessity information setting means for setting necessity information to determination necessity . A communication history information storage means for storing communication history information of the communication partner for each user,
Based on the communication history information stored in the communication history information storage unit, the permitted caller compression information automatic deletion unit that identifies and deletes the permitted caller compression information that is automatically deleted from the permitted caller compression information storage unit;
The message delivery system according to claim 1 , further comprising: The communication history information storage means stores the last message communication time as communication history information,
The permitted sender compressed information automatic deletion means corresponds to the user and the communication partner when the difference between the last message communication time point stored in the communication history information storage means and the current time point is larger than a predetermined value. The message delivery system according to claim 2 , wherein the permitted sender compressed information to be automatically deleted from the permitted sender compressed information storage means. The communication history information storage means stores the last message communication time as communication history information,
The permitted sender compressed information automatic deleting means registers the new permitted sender compressed information in the permitted sender compressed information storage means in association with the user and registers the permitted sender compressed information storage means for the user. When the number of stored permitted sender compressed information is a predetermined maximum value, of the permitted sender compressed information stored for the user, the last message communication time point stored in the communication history storage unit 3. The message delivery system according to claim 2 , wherein the permitted sender compression information relating to the oldest communication partner is deleted. It further comprises a permitted sender compressed information automatic registration means for compressing information relating to the communication partner and automatically registering it in the permitted sender compressed information storage means when a user transmits a message to a new communication partner. The message delivery system according to any one of claims 1 to 4 . And authorized caller uncompressed information storage means for storing without the user to compress the permission caller information is information about the caller you allow incoming,
Permitted sender information manual registration means for accepting a registration request for new authorized sender information from the user and registering it in the permitted sender uncompressed information storage means;
Further comprising an authorized sender compressed information automatic registration means for automatically registering new authorized sender compressed information without receiving a registration request from a user;
It said transfer permission determination means compares the arriving caller compression information to allow caller compression information that corresponds to the destination of the message generated by the calling party information compression means reads from the authorized caller compression information storage means and, if there is permission caller compression information matching, or compared to the caller information of the message described above arrived reads permission caller information that corresponds to the destination from the authorized caller uncompressed information storage means 2. The message delivery system according to claim 1, wherein if there is matching permitted sender information, the message is determined to be transferable. Not match any of the authorized caller compression information caller compressed information generated by the previous SL caller information compression means corresponding to the destination of the message the arrival, caller information of the arrived message is the message If the message does not match any of the rejected sender information corresponding to the destination, the message address including the transfer condition generated based on the sender information of the message is transmitted to the sender of the message and the message address is set as the destination. When a message transmitted with the message address as a destination is received, the message is transferred when the sender information of the message satisfies the transfer condition included in the message address. Transfer condition in which the sender information of the message is included in the message address. Filled if not, a message delivery system according to any one of claims 1 to 6, further comprising a disable and determining transfer possibility determination hand stage transfer of the message. A permitted caller uncompressed information storage means for storing the permitted caller information, which is information relating to the caller permitted to be received by the user, without compression;
One of the permitted sender information stored in the permitted sender uncompressed information storage means on condition that the number of permitted sender information stored in the permitted sender uncompressed information storage means has reached a predetermined number. A part of the permitted sender compressed information registering means for compressing the permitted sender information and generating the permitted sender compressed information and registering the generated permitted sender compressed information in the permitted sender compressed information storage means;
  The message delivery system according to claim 1, further comprising: A message transfer device that transfers a message based on caller information that is information about the caller of the message,
A sender information compression means for compressing the sender information of the arrived message and generating the sender compressed information;
User generated by the caller information compression means to obtain an authorization caller compressed information corresponding to the destination of the arrived messages among the authorized caller compressed information obtained by compressing the information about the caller you allow reception Information indicating the necessity of transfer rejection determination by rejected caller information, which is information related to a caller whose reception is rejected by the user as compared with the caller compressed information, and which matches the permitted caller compressed information. When the necessity information registered in association with the permitted sender compression information is not required to be determined, it is determined that the message can be transferred, the matching permitted sender compression information exists, and the permitted sender When the necessity information registered in association with the compressed information is necessary for determination, rejected sender information corresponding to the destination of the arrived message is obtained, compared with the sender information of the message, and matched. And No and determining transfer permission determination means for forwarding the message if there is a refusal caller information,
When registering new caller information as rejected caller information, the new caller information is compressed to generate compressed caller information, and the generated compressed caller information is the registration target of rejected caller information. And a necessity information setting means for setting necessity information corresponding to the matched permitted sender compression information to need to be determined when it matches any of the permitted sender compression information corresponding to the user. A message transfer device. The sender compressed information generated by the sender information compressing means does not match any of the permitted sender compressed information corresponding to the destination of the arrived message, and the sender information of the arrived message is the destination of the message If the message does not match any of the rejected sender information corresponding to the message address, the message address including the transfer condition generated based on the sender information of the message is transmitted to the sender of the message and the message address is set as the destination. When a request is made to send a message and a message sent with the message address as a destination is received, the message is transferred if the sender information of the message satisfies the transfer condition included in the message address. A transfer condition in which the message sender information is included in the message address. Filled If not, the message transfer device according to claim 9, further comprising a disable and determining transfer possibility determination means for forwarding the message. Registered permitted caller information on condition that the number of permitted caller information registered without compression of the permitted caller information, which is information related to the caller permitted to be received by the user, has reached a predetermined number. Partially permitted sender compression for generating a permitted sender compressed information by compressing so that a storage area required for storing the permitted sender information is reduced for a part of the registered, and registering the generated permitted sender compressed information 11. The message transfer device according to claim 9, further comprising information registration means. A message transfer method by a message transfer device that transfers a message based on caller information that is information about the caller of the message,
A caller information compression process for generating caller compression information by compressing the caller information of the arrived message;
User generated by the caller information compression means to obtain an authorization caller compressed information corresponding to the destination of the arrived messages among the authorized caller compressed information obtained by compressing the information about the caller you allow reception Information indicating the necessity of transfer rejection determination by rejected caller information, which is information related to a caller whose reception is rejected by the user as compared with the caller compressed information, and which matches the permitted caller compressed information. When the necessity information registered in association with the permitted sender compression information is not required to be determined, it is determined that the message can be transferred, the matching permitted sender compression information exists, and the permitted sender When the necessity information registered in association with the compressed information is necessary for determination, rejected sender information corresponding to the destination of the arrived message is obtained, compared with the sender information of the message, and matched. And No and determining transfer permission determination step the transfer of the message if there is a refusal caller information,
When registering new caller information as rejected caller information, the new caller information is compressed to generate compressed caller information, and the generated compressed caller information is the registration target of rejected caller information. And a necessity information setting step for setting necessity information corresponding to the matched permitted sender compression information when it matches any of the permitted sender compression information corresponding to the user. A characteristic message transfer method. The sender compressed information generated by the sender information compression step does not match any of the permitted sender compressed information corresponding to the destination of the arrived message, and the sender information of the arrived message is the destination of the message If the message does not match any of the rejected sender information corresponding to the message address, the message address including the transfer condition generated based on the sender information of the message is transmitted to the sender of the message and the message address is set as the destination. When a request is made to send a message and a message sent with the message address as a destination is received, the message is transferred if the sender information of the message satisfies the transfer condition included in the message address. A transfer condition in which the message sender information is included in the message address. Filled if not, a message transfer method according to claim 12, further comprising a disable and determining transfer possibility determination step the transfer of the message. Registered permitted caller information on condition that the number of permitted caller information registered without compression of the permitted caller information, which is information related to the caller permitted to be received by the user, has reached a predetermined number. Partially permitted sender compression for generating a permitted sender compressed information by compressing so that a storage area required for storing the permitted sender information is reduced for a part of the registered, and registering the generated permitted sender compressed information The message transfer method according to claim 12 or 13, further comprising an information registration step. A message transfer program for causing a computer to execute the message transfer method according to claim 12.

Images