JP2018005415A - Information processing device, information processing method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To reduce troubles of a manager by learning information to be used for transmission control in performing transmission confirmation.SOLUTION: A transmission history is managed in each combination of an organization name extracted from a text of an e-mail and a transmission destination domain of the e-mail, and in the case that a combination of an organization name extracted from an e-mail subjected to a transmission instruction and a transmission destination domain of the e-mail does not exist in managed combinations, the transmission of the e-mail subjected to the transmission instruction is held. In receiving an audit result as to whether to permit transmission about the held e-mail, selection as to whether to manage the combination of the organization name and the transmission destination domain is received.SELECTED DRAWING: Figure 1

Description

  The present invention relates to an information processing apparatus, an information processing method, and a program.

  An erroneous email transmission may cause confidential information to be leaked, loss of customer trust, and a great deal of damage to corporate activities.

  To prevent erroneous transmission, emails that meet a predetermined condition (transmission control rule) such as “attached file attached” or “having more than 10 recipients” are temporarily suspended. In addition, products that are controlled so that an e-mail is sent after others have confirmed are on the market.

  Patent Document 1 describes a technique for deciding a time for suspending transmission of an e-mail based on predetermined hold degree determination information and for suspending transmission during the time.

JP 2009-295076 A

  In the technique disclosed in Patent Document 1, it is necessary for an administrator or the like to set in advance a condition and a degree of hold for determining whether or not to hold transmission. Moreover, if the conditions are not set appropriately, the conditions become ineffective and a situation may occur in which erroneous transmission cannot be prevented.

  Therefore, an object of the present invention is to provide a mechanism that can reduce the labor of an administrator by learning information used for transmission control at the time of transmission confirmation.

  The information processing apparatus according to the present invention includes a management unit that manages a transmission history for each combination of an organization name extracted from a body of an email and a destination domain of the email, and an organization extracted from an email instructed to send When the combination of the name and the destination domain of the e-mail does not exist in the combination managed by the management unit, the transmission control unit for holding the transmission of the e-mail instructed to transmit and the transmission control unit Manages the combination of the organization name and destination domain when accepting the audit result by the audit result accepting means for accepting the audit result as to whether transmission is permitted or not for the suspended email. Selection accepting means for accepting selection as to whether or not to do.

  The information processing method of the present invention is an information processing method in an information processing device, wherein the management means of the information processing device includes an organization name extracted from the body of an email and a destination domain of the email The management step of managing the transmission history for each combination and the combination of the organization name extracted from the e-mail instructed by the transmission control means of the information processing apparatus and the destination domain of the e-mail And the transmission control process for holding the transmission of the e-mail instructed to transmit, and the audit result accepting means of the information processing apparatus for the e-mail whose transmission has been deferred by the transmission control process. An audit result accepting step for accepting an audit result as to whether or not transmission is permitted, and a selection accepting means of the information processing device accepting the audit result When accepting the audit results by degree, characterized in that it comprises a selection accepting step for accepting a selection of whether to manage the combination of the organization name and the destination domain, a.

  The program of the present invention is a program that can be executed in an information processing apparatus, and transmits the information processing apparatus for each combination of an organization name extracted from the body of an email and a destination domain of the email. If the combination of the management means for managing the history and the organization name extracted from the e-mail instructed to send and the destination domain of the e-mail does not exist in the combination managed by the management means, the transmission instructed Transmission control means for holding transmission of e-mail, audit result receiving means for receiving an audit result as to whether or not transmission is permitted for the e-mail whose transmission is held by the transmission control means, and auditing by the audit result receiving means Selection to accept selection of whether or not to manage the combination of organization name and destination domain when accepting results Program to function as a biasing means.

  ADVANTAGE OF THE INVENTION According to this invention, it becomes possible to reduce an administrator's effort by learning the information used for transmission control in the case of transmission confirmation.

