JP5410811B2 - E-mail delivery system, e-mail delivery method, and e-mail delivery program - Google Patents

Description

The present invention relates to the preferred e-mail delivery system, e-mail delivery how you and e-mail delivery program to apply when sending and receiving e-mail between enterprises.

  In recent years, with the spread of the Internet, e-mail has become indispensable as a business communication tool between companies.

  However, when an individual belonging to one company sends an e-mail to another company, due to human factors (inadvertently), the company inadvertently sent the e-mail destination, and the company listed in the email text or attached file Important information such as know-how and personal information may be leaked to third parties. In this case, there is a risk that it may become a serious incident related to the viability of the company.

  Therefore, in order to avoid such inconvenience due to the erroneous transmission of the email, the sender (sender) confirms the correctness of the domain name in the recipient's email address immediately before sending the email, thereby sending the email incorrectly. Has been proposed (hereinafter referred to as known method 1) (see, for example, Patent Document 1).

JP 2008-117027 (paragraphs [0009] and [0018], FIG. 3)

  However, in the publicly known method 1, the domain name of the email address is corrected for all emails including those with the correct domain name of the recipient's email address (that is, there is no risk of erroneous transmission). There is a problem that the burden on the sender increases, particularly when the number of outgoing mails is large, because the sender is troublesome to check by himself / herself.

In view of such circumstances, the present invention provides an e-mail delivery system and e-mail delivery method that can prevent information leakage due to erroneous transmission of e-mail while reducing the burden on the e-mail sender as much as possible. an object of the present invention is to provide a law you and e-mail delivery program.

  In order to achieve this purpose, first, the domain name of the recipient's email address is checked against the recipient in the email body to divide the email to be sent into those that are not likely to be sent incorrectly. In the above, the former (e-mail that is not likely to be sent incorrectly) is sent immediately without confirmation of the sender, while the latter (e-mail that is likely to be sent incorrectly) is confirmed by the sender. We focused on preventing erroneous transmission.

That is, in the electronic mail delivery system according to the present invention, a plurality of electronic mail delivery servers (2) and a database integration server (7) are connected via a communication network (11, 12), and the electronic mail is an electronic mail transmission server. (3) through the communication network from an electronic mail delivery system that is delivered to the e-mail receiving server (9) (1), and the domain name of the specified e-mail address to send the e-mail It is determined whether or not the organization name described as the destination in the mail text corresponds correctly, and the domain name of the mail address specified as the destination of the e-mail and the address described in the mail text When it is determined that the organization name corresponds correctly, the e-mail is delivered to the e-mail receiving server. In both cases, when it is determined that the domain name of the email address specified as the destination of the email does not correctly correspond to the organization name described as the destination in the email text, the email The URL of the site describing the fact that the delivery to the mail receiving server is canceled and the electronic mail is suspended, and the suspended electronic mail is notified to the sender that the electronic mail is suspended. Is sent to the sender , and the corresponding relationships shown in the in-house master database (DB5) of each of the e-mail delivery servers are statistically processed, and the grand master database ( DB1) and the organization information is periodically acquired from the grand master database. The e-mail delivery server and the database integration server are reflected in the in-organization master database so that the in-organization master database is always up-to-date and the grand master database is always up-to-date. It is characterized by a collaborative e-mail delivery system.

The electronic mail delivery method according to the present invention includes an electronic mail delivery system (1) in which a plurality of electronic mail delivery servers (2) and a database integration server (7) are connected via a communication network (11, 12). in the electronic mail to a mail delivery method for delivering electronic mail receiving server (9) through the communication network from the email server (3), designated as the destination of the e-mail mail A destination check step for determining whether or not the domain name of the address and the organization name described as the destination in the mail body correctly correspond; the domain name of the mail address designated as the destination of the e-mail; When it is determined that the organization name described as the address in the mail text corresponds correctly, the e-mail It is determined that the domain name of the mail address specified as the destination of the e-mail does not correctly correspond to the organization name described as the destination in the mail text. In this case, a mail selection and delivery process for canceling delivery of the e-mail to the e-mail receiving server and holding the e-mail, and for the held e-mail to the sender that the e-mail is held. In order to notify, a hold notification step of transmitting an e-mail in which the URL of the site describing that fact is described to the sender, and the correspondence relationship shown in the in-organization master database (DB5) of each e-mail delivery server Are statistically processed and reflected in the grand master database (DB1) of the database integration server. A data reflection process for periodically obtaining organization information from the master database and reflecting it in the organization master database, keeping the organization master database always up-to-date and keeping the grand master database up-to-date In order to maintain, the electronic mail delivery method includes a collaboration rate cooperation step in which each of the email delivery servers and the database integration server cooperate in a collaborative manner.

Furthermore, the electronic mail delivery program (1) according to the present invention includes a plurality of electronic mail delivery servers (2) and a database integration server (7) connected via a communication network (11, 12). in the electronic mail to a mail transmission server (3) from said communication network a via by email receiving server (9) to the delivery to order electronic mail delivery program (PRG1), the transmission of the previous SL email A destination check process for determining whether or not the domain name of the email address designated as the destination and the organization name described as the destination in the email body correspond correctly, and the email designated as the destination of the email It was determined that the domain name of the address and the organization name described as the destination in the email text correspond correctly When the delivery of the email to the email receiving server is executed, the domain name of the email address specified as the destination of the email and the organization name described as the destination in the email text are correct. If it is determined that the e-mail is not supported, the e-mail is suspended for the e-mail selection and delivery process for canceling delivery of the e-mail to the e-mail receiving server and holding the e-mail In order to notify the sender that the message has been sent, a suspension notification process for sending an e-mail with the URL of the site describing the fact to the sender, and an in-house master database (DB5) of each e-mail delivery server ) Is statistically processed to show the grandmaster database (D 1), reflecting the data periodically from the grand master database and reflecting it in the in-organization master database, and keeping the in-organization master database always up-to-date, In order to keep the master database always up-to-date, an e-mail delivery program for executing a collaboration rate linking process for linking each e-mail delivery server and the database integration server in a collaborative manner is provided.

  Here, in order to explain the present invention in an easy-to-understand manner, the description has been made in association with the reference numerals of the drawings representing the embodiments, but it goes without saying that the present invention is not limited to the embodiments.

