System, method and program

Abstract

To prevent an e-mail from being erroneously transmitted.SOLUTION: An information processing device includes a first determination part for determining whether or not a set of mail addresses inhibited from being simultaneously set as a transmission destination is included in transmission destination mail addresses set as a transmission destination of an e-mail, and a second determination part for determining whether or not to transmit the e-mail or perform transmission suppression of the e-mail on the basis of a determination result by the first determination part.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention provides System, method Regarding laws and programs. [Background technology]

[0002] Mailers with an address book function that allows users to pre-register names, email addresses, etc. have been known for some time. By using such mailers, users can set destination email addresses simply by selecting the desired email address, name, etc. from the address book. Mailers are also called email software or email clients.

[0003] In addition, there are conventionally known mailers that, when an email address registered in an address book is set as a destination email address or a sender email address, display the name, etc., registered in association with that email address. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-13020 Summary of the Invention [Problem to be solved by the invention]

[0005] However, if the email address you want to set as the destination email address is not registered in the email client's address book, you must manually enter that email address as the destination email address, which can lead to emails being sent to the wrong email address due to an incorrect email address entry.

[0006] In addition, if an email address that is not registered in the email client's address book is set as the destination email address or sender email address, the name, etc. corresponding to that email address will not be displayed. As a result, when creating or sending a new email, or replying to or forwarding an email, it is not possible to confirm who the email is being sent to, which can lead to sending the email to the wrong person.

[0007] The present invention has been made in view of the above points, and has as its object to prevent the erroneous sending of e-mails. [Means for solving the problem]

[0008] In order to achieve the above-mentioned object, an information processing device in an embodiment of the present invention has a first judgment unit that judges whether the destination email addresses set as destinations for an email include a pair of email addresses that are prohibited from being set as destinations at the same time, and a second judgment unit that judges whether to send the email or to prevent the email from being sent based on the judgment result by the first judgment unit. [Effects of the Invention]

[0009] This can prevent emails from being sent to the wrong person. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a diagram illustrating an example of the overall configuration of an email system according to an embodiment of the present invention. [Figure 2] FIG. 1 is a diagram illustrating an example of a functional configuration of an email system according to an embodiment of the present invention. [Figure 3] FIG. 2 is a diagram showing an example of a personal address book stored in a personal address book storage unit. [Figure 4] FIG. 2 is a diagram illustrating an example of a shared address book stored in a shared address book storage unit. [Figure 5] 10 is a diagram showing an example of an in-house address book stored in an in-house address book storage unit; FIG. [Figure 6]FIG. 10 is a diagram illustrating an example of a prohibition relationship table stored in a prohibition relationship storage unit. [Figure 7] FIG. 10 is a sequence diagram illustrating an example of an email creation process according to the embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of a new email creation screen. [Figure 9] FIG. 10 is a diagram illustrating an example of a search screen. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of an email transmission process according to the embodiment. [Figure 11] FIG. 10 is a diagram illustrating another example of the prohibition relationship table stored in the prohibition relationship storage unit. [Figure 12] FIG. 10 is a diagram illustrating an example of a destination confirmation screen. DETAILED DESCRIPTION OF THE INVENTION

[0011] An embodiment of the present invention (hereinafter referred to as "the present embodiment") will be described below. In this embodiment, an email system 1 that can prevent emails from being sent by mistake will be described. Note that hereinafter, email will also be simply referred to as "mail."

[0012] <Overall structure> First, the overall configuration of an email system 1 according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of the overall configuration of an email system 1 according to this embodiment.

[0013] 1, the email system 1 according to this embodiment includes one or more user terminals 10, an address book management server 20, and a mail server 30. The user terminals 10, the address book management server 20, and the mail server 30 are communicatively connected via a communication network N, such as an in-house LAN (Local Area Network).

[0014] The user terminal 10 is a computer used by a user of the email system 1. As the user terminal 10, various information processing devices such as a PC (personal computer), a smartphone, a tablet terminal, etc. can be used.