The figure explaining the function with which the mail wrong transmission prevention system is equipped The figure which shows the hardware constitutions of the information processing apparatus which can apply a mail mistransmission prevention system Flow chart showing destination information extraction processing Flow chart showing transmission control rule determination processing Flow chart showing destination rule determination processing Flow chart showing text organization name classification process Flow chart showing destination domain classification processing Flow chart showing attached organization name classification process Flow chart showing hold determination processing The figure which shows an example of the email used by a present Example Figure showing an example of the pending mail list screen Figure showing an example of an email audit screen Figure showing an example of a screen for confirming transmission and adding a new domain Figure showing the extracted destination information Diagram showing transmission history and transmission control rules Diagram showing the extracted organization name / destination domain classification results The figure which shows the information regarding the invalidation of the transmission control rule The figure which shows the judgment division of the transmission control rule The figure which shows the information which is registered in hold mail DB The figure which shows the information regarding the invalidation of the updated transmission control rule Diagram showing the updated transmission history

  The present invention is a system capable of controlling, for each control rule, whether or not “the omission of confirmation work for the second and subsequent times” is possible for “the same sender / receiver combination”. In addition, the system can learn a combination of a destination and an address at the time of transmission confirmation, and can use the system without creating a detailed control rule in advance. Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

  FIG. 1 is a diagram showing a configuration of an erroneous mail transmission prevention system according to an embodiment of the present invention.

  The erroneous mail transmission prevention system 100 includes a mail reception unit 101, a destination information extraction unit 102, a transmission control rule determination unit 103, a hold determination unit 104, a hold mail operation / system setting unit 105, a mail transmission unit 106, A transmission control rule DB 110, a confirmation operation cache DB 120, and a pending mail DB 130 are provided.

  In the present embodiment, the erroneous mail transmission prevention system 100 is described as a server device (information processing device) that is communicably connected to a client terminal as shown in FIG. 1, but the client terminal is shown in FIG. It may have a function.

  The mail reception unit 101 receives mail transmitted by the system user and sends the mail to the destination information extraction unit 102. The user of the system can use the erroneous mail transmission prevention system 100 by setting the mail reception unit 101 as the mail transmission destination in the mail client used by the system user.

  The destination information extraction unit 102 extracts destination information (domain, organization name, name, etc.) from the email address, the body of the email, and the attached file using natural language processing, and sends it to the transmission control rule determination unit 103 together with the email. send. The destination information extraction processing in the destination information extraction unit 102 will be described in detail later using an example.

  The transmission control rule determination unit 103 refers to the transmission control rule DB 110, acquires all transmission control rules to be applied to the mail input from the destination information extraction unit 102, and sends the destination information and the mail together to the hold determination unit 104. send. The transmission control rule determination processing in the transmission control rule DB 110 and the transmission control rule determination unit 103 will be described in detail later using an example.

  The hold determination unit 104 refers to the confirmation operation cache DB 120 and determines whether or not to hold the transmission of the mail from the combination of the rule applied to the mail by the transmission control rule determination unit 103 and the mail destination address. If the mail is to be put on hold, the mail and the reason for hold (such as a rule applied to the mail) are registered in the hold mail DB 130, and if not on hold, the mail is sent to the mail sending unit 106. The hold determination process in the confirmation operation cache DB 120, the hold mail DB 130, and the hold determination unit 104 will be described in detail later using an example.

  The hold mail operation / system setting unit 105 provides a system user with a mail transmission process registered in the hold mail DB 130 and a maintenance process of the transmission control rule DB 110 and the confirmation operation cache DB 120 through a WEB browser or the like. The operation screen provided to the system user by the hold mail operation / system setting unit 105 will be described in detail later using an example.

  The e-mail transmission unit 106 sends e-mails that the hold determination unit 104 determines to be able to be sent and e-mails sent by the system user through the hold e-mail operation / system setting unit 105 to the e-mail destination address. Send.

  The transmission control rule DB 110 includes a transmission history table 111, a destination rule table 112, and a manual rule table 113.

  The transmission history table 111 holds the past number of transmissions for each combination of domain and organization name. Note that the number of times of transmission of combinations existing in the transmission history table 111 is automatically updated during mail transmission processing in the mail transmission unit 106, and addition of a new combination is performed during mail confirmation processing by the system user. . The destination rule table 112 and the manual rule table 113 hold a list of rules used in the transmission control rule determination process. Details of each item in the transmission control rule DB 110 will be described in detail later in the description of the transmission control determination process.

  The confirmation operation cache DB 120 includes a cache use setting table 121 and a confirmation operation cache table 122. The cache use setting table 121 holds a setting for whether or not omission of the hold operation using the mail check operation history is performed for each transmission control rule. The confirmation operation cache table 122 holds a list of suspension reasons (transmission control rules) recently confirmed by the user of the system for each combination of sender and receiver. Details of the confirmation operation cache DB 120 will be described in detail in the description of the subsequent hold determination process and the hold mail operation process.

  The hold mail DB 130 is a DB that temporarily stores mail that the hold determination unit 104 determines to be hold, and includes a hold mail table 131. In addition to the mail source (original data), the hold mail table 131 holds the destination information extracted by the destination information extraction unit 102 and the transmission control rule information applied by the transmission control rule determination unit 103. Details of the hold mail DB 130 will be described in detail in the description of the hold determination process and the hold mail operation process later.

  FIG. 2 is a block diagram showing an example of a hardware configuration of the information processing apparatus 100 to which the erroneous mail transmission prevention system 100 according to the embodiment of the present invention can be applied.

  As shown in FIG. 2, in the information processing apparatus, a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, a storage device 204, an input controller 205, An audio input controller 206, a video controller 207, a memory controller 208, and a communication I / F controller 209 are connected.

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

  The ROM 202 or the storage device 204 is a control program executed by the CPU 201 such as a basic input / output system (BIOS) or an operating system (OS), a computer-readable program for realizing this information processing method, and various necessary programs. Holds data (including data table).

  The RAM 203 functions as a main memory, work area, and the like for the CPU 201. The CPU 201 implements various operations by loading a program or the like necessary for executing the processing from the ROM 202 or the storage device 204 to the RAM 203 and executing the loaded program.

  The input controller 205 controls input from an input device such as a keyboard / touch panel 210. The input device is not limited to this, and may be a touch panel capable of detecting a position touched by a plurality of fingers, such as a mouse or a multi-touch screen.

  Various instructions can be performed when the user presses (touches with a finger or the like) in accordance with an icon, a cursor, or a button displayed on the touch panel.

  This input device is used to input a destination for a communication destination that can be used by various communication devices.

  The voice input controller 206 controls input from the microphone 211. Voice input from the microphone 211 can be recognized.

  The video controller 207 controls display on an external output device such as the display 212. The display includes a display of a notebook computer integrated with the main body. The external output device is not limited to a display, and may be a projector, for example. Further, for devices that can be received by the touch operation described above, it is also possible to receive input from the keyboard / touch panel 210.

  Note that the video controller 207 can control a video memory (VRAM) for display control, and a part of the RAM 203 can be used as a video memory area, or a dedicated video memory can be provided separately. Is possible.

  In the present invention, the first video memory area used for display when the user normally uses the information processing apparatus and the display overlaid on the display content of the first video memory area when a predetermined screen is displayed. A second video memory area used in The number of video memory areas is not limited to two, and a plurality of video memory areas can be provided as long as the resources of the information processing apparatus permit.

  The memory controller 208 controls access to the external memory 213. The external memory is connected via an adapter to an external storage device (hard disk), flexible disk (FD), or PCMCIA card slot that stores boot programs, various applications, font data, user files, editing files, and various data. A compact flash (registered trademark) memory or the like can be used.

  The communication I / F controller 209 is connected to and communicates with an external device via the network 214, and executes communication control processing in the network. For example, communication using TCP / IP, telephone lines such as ISDN, and communication using 3G lines of mobile phones are possible.

  The storage device 204 is a medium for permanently storing information, and the form is not limited to a storage device such as a hard disk. For example, a medium such as SSD (Solid State Drive) may be used.

  It can also be used as a temporary memory area during various processes performed by the communication terminal in the present embodiment.

  Next, the erroneous mail transmission prevention process in this embodiment will be described with reference to the flowcharts shown in FIGS.

  3 to 9 are processes in which the CPU 201 of the information processing apparatus 100 reads and executes a predetermined control program.

  First, destination information extraction processing in the destination information extraction unit 102 will be described with reference to FIGS. 3, 10, and 14. FIG. 3 is a flowchart of the destination information extraction process. Hereinafter, an example in which various types of information shown in FIG. 4 are extracted from the mail (mail 1) shown in FIG. 10 according to the processing of FIG.

  First, in step S101, the sender's email address is extracted from the email. The sender's mail address is extracted from the From value in the mail header. Note that, in an environment where the envelope information can be referred to, the sender address described in the envelope may be acquired. The sender address in the mail 1 is the From value “Kuramitsu@EXAMPLE.JP”.

  In step S102, only the domain part (character string after “@”) is extracted from the sender address acquired in step S101. In this system, the sender's domain is called the internal domain, and is handled separately from domains other than the internal domain (external domain). The internal domain in the mail 1 is “EXAMPLE.JP”.

  Note that even if the domain is different from the sender's domain, the group company or the like can be treated as an internal domain. Therefore, a domain associated in advance may be determined as an internal domain.

  In step S103, a list of destination mail addresses is acquired. The destination address is extracted from the values of To and Cc in the mail header. Similarly to the sender address, in an environment in which envelope information can be referred to, it may be acquired from the envelope information. There are four destination addresses in the mail 1, namely “nakamura@EXAMPLE1.JP”, “ito@EXAMPLE2.JP”, “otani@EXAMPLE1.SUB.JP”, and “kuramitsu@EXAMPLE.JP”.

  In step S104, only the external domain is extracted from each destination address acquired in step S103. Here, the same domain is removed as a single element without duplication. The mail 1 has three destination domains, “EXAMPLE1.JP”, “EXAMPLE2.JP”, and “EXAMPLE1.SUB.JP”.

  In step S105, a list of organization names (text organization names) included in the text address is extracted. In order to simplify the description, in this embodiment, “text address” is assumed to be a line ending with a title (such as “sama”, “san”, “dono”), and “text organization name” is set to “text”. Is extracted as the first element divided by white space. When the number of elements divided by blank characters is 1 or less, it is handled as not including the organization name. The text organization name in the mail 1 is one of “EX1”.

  In step S106, a list of organization names (attached organization names) is extracted from the attached file. In order to simplify the description, in the present embodiment, “attached organization name” is extracted as a character string that appears immediately before “Gochu” in the text included in the attached file. If the corresponding character string does not exist, it is treated as not including the organization name. The attached organization name in the mail 1 is one of “EXAMPLE1”.

  The destination information extraction process in the destination information extraction unit 102 has been described above using an example. In addition, for simplicity of explanation, a simple method has been described as an example of the method for extracting the organization name (text organization name, attached organization name). By combining methods such as extracting the character string that looks like an organization name using natural language processing technology such as morphological analysis, the extraction accuracy is improved and more flexible It is possible to cope with the format.

  The destination information extracted in the flowchart of FIG. 3 is shown in FIG.

  Next, transmission control rule determination processing in the transmission control rule determination unit 103 will be described with reference to FIGS. 4 to 8, 15, and 16. 4 to 8 are flowcharts of the transmission control rule determination process. FIG. 15 shows an example of the transmission control rule DB 110, which includes a transmission history table 111, a destination rule table 112, and a manual rule table 113.

  The transmission history table 111 holds the past number of transmissions for each combination of domain and organization name. Note that the number of transmissions of combinations existing in the transmission history table 111 is automatically updated at the time of mail transmission processing in the mail transmission unit 106, and addition of a new combination will be described later in the mail confirmation processing by the system user. Done when.

  The destination rule table 112 and the manual rule table 113 hold a list of rules used in the transmission control rule determination process, and are used to determine a “rule ID” that uniquely identifies the rule and whether the rule can be applied. The “judgment conditions” and “explanations” that indicate the rules in easy-to-understand language. Hereinafter, according to the processing of FIG. 4 to FIG. 8, from the mail 1, “text organization name classification result”, “destination domain classification result”, “attached organization name classification result”, “address rule ID”, “manual” shown in FIG. An example of extracting “Rule ID” is shown.

  First, in step S201, a destination rule determination process is executed. Details of the destination rule determination processing will be described with reference to the flowchart of FIG.

  In step S301 in the flowchart of FIG. 5, a plausible combination of domains (hereinafter, maximum likelihood domain) is extracted from the transmission history table 111 for the text organization name and the attached organization name in the processing target e-mail.

  In order to simplify the description, in the present embodiment, the “maximum likelihood domain” for a certain organization name is defined as the domain of the record having the largest number of transmissions among the records including the organization name in the transmission history table 111. For example, the maximum likelihood domain in the text organization name “EX1” in the mail 1 and the attached organization name “EXAMPLE1” is “EXAMPLE1.JP”.

  In step S302, a plausible combination of organization names (hereinafter referred to as maximum likelihood organization names) is extracted from the transmission history table 111 for the destination domain of the email to be processed.

  In order to simplify the description, in the present embodiment, the “maximum likelihood organization name” for a certain domain is defined as the organization name of the record having the largest number of transmissions among the records including the domain in the transmission history table 111. For example, the maximum likelihood organization names of the destination domains “EXAMPLE1.JP” and “EXAMPLE2.JP” in mail 1 are “EXAMPLE1” and “EX2”, respectively, and there is a maximum likelihood organization name for “EXAMPLE1.SUB.JP”. do not do.

  Next, in step S303, “determination classification” and “organization code” are obtained for the combination of the text organization name and the destination domain based on the text organization name in the processing target e-mail.

  Details of the processing in step 303 will be described with reference to the flowchart of FIG.

  The “judgment category” is “match”, which means that the combination of the destination domain and the text organization name in the email to be processed is a correct combination, “inconsistency” which means that the combination is not correct, These are three categories of “new” indicating that they are registered destinations (no transmission history exists), and are classified based on the text organization name, destination domain, and past transmission history.

  The “organization code” is a numerical value for identifying the correspondence between the text organization name and the destination domain, and is used when determining the display color of the text organization name and the destination domain on the hold reason confirmation screen described later.

  In step S402, it is determined whether or not the maximum likelihood domain for the text organization name has been acquired in the process of step S301.

  If acquired, the process proceeds to step S403. If not acquired, the process proceeds to step S404, and the determination category is set to “new”. That is, it means that an e-mail in which the text organization name is described has never been transmitted in the past.

  Since the maximum likelihood domain “EXAMPLE1.JP” exists in the text organization name “EX1” of the mail 1, the process proceeds to step S403.

  In step S403, it is determined whether or not the destination domain in the processing target e-mail is the maximum likelihood domain corresponding to the text organization name acquired in step S301.

  If the destination domain in the email to be processed is the maximum likelihood domain for the text organization name, the process proceeds to step S405.

  If the destination domain is not the maximum likelihood domain, the process advances to step S406 to set the determination category to “inconsistent”. That is, it means that the mail is sent to a destination domain other than the maximum likelihood domain.

  Since the destination domain of the mail 1 is “EXAMPLE1.JP” which is the maximum likelihood domain of the text organization name “EX1”, the process proceeds to step S405.

  In step S405, regarding the combination of the text organization name and the destination domain in the processing target e-mail, the determination classification is set to “match”, and the process proceeds to step S407. In this embodiment, when it is classified as “match”, it means that at least one email address of the maximum likelihood domain corresponding to the text organization name is set as a transmission destination in the processing target email. ing.

  The processing from step S407 to step S411 is processing for determining an organization code in a combination of a text organization name and a destination domain. If the determination category is “new” or “inconsistent”, a new organization code is uniquely assigned in step S411. On the other hand, if the determination category is “match” and the maximum likelihood domain is the same, the same organization code is assigned in steps S407 to S410 (the process of making the organization codes of different organization names have the same value is performed by assigning a plurality of organization names). Equivalent to treating it as an alias for a single organization).

  In step S407, it is determined whether or not the organization code of the maximum likelihood domain has been determined. If it has been determined, the organization code of the maximum likelihood domain is assigned in step S408, and if not, a new organization code is assigned in step S409. Allocate and proceed to step S410. In mail 1, since the organization code of the maximum likelihood domain “EXAMPLE1.JP” of the organization name “EX1” has not yet been determined, a new organization code “1” is assigned in step S409.

  In step S410, the maximum likelihood domain determination category and the organization code are updated with the values obtained in the previous step. In the above-described example, the determination category and organization code of the maximum likelihood domain “EXAMPLE1.JP” are updated with “match” and “1”, respectively.

  Similarly, a determination classification and an organization code are obtained for each text organization name, the text organization name classification process is terminated, and the process proceeds to step S304.

  In step S304, a destination domain classification process is performed. The destination domain classification process is a process for determining “determination category” and “organization code” for the combination of the text organization name and the destination domain, based on each destination domain of the email to be processed. It demonstrates using the flowchart shown in FIG.

  First, in step S502, it is determined whether or not the organization code based on the text organization name and the determination classification have been determined for the destination domain to be processed by the text organization name classification process of FIG. If determined, the process proceeds to step S503, and if not, the process proceeds to step S504. In the mail 1, the determination classification and the organization code in the destination domain “EXAMPLE1.JP” have already been determined as “match” and “1” by the text organization name classification process, and thus the process proceeds to step S503. (The maximum likelihood organization name in “EXAMPLE1.JP” is “EXAMPLE1” and does not exist in the text organization name. In this embodiment, the maximum likelihood domain name for the text organization name or the maximum likelihood organization name for the destination domain. (A combination that has any of the above is treated as "consistent".)

  In step S503, if the maximum likelihood organization name in the destination domain exists in the body organization name and the determination category is other than “match”, the determination category and organization code of the organization name are changed to the destination in step S505. Update each with the judgment category based on domain and the value of organization code. In the above example, since the maximum likelihood organization name “EXAMPLE1” in the destination domain “EXAMPLE1.JP” does not exist in the text organization name, the processing for the next destination domain “EXAMPLE2.JP” is performed without executing step S505. The process proceeds from step S502.

  In step S504, it is determined whether the maximum likelihood organization name exists. If it exists, the process proceeds to step S506. If not, the determination category is set to “new” in step S507, and a new organization code is determined in step S512. Assign. In the above example, since the maximum likelihood organization name “EX2” exists in the destination domain “EXAMPLE2.JP”, the process proceeds to step S506.

  In step S506, it is determined whether the text organization name in the processing target e-mail is the maximum likelihood organization name corresponding to the destination domain (whether the maximum likelihood organization name exists in the text organization name).

  When the text organization name is the maximum likelihood organization name corresponding to the destination domain (the maximum likelihood organization name exists in the text organization name), the process proceeds to step S508, and the determination classification is set to “match”. Then, the process proceeds to step S510.

  If the text organization name is not the maximum likelihood organization name corresponding to the destination domain (the maximum likelihood organization name does not exist in the text organization name), the process proceeds to step S509 and the determination classification is set to “inconsistent”. Then, the process proceeds to step S512.

  In the above example, since the maximum likelihood organization name “EX2” does not exist in the body organization name, the determination classification for the destination domain “EXAMPLE2.JP” is “inconsistent”, and the organization code is “2” of the new value. Become.

  In step S510, the organization code of the maximum likelihood organization name is assigned as the organization code of the destination domain, and in step S511, the determination category of the maximum likelihood organization name is updated with “match”. (The organization code of the most likely organization name is not updated)

Similarly, the determination classification and the organization code are obtained for each destination domain, the destination domain classification process is terminated, and the process proceeds to step S305. In the above-described example, the remaining destination domain “EXAMPLE1.SUB.JP” has no maximum likelihood organization name, so the determination category is “new”, and the organization code has a new value “3”.

  In step S305, an attached organization name classification process is performed. The attached organization name classification process is a process for obtaining a “determination category” and an “organization code” for each attached organization name of an electronic mail to be processed, and will be described with reference to the flowchart of FIG. In the attached organization name classification process, the text organization name, the destination domain determination category, and the organization code are not updated.

  First, in step S602, it is determined whether or not the attached organization name is included in the text organization name. If it is included, the determination classification is set to “match” in step S603, and then the organization code of the text organization name is assigned in step S605. . If not included, the process proceeds to step S604. Since the attached organization name “EXAMPLE1” in the mail 1 does not exist in the text organization name, the process proceeds to step S604.

  In step S604, it is determined whether or not the maximum likelihood domain exists in the attached organization name. If it exists, the process proceeds to step S606. If it does not exist, the determination category is set to “new” in step S607, and in step S611. Assign a new organization code. In the above example, since the maximum likelihood domain “EXAMPLE1.JP” exists in the attached organization name “EXAMPLE1”, the process proceeds to step S606.

  In step S606, it is determined whether or not the maximum likelihood domain of the attached tissue name is included in the destination domain. If it exists, the determination classification is “matched” in step S608, and the organization code of the maximum likelihood domain is assigned in step S610. . If it does not exist, the determination classification is set to “inconsistent” in step S609, and a new organization code is assigned in step S611. In the above example, since the maximum likelihood domain “EXAMPLE1.JP” is included in the destination domain, the determination classification of the attached organization name “EXAMPLE1” is set to “match”, and the organization code is the organization code of the maximum likelihood domain “EXAMPLE1.JP”. Set to “1”.

  Similarly, a determination classification and an organization code are obtained for each attached organization name, the attached organization name classification process is terminated, and the process proceeds to step S306.

  In step S306, based on the classification results acquired in steps S303 to S305, a list of rule IDs that match the determination conditions described in the destination rule table 112 is acquired, and the destination rule determination process ends. In the above-described example, since the destination domain “EXAMPLE2.JP” whose determination classification is “inconsistent” and the destination domain “EXAMPLE1.SUB.JP” whose determination classification is “new” exist, the destination rule ID is “ INCORRECT "and" NEWDOMAIN "are acquired.

  In step S202, the manual rule table 113 is referred to, and a list of rule IDs satisfying the determination condition is acquired. In the mail 1, since the keyword “estimate” is included in the text information of the attached file “estimate.pdf”, “rule 4” is acquired as the manual rule ID.

  The transmission control rule determination process in the transmission control rule determination unit 103 has been described above using an example. In order to simplify the explanation, the maximum likelihood domain and the maximum likelihood organization name were treated as having the largest number of transmissions in the same combination, but transmissions that have been transmitted in the same combination as a measure of likelihood. A result obtained by combining a plurality of criteria such as the number of persons, the department name included in the address, and the probability that the person name co-occurs with the organization name or domain may be used. In addition, although the method for determining whether the determination category is “matched” based on whether the maximum likelihood domain or the maximum likelihood organization name exists has been described, the transmission history table 111 exceeds a certain number of transmissions. Other judgment descriptions may be combined, such as allowing combinations.

Next, the hold determination process in the hold determination unit 104 will be described with reference to FIGS. 9 and 17 to 19.
FIG. 9 is a flowchart of the hold determination process.

  FIG. 17 shows an example of the confirmation operation cache DB 120, which includes a cache use setting table 121 and a confirmation operation cache table 122.

  FIG. 18 shows an example of the hold mail DB 130, which temporarily stores the mail that the hold determination unit 104 determines to hold, various classification results, and the applied rule ID.

  The cache use setting table 121 holds a setting for whether or not omission of the hold operation using the mail check operation history is performed for each transmission control rule. The confirmation operation cache table 122 holds a list of rule IDs and transmission dates and times confirmed by the user of the system through the hold mail operation for each combination of the sender and receiver and the text organization name.

  In the following, the process of obtaining the “applicable rule ID classification result” shown in FIG. 18 for the mail 1 and determining whether or not to defer transmission of the mail according to the process of FIG. 9 will be described.

  First, in step S701, a sender / receiver address is acquired. In the present embodiment, the “sender address” is defined as a character string in which the sender address and the receiver address are arranged in the dictionary order, are duplicated, and are connected with a blank character. The sender / receiver address in the mail 1 is “ito@EXAMPLE2.JP kuramitsu@EXAMPLE.JP nakamura@EXAMPLE1.JP otani@EXAMPLE1.SUB.JP”.

  In step S <b> 702, it is confirmed whether the combination of the sender / receiver address and the text organization name exists in the confirmation operation cache table 122. If there is a combination, the process proceeds to step S703, and if not, in step S708, the determination classification of all rule IDs is set to “necessary confirmation”, and the process proceeds to step S709. Note that the text organization name used in the confirmation is arranged in the order of the dictionary as in the case of the sender / receiver address, and a character string concatenated with a blank character is used after eliminating duplication. In the above example, the text organization name used for confirmation is “EX1”, and since there is a combination with the sender / receiver address in the confirmation operation cache table 122, the process proceeds to step S703.

  Steps S703 to S707 are processes for determining whether or not each rule ID applied by the transmission control rule determination process is a rule to be confirmed (whether or not it has been confirmed recently).

  First, in step S704, the cache usage setting table 121 is referenced to determine whether or not the cache can be used for the rule ID. If it can be used, the process proceeds to step S705, and if it cannot be used, the process proceeds to step S707. Note that the use permission / inhibition determination process is performed from the cache use setting table 121 having the smallest application order value. If there is no corresponding setting, the use is prohibited. In the above example, since the destination rule ID “INCORRECT” can be used in conformity with the conditions of the application order 1, the process proceeds to step S705. (In the destination rule ID “NEWDOMAIN” and the manual rule ID “rule 4”, the process proceeds to step S705 in order to meet the conditions of the application order 5 and the application order 7.)

  In step S705, whether or not the rule ID exists in the confirmed item in the record corresponding to the combination of the sender / receiver address and the text organization name in the confirmation operation cache table 122, and whether or not the confirmation date / time is the cache period. judge. If the condition is satisfied, the rule ID determination category is set to “confirmed” in step S706, and if not, the determination category is set to “confirmation required” in step S707. In the above example, since the destination rule IDs “INCORRECT” and “NEWDOMAIN” satisfy the conditions, the determination category is “Confirmed”, and the manual rule ID “Rule 4” does not exist in the confirmed item. Is “confirmed”.

  Next, in step S709, if there is at least one rule ID whose determination category is “confirmation required”, mail hold processing is performed in step S710, and if there is no rule ID, mail is sent to the mail transmission unit in step S711. In the above-described example, since the determination classification of the manual rule ID “rule 4” is “confirmation required”, the process proceeds to step S710.

  The mail hold process in step S710 is a process of temporarily holding the mail transmission. In the hold mail table 131, the mail ID, the mail source, the body organization name classification result, the destination domain classification result, and the attached organization name classification are stored. As a result, the application rule ID is stored. FIG. 19 shows an example of the hold mail DB 130 and shows a state after the mail 1 is put on hold.

  The hold determination process in the hold determination unit 104 has been described above. The above example says, “Since I ’ve recently sent the same sender / text organization name combination, I ’ve never sent an email with a quote (matching rule 4) to the same combination, This represents an operation that “hold operation was performed”.

  As described above, in this embodiment, a cache period (corresponding to a period during which the transmission control rule is invalidated) is set for each transmission control rule. Then, when the auditor accepts a transmission permission instruction (audit result) for an email whose transmission control rule is applied and the transmission is suspended, the cache period is from the time when the transmission permission instruction is made. Does not hold the transmission due to the transmission control rule on the assumption that the transmission control rule has been confirmed (transmission control rule is invalidated).

  With such control, it is possible to save the trouble of auditing an electronic mail whose transmission has been suspended for the same reason, and to reduce the burden on the auditor. Also, by reducing the number of emails to be audited, it is possible to appropriately audit emails that really need to be audited.

  In this embodiment, the e-mail that matches the transmission control rule (to which the transmission control rule is applied) has been described as being suspended. However, the transmission control rule is defined by “condition” and “operation”. Then, “transmission”, “hold”, “deletion”, etc. may be defined as operations. For example, “e-mail with attached file (= condition) is put on hold (= operation)” or “email (= condition) included in CC by sender's boss is sent (= operation)”. . In this case, it is possible to achieve the same effect as in the present embodiment by controlling the operation to be changed from “pending” to “transmission” during the cache period.

  Next, the screen provided by the hold mail operation / system setting unit 105 to the system user and the processing in the mail transmission unit 106 will be described with reference to FIGS. 11 to 13, 20, and 21.

  FIG. 11 shows an example of the pending mail list screen in the present embodiment, and the system user can refer to and operate the screen via a WEB browser. On the hold mail list screen, for each mail existing in the hold mail table 131, a list of transmission date / time, subject, text organization name, destination domain, and hold reason is presented. Here, a description for each application rule ID (obtained from the destination rule table 112 and the manual rule table 113) is displayed in the hold reason item. In particular, a rule ID whose determination category is “confirmation required” is highlighted and displayed in bold or red as an item requiring confirmation.

  The user of the system can refer to the hold reason confirmation screen for the mail by pressing the item of transmission date and time on the hold mail list screen.

  FIG. 12 shows an example of the hold reason confirmation screen in the present embodiment. The hold reason confirmation screen includes a hold reason, mail contents, a delete button, and a send button.

  In the hold reason confirmation screen, a check box for each applicable rule ID is provided for the hold reason. If the check category is “Confirmed”, the check box is displayed in a checked state. Present in state. In addition, in the rule ID related to the destination rule, in addition to the explanation for each rule, the organization name to be confirmed and the domain are presented together. The organization name and domain to be presented are displayed in different colors for each organization code. The organization name and domain displayed here have a function of displaying the maximum likelihood domain or the maximum likelihood organization name in a pop-up by a click operation.

  Information such as the sender / receiver's address, subject, attached file name, text, etc. is presented in the mail content on the hold reason confirmation screen. In displaying each item, the text organization name, the destination domain, and the attached organization name are highlighted and displayed in a color for each organization code. The organization name and domain displayed here also have a function of popping up the maximum likelihood domain or the maximum likelihood organization name by a click operation. The attached file having the attached organization name is provided with a function of displaying all attached organization names existing in the attached file by pop-up by a click operation.

  The delete button on the hold reason confirmation screen is a button for deleting the temporarily held mail without transmitting it. When the user of the system presses the delete button, the hold mail operation / system setting unit 105 deletes the corresponding record from the hold mail DB and presents the hold mail list screen to the user.

  The send button on the hold reason confirmation screen is a button for shifting to a transmission confirmation screen, which will be described later, and can be pressed when all the check boxes for the hold reason are checked. When the system user presses the send button, the hold mail operation / system setting unit 105 presents a transmission confirmation screen to the system user.

  FIG. 13 shows an example of a transmission confirmation screen in the present embodiment. The transmission confirmation screen includes a new learning target list, a cancel button, and a send button.

  The new learning target list on the transmission confirmation screen is a combination that does not exist in the transmission history table 111 among all combinations of the text organization name or attached organization name and the destination domain, and a new transmission history table is created for each combination. A check box indicating whether or not to register is provided.

  The cancel button on the transmission confirmation screen is a button for canceling mail transmission. When the user of the system presses the cancel button, the hold mail operation / system setting unit 105 presents a hold reason confirmation screen for the mail to the system user.

  The send button on the transmission confirmation screen is a button for sending the mail. When the system user presses the send button, the pending mail operation / system setting unit 105 adds the checked combination in the new learning target list to the transmission history table 111 (the value of the number of transmissions is 0), and the confirmation operation cache table At 122, the confirmation date is updated for each application rule ID. Then, after sending the mail to the mail transmitting unit 106, the corresponding record is deleted from the hold mail DB, and the hold mail list screen is presented to the user.

  FIG. 20 shows the confirmation operation cache table 122 after the mail 1 sending operation. Compared with the state before the sending operation (FIG. 17), the confirmation date and time for the rule IDs “INCORRECT” and “NEWDOMAIN” are updated, and a record related to the rule ID “rule 4” is added.

  FIG. 21 shows the transmission history table 111 after the mail 1 is sent in a state where the organization name “EX1” and the domain “EXAMPLE1.SUB.JP” are checked on the transmission confirmation screen of FIG. Compared with the state before transmission (FIG. 15), the number of transmissions in the combination of the domain “EXAMPLE1.JP” and the organization name “EX1” is increased by one, and the domain “EXAMPLE1.SUB.JP” and the organization name “EXAMPLE1.JP” are increased. A combination of “EX1” is added.

  The screen provided by the pending mail operation / system setting unit 105 and the processing in the mail transmission unit 106 have been described above. With regard to the same sender / receiver address and text organization name combination, once confirmed hold control rules are saved in the check operation cache table, and hold operations are omitted from the second time onward, preventing the confirmation operation from becoming a fake. it can. On the other hand, a rule such as “Destination of attachment file and destination domain” (destination rule ID: A_INCORRECT) uses a cache for a rule that does not want to omit the second and subsequent hold operations even if the contents are confirmed once. By setting “use prohibited” in the setting table 121, it is possible to define not to omit the hold operation.

  The hold email list screen is displayed with the reason for hold as “confirmed” highlighted, and on the hold reason check screen, the organization name and domain are displayed in different colors for each same organization. The points to be confirmed become clear.

  Since the transmission history table 111 is a mechanism that is updated when the reason for holding is confirmed and when an email is sent out, the cost required for rule maintenance can be significantly reduced compared to the case where detailed manual rules are set. Is possible. In the above description, the embodiment for learning the combination of the domain and the organization name has been described. However, by learning the combination of the mail address and the entire address, the same idea can be applied to mail for individuals. Is possible.

  Moreover, the program in this invention is a program which makes a computer perform the process of FIGS. The program in the present invention may be a program for each process in FIGS.

  As described above, a recording medium that records a program that implements the functions of the above-described embodiments is supplied to a system or apparatus, and a computer (or CPU or MPU) of the system or apparatus stores the program stored in the recording medium. It goes without saying that the object of the present invention can also be achieved by reading and executing.

  In this case, the program itself read from the recording medium realizes the novel function of the present invention, and the recording medium recording the program constitutes the present invention.

  As a recording medium for supplying the program, for example, a flexible disk, hard disk, optical disk, magneto-optical disk, CD-ROM, CD-R, DVD-ROM, magnetic tape, nonvolatile memory card, ROM, EEPROM, silicon A disk or the like can be used.

  Further, by executing the program read by the computer, not only the functions of the above-described embodiments are realized, but also an OS (operating system) operating on the computer based on an instruction of the program is actually It goes without saying that a case where the function of the above-described embodiment is realized by performing part or all of the processing and the processing is included.

  Furthermore, after the program read from the recording medium is written to the memory provided in the function expansion board inserted into the computer or the function expansion unit connected to the computer, the function expansion board is based on the instructions of the program code. It goes without saying that the case where the CPU or the like provided in the function expansion unit performs part or all of the actual processing and the functions of the above-described embodiments are realized by the processing.

  The present invention may be applied to a system constituted by a plurality of devices or an apparatus constituted by a single device. Needless to say, the present invention can be applied to a case where the present invention is achieved by supplying a program to a system or apparatus. In this case, by reading a recording medium storing a program for achieving the present invention into the system or apparatus, the system or apparatus can enjoy the effects of the present invention.

  Furthermore, by downloading and reading a program for achieving the present invention from a server, database, etc. on a network using a communication program, the system or apparatus can enjoy the effects of the present invention. In addition, all the structures which combined each embodiment mentioned above and its modification are also included in this invention.

100 E-mail erroneous transmission prevention system (information processing equipment)

Claims (5)

Management means for managing the transmission history for each combination of the organization name extracted from the body of the email and the destination domain of the email;
If the combination of the organization name extracted from the instructed e-mail and the destination domain of the e-mail does not exist in the combination managed by the management means, the transmission for holding the transmission of the instructed e-mail Control means;
Audit result acceptance means for accepting an audit result as to whether or not transmission is permitted for an electronic mail whose transmission is suspended by the transmission control means;
A selection receiving unit that receives a selection as to whether or not to manage a combination of the organization name and the destination domain when receiving the audit result by the audit result receiving unit;
An information processing apparatus comprising: The management means includes
The combination of the organization name and the transmission destination domain that have received the selection to be managed by the selection receiving unit is managed when the audit result receiving unit receives an instruction to permit transmission. Item 4. The information processing apparatus according to Item 1. Display control means for displaying a screen for auditing an email whose transmission is suspended by the transmission control means;
The screen displayed by the display control means includes a destination domain that is managed in association with the organization name extracted from the e-mail and has the largest number of transmission histories, and transmission in the e-mail. The information processing apparatus according to claim 1 or 2, wherein a destination domain having the largest number of transmission histories and an organization name managed in association with the destination domain is displayed. An information processing method in an information processing apparatus,
A management step in which the management means of the information processing apparatus manages the transmission history for each combination of the organization name extracted from the body of the email and the destination domain of the email;
When the combination of the organization name extracted from the e-mail instructed to be transmitted and the destination domain of the e-mail does not exist in the combination managed in the management step, the transmission control unit of the information processing apparatus A transmission control step for deferring transmission of the instructed email;
The audit result receiving unit of the information processing apparatus receives an audit result as to whether or not to permit transmission of the email suspended from transmission by the transmission control step; and
A selection receiving step for receiving selection of whether or not to manage a combination of the organization name and the transmission destination domain when the selection receiving unit of the information processing apparatus receives an audit result by the audit result receiving step;
An information processing method comprising: A program executable in the information processing apparatus,
The information processing apparatus;
Management means for managing the transmission history for each combination of the organization name extracted from the body of the email and the destination domain of the email;
If the combination of the organization name extracted from the instructed e-mail and the destination domain of the e-mail does not exist in the combination managed by the management means, the transmission for holding the transmission of the instructed e-mail Control means;
Audit result acceptance means for accepting an audit result as to whether or not transmission is permitted for an electronic mail whose transmission is suspended by the transmission control means;
A program for functioning as a selection receiving unit for receiving selection of whether or not to manage a combination of an organization name and a transmission destination domain when receiving an audit result by the audit result receiving unit.

Images