According to the first to sixth aspects of the present invention, there is no possibility of erroneous transmission of an e-mail to be transmitted by checking the domain name of the e-mail address of the recipient against the destination in the mail text. For emails that are not likely to be sent incorrectly, send them immediately without confirmation from the sender, while for emails that might be sent incorrectly, let the sender confirm and send the emails incorrectly. Can be prevented in advance. As a result, it is possible to prevent information leakage due to erroneous transmission of electronic mail while reducing the burden on the sender of electronic mail as much as possible.
In addition, since the in-organization master database is always kept up-to-date on the e-mail delivery server, the usability of the e-mail delivery system can be further enhanced. Furthermore, since the company information is updated at any time in the electronic mail delivery server and the database integration server, the reliability of the electronic mail delivery system can be improved.

According to the invention described in claim 4 , in addition to the above-described effects, the in-organization master database automatically grows automatically, so that the usability of the electronic mail delivery system can be improved over time.

1 is an overall configuration diagram showing an electronic mail delivery system according to Embodiment 1 of the present invention. It is a control block diagram of the database integrated server which comprises the electronic mail delivery system which concerns on the same Embodiment 1. FIG. It is a schematic diagram of a grand master database. It is a schematic diagram of a company name misprint grandmaster database. It is a control block diagram of a partner company server. It is a schematic diagram of a company URL database. It is a control block diagram of the electronic mail delivery server which comprises the electronic mail delivery system which concerns on the same Embodiment 1. FIG. It is a schematic diagram of a personal database. It is a schematic diagram of an in-company master database. It is a schematic diagram of a company name error database. It is a schematic diagram which shows the mail preparation screen 1 of a mailer. It is a schematic diagram which shows the mail preparation screen 2 of a mailer. It is a flowchart of an e-mail delivery program. It is a flowchart of a 1st company information registration program. It is a flowchart of a 2nd company information registration program. It is a flowchart of a 3rd company information registration program. It is a flowchart of a 1st company information reflection program. It is a flowchart of a 2nd company information reflection program. It is a flowchart of a company information transmission program. It is a flowchart of a company information receiving program. It is a flowchart of a company information update program. It is a flowchart of a 3rd company information reflection program. It is a flowchart of a 4th company information reflection program. It is a control block diagram of the electronic mail delivery server which comprises the electronic mail delivery system which concerns on Embodiment 2 of this invention.