[0015] A mailer 100 is installed in the user terminal 10 for creating, sending, and receiving emails. A plug-in 110 is also installed in the mailer 100 for communicating with the address book management server 20 and searching for email addresses. In this embodiment, the mailer 100 is software that functions as an email client, but is not limited to this. For example, the mailer 100 may be so-called webmail (i.e., a web application that functions as an email client and is available via a web browser).

[0016] When creating, sending, or receiving emails, the user of the user terminal 10 communicates with the address book management server 20 to search for email addresses and check the destination (for example, check the name or company name corresponding to the destination email address), thereby preventing emails from being sent by mistake.

[0017] Furthermore, for example, when an email address that is prohibited from being set as a destination email address (hereinafter also referred to as a "prohibited email address") is set for an email that the user has sent (for example, when the email address of an employee of Company A and the email address of an employee of Company B, a company that competes with Company A, are set), the user terminal 10 will suppress the sending of the email. This makes it possible to prevent erroneous sending of emails, such as sending the same email to employees of competing companies at the same time.

[0018] The destination email address is the email address entered in the TO field (or To field), CC field, or BCC field of the email, while the sender email address is the email address entered in the FROM field (or Sender field) of the email.

[0019] The address book management server 20 is a computer or computer system that manages an address book and the like used by the user of the user terminal 10 when creating, sending, and receiving emails. In this embodiment, the address book management server 20 is assumed to exist on a communication network N such as an in-house LAN, but this is not limiting, and for example, the address book management server 20 may be located on a cloud (that is, the address book management server 20 may be able to communicate with the user terminal 10 via the Internet).

[0020] The mail server 30 is a computer or computer system that transfers emails sent from the user terminal 10 to other terminals or devices and delivers emails to the user terminal 10. The mail server 30 performs the above transfers and deliveries in accordance with common email protocols such as POP (Post Office Protocol) / SMTP (Simple Mail Transfer Protocol) and IMAP (Internet Message Access Protocol). Note that in this embodiment, the mail server 30 and the address book management server 20 are separate entities, but this is not limiting. For example, the mail server 30 and the address book management server 20 may be integrated (that is, for example, the address book management server 20 may have a mail server function).

[0021] <Functional configuration> Next, the functional configuration of the email system 1 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a diagram showing an example of the functional configuration of the email system 1 according to this embodiment.

[0022] <User terminal 10> 2, the user terminal 10 according to this embodiment has a mail function unit 111, a search function unit 112, and a prohibition setting function unit 113. Of these function units, the mail function unit 111 is realized by processing that the mailer 100 causes a processor to execute, and the search function unit 112 and the prohibition setting function unit 113 are realized by processing that the mailer 100 and the plug-in 110 cause a processor to execute.

[0023] The user terminal 10 according to this embodiment also includes a mailer address book storage unit 120. This storage unit can be realized using an auxiliary storage device such as an HDD (Hard Disk Drive) or an SSD (Solid State Drive). The mailer address book storage unit 120 may also be realized using a storage device connected to the user terminal 10 via the communication network N.

[0024] The mail function unit 111 performs processing to realize various functions such as sending and receiving mail, replying, forwarding, and creating new mail.

[0025] When setting an email address as a destination email address, the search function unit 112 performs processing to search for the email address in the address book managed by the address book management server 20. For example, the search function unit 112 accepts input of a search word and sends a search request including the search word to the address book management server 20. Here, the address books managed by the address book management server 20 include, for example, a "personal address book," a "shared address book," and an "internal address book," as will be described later.

[0026] The prohibition setting function unit 113 performs processing to determine whether a prohibited email address is set as a destination email address. For example, the prohibition setting function unit 113 transmits a determination request to the address book management server 20 as to whether a prohibited email address is set as a destination email address.

[0027] Furthermore, when it is determined that a prohibited email address is set as the destination email address, the prohibition setting function unit 113 performs processing to display a warning to that effect. On the other hand, when it is determined that a prohibited email address is not set as the destination email address, the prohibition setting function unit 113 performs processing to have the user confirm the destination.

[0028] The mailer address book storage unit 120 stores the address book of the mailer 100 (hereinafter also referred to as the "mailer address book"). The mailer address book is an address book that can be used as a default function of the mailer 100 (that is, an address book that can be used regardless of whether the plug-in 110 is installed). The user can register address information such as a name and an email address in the mailer address book. The user can then set a destination email address using the address information registered in the mailer address book. Note that address information refers to one record stored in the address book, and address information includes, for example, a name and an email address.

[0029] It should be noted that the user terminal 10 does not have to have the mailer address book storage unit 120 (that is, the mailer 100 does not have to have an address book available as a default function).

[0030] <Address book management server 20> 2, the address book management server 20 according to this embodiment includes a search unit 211 and a prohibition determination unit 212. These functional units are realized by processes executed by a processor of one or more programs installed in the address book management server 20.

[0031] The address book management server 20 according to this embodiment includes a personal address book storage unit 220, a shared address book storage unit 230, an internal address book storage unit 240, and a prohibition relationship storage unit 250. Each of these storage units can be realized using an auxiliary storage device such as an HDD or SSD.

[0032] In response to a search request from the user terminal 10, the search unit 211 searches the personal address book stored in the personal address book storage unit 220, the shared address book stored in the shared address book storage unit 230, and the internal company address book stored in the internal company address book storage unit 240. Then, the search unit 211 returns the search results to the user terminal 10.

[0033] In response to a determination request from the user terminal 10, the prohibition determination unit 212 refers to the prohibition relationship table stored in the prohibition relationship storage unit 250 and determines whether or not any of the email addresses set as destination email addresses includes an email address in a prohibited relationship. The prohibition determination unit 212 then returns the determination result to the user terminal 10.

[0034] The personal address book storage unit 220 stores a personal address book that manages address information for each user of the user terminal 10. The shared address book storage unit 230 stores a shared address book that manages address information for each group of users. A group is a collection of one or more users, and a group may represent, for example, a department, team, or section.

[0035] The in-house address book storage unit 240 stores an in-house address book that manages address information of employees of the company that has introduced the email system 1 according to this embodiment (that is, users of the user terminals 10).

[0036] The prohibition relationship storage unit 250 stores a prohibition relationship table for determining which email addresses are in a prohibition relationship.

[0037] Here, the personal address book stores the user's personal address information (for example, address information of friends and acquaintances), while the shared address book stores address information shared among users belonging to a group (for example, if the group is a sales department, address information of customers). In other words, the personal address book and the shared address book generally store address information of people outside the company. Therefore, the personal address book and the shared address book may be collectively referred to as the "external address book."

[0038] <Personal Address Book> Here, the personal address book stored in the personal address book storage unit 220 will be described with reference to Fig. 3. Fig. 3 is a diagram showing an example of the personal address book stored in the personal address book storage unit 220. As described above, the personal address book registers (stores) personal address information of the user (for example, address information of friends and acquaintances).

[0039] As shown in Figure 3, the personal address book stores address information available to each user. Each address includes data items such as a user ID, phone number, email address, and attribute information. The attribute information includes name, type, etc.

[0040] The "User ID" item is set to the identification information of the user who can use the address information. The "Phone Number" item is set to the phone number registered as the address information. The "Email Address" item is set to the email address registered as the address information. The "Name" item is set to the name registered as the address information. The "Type" item is set to a type such as "Friend" or "Acquaintance".

[0041] In this way, the personal address book stored in the personal address book storage unit 220 stores address information available to each user of the user terminal 10. Note that the address information stored in the personal address book does not have to include, for example, a telephone number. Furthermore, the attribute information of the address information stored in the personal address book may include, for example, an address, a company name, etc. in addition to the name and type.