Embodiments of the present invention will be described below.
Embodiment 1 of the Invention

  1 to 23 show a first embodiment of the present invention.

  First, the configuration will be described.

  As shown in FIG. 1, the electronic mail delivery system 1 includes an electronic mail transmission server 3, a plurality of administrator clients 5, and a plurality of individual clients 6, and these electronic mail transmission server 3, administrator client 5, The personal clients 6 are installed in the company 13 so as to be connected to each other via a LAN (local area network) 11. In FIG. 1, only one of the administrator clients 5 is illustrated and the remainder is not illustrated, and only one of the individual clients 6 is illustrated, and the remaining is omitted. Yes.

  Here, as shown in FIG. 1, each administrator client 5 includes an information processing device 51, an input device 52 such as a keyboard, a display device 53 such as a CRT (CRT), and a storage device 54 such as a magnetic disk. In the storage device 54, a mailer (mail software) and a browser (homepage browsing software) are installed. Each personal client 6 includes an information processing device 61, an input device 62 such as a keyboard, a display device 63 such as a CRT (CRT), and a storage device 64 such as a magnetic disk. A browser is installed.

  Further, as shown in FIG. 1, the electronic mail delivery system 1 includes a database integrated server 7, an affiliated company server 8, and an electronic mail receiving server 9. These database integrated server 7, affiliated company server 8, electronic mail The receiving servers 9 are connected to each other via the Internet 12.

  Here, the database integration server 7 includes a main control unit 71 as shown in FIG. 2, and a data memory 72 is connected to the main control unit 71. In the data memory 72, a grand master database DB1 and a company name error grand master database DB2 are readable and writable.

  As shown in FIG. 3, the grand master database DB 1 includes a plurality of partner companies that may send e-mails from other companies as well as one company 13. It is a file that describes the correspondence relationship that associates company names. Here, the company name includes an official company name and a company alias name (abbreviation, common name, etc.). The same applies hereinafter. In the grand master database DB1 shown in FIG. 3, “Kyuto Shoji Co., Ltd.” is registered as the official company name, “Kyuto Shoji” and others as the company alias name for the domain name “cute123.com” of the email address. , “Iroha Gakuen” is registered as the official company name, “Iroha Gakuen” and others are registered as the corporate alias name for the domain name “iroha.ac.jp”, and the domain name “ For "a-hospital.or.jp", "Medical Corporation Reliable Hospital" is registered as the official company name, and "Reliable Hospital" and others are registered as the company alias name.

  In addition, as shown in FIG. 4, the company name error grandmaster database DB2 is not limited to one company 13, but is a domain of mail addresses for a plurality of partner companies that may send e-mails from other companies. It is a file in which a correspondence relationship in which each company name is associated with an easily mistaken name is described in the name. In the company name error grandmaster database DB2 shown in FIG. 4, “Cute Shoji” is registered as an easily mistaken name for the email address domain name “cute123.com”, and the domain name “japan-film” “Japan Film” is registered as an easy name for “.co.jp”, and “Naomi” is registered as an easy name for the domain name “nahomi.to” of the email address.

  Further, as shown in FIG. 5, the partner server 8 includes a main control unit 81, and a data memory 82 is connected to the main control unit 81. In the data memory 82, a company URL database DB3 is stored in a readable and writable manner.

  As shown in FIG. 6, the company URL database DB3 is a file in which correspondences between company names and URLs (Uniform Resource Locator) are described for a large number of companies. In the company URL database DB3 shown in FIG. 6, “http://www.abc.co.jp” is registered as the URL for the company name “ABC Co., Ltd.”, and the company name “Kyuto Corporation” is registered. In contrast, “http://cute123.com” is registered as the URL, and “https://www.nahomi.to” is registered as the URL for the company name “Nahomi GK”. .

  Further, as shown in FIG. 1, the e-mail delivery system 1 has an e-mail delivery server 2, and this e-mail delivery server 2 is installed in the company 13 as a gateway for relaying between the LAN 11 and the Internet 12. Has been.

  Here, as shown in FIG. 7, the electronic mail delivery server 2 includes a main control unit 20. The main control unit 20 includes a first determination unit 21, a second determination unit 22, and a mail selection / delivery unit 23. The mail cancellation notification unit 25 and the data memory 26 are connected. In the data memory 26, a plurality of personal databases DB4, a company master database DB5, a company name error database DB6, and a system database DB7 are readable and writable.

  As shown in FIG. 8, each personal database DB4 has a company name in the domain name of the mail address for a plurality of partner companies that may send an email from each individual belonging to the company 13. It is a file that describes the associated correspondence. In the personal database DB4 shown in FIG. 8, "Kyuto Shoji Co., Ltd." is registered as the official company name and "Kyuto Shoji" and others are registered as the company alias name for the domain name "cute123.com" of the email address. For the domain name "a-hospital.or.jp" of the email address, "Medical Corporation Reliable Hospital" is registered as the official company name, "Reliable Hospital" and others are registered as the company alias name.

  In addition, as shown in FIG. 9, the in-company master database DB5 has a correspondence in which each company name is associated with the domain name of the mail address for a plurality of partner companies that may send an e-mail from the company 13. A file describing the relationship. In the corporate master database DB5 shown in FIG. 9, “Kyuto Shoji Co., Ltd.” is registered as the official company name, “Kyuto Shoji” and others are registered as the corporate alias name for the domain name “cute123.com” of the email address. For the domain name “a-hospital.or.jp” of the email address, “Medical Corporation Reliable Hospital” is registered as the official company name, “Reliable Hospital” and others as the company alias name, and the email address For the domain name “japan-film.co.jp”, “Nippon Film GK” is registered as the official company name, and “Nippon Film” and others are registered as the company alias name.

  In addition, as shown in FIG. 10, the company name error database DB6 is likely to mistake each company name for the domain name of the mail address for a plurality of partner companies that may send an e-mail from the company 13. It is a file in which a correspondence relationship in which names are associated is described. In the company name error database DB6 shown in FIG. 10, “cute trading” is registered as an easily mistaken name for the domain name “cute123.com” of the email address, and the domain name “nahomi.to” of the email address is registered. On the other hand, “Naomi” is registered as an easily mistaken name.

  Furthermore, the system database DB7 is a file in which a threshold value used when reflecting the correspondence relationship of each personal database DB4 in the correspondence relationship of the in-company master database DB5 is described.

  Next, the operation will be described.

  Since the electronic mail delivery system 1 has the above-described configuration, when an individual belonging to the company 13 transmits an electronic mail, the sender (individual) operates the input device 62 on the personal client 6 to operate the mailer. And click the mail creation button (not shown). Then, a mail creation screen P1 is displayed on the display device 63 as shown in FIG. The mail creation screen P1 includes a destination field (To field) 15, a subject field (Subject field) 16, a body text field 17, and a send button 18. Therefore, as shown in FIG. 12, the sender inputs a predetermined mail address (for example, “suzuki.ichiro@cute123.com” in FIG. 12) in the destination field 15 and designates it as the destination of the e-mail. In the subject field 16, a predetermined subject (for example, “meeting” in FIG. 12) is entered, and in addition, in the body field 17, an e-mail text (for example, “Kyuto Corporation, Mr. Suzuki ...” in FIG. 12). After inputting appropriately, the transmission button 18 is clicked. Then, the personal client 6 outputs a mail transmission command to the electronic mail transmission server 3 together with the electronic mail information (email address, subject, mail text).

  In response to this, the e-mail transmission server 3 outputs these e-mail information (e-mail address, subject, e-mail body) to the e-mail delivery server 2.

  In response to this, the e-mail delivery server 2 performs e-mail delivery processing while eliminating erroneous transmission, as described below, based on the e-mail delivery program PRG1 shown in FIG.

  First, the main control unit 20 picks up a company name associated with the domain name of the mail address, picks up a name easily mistaken for the company name, and further extracts the company name in the mail body (step S1). .

  That is, the main control unit 20 reads the personal database DB4 and the in-company master database DB5 from the data memory 26, refers to the individual database DB4 and the in-company master database DB5, and is associated with the domain name of the mail address. Pick out the company name. Further, the main control unit 20 reads the company name error database DB6 from the data memory 26, and refers to the company name error database DB6 to pick up names that are easily mistaken for the company name associated with the domain name of the mail address. Further, the main control unit 20 analyzes the mail text and extracts the company name in the mail text.

  Various methods are conceivable as methods for analyzing the mail text. For example, if the first five lines in the email text are extracted, and there are lines that end with a title (such as “Gochu”, “Everyone”, “Sama”, “Tono”, etc.), the word that appears before the title Can be considered as a company name. In addition to extracting the first five lines in the email text, combining the checking of the number of blank lines, blanks, punctuation marks, and particles that exist from the first line of the email text makes it more accurate. One method is to extract the company name.

  Next, the main control unit 20 outputs to the first determination unit 21 the name easily picked up earlier and the company name in the email text extracted earlier, and checks the company name error in the email text. Is commanded. In response to this instruction, the first determination unit 21 determines whether or not the company name in the email text matches an easily mistaken name, and if the company name in the email text matches an easily mistaken name. If it is determined that there is a mistake in the company name in the mail text, and if the company name in the mail text does not match the easily mistaken name, it is determined that there is no mistake in the company name in the mail text (step S2).

  If it is determined that there is an error in the company name in the mail text, the first determination unit 21 outputs that fact to the main control unit 20. Then, for the purpose of expanding the company name error database DB6, the main control unit 20 overwrites the company name error database DB6 so that the count of company names with errors (an index indicating the frequency of misuse) increases by one. Later (step S3), this e-mail is temporarily suspended (step S4) from the viewpoint that there is a risk of losing thanks to the other party (recipient) if it is transmitted as it is.

  On the other hand, when it is determined that there is no error in the company name in the mail text, the first determination unit 21 outputs that fact to the main control unit 20. Then, from the viewpoint that there is no risk of losing thanks to the other party (recipient) even if the transmission is continued as it is, the main control unit 20 asks the second determination unit 22 about the company name ( The company name associated with the domain name of the email address) and the company name in the email body extracted earlier, and the domain name of the email address and the company name listed in the email body correspond correctly A determination is made as to whether or not there is (step S5).

  Upon receiving this instruction, the second determination unit 22 determines whether or not the company name in the email text matches the company name associated with the domain name of the email address, and then the company name in the email text. If it matches the company name associated with the domain name of the email address, it is determined that the domain name of the email address corresponds to the company name listed in the email text, and the company in the email text If the name does not match the company name associated with the domain name of the email address, it is determined that the domain name of the email address and the company name described in the email text do not correspond correctly.

  For example, in the case shown in FIG. 12, since “suzuki.ichiro@cute123.com” is entered in the destination field 15, the domain name of the email address is “cute123.com”, and the personal database DB4, the in-company master database According to DB5, the company names corresponding to this domain name “cute123.com” are “Kyuto Shoji Co., Ltd.”, “Kyuto Shoji Co., Ltd.” and others. Therefore, it is determined that the domain name of the email address and the company name described in the email text correspond correctly.

  When it is determined that the domain name of the mail address and the company name described in the mail text correspond correctly, the second determination unit 22 outputs the fact to the mail selection / delivery unit 23. In response to this, the mail selection / delivery unit 23 delivers this e-mail to the e-mail receiving server 9 via the LAN 11 and the Internet 12 from the viewpoint that there is no possibility of erroneous transmission even if it is transmitted as it is ( Step S6).

  On the other hand, if it is determined that the domain name of the mail address and the company name described in the mail text do not correspond correctly, the second determination unit 22 notifies the mail selection delivery unit 23 and the mail cancellation notification unit. To 25. In response to this, the mail selection / delivery unit 23 temporarily holds the electronic mail from the viewpoint that there is a risk of erroneous transmission if it is transmitted as it is (step S4). In addition, the mail cancellation notification unit 25 transmits an e-mail in which the URL of the site describing this is written to the sender in order to notify the sender that the e-mail is suspended due to a destination error.

  Upon receiving this e-mail, the sender operates the input device 62 in the personal client 6 to activate the browser and accesses this site. Can know. Thus, the sender decides whether to send or discard this e-mail and selects “send” or “discard” at this site. Then, the mail selection / delivery unit 23 appropriately processes the e-mail based on the instruction content (“transmission” or “discard”) of the sender.

  That is, when the instruction content of the sender is “send”, the mail selection / delivery unit 23 sends the e-mail to the e-mail via the LAN 11 and the Internet 12 based on the instruction of the sender to send the e-mail. Delivered to the receiving server 9 (step S7). On the other hand, if the sender's instruction content is “discard”, the mail selection / delivery unit 23 does not deliver the e-mail to the e-mail receiving server 9 based on the sender's instruction to discard the e-mail. Discard.

  In addition, for the e-mail that has been put on hold in this manner, when registering the correspondence between the domain name of the e-mail address and the company name for the purpose of expanding the personal database DB4, the sender instructs the site to do so. To do. In response to this, the main control unit 20 reads the company name error database DB6 from the data memory 26, and refers to the company name error database DB6 to identify a name that is easily mistaken for the company name associated with the domain name of the mail address. Pick up (step S8). Next, the main control unit 20 outputs an easily mistaken name picked up earlier to the first determination unit 21 and instructs a company name error check. In response to this instruction, the first determination unit 21 determines whether or not the correspondence to be registered is described in the company name error database DB6 (step S9).

  When it is determined that the correspondence to be registered is described in the company name error database DB6, the first determination unit 21 outputs the fact to the main control unit 20. Then, the main control unit 20 rejects the registration of this correspondence from the viewpoint that it is not preferable for the sender to register this correspondence in the personal database DB4 (step S10).

  On the other hand, when it is determined that the correspondence to be registered is not described in the company name error database DB6, the first determination unit 21 outputs the fact to the main control unit 20. Then, from the viewpoint that there is no problem even if this correspondence relationship is registered in the personal database DB4, the main control unit 20 additionally writes this correspondence relationship in the personal database DB4 (step S11).

  Since the email delivery process is executed in this way, the email that is not likely to be erroneously sent is immediately sent without confirmation of the sender, while the email that is likely to be erroneously sent is By making the sender confirm, it is possible to prevent erroneous transmission. As a result, it is possible to prevent information leakage due to erroneous transmission of electronic mail while reducing the burden on the sender of electronic mail as much as possible.

  Further, by additionally registering the correspondence between the domain name of the mail address and the company name, the personal database DB4 is expanded, so that the usability of the electronic mail delivery system 1 is improved.

  When an individual manually registers new company information (company name and e-mail address), the registrant (individual), as shown in FIG. 1, is based on the first company information registration program PRG2 shown in FIG. In the personal client 6, after operating the input device 62 to start a browser, accessing a specific site and displaying the personal registration screen on the display device 63, a new company is displayed on the personal registration screen. Enter information (company name and email address) and order registration.

  In response to this instruction, the electronic mail delivery server 2 writes and reflects the company information input on the personal registration screen in the personal database DB4 in a form in which the company name is associated with the domain name of the mail address (step S21). ).

  In addition, it is appropriate that the new company information written in the personal database DB4 in this way is used by another individual by an administrator such as a department head based on the second company information registration program PRG3 shown in FIG. Only company information determined to be present is reflected in the in-company master database DB5.

  That is, as shown in FIG. 1, the administrator operates the input device 52 in the administrator client 5 to start a browser, accesses a specific site, and causes the display device 53 to display a registration screen for administrator. After that, on this administrator registration screen, it is instructed to display the correspondences described in all the personal databases DB4.

  In response to this instruction, the e-mail delivery server 2 reads the corresponding relationship from each personal database DB 4 and displays the corresponding relationship together with the statistical value on the display device 53 of the administrator client 5 (step S31).

  Therefore, the administrator looks at the statistical value of the correspondence displayed on the display device 53, selects the company information to be reflected in the in-company master database DB5, and instructs the reflection. Upon receiving this command, the e-mail delivery server 2 writes this company information in the in-company master database DB5 and reflects it (step S32).

  In addition, the manager selects the company information having the wrong company name from the correspondence displayed on the display device 53, and instructs the reflection. Upon receiving this command, the electronic mail delivery server 2 writes this company information in the company name error database DB6 and reflects it (step S33).

  When the administrator manually registers new company information (company name and e-mail address), the registrant (administrator) in FIG. 1 uses the third company information registration program PRG4 shown in FIG. As shown, after the administrator client 5 operates the input device 52 to start a browser, accesses a specific site, and displays the administrator registration screen on the display device 53, the administrator registration screen Then, registration is instructed by inputting new company information. In response to this instruction, the electronic mail delivery server 2 writes and reflects the company information input on the administrator registration screen in the in-company master database DB 5 in a form in which the company name is associated with the domain name of the mail address ( Step S41).

  Further, when manually registering the company information with the wrong company name, the administrator inputs the company information with the wrong company name on the administrator registration screen and instructs the registration. Upon receiving this instruction, the electronic mail delivery server 2 writes and reflects the company information input on the administrator registration screen in the company name error database DB6 in a form in which the company name is associated with the domain name of the mail address ( Step S42).

  In addition, company information manually registered by each individual is sequentially accumulated in each individual database DB4, and the company information accumulated in all individual database DB4 exceeds a certain number (threshold) The company information is highly versatile in the company 13 and can be regarded as correct information. Therefore, the company information is preferably reflected in the company master database DB5. Therefore, after the administrator determines this threshold (for example, 100) based on the first company information reflection program PRG5 shown in FIG. 17, the e-mail delivery server 2 uses the in-company master database DB5 based on the threshold. Automatically reflected in

  That is, as shown in FIG. 1, the administrator operates the input device 52 in the administrator client 5 to activate the browser in advance, accesses a specific site, and displays the administrator registration screen on the display device 53. After the display, on this administrator registration screen, a threshold value is input to instruct registration. In response to this instruction, the e-mail delivery server 2 writes the threshold value input on the administrator registration screen in the system database DB 7 and reflects it (step S51).

  When the individual inputs new company information and instructs registration by the above-described procedure, the e-mail delivery server 2 sets the company name in the domain name of the mail address using the company information entered on the personal registration screen. The data is written in the personal database DB4 in the associated form (step S52). Next, the e-mail delivery server 2 refers to all the other personal databases DB4, calculates the number of cases where the company information is stored, and reads the threshold value with reference to the system database DB7 (step S53). Then, it is determined whether or not the number exceeds the threshold value (step S54).

  As a result, when it is determined that the number of cases exceeds the threshold, the e-mail delivery server 2 uses the company information from the viewpoint of reflecting the company information in the in-company master database DB5. It is written and reflected in the internal master database DB5 (step S55).

  Conversely, if it is determined that this number does not exceed the threshold value, the e-mail delivery server 2 is premature to reflect this company information in the in-company master database DB5. Is written in the in-company master database DB5, and the first company information reflection program PRG5 is terminated.

  As a result, the in-company master database DB5 is updated based on the statistical data of the electronic mail delivered within the company 13, and automatically grows itself. As a result, the usability of the electronic mail delivery system 1 is improved over time.

  In the electronic mail delivery system 1, as described below, the electronic mail delivery server 2 and the database integration server 7 cooperate in a collaborative manner. Here, the collaboration type cooperation means that the two (the e-mail delivery server 2 and the database integration server 7) cooperate to maintain the latest state in cooperation with each other.

  First, the e-mail delivery server 2 periodically accesses the database integration server 7 via the Internet 12 based on the second company information reflection program PRG6 shown in FIG. 18, and receives the grandmaster database DB1 and the company name error grandmaster. By reflecting the database DB2 in the company master database DB5 and the company name error database DB6, the company master database DB5 and the company name error database DB6 are always kept up-to-date.

  That is, the e-mail delivery server 2 refers to the grand master database DB1 and the company name error grand master database DB2 of the database integration server 7 each time a predetermined update time (for example, 24 hours) elapses. Is read (step S61), and these correspondences are written and reflected in the in-company master database DB5 and the company name error database DB6 (step S62).

  As a result, in the electronic mail delivery server 2, the in-company master database DB5 and the company name error database DB6 are always kept up-to-date. Therefore, the usability of the electronic mail delivery system 1 is further improved.

  On the other hand, the database integration server 7 periodically stores the company information by accessing the database integration server 7 via the Internet 12 based on the company information transmission program PRG7 shown in FIG. Correspondingly, based on the company information receiving program PRG8 shown in FIG. 20, by selectively taking in the company information, the grand master database DB1 and the company name erroneously recorded grand master database DB2 are always kept up-to-date.

  That is, the e-mail delivery server 2 responds by referring to the in-company master database DB5, the company name error database DB6, and the plurality of personal databases DB4 each time a predetermined update time (for example, one week) elapses. The relationship is read (step S71), and the correspondence relationship is transmitted to the database integration server 7 (step S72).

  Then, the database integration server 7 receives these correspondences (step S81), statistically processes these correspondences, and then writes and reflects them in the grandmaster database DB1 and the company name error grandmaster database DB2 ( Step S82). At this time, since the correspondence relationship between the in-company master database DB5, the company name error database DB6, and the plurality of personal databases DB4 can be regarded as correct information as described above, the grand master database DB1 and the company name error database grandmaster database DB2 Correspondences written in are also correct information.

  As a result, in the database integrated server 7, the grand master database DB1 and the company name erroneously recorded grand master database DB2 are always kept up-to-date. Therefore, the usability of the electronic mail delivery system 1 is further improved.

  Thus, the e-mail delivery server 2 and the database integration server 7 are collaboratively linked. Accordingly, since the company information is updated at any time in the e-mail delivery server 2 and the database integration server 7, the reliability of the e-mail delivery server 2, the database integration server 7, and the e-mail delivery system 1 is improved.

  Further, in the database integration server 7, if there is an instruction from the person in charge, the company information of the grand master database DB1 and the company name erroneously recorded grand master database DB2 is obtained from the person in charge based on the company information update program PRG9 shown in FIG. By updating according to the instruction, the grand master database DB1 and the company name erroneously recorded grand master database DB2 are always kept up-to-date.

  That is, when the database integration server 7 receives an instruction from the person in charge, the company information of the in-company master database DB5, the company name error database DB6, and the plurality of personal databases DB4 transmitted from the e-mail delivery server 2 is stored in them. Displayed together with statistical data (step S91).

  Therefore, the person in charge selects company information to be reflected in the grand master database DB1 and commands registration. In response to this command, the database integration server 7 writes and reflects this company information in the grand master database DB1 (step S92).

  In addition, the person in charge selects the company information to be reflected in the company name error grandmaster database DB2 and instructs registration. In response to this instruction, the database integration server 7 writes and reflects this company information in the company name erroneously recorded grand master database DB2 (step S93).

  As a result, in the database integrated server 7, the grand master database DB1 and the company name erroneously recorded grand master database DB2 are always kept up-to-date.

  When the person in charge manually registers new company information, the registrant (person in charge) tries to register in the database integration server 7 based on the third company information reflection program PRG10 shown in FIG. Enter company information and order registration. Upon receiving this command, the database integration server 7 writes and reflects this company information in the grand master database DB1 in a form in which the company name is associated with the domain name of the mail address (step S101).

  When the person in charge manually registers the company information with the wrong company name, the person in charge inputs the company information with the wrong company name in the database integration server 7 and instructs the registration. In response to this command, the database integration server 7 writes and reflects this company information in the company name erroneous grandmaster database DB2 in a form in which the company name is associated with the domain name of the mail address (step S102).

  In the electronic mail delivery system 1, the database integration server 7 periodically captures and uses the company data of the partner server 8 based on the fourth company information reflection program PRG11 shown in FIG. Keep DB1 up to date.

  That is, the database integration server 7 refers to the company URL database DB3 of the partner server 8 and obtains company data indicating the correspondence between the company name and the URL (step S111), and from this company data, the mail address A domain name is acquired (step S112). Further, the database integration server 7 generates company information by associating the company name with the domain name of the mail address (step S113), and then writes and reflects this company information in the grand master database DB1 (step S114).

As a result, in the database integrated server 7, the grand master database DB1 is always kept up-to-date.
[Embodiment 2 of the Invention]

  FIG. 24 shows a second embodiment of the present invention.

  In the second embodiment, as shown in FIG. 24, the electronic mail delivery system 1 includes a first determination unit 21, a second determination unit 22, and a mail selection / delivery unit 23 in the main control unit 20 of the electronic mail delivery server 2. In addition to the cancellation notification unit 25 and the data memory 26, a third determination unit 27 for checking the date / day of the week in the mail body is connected, and a calendar database DB8 that associates the date with the day of the week is connected to the data memory 26. Is stored in a freely readable manner. About another point, it has the same structure as Embodiment 1 mentioned above.

  In this electronic mail delivery system 1, when an individual belonging to the company 13 sends an electronic mail, processing based on the electronic mail delivery program PRG1 proceeds in the same procedure as in the first embodiment described above. . Therefore, this electronic mail delivery system 1 has the same effects as those of the first embodiment described above.

  In addition, in this electronic mail delivery system 1, the time immediately after it is determined that the domain name of the mail address corresponds to the company name described in the mail body (that is, the electronic mail delivery program PRG1). In step S5 and step S6), the third determination unit 27 of the e-mail delivery server 2 checks the date / day of the week in the e-mail body of the e-mail so that the date does not match the day of the week. The e-mail not included in the text is immediately transmitted without confirmation of the sender, and the e-mail including the description in which the date and the day of the week do not match is prevented from being transmitted.

  That is, when it is determined in step S5 of the e-mail delivery program PRG1 that the domain name of the e-mail address corresponds to the company name described in the e-mail body, the second determination unit 22 The data is output to the third determination unit 27. In response to this, the third determination unit 27 reads the calendar database DB8 from the data memory 26 and refers to the calendar database DB8, so that a description in which the date does not match the day of the week is included in the mail text. Determine whether.

  For example, regarding the description of the date and day of the week in the mail text, a case where “December 10, 2008 (Wednesday)” should be described will be described. At this time, if it is correctly described as “December 10, 2008 (Wednesday)” in the mail text, it is determined that the description in which the date and the day of the week do not match is not included in the mail text. In addition, if the day of the week is mistakenly described as “December 10, 2008 (Thursday)” or the date is incorrectly stated as “December 11, 2008 (Wednesday)” It is determined that a description in which the date does not match the day of the week is included in the mail body.

  If it is determined that a description in which the date does not match the day of the week is included in the mail text, the fact is output to the main control unit 20. Then, the main control unit 20 temporarily holds the e-mail from the viewpoint that there is a risk that the destination (recipient) may be confused about whether the date or the day of the week is correct if it is transmitted as it is. Ask the sender to confirm that they can send it.

  On the other hand, when it is determined that the description in which the date and the day of the week do not match is included in the mail text, the fact is output to the main control unit 20. Then, the main control unit 20 sends this e-mail via the LAN 11 and the Internet 12 from the viewpoint that the destination (recipient) does not have a risk of deciding which of the date and the day of the week is correct even if it is transmitted as it is. To the electronic mail receiving server 9.