[0042] Furthermore, the address information stored in the personal address book may be synchronized with the address information stored in the mailer address book for each user, thereby making it possible to match the address information stored in the personal address book with the address information stored in the mailer address book for each user.

[0043] <Shared Address Book> Next, the shared address book stored in the shared address book storage unit 230 will be described with reference to Fig. 4. Fig. 4 is a diagram showing an example of the shared address book stored in the shared address book storage unit 230. As described above, address information shared between users belonging to a group (for example, address information of customers in the sales department) is registered (stored) in the shared address book.

[0044] As shown in FIG. 4, the shared address book storage unit 230 stores a user group table (FIG. 4(a)) and a shared address book (FIG. 4(b)).

[0045] As shown in FIG. 4(a), the user group table stores group information. Each group information item includes a group ID, a user ID, and the like as data items. The "group ID" item is set with group identification information. The "user ID" item is set with user identification information. As mentioned above, a group is a unit that represents, for example, a department, team, section, etc.

[0046] The group information stored in the user group table manages which users belong to which groups. Note that one user may belong to multiple groups.

[0047] 4(b), the shared address book stores, for each group ID, address information available to users belonging to the group indicated by the group ID. Each address information item includes the group ID, phone number, email address, and attribute information. The attribute information includes the name, company name, job title, type, and so on.

[0048] The "Group ID" item is set to the identification information of the group that can use the address information. The "Phone Number" item is set to the phone number registered as the address information. The "Email Address" item is set to the email address registered as the address information. The "Name" item is set to the name registered as the address information. The "Company Name" item is set to the company name registered as the address information. The "Job Title" item is set to the job title registered as the address information. The "Type" item is set to a type such as "Business Partner," "Customer," or "Affiliate Company."

[0049] In this way, the shared address book stored in the shared address book storage unit 230 stores, for each group, address information available to users belonging to that group. Note that the address information stored in the shared address book does not have to include, for example, a telephone number. Furthermore, the attribute information of the address information stored in the personal address book may include, for example, an address in addition to the name, company name, job title, and type.

[0050] <<Internal Address Book>> Next, the in-house address book stored in the in-house address book storage unit 240 will be described with reference to Fig. 5. Fig. 5 is a diagram showing an example of the in-house address book stored in the in-house address book storage unit 240. As described above, the in-house address book stores (registers) address information of employees of the company that has introduced the email system 1.

[0051] As shown in Figure 5, the in-house address book stores address information for each user (employee). Each piece of address information includes data items such as user ID, phone number, email address, and attribute information. The attribute information includes name, department name, job title, etc.

[0052] The "User ID" item is set with the identification information of a user who is an employee of the company that has implemented the email system 1. The "Phone Number" item is set with the phone number of the user. The "Email Address" item is set with the email address of the user. The "Name" item is set with the name of the user. The "Department Name" item is set with the department name of the user. The "Job Title" item is set with the job title of the user.

[0053] In this way, the in-house address book stored in the in-house address book storage unit 240 stores address information for each user who is an employee of the company that has introduced the electronic mail system 1.

[0054] Although the in-house address book uses the user ID as a key, the key may be, for example, a telephone number, an email address, etc. Furthermore, the address information stored in the in-house address book does not necessarily have to include, for example, a telephone number.

[0055] <Prohibition Relationship Table> Next, the prohibition relationship table stored in the prohibition relationship storage unit 250 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of the prohibition relationship table stored in the prohibition relationship storage unit 250.

[0056] As shown in Fig. 6, prohibition relationship information is stored in the prohibition relationship table. Each prohibition relationship information includes data items such as a company name and a prohibition list.

[0057] The item "Company Name" is set to the company name. The item "Prohibition List" is set to a list of company names that are in a prohibited relationship with the company name set in the item "Company Name" (for example, companies in a competitive relationship).

[0058] For example, in the prohibition relationship information in the first row of the prohibition relationship table, the item "Company Name" is set to "Company Name 1," and the item "Prohibition List" is set to "Company Name 5, Company Name 10, Company Name 11." This indicates that the company with Company Name 1 is in a prohibition relationship with the companies with Company Name 5, Company Name 10, and Company Name 11.