In this way, the e-mail to be sent is divided into two categories: the date and day of the week that do not match the date and day of the week, and the latter is not included in the body of the mail. While it is transmitted immediately without passing through, the transmission of the former is blocked in advance. As a result, it is possible to reduce the burden on the sender of the e-mail as much as possible and to avoid confusion due to the date / day error in the e-mail body of the e-mail.
[Other Embodiments of the Invention]

  In the first and second embodiments described above, as shown in FIG. 13, after executing the process of analyzing the mail text and extracting the company name in the mail text (step S1), the domain name of the mail address The case where the process of determining whether or not the company name described in the mail text corresponds correctly (step S5) has been described. However, all or part of the email body (for example, the first five lines) is taken out, and depending on whether or not the company name associated with the domain name of the email address is included in this, the domain name of the email address and the email You may make it determine whether the company name described in the text corresponds correctly. In this case, since it is not necessary to analyze the email body to extract the company name in the email body, it is necessary to determine whether the domain name of the email address and the company name described in the email body correspond correctly. It becomes easy, and the electronic mail delivery program PRG1 can be simplified accordingly.

  Furthermore, in Embodiments 1 and 2 described above, the case where a POP mail is transmitted has been described. However, the present invention can be similarly applied to a case where a Web mail is transmitted. That is, in the present invention, the electronic mail may be a POP mail or a Web mail.

  Furthermore, in the first and second embodiments described above, the electronic mail delivery system 1 in which the electronic mail delivery server 2 is installed as a gateway for relaying the LAN 11 and the Internet 12 has been described. As long as the e-mail transmitted to the receiving server 9 is surely passed through the e-mail delivery server 2 on the way, the e-mail delivery system 1 having any configuration may be used. For example, an existing mail transfer server (not shown) can be interposed between the electronic mail delivery server 2 and the Internet 12.

  In the first and second embodiments described above, the e-mail transmission server 3, the administrator client 5, and the personal client 6 are connected to each other via the LAN 11, and the database integration server 7, the partner server 8, and the e-mail reception The electronic mail delivery system 1 in which the servers 9 are connected to each other via the Internet 12 has been described. However, as a communication network for connecting the e-mail transmission server 3, the administrator client 5 and the personal client 6 to each other, and a communication network for connecting the database integration server 7, the partner server 8 and the e-mail receiving server 9 to each other, an intranet, A network using a dedicated line for personal computer communication, an extranet using a dedicated line provided by a VAN line or a communication carrier, or the like can be used instead.

  In the first and second embodiments described above, the e-mail delivery system 1 in which the e-mail delivery server 2 is installed in the company has been described. However, the e-mail delivery server 2 is not necessarily installed in the company.

  In the first and second embodiments described above, the case where an e-mail is transmitted from the company 13 has been described. However, organizations other than the company 13 (for example, central / local government offices, mutual companies, foundations, incorporated associations, social welfare) Corporations, public interest corporations, religious corporations, medical corporations, independent administrative corporations, associations of local governments, special local governments, NPO corporations, schools / schools / vocational schools, hospitals / clinics, research institutions, etc.) As long as there is a possibility of sending an email from the organization, the present invention can be similarly applied.

  In the first embodiment described above, a case has been described in which an email is prevented from being erroneously transmitted by collating the company name described as the destination in the mail body with the domain name of the destination mail address. . However, when a document file is attached to the e-mail, the e-mail is checked by matching the company name described as the destination in the document file (attached file) with the domain name of the e-mail address of the destination. It is also possible to prevent erroneous transmission.

  Further, in the above-described second embodiment, in order to prevent the transmission of an e-mail including a description in which the date and the day of the week do not match in the mail body, the date / day of week consistency is referred to with reference to the calendar database DB8. Explained the case of checking. However, in general, if a date (for example, April 1, 2009) is determined, the day of the week corresponding to that date is always determined to be one (for example, Wednesday), so instead of referring to the calendar database DB8, the date to the day of the week is determined. By calculating, it is possible to prevent transmission of an electronic mail that includes a description in which the date and day of the week do not match in the mail text. In this case, the calendar database DB8 becomes unnecessary, so that the capacity of the data memory 26 for storing it can be reduced.

1 ... E-mail delivery system 2 ... E-mail delivery server 3 ... E-mail sending server 5 ... Administrator client 6 ... Individual client 7 ... Database integration server 8 ... Partner supplier server 9 ... E-mail reception Server 11 ... LAN (communication network)
12 …… Internet (communication network)
13 …… Company (Organization)
20 …… Main control unit 21 …… First determination unit 22 …… Second determination unit (destination check means)
23 …… Mail selection delivery section (Mail selection delivery means)
25 …… Mail cancellation notification section (holding notification means)
26 …… Data memory 27 …… Third determination unit 51 …… Information processing device 52 …… Input device 53 …… Display device 54 …… Storage device 61 …… Information processing device 62 …… Input device 63 …… Display device 64 …… Storage device 71 …… Main control unit 72 …… Data memory 81 …… Main control unit 82 …… Data memory DB1 …… Grand master database DB2 …… Grand master database DB3 …… Corporate URL database DB4 …… Personal database DB5 ... Corporate master database (internal master database)
DB6 …… Company name error database DB7 …… System database DB8 …… Calendar database P1 …… Mail creation screen PRG1 …… E-mail delivery program PRG2 …… First company information registration program PRG3 …… Second company information registration program PRG4… ... Third company information registration program PRG5 …… First company information reflection program PRG6 …… Second company information reflection program PRG7 …… Company information transmission program PRG8 …… Company information reception program PRG9 …… Company information update program PRG10 …… No. 3 company information reflection program PRG11 …… 4th company information reflection program