[0059] In this way, the prohibition relationship table stored in the prohibition relationship storage unit 250 stores prohibition relationship information for each company name, which includes a list of company names that are in a prohibition relationship with the company of that company name. This makes it possible to determine whether a prohibition-related email address is set as a destination email address.

[0060] In the example shown in FIG. 6, the prohibition relationship information includes, for each company name, a list of company names that are in a prohibition relationship with the company with that company name. However, this is not limited to this. For example, the prohibition relationship information may include, for each company name, a list of company names that are not in a prohibition relationship with the company with that company name. Alternatively, for each email address, the prohibition relationship information may include a list of email addresses that are in a prohibition relationship with that email address, or a list of email addresses that are not in a prohibition relationship with that email address. Alternatively, for example, the prohibition relationship table may store prohibition relationship information indicating that "if the domain names of the email addresses are different, the prohibition relationship applies." Alternatively, the prohibition relationship table may store prohibition relationship information indicating that "if the email address stored in the personal address book and the email address stored in the shared address book are set to the same email address, the prohibition relationship applies." Alternatively, the prohibition relationship table may store prohibition relationship information indicating that "if the email address stored in the personal address book and the email address stored in the internal address book are set to the same email address, the prohibition relationship applies." Alternatively, the prohibition relationship table may store prohibition relationship information indicating that "if the email address stored in the personal address book and the email address stored in the internal address book and the shared address book are set to the same email address, the prohibition relationship applies."

[0061] For example, the prohibition relationship table may be common to all users, or there may be a prohibition relationship table for each user, a prohibition relationship table for each group, and a prohibition relationship table for each company.Furthermore, for example, a priority may be set to indicate which prohibition relationship table is to be used preferentially among the prohibition relationship table for each user, the prohibition relationship table for each group, and the prohibition relationship table for each company.

[0062] Furthermore, although the present embodiment uses a prohibition table, it is also possible to set a prohibition flag for each email address stored in a shared address book without using the prohibition table. In this case, for example, an email address with a prohibition flag set can be set to be in a prohibition relationship with email addresses of other companies. Alternatively, for example, a flag with the same identifier can be set for email addresses that are not in a prohibition relationship.

[0063] <Email creation process> Next, a process for creating an email using the mailer 100 (an email creation process) will be described with reference to Fig. 7. Fig. 7 is a sequence diagram showing an example of an email creation process according to this embodiment.

[0064] First, the email function unit 111 of the user terminal 10 displays, for example, a new email creation screen 1000 shown in FIG. 8 (step S101). Note that, in this embodiment, a case where an email address is set in the destination email address setting field 1100 on the new email creation screen 1000 will be described, but this is not limited to this. In step S101, instead of the new email creation screen 1000, for example, an email reply screen or an email forwarding screen may be displayed. Also, this embodiment is not limited to the case where an email address is set in the destination email address setting field 1100, but can be similarly applied to the case where an email address is set in the CC field or the BCC field.

[0065] The subsequent steps S102 to S109 are repeatedly executed until a desired number of email addresses are set in the destination email address setting field 1100.

[0066] When the user presses the search start button G1200 on the new email composition screen 1000, the search function unit 112 displays, for example, a search screen 2000 shown in FIG. 9 (step S102).

[0067] Next, the search function unit 112 of the user terminal 10 accepts a search operation for an email address (step S103). Here, the user can perform a search operation for an email address by, for example, setting a search word in the search word input field 2100 on the search screen 2000 shown in Fig. 9 and then pressing the start search button 2200.