Claims (6)

A plurality of electronic mail delivery servers and database integration server is connected via a communications network, an electronic mail delivery system e-mail is delivered to the e-mail receiving server through the communication network from the email server,
It is determined whether or not the domain name of the email address designated as the destination of the email and the organization name described as the destination in the email body correctly correspond,
When it is determined that the domain name of the email address specified as the destination of the email and the organization name described as the destination in the email text correctly correspond, the email reception of the email When delivery to the server is executed and it is determined that the domain name of the email address specified as the destination of the email does not correctly correspond to the organization name described as the destination in the email text The delivery of the e-mail to the e-mail receiving server is stopped and the e-mail is put on hold,
In order to notify the sender that the electronic mail is suspended, an electronic mail in which the URL of the site describing it is sent to the sender .
The correspondence shown in the organization master database of each e-mail delivery server is statistically processed and reflected in the grand master database of the database integration server, and the organization information is periodically updated from the grand master database. Acquired and reflected in the internal master database,
The e-mail delivery server and the database integration server are collaboratively linked so that the in- organization master database is always up-to-date and the grand master database is always up-to-date. E-mail delivery system featuring.   The electronic mail delivery system according to claim 1, wherein the organization name includes an official organization name and an organization alias name. Whether or not the domain name of the email address designated as the destination of the email and the organization name described as the destination in the email text correctly correspond is determined based on the domain name of the email address and the domain name. electronic mail delivery system of claim 1 or 2, characterized in that is performed based on the tissue in the master database indicating correspondence between the corresponding organization name. The e-mail delivery system according to any one of claims 1 to 3, wherein the in-organization master database is updated based on statistical data of e-mail delivered within the organization. In an e-mail delivery system in which a plurality of e-mail delivery servers and a database integration server are connected via a communication network, an e-mail delivery method for delivering an e-mail from an e-mail sending server to an e-mail receiving server via the communication network There,
A destination check step for determining whether or not the domain name of the email address designated as the destination of the email and the organization name described as the destination in the email body correctly correspond;
When it is determined that the domain name of the mail address designated as the destination of the e-mail and the organization name described as the destination in the mail body correspond correctly, the e-mail receiving server of the e-mail And when it is determined that the domain name of the e-mail address specified as the destination of the e-mail and the organization name described as the destination in the e-mail text do not correspond correctly A mail selection delivery process for canceling delivery of the e-mail to the e-mail receiving server and holding the e-mail;
About the suspended e-mail, in order to notify the sender that the e-mail is being suspended, a hold notification step of transmitting to the sender an e-mail in which the URL of the site describing that is written;
The correspondence shown in the organization master database of each e-mail delivery server is statistically processed and reflected in the grand master database of the database integration server, and organization information is periodically acquired from the grand master database. Data reflecting step to be reflected in the in-organization master database,
A collaborative linkage step of collaborating with each email delivery server and the database integration server so that the in-organization master database is always up-to-date and the grand master database is always up-to-date.
E-mail delivery method, which comprises a. A plurality of electronic mail delivery servers and databases integrated server and e-mail delivery system connected via a communication network, e-mail delivery for delivering the e-mail receiving server an e-mail through the communication network from the email server A program,
And determining a destination check process in the domain name and email specified mail address Text whether the organization name that is described as the destination corresponds correctly as the destination of the previous SL Email,
When it is determined that the domain name of the mail address designated as the destination of the e-mail and the organization name described as the destination in the mail body correspond correctly, the e-mail receiving server of the e-mail And when it is determined that the domain name of the e-mail address specified as the destination of the e-mail and the organization name described as the destination in the e-mail text do not correspond correctly A mail selection delivery process for canceling delivery of the e-mail to the e-mail receiving server and holding the e-mail;
With respect to the suspended e-mail, in order to notify the sender that the e-mail is suspended, a hold notification process for transmitting an e-mail in which the URL of the site describing the e-mail is written to the sender ;
The correspondence shown in the organization master database of each e-mail delivery server is statistically processed and reflected in the grand master database of the database integration server, and organization information is periodically acquired from the grand master database. Data reflection processing to be reflected in the organization master database,
Collaborate linkage processing for collaborating each email delivery server and the database integration server so that the in-organization master database is always up-to-date and the grand master database is always up-to-date.
E-mail delivery program, characterized in that to the execution.

Images