[0068] The user can set a desired character string as a search word. In addition to the search word, the user may also be able to set various search conditions (for example, comparison conditions ("=", ">", "<", etc.) and items to be searched (for example, only the item "Name" is searched).

[0069] When the search function unit 112 of the user terminal 10 receives the email address search operation, it sends a search request to the address book management server 20 (step S104). Here, the search request includes, for example, the search word set in the search word input field 2100 of the search screen 2000 shown in FIG.

[0070] When the search unit 211 of the address book management server 20 receives the search request, it searches the personal address book, the shared address book, and the internal address book using the search word included in the search request (step S105). Here, the search unit 211 extracts, for example, address information including the search word from the personal address book, the shared address book, and the internal address book as the search result.

[0071] Then, the search unit 211 of the address book management server 20 transmits the search results to the user terminal 10 (step S106).

[0072] The search function unit 112 of the user terminal 10 displays the search results in the search result display field 2300 on the search screen 2000 shown in Fig. 9 (step S107). The example shown in Fig. 9 shows a case where six pieces of address information are displayed as search results. Note that the "address book" in the search results is information indicating which address book the search (extract) was made from, with "internal" indicating that the search was made from the "internal address book," "shared" indicating that the search was made from the "shared address book," and "personal" indicating that the search was made from the "personal address book."

[0073] Next, the search function unit 112 of the user terminal 10 accepts an operation to select an email address (step S108). The user can select an email address by, for example, selecting one or more desired search results from the search result display field 2300 on the search screen 2000 shown in FIG.

[0074] When an email address selection operation is performed, the email function unit 111 of the user terminal 10 sets the email address included in the search results selected by the selection operation in the destination email address setting field 1100 of the new email creation screen 1000 shown in Figure 8, for example (step S109).

[0075] In this embodiment, the search request in step S104 above is sent to the address book management server 20 by pressing the search start button 2200 on the search screen 2000 shown in Fig. 9, but this is not limiting. For example, when a partial character string of an email address is entered in the destination email address setting field 1100 on the new email creation screen 1000 shown in Fig. 8, a search request using this partial character string as a search word may be sent to the address book management server 20. In this case, for example, the email address with the highest likelihood among the email addresses obtained as the search results may be automatically set in the destination email address setting field 1100. Here, the likelihood may be, for example, the degree of match with the search word.

[0076] As described above, the email system 1 according to this embodiment searches for address information from address books (internal address book and external address book) managed by the address book management server 20, which can communicate with the user terminal 10 via the communication network N. At this time, the email system 1 according to this embodiment displays the name, address book category, company name, department name, type, etc. as the search results. This allows the user of the user terminal 10 to set the desired email address as the destination email address without making a mistake.

[0077] <Email sending process> Next, the process of sending an email using the mailer 100 (email sending process) will be described with reference to Fig. 10. Fig. 10 is a sequence diagram showing an example of the email sending process according to this embodiment. Note that email sending includes not only sending a newly created email, but also replying to or forwarding a received email.

[0078] First, the email function unit 111 of the user terminal 10 accepts an email sending operation (step S201). Here, the user can perform an email sending operation by, for example, pressing the send button 1300 on the new email creation screen 1000 shown in FIG.

[0079] When an email sending operation is performed, the prohibition setting function unit 113 of the user terminal 10 sends a prohibition relationship determination request to the address book management server 20 (step S202). The prohibition relationship determination request includes the email address set as the destination email address. If an email address is also set in the CC field, the prohibition relationship determination request may include the email address set in the CC field. Similarly, if an email address is also set in the BCC field, the prohibition relationship determination request may include the email address set in the BCC field.

[0080] When the prohibition determination unit 212 of the address book management server 20 receives the prohibition determination request, it determines whether or not the email addresses included in the determination request include any prohibited email addresses (step S203). Here, the prohibition determination unit 212 determines whether or not any prohibited email addresses are included, for example, by the following steps S203-1 to S203-3.

[0081] Step S203-1: First, the prohibition determination unit 212 refers to the personal address book, the shared address book, and the in-house address book to identify the company name corresponding to each email address included in the determination request.

[0082] In some cases, it may not be possible to identify the company name for an email address that is registered only in the personal address book. In such cases, for example, a flag indicating that the company name could not be identified may be associated with the email address.

[0083] Step S203-2: Next, the prohibition determination unit 212 refers to the prohibition relationship table and determines whether or not there is a company name in a prohibited relationship among the company names identified in the above step S203-1.

[0084] Step S203-3: If it is determined in step S203-2 above that a prohibited company name exists, prohibition determination unit 212 determines that a prohibited email address is included. On the other hand, if it is not determined in step S203-2 above that a prohibited company name exists, prohibition determination unit 212 determines that a prohibited email address is not included.

[0085] In step S203-2, the prohibition determination unit 212 may refer to the prohibition relationship table shown in FIG. 11, for example, to determine whether any prohibited company names exist among the company names identified in step S203-1. In the example shown in FIG. 11, a prohibition relationship table corresponding to each group ID is stored in the prohibition relationship storage unit 250. In this case, the prohibition determination unit 212 identifies the user ID of the user terminal 10 that sent the prohibition relationship determination request, and then refers to the prohibition relationship table corresponding to the identified user ID to determine whether any prohibited email address is included. This makes it possible to determine whether any prohibited email address exists depending on the group to which the user belongs, even if the prohibited companies differ depending on the group (for example, if competing companies A and B are prohibited in the sales department but not in the development department).

[0086] In this embodiment, whether or not a prohibited email address is included is determined when an email is sent, but this is not limiting and may be performed, for example, in step S109 above (i.e., when an email address is set). In this case, when a prohibited email address is set in the destination email address setting field 1100, an alarm may be issued, or a pop-up or the like may be displayed indicating that setting is prohibited. Alternatively, it may be configured so that prohibited email addresses cannot be set in the destination email address setting field 1100.

[0087] Following step S203, the prohibition determination unit 212 of the address book management server 20 transmits the determination result of step S203 to the user terminal 10 (step S204). The determination result includes, for example, email addresses that are in a prohibition relationship.

[0088] If a determination result indicating that a prohibited email address is included is received, the prohibition setting function unit 113 of the user terminal 10 displays a warning indicating that a prohibited email address has been set as the destination email address (step S205). Note that in this embodiment, the sending of the email is suppressed at this time, but this is not limiting, and for example, the email may be sent to an email address other than a prohibited email address among the email addresses set as the destination email address.

[0089] If a determination result indicating that no prohibited email addresses are included is received, the prohibition setting function unit 113 of the user terminal 10 displays, for example, a destination confirmation screen 3000 shown in Fig. 12 (step S206). The destination confirmation screen 3000 shown in Fig. 12 displays information about the email address set as the destination email address (for example, the name, address book category, company name, department name, type, etc. corresponding to the email address). This allows the user to confirm to whom the email is being sent, thereby preventing erroneous sending.

[0090] At this time, the prohibition setting function unit 113 may highlight information relating to email addresses whose address book classification is "personal" or "shared" (i.e., information relating to email addresses outside the company). In the example shown in Fig. 12, information 3001 relating to email addresses is highlighted. Such highlighting makes it possible to prevent erroneous sending to email addresses outside the company in particular.

[0091] Next, the prohibition setting function unit 113 of the user terminal 10 accepts a sending operation (step S207). Here, the user can perform a sending operation by, for example, pressing the send button 3100 on the destination confirmation screen 3000 shown in FIG.

[0092] Then, the mail function unit 111 of the user terminal 10 transmits the mail to the mail server 30 (step S208). As a result, the mail server 30 transmits the mail to the mail address set as the destination mail address.

[0093] In this embodiment, in step S206 above, the destination confirmation screen is displayed before sending the email, but this is not limiting, and for example, the destination confirmation screen may be displayed after sending the email.

[0094] As described above, in the email system 1 according to this embodiment, before an email is sent from the user terminal 10, it is determined whether a prohibited email address has been set as the destination email address. If a prohibited email address has been set as the destination email address, the email system 1 according to this embodiment displays a warning and prevents the email from being sent. This makes it possible to prevent, for example, the mistaken sending of the same email to a competitor.

[0095] In this embodiment, whether or not a prohibited email address is set as a destination email address is determined when an email is sent, but this determination may also be made when an email is received. When making the determination when an email is received, for example, the user terminal 10 executes steps S202 to S204 described above when it receives an email, and then executes step S205 described above if a prohibited email address is set as a destination email address. This allows the user to know that a prohibited email address has been set as a destination email address for the received email. Therefore, for example, it is possible to prevent erroneous sending when replying to or forwarding this email.

[0096] Furthermore, when receiving an email, the user terminal 10 may access a personal address book, a shared address book, or an internal company address book to display information (e.g., company name, department, name, etc.) corresponding to the destination email address (the email address set in the TO field, CC field, and BCC field). This allows the email recipient to know who the email was sent to, and also to confirm who to send the email to when replying to or forwarding the email. The timing for accessing the personal address book, shared address book, or internal company address book may be other than when the email is received, for example, when the email is opened, or at a timing specified by the user.

[0097] The present invention is not limited to the specifically disclosed embodiments above, but various modifications and variations are possible without departing from the scope of the claims. [Explanation of symbols]

[0098] 1. Email System 10 User terminal 20 Address Book Management Server 30 Mail Server 100 Mailers 110 Plugins 111 Mail function section 112 Search Function Section 113 Prohibition setting function section 120 Mailer address book storage section 211 Search Department 212 Prohibition judgment section 220 Personal Address Book Storage Unit 230 Shared Address Book Storage Unit 240 Internal address book storage section 250 Prohibition Relations Memory Unit

Claims

1. A system including a first device and a second device, The first device is a first determination unit that determines whether or not a set of email addresses that are prohibited from being simultaneously set as destinations of an email is included in the destination email addresses of the email; The second device is a generation unit that generates content to be presented to a user based on a determination result by the first determination unit, The pair of email addresses that are prohibited from being simultaneously set as the destination is a pair of an email address stored in a personal address book, which is a personal address book of the user, and an email address stored in an internal address book, which is an address book that stores internal email addresses of the company to which the user belongs, or an email address stored in a shared address book, which is an address book that stores external email addresses shared by a group to which the user belongs. system.

2. A system including a first device and a second device, The first device is a first determination unit that determines whether or not the destination email addresses include a pair of email addresses that are prohibited from being set as destinations at the same time, based on a first group to which a user who is a sender of an email belongs, a second group to which a destination email address set as a destination of the email belongs, and a third group in the first group that is prohibited from being set as destinations at the same time as the second group; The second device is a second determination unit that determines whether to transmit the email or to inhibit transmission of the email based on the determination result by the first determination unit; system.

3. 1. A method for use in a system including a first device and a second device, comprising: The first device comprises: a first determination step of determining whether the destination email addresses of the email include a pair of email addresses that are prohibited from being set as destinations at the same time; The second device comprises: a generation step of generating content to be presented to a user based on a determination result of the first determination step; A method in which the pair of email addresses that are prohibited from being set simultaneously as destinations is a pair of email addresses stored in a personal address book, which is the user's personal address book, and an email address stored in an internal address book, which is an address book that stores internal email addresses of the company to which the user belongs, or an email address stored in a shared address book, which is an address book that stores external email addresses shared by a group to which the user belongs.

4. 1. A method for use in a system including a first device and a second device, comprising: The first device comprises: a first determination procedure for determining whether the destination email addresses include a pair of email addresses that are prohibited from being simultaneously set as destinations, based on a first group to which a user who is a sender of an email belongs, a second group to which a destination email address set as a destination of the email belongs, and a third group in the first group that is prohibited from being simultaneously set as a destination with the second group; The second device comprises: a second determination procedure for determining whether to transmit the email or to inhibit transmission of the email based on the determination result of the first determination procedure; method.

5. A program that causes a computer to function as the first device included in the system according to claim 1 or 2.

Images