JP7528516B2 - SERVER, COMPUTER PROGRAM FOR SERVER, COMMUNICATION DEVICE, AND COMMUNICATION SYSTEM - Google Patents

Description

This specification discloses technology related to a device that has the functionality to send e-mail.

Patent Document 1 discloses a multi-function device that sends an e-mail with image data attached. When a specific destination is specified by the user from among multiple destinations stored inside the multi-function device, the multi-function device sends an e-mail with image data generated by a scanner unit attached to the specified destination. Here, the e-mail contains a unique message ID. When the multi-function device receives an error e-mail containing the message ID after sending the e-mail, the multi-function device uses the message ID to identify the destination address of the e-mail in which the error occurred. The multi-function device then registers error information in association with the identified destination address. Thereafter, when the user specifies the destination address as the destination address of a new e-mail, the multi-function device displays based on the error information.

JP 2002-297506 A

In the above technology, the multi-function device needs to have the ability to send e-mail. For example, a configuration is envisaged in which, instead of the multi-function device, a server capable of communicating with the multi-function device sends e-mail. The above technology does not envisage such a configuration at all.

This specification provides technology that can execute appropriate processing in response to email-related alerts in a configuration in which a server sends email.

The server disclosed in this specification includes a memory that stores first device identification information that identifies a first device and a first email address in association with each other, a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first email from the first device, the first email being an email regarding the transmission of first image data, a first email sending unit that, when the first transmission information is received from the first device, sends the first email to the first email address stored in association with the first device identification information that identifies the first device, a first storage control unit that, when the first transmission information is received from the first device, stores the first device identification information that identifies the first device and email identification information that identifies the first email in association with each other in the memory, and, when alert information including the email identification information is received after the first email has been transmitted, stores the email identification information in the memory. The electronic mail server may further include a second storage control unit that stores in the memory the first device identification information associated with the first device and restriction information indicating that the transmission of the e-mail is restricted in association with each other; a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail from the first device, the second e-mail being an e-mail regarding the transmission of second image data; and a second e-mail sending unit that sends the second e-mail to the first e-mail address stored in association with the first device identification information that identifies the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are not stored in association with each other, and the second e-mail sending unit that sends the second e-mail to the first e-mail address stored in association with the first device identification information that identifies the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other, the transmission of the second e-mail being restricted.

According to the above configuration, when the server receives first transmission information from the first device, it transmits a first e-mail including the first e-mail identification information, and associates the first device identification information with the first e-mail identification information and stores them in memory. Then, when the server transmits alert information including the first e-mail identification information, it associates the first device identification information associated with the first e-mail identification information with the restriction information and stores them in memory. This allows the server to restrict the transmission of the second e-mail when receiving second transmission information from the first device. As a result, the server can suppress unnecessary transmission of the second e-mail. In a configuration in which the server transmits e-mail, it is possible to execute appropriate processing in response to an alert regarding the e-mail.

The communication device disclosed in this specification includes a first mail transmission request sending unit that sends a first mail transmission request to a server when a first instruction to send a first email is accepted, the first email being an email related to the transmission of first image data, and a storage request receiving unit that receives a storage request from the server when the server receives alert information including email identification information that identifies the first email after the server sends the first email in accordance with the first mail transmission request, the storage request indicating that the sending of the email is to be restricted in association with an email address indicating the destination of the first email. The storage request receiving unit is a command that requests that the server store the restriction information in memory, and a second mail transmission request sending unit sends a second mail transmission request to the server when a second instruction to send a second mail addressed to the mail address in the memory is received in a state where the restriction information is not stored in the memory, the second mail transmission request sending unit sending the second mail transmission request to the server when the second instruction is received in a state where the restriction information is stored in the memory in association with the mail address, the second mail transmission request sending unit restricts the transmission of the second mail transmission request to the server when the second instruction is received in a state where the restriction information is stored in the memory in association with the mail address.

According to the above configuration, when the communication device accepts the first instruction, it transmits a first mail transmission request to the server, which requests the transmission of the first email. As a result, the server transmits the first email. Then, when the server receives alert information including email identification information that identifies the first email, the communication device receives a storage request from the server and stores the restriction information in memory in association with the email address. As a result, when the communication device accepts the second instruction, it is possible to restrict the transmission of a second email transmission request to the server, which requests the transmission of a second email. As a result, the server can be prevented from unnecessarily transmitting the second email. In a configuration in which the server transmits email, it is possible to execute appropriate processing in response to an alert regarding the email.

A control method for implementing the above-mentioned server, a computer program, and a computer-readable recording medium storing the computer program are also novel and useful. Also, a communication system including the above-mentioned server and another device (e.g., a first device) is novel and useful.

1 shows the configuration of a communication system. A sequence diagram outlining each function is shown below. 13 shows a flowchart of a first server process. 1 shows a flowchart of a mail sending process. 1 shows a flowchart of a restriction process. 13 shows a flowchart of a second server process. 1 shows a flowchart of a first MFP process. 13 shows a flowchart of a second MFP process. A specific case of Scan to Email will be shown. Continuation of FIG. 10. This is a continuation of case A2 in FIG. A specific case of FAX to Email will be shown. 13 shows a flowchart of a deletion process. A specific case of Scan to Email according to the second embodiment will be described. Continuation of FIG. 14 is shown.

(First embodiment)
(Configuration of communication system 2; FIG. 1)
As shown in FIG. 1, the communication system 2 includes a server 10, two multi-function devices 100 and 200, a terminal device 500, and a Cloud server 600. Each of the devices 10, 100, 200, 500, and 600 is connected to the Internet 6. The server 10 can communicate with each of the devices 100, 200, 500, and 600 via the Internet 6. In the following, the multi-function device is referred to as an "MFP (abbreviation of Multi-Function Peripheral)". The terminal device 500 is a terminal such as a desktop PC, a tablet PC, or a smartphone. The Cloud server 600 is a server that provides a service of storing image data received from another device (e.g., the MFP 100). The cloud server 600 is a known third-party server such as "Evernote (registered trademark)", "Dropbox (registered trademark)", "Google (registered trademark) Drive", or "FACEBOOK (registered trademark)".

(Configuration of Server 10)
The server 10 is a server for transmitting e-mails in accordance with instructions from the MFP 100. The server 10 is installed on the Internet 6 by a vendor of each MFP 100, etc. In a modified example, the server 10 may be installed on the Internet 6 by a business entity different from the vendor.

The server 10 includes a network interface 12 and a control unit 20. Each unit 12, 20 is connected to a bus line (reference numerals omitted). In the following, the interface is referred to as "I/F". The network I/F 12 is an interface for performing communication via the Internet 6, and is connected to the Internet 6. The control unit 20 includes a CPU 22 and a memory 24. The CPU 22 executes various processes according to a program 26 stored in the memory 24. The memory 24 is composed of a volatile memory, a non-volatile memory, etc. In addition to the above program 26, the memory 24 stores a mail table 30, a sending table 32, a restriction table 34, and a Cloud URL (short for Uniform Resource Locator) 36. The Cloud URL 36 is a URL indicating the location of the Cloud server 600. In a modified example, each table 30, etc. may be stored in an external memory that is communicatively connected to the server 10. In this modified example, a system including the server 10 and an external memory is an example of a "server."

The mail table 30 is a table that manages email addresses. For each of a plurality of MFPs, the mail table 30 stores a device ID (short for Identifier) that identifies the MFP, an address for "Scan to Email", an address for "FAX to Email", and an address for "FAX to Cloud" in association with each other. The address for "Scan to Email" is an email address that indicates the destination of emails related to the "Scan to Email" function. The address for "FAX to Email" is an email address that indicates the destination of emails related to the "FAX to Email" function. The address for "FAX to Cloud" is an email address that indicates the destination of emails related to the "FAX to Cloud" function. In the following, the "Scan to Email" function, the "FAX to Email" function, and the "FAX to Cloud" function will be collectively referred to as the "email function." The email function will be described later with reference to Figure 2.

The sending table 32 is a table that manages information related to e-mails sent by the server 10 (hereinafter referred to as "server mail"). For each of a plurality of server mails, the sending table 32 stores in association with the device ID that identifies the MFP that instructed the sending of the server mail, the e-mail address indicating the destination of the server mail, the e-mail ID that identifies the server mail, the URL ID that identifies the URL included in the body of the server mail, the timestamp indicating the date and time when the server mail was sent, and the cause information related to the server mail. The above URLs are the restriction URL and the deletion URL. The restriction URL is the URL that the user clicks when the user refuses to receive the server mail. The deletion URL is the URL that the user clicks when the user allows the reception of the server mail after refusing to receive the server mail.

The cause information is information indicating the cause of the alert regarding the server mail. The cause information indicates one of a number of causes including "temporarily unavailable", "no address", "blocked", and "requested restriction". Here, "temporarily unavailable" indicates a temporary error that prevents the server mail from being sent to its destination. A temporary error occurs, for example, when the mail server corresponding to the domain name of the email address indicating the destination of the server mail is temporarily disconnected from the Internet 6. "no address" indicates an error that prevents the server mail from being sent to its destination due to the absence of an email address indicating the destination of the server mail. "Blocked" indicates that the server mail is sent to its destination, but is blocked by the destination (for example, a mail server, mailer). For example, the server mail is blocked when it is determined to be spam. When the server mail is blocked, it cannot be sent to the destination. "Requested restriction" indicates that the user clicked on a restriction URL, which will be described later, and the server mail was refused reception.

The restriction table 34 is a table that manages restriction flags. The restriction flag indicates one of two values: "ON", which indicates that the sending of e-mail is restricted, and "OFF", which indicates that the sending of e-mail is not restricted. The restriction table 34 stores, for each of a number of restriction flags, a device ID, an e-mail address, and the restriction flag in association with each other.

(Configuration of MFP100, 200)
The MFP 100 is a peripheral device (i.e., a peripheral device of the terminal device 500) capable of performing multiple functions including a print function, a scan function, and a FAX function. The MFP 100 includes a network I/F 112, an operation unit 114, a display unit 116, a PSTN (abbreviation of Public Switched Telephone Network) I/F 118, a scan execution unit 119, and a control unit 120. Each unit 112 to 120 is connected to a bus line (reference numerals omitted). The network I/F 112 is connected to the Internet 6. The operation unit 114 includes a number of keys. A user can input various instructions to the MFP 100 by operating the operation unit 114. The display unit 116 is a display for displaying various information. The display unit 116 is a so-called touch panel, and also functions as an operation unit. The PSTN I/F 118 is an I/F for performing FAX communication.

The control unit 120 includes a CPU 122 and a memory 124. The CPU 122 executes various processes according to the programs 126 and 128 stored in the memory 124. The memory 124 is composed of a volatile memory, a non-volatile memory, and the like. The memory 124 stores an OS (short for Operating System) program 126 for implementing basic processes, a server program 128 for accessing the server 10, and FAX setting information 130. The FAX setting information 130 indicates one of the following values: "FAX to Email" indicating that the "FAX to Email" function is used, "FAX to Cloud" indicating that the "FAX to Cloud" function is used, and "Normal FAX" indicating that neither of the functions is used. The FAX setting information 130 is input by the user operating the operation unit 114. The fax setting information 130 is set to "normal fax" by default.

MFP100 is assigned the device ID "d01". MFP200 has the same configuration as MFP100. MFP200 is assigned the device ID "d02".

(Overview; Figure 2)
The outline of the mail function will be described with reference to FIG. 2. The process of FIG. 2 is realized by the processes of FIG. 3 to FIG. 8 described later. Before describing the outline of the mail function, the user's advance preparation will be described. The user operates the operation unit 114 of the MFP 100 to input addresses MA1 and MA2 for "Scan to Email". When each of the mail addresses MA1 and MA2 is input, the MFP 100 transmits a storage request including each of the mail addresses MA1 and MA2 and the device ID "d01" of the MFP 100 to the server 10. As a result, the server 10 stores each of the mail addresses MA1 and MA2 and the device ID "d01" in the mail table 30. Furthermore, the server 10 stores each of the mail addresses MA1 and MA2, the device ID "d01", and the restriction flag "OFF" in the restriction table 34. Similarly, the "FAX to Email" address MA3 and the "FAX to Cloud" address MA3 are stored in the mail table 30 and the restriction table 34.

(Scan to Email)
At T0, the user operates the operation unit 114 of the MFP 100 to execute the "Scan to Email" operation. The operations include an operation of selecting the address MA1 for "Email" and an operation of instructing execution of the scan function.

When the MFP 100 receives the "Scan to Email" operation at T0, it scans the document and generates scan data (i.e., image data). Then, at T1, the MFP 100 transmits the generated scan data and the "Scan to Email" address MA1 to the server 10.

When the server 10 receives the scan data and the "Scan to Email" address MA1 from the MFP 100 at T1, it sends an email with the scan data attached to the "Scan to Email" address MA1 at T2.

(FAX to Email)
When the MFP 100 receives the fax data via the PSTN I/F 118 at T3, the MFP 100 transmits the fax data to the server 10 at T4. The fax data is transmitted to the MFP 100 from a fax device different from the MFP 100 via fax communication. The FAX data is generated by scanning an original document with the FAX device.

When the server 10 receives the fax data from the MFP 100 at T4, it sends an email with the fax data attached to the "FAX to Email" address MA3 at T5.

(FAX to Cloud)
When the MFP 100 receives the FAX data via the PSTN I/F 118 in T6, the MFP 100 transmits a Cloud URL request for requesting the Cloud URL 36 to the server 10 in T7. Receive URL 36.

At T9, the MFP 100 transmits the fax data received at T6 to the Cloud server 600 indicated by the Cloud URL 36 received at T8. As a result, the fax data is stored in the Cloud server 600.

At T10, the MFP 100 sends a completion notification to the server 10 indicating that the transmission of the fax data to the Cloud server 600 has been completed.

When the server 10 receives a completion notification from the MFP 100 in T10, in T11 it sends an email to the "FAX to Cloud" address MA3, which includes a completion message indicating that the transmission of the FAX data to the Cloud server 600 has been completed.

(First Server Process; FIG. 3)
3, the first server process executed by the CPU 22 of the server 10 will be described. The first server process is a process for mainly executing the "Scan to Email" function. The first server process is started when the power of the server 10 is turned on.

In S2, the CPU 22 monitors whether an access request is received from a specific MFP (e.g., 100) via the network I/F 12. The access request is information transmitted from the specific MFP when a program usage operation for using the server program 128 is executed on the specific MFP. The access request includes the device ID of the specific MFP (e.g., "d01"). If the CPU 22 receives an access request from the specific MFP (YES in S2), it proceeds to S4.

In S4, the CPU 22 identifies the fax email address stored in association with the device ID included in the access request from the mail table 30. Here, the "fax email address" refers to the "fax to email" address and the "fax to cloud" address. The CPU 22 identifies the restriction flag stored in association with both the device ID included in the access request and the identified fax email address from the restriction table 34. The CPU 22 then determines whether the identified restriction flag indicates "ON". If the CPU 22 determines that the identified restriction flag indicates "ON" (YES in S4), the CPU 22 proceeds to S6. On the other hand, if the CPU 22 determines that the identified restriction flag indicates "OFF" (NO in S4), the CPU 22 skips S6 and proceeds to S8.

In S6, the CPU 22 transmits the first fax restriction screen data to the specific MFP via the network I/F 12 to cause the specific MFP to display the first fax restriction screen. The first fax restriction screen indicates that sending of e-mail addressed to the fax e-mail address is restricted.

In S8, the CPU 22 transmits menu screen data to the specific MFP via the network I/F 12 to display the menu screen on the specific MFP. The menu screen is a screen for using the email function. The menu screen includes a "Scan to Email" button for executing a scan according to the "Scan to Email" function, and a setting button for inputting information for using the email function (e.g., a "FAX to Email" address, fax setting information 130).

In S10, the CPU 22 determines whether or not "Scan to Email" selection information is received from a specific MFP via the network I/F 12. The "Scan to Email" selection information is information indicating that the "Scan to Email" button has been selected on the menu screen. If the CPU 22 determines that "Scan to Email" selection information has been received from a specific MFP (YES in S10), the process proceeds to S12. On the other hand, if the setting button has been selected on the menu screen and, for example, a storage request including a "FAX to Email" address is received (NO in S10), the CPU 22 proceeds to S16. In S16, the CPU 22 stores the "FAX to Email" address included in the storage request in the mail table 30, for example, in accordance with the above storage request. When S16 ends, the process of FIG. 3 ends.

In S12, the CPU 22 transmits scan screen data to a specific MFP via the network I/F 12 to display a scan screen on the specific MFP. The scan screen data includes one or more "Scan to Email" addresses stored in association with the device ID of the specific MFP. The scan screen includes an input field for inputting scan settings (e.g., data format, size, resolution, etc.), a selection field for selecting one email address from the one or more "Scan to Email" addresses, and a Scan button for instructing execution of the scan function.

In S14, the CPU 22 receives an email transmission request from a specific MFP via the network I/F 12. The email transmission request is a command for requesting the transmission of an email in accordance with the information in the email transmission request. The email transmission request includes an email address selected in the selection field on the scan screen, scan data generated in accordance with the scan settings entered in the input field on the scan screen in response to the selection of the Scan button on the scan screen, and the device ID of the specific MFP. Note that the process of T1 in FIG. 2 is realized by the process of S14.

In S20, the CPU 22 identifies from the restriction table 34 the restriction flags stored in association with the information contained in the email transmission request, i.e., both the device ID and the email address.

In S22, the CPU 22 determines whether the identified restriction flag indicates "ON". If the CPU 22 determines that the identified restriction flag indicates "OFF" (NO in S22), the CPU 22 executes the email sending process (see FIG. 4) described below in S24. On the other hand, if the CPU 22 determines that the identified restriction flag indicates "ON" (YES in S22), the CPU 22 executes the restriction process (see FIG. 5) described below. When S24 or S26 ends, the process in FIG. 3 ends.

(Email sending process; Figure 4)
The mail transmission process executed by the CPU 22 of the server 10 will be described with reference to Fig. 4. In S30, the CPU 22 generates a unique mail ID and a unique URL ID.

In S32, the CPU 22 generates an e-mail that includes a header describing the mail ID generated in S30 and a predetermined body, and to which the scan data in the mail transmission request received in S14 of FIG. 3 is attached. The predetermined body includes a restriction URL including the URL ID generated in S30 and a deletion URL including the URL ID generated in S30. The CPU 22 then sends the generated e-mail to the e-mail address in the mail transmission request. Furthermore, the CPU 22 stores in the transmission table 32 the device ID in the mail transmission request, the e-mail address in the mail transmission request, the mail ID generated in S30, the URL ID generated in S30, and a timestamp indicating the date and time when the above e-mail was sent, in association with each other.

In S34, the CPU 22 determines whether or not a non-delivery notification has been received for the email (i.e., server mail) sent in S32. The non-delivery notification is information for notifying an error that prevents the server mail from being sent to the destination. The non-delivery notification includes an error code that indicates the cause of the error that prevents the server mail from being sent to the destination. The non-delivery notification is received via a mail server (not shown). For example, if the server mail cannot be sent to the destination due to a "temporary outage", the non-delivery notification includes error code EC1. Also, for example, if the server mail cannot be sent to the destination due to a "no address", the non-delivery notification includes error code EC2, which is different from error code EC1. Also, the non-delivery notification includes the mail ID included in the header of the server mail. If the CPU 22 determines that a non-delivery notification has been received (YES in S34), the process proceeds to S36.

In S36, the CPU 22 associates the cause information indicated by the error code included in the non-delivery notification (e.g., "temporarily unavailable") with the email ID included in the non-delivery notification and stores it in the transmission table 32.

In S38, the CPU 22 identifies information stored in association with the email ID included in the non-delivery notification from the transmission table 32. The CPU 22 then changes the restriction flag stored in association with both the device ID and email address in the identified information in the restriction table 34 from "OFF" to "ON." When S38 ends, the process of FIG. 4 ends.

If the CPU 22 determines that it has not received a non-delivery notification (NO in S34), it determines in S40 whether or not it has received a block notification for the server mail. A block notification indicates that the server mail has been blocked by the destination of the server mail. The block notification includes the mail ID contained in the header of the server mail. The block notification is received via a mail server (not shown). If the CPU 22 determines that it has received a block notification (YES in S40), it proceeds to S42.

In S42, the CPU 22 associates the cause information indicated by the block notification (i.e., "block") with the mail ID included in the block notification and stores it in the sending table 32. When S42 ends, the process proceeds to S38. In S38, which is executed after S42, the CPU 22 uses the mail ID included in the block notification to identify information from the sending table 32, and changes the restriction flag that is associated with the identified information and stored from "OFF" to "ON."

If the CPU 22 determines that it has not received a block notification (NO in S40), it determines in S44 whether or not it has received a restriction request for the server mail. The restriction request is information that is received from the terminal device (e.g., 500) on which the server mail is displayed, without going through the mail server, when a restriction URL in the body of the server mail is clicked. The restriction request is a request to change the restriction flag stored in association with the destination of the server mail from "OFF" to "ON". The restriction request includes the URL ID included in the restriction URL. If the CPU 22 determines that it has received a restriction request (YES in S44), it proceeds to S46.

In S46, the CPU 22 associates the cause information indicated by the restriction request (i.e., the "restriction request") with the URLID included in the restriction request and stores it in the transmission table 32. When S46 ends, the process proceeds to S38. In S38, which is executed after S46, the CPU 22 uses the URLID included in the restriction request to identify information from the transmission table 32, and changes the restriction flag stored in association with the identified information from "OFF" to "ON."

If the CPU 22 determines that a restriction request has not been received (NO in S44), it skips S38 and ends the process in FIG. 4.

(Limitation process; Figure 5)
The restriction process executed by the CPU 22 of the server 10 will be described with reference to FIG. 5. In S50, the CPU 22 identifies cause information stored in association with the information (i.e., the device ID and the email address) included in the email transmission request received in S14 of FIG. 3 from the transmission table 32. Then, the CPU 22 judges whether the identified cause information indicates "temporary interruption". If the CPU 22 judges that the identified cause information indicates "temporary interruption" (YES in S50), the CPU 22 changes the restriction flag identified in S20 of FIG. 3 from "ON" to "OFF" in S52. On the other hand, if the CPU 22 judges that the identified cause information does not indicate "temporary interruption" (NO in S50), the CPU 22 skips S52 and proceeds to S53. The cause information indicating "temporary interruption" means that a temporary error has occurred. In this case, there is a possibility that the temporary error will be resolved and the email will be able to be sent to the destination. By changing the restriction flag to "OFF" when the cause information indicates "temporary outage," it is possible to properly send email when the temporary error is resolved.

In S53, the CPU 22 determines whether or not restriction processing is being performed in the first server processing in FIG. 3 (i.e., processing for the "Scan to Email" function). As will be described in detail later, the restriction processing in FIG. 5 is also performed in the second server processing (see FIG. 6). If the CPU 22 determines that restriction processing is being performed in the first server processing (YES in S53), it proceeds to S54A.

In S54A, the CPU 22 transmits scan restriction screen data to the specific MFP via the network I/F 12 to display the scan restriction screen on the specific MFP. The scan restriction screen indicates that sending e-mail addressed to the "Scan to Email" address is restricted. The scan restriction screen includes a cause message indicating the reason why sending e-mail is restricted, a delete button for instructing the deletion of the e-mail address, and a NO button. The delete button is associated with the information (i.e., the device ID and the e-mail address) included in the e-mail sending request received in S14 of FIG. 3. When the delete button or the NO button is selected, the scan restriction screen is erased from the display unit of the specific MFP.

The cause message is a message indicating the cause indicated by the cause information identified in S50. That is, as shown in FIG. 5, the Scan restriction screen includes various cause messages according to the cause of the restriction on sending e-mail. This allows the user to know the cause of the restriction on sending e-mail.

If the CPU 22 determines that a restriction process is being executed in the second server process (i.e., the process for the "FAX to Email" function and the "FAX to Cloud" function) described later (NO in S53), the CPU 22 proceeds to S54B. In S54B, the CPU 22 transmits the second FAX restriction screen data to the specific MFP via the network I/F 12 to cause the specific MFP to display the second FAX restriction screen. The second FAX restriction screen indicates that sending of e-mail addressed to the FAX e-mail address is restricted. The second FAX restriction screen is different from the first FAX restriction screen of S6 in FIG. 3. The second FAX restriction screen includes a cause message similar to that of the Scan restriction screen, a Delete button, and a NO button. On the other hand, the first FAX restriction screen does not include a Delete button. Furthermore, the second FAX restriction screen is automatically erased from the display unit of the specific MFP even if no button in the second restriction screen is selected. On the other hand, the first FAX restriction screen is erased from the display unit of the specific MFP in response to the selection of the OK button in the first FAX restriction screen. In other words, the first FAX restriction screen continues to be displayed until the OK button in the first FAX restriction screen is selected. When S54A or S54B ends, proceed to S56.

In S56, the CPU 22 determines whether or not to receive delete selection information from a specific MFP via the network I/F 12. The delete selection information is information indicating that the delete button has been selected on the scan restriction screen or the second fax restriction screen. The delete selection information includes information associated with the delete button (i.e., the device ID and email address). If the CPU 22 determines that it has received delete selection information from a specific MFP (YES in S56), it proceeds to S58, and if it determines that it has not received delete selection information from a specific MFP (NO in S56), it skips the process of S58 and ends the process of FIG. 5.

In S58, the CPU 22 deletes from the mail table 30 any email address that matches an email address in the deletion selection information among the email addresses stored in the mail table 30 in association with the device ID in the deletion selection information. Furthermore, the CPU 22 also deletes from the restriction table 34 the same email address that is stored in association with the device ID in the deletion selection information. When the processing of S58 ends, the processing of FIG. 5 ends.

(Second Server Processing)
The second server process executed by the CPU 22 of the server 10 will be described with reference to Fig. 6. The second server process is a process for executing the "FAX to Email" function and the "FAX to Cloud" function. The second server process is started when the power of the server 10 is turned on.

In S60, the CPU 22 monitors whether a "FAX to Email" request has been received from a specific MFP via the network I/F 12. The "FAX to Email" request is information sent from a specific MFP when the specific MFP receives fax data. The "FAX to Email" request includes fax data and the device ID of the specific MFP. Note that T4 in FIG. 2 is realized by the processing of S60. If the CPU 22 receives a "FAX to Email" request from a specific MFP (YES in S60), the CPU 22 proceeds to S62.

In S62, the CPU 22 identifies the "FAX to Email" address stored in association with the device ID included in the "FAX to Email" request from the mail table 30. When the CPU 22 finishes the process of S62, it proceeds to S80.

In addition to monitoring S60, the CPU 22 also monitors in S64 whether a Cloud URL request is received from a specific MFP via the network I/F 12. If the CPU 22 receives a Cloud URL request from a specific MFP (YES in S64), in S66, the CPU 22 transmits the Cloud URL 36 in the memory 24 to the specific MFP via the network I/F 12. Next, in S68, the CPU 22 receives a completion notification from the specific MFP via the network I/F 12 indicating that the transmission of the FAX data to the Cloud server 600 has been completed. The completion notification includes the device ID of the specific MFP. Here, the processes of T7, T8, and T10 in FIG. 2 are realized by the processes of S64 to S68.

In S70, the CPU 22 identifies the "FAX to Cloud" address stored in association with the device ID included in the completion notification from the mail table 30. When the CPU 22 finishes the process of S70, it proceeds to S80.

In S80, the CPU 22 identifies a restriction flag from the restriction table 34. Specifically, in S80, which is executed after S62, the CPU 22 identifies a restriction flag stored in association with both the device ID included in the "FAX to Email" request and the "FAX to Email" address identified in S62 from the restriction table 34. Also, in S80, which is executed after S70, the CPU 22 identifies a restriction flag stored in association with both the device ID included in the completion notification and the "FAX to Cloud" address identified in S70 from the restriction table 34.

S82 to S86 are the same as S22 to S26 in FIG. 3. When S84 or S86 ends, the processing in FIG. 6 ends.

(First MFP process; FIG. 7)
7, a first MFP process executed by the CPU 122 of the MFP 100 will be described. The first MFP process is a process for mainly executing the "Scan to Email" function. The first MFP process is started when the power of the MFP 100 is turned on.

In S100, the CPU 122 monitors whether a program use operation is being executed in the operation unit 114. If a program use operation is being executed (YES in S100), the CPU 122 proceeds to S102 in accordance with the server program 128.

In S102, the CPU 122 sends an access request to the server 10 via the network I/F 112 (see S2 in Figure 3).

In S104, the CPU 122 judges whether or not to receive the first fax restriction screen data from the server 10 via the network I/F 112 (see S6 in FIG. 3). If the CPU 122 judges that the first fax restriction screen data will be received from the server 10 (YES in S104), the CPU 122 displays the first fax restriction screen on the display unit 116 in accordance with the first fax restriction screen data in S105. Then, the CPU 122 receives menu screen data from the server 10 via the network I/F 112. On the other hand, if the CPU 122 receives menu screen data from the server 10 without receiving the first fax restriction screen data from the server 10 (NO in S104), the process skips S105 and proceeds to S106.

In S106, the CPU 122 displays the menu screen on the display unit 116 in accordance with the menu screen data.

In S108, the CPU 122 determines whether the "Scan to Email" button in the menu screen has been selected. If the CPU 122 determines that the "Scan to Email" button has been selected (YES in S108), it proceeds to S110, and if the CPU 122 determines that the setting button in the menu screen has been selected (NO in S108), it proceeds to S116. In S116, the CPU 122 displays an input screen for inputting information for using the email function (e.g., a "FAX to Email" address). When the processing of S116 ends, the processing of FIG. 7 ends.

In S110, the CPU 122 transmits the "Scan to Email" selection information to the server 10 via the network I/F 112 (see S10 in FIG. 3).

In S112, the CPU 122 receives scan screen data from the server 10 via the network I/F 112 (see S12 in Figure 3).

In S114, the CPU 122 displays the scan screen on the display unit 116 according to the scan screen data. When scan settings are input, an email address is selected, and the Scan button is selected on the scan screen, the CPU 122 causes the scan execution unit 119 to execute a scan according to the input scan settings. The CPU 122 then transmits an email transmission request to the server 10, which includes the selected email address, the scan data generated by the scan execution unit 119, and the device ID "d01" of the MFP 100 (see S14 in FIG. 3).

In S120, the CPU 122 determines whether or not to receive scan-restricted screen data from the server 10 via the network I/F 112 (see S54A in FIG. 5). If the CPU 122 determines that it has received scan-restricted screen data from the server 10 (YES in S120), it proceeds to S122. If the CPU 122 determines that it has not received scan-restricted screen data from the server 10 (NO in S122), it skips the processes from S122 onward and ends the process in FIG. 7.

In S122, the CPU 122 displays the scan restriction screen on the display unit 116 in accordance with the scan restriction screen data.

In S124, the CPU 122 determines whether or not the Delete button in the Scan restriction screen has been selected. If the CPU 122 determines that the Delete button has been selected (YES in S124), then in S126 it transmits the delete selection information to the server 10 via the network I/F 112 (see S56 in FIG. 5). When the process of S126 ends, the process of FIG. 7 ends. On the other hand, if the CPU 122 determines that the NO button has been selected (NO in S124), it skips the process of S126 and ends the process of FIG. 7. Note that if the Delete button or the NO button is selected, the Scan restriction screen is erased.

(Second MFP process; FIG. 8)
The second MFP process executed by the CPU 122 of the MFP 100 will be described with reference to Fig. 8. The second MFP process is a process for executing the "FAX to Email" function and the "FAX to Cloud" function. The second MFP process is started when the power of the MFP 100 is turned on.

In S150, the CPU 122 monitors whether fax data is received via the PSTN I/F 118. Note that the processes of T3 and T6 in FIG. 2 are realized by the process of S150. If fax data is received (YES in S150), the CPU 122 proceeds to S152.

In S152, the CPU 122 determines whether the fax setting information 130 in the memory 124 indicates "FAX to Email." If the CPU 122 determines that the fax setting information 130 indicates "FAX to Email" (YES in S152), the CPU 122 proceeds to S154.

In S154, the CPU 122 transmits a "FAX to Email" request including the FAX data and the device ID "d01" of the MFP 100 to the server 10 via the network I/F 112 (see S60 in FIG. 6). After completing the processes of S154 and S164, the CPU 122 proceeds to S170.

If the CPU 122 determines that the fax setting information 130 does not indicate "FAX to Email" (NO in S152), it determines in S156 whether the fax setting information 130 indicates "FAX to Cloud." If the CPU 122 determines that the fax setting information 130 indicates "FAX to Cloud" (YES in S156), it proceeds to S158.

In S158, the CPU 122 sends a Cloud URL request to the server 10 via the network I/F 112 (see S66 in FIG. 6). In S160, the CPU 122 receives the Cloud URL 36 from the server 10 via the network I/F 112 (see S68).

In S162, the CPU 122 transmits (i.e., uploads) the FAX data to the Cloud server 600 indicated by the Cloud URL 36. Note that the process of T9 in FIG. 2 is realized by the process of S162.

In S164, the CPU 122 transmits a completion notification including the device ID "d01" to the server 10 via the network I/F 112 (see S68 in FIG. 6). When the CPU 122 finishes the process of S164, it proceeds to S170.

Also, if it is determined that the fax setting information 130 indicates "normal fax" (NO in S156), the process proceeds to S168. In S168, the CPU 122 causes the print execution unit (not shown) of the MFP 100 to print an image corresponding to the fax data. When the process of S168 ends, the process of FIG. 8 ends.

In S170, the CPU 122 determines whether or not the second FAX restriction screen data has been received from the server 10 via the network I/F 112 (see S54B in FIG. 5). If the CPU 122 determines that the second FAX restriction screen data has been received from the server 10 (YES in S170), it proceeds to S172, and if the CPU 122 determines that the second FAX restriction screen data has not been received from the server 10 (NO in S170), it skips the processing from S172 onward and ends the processing in FIG. 8.

In S172, the CPU 122 displays the second fax restriction screen on the display unit 116 in accordance with the second fax restriction screen data.

In S174, the CPU 122 determines whether the Delete button in the second FAX restriction screen has been selected. If the CPU 122 determines that the Delete button has been selected (YES in S174), the process proceeds to S176. S176 is the same as S126 in FIG. 7. Then, in S180, the CPU 122 erases the second FAX restriction screen from the display unit 116. Note that even if the NO button in the second FAX restriction screen is selected, the CPU 122 also erases the second FAX restriction screen from the display unit 116 in S180. When S180 ends, the process in FIG. 8 ends.

If the CPU 122 determines that none of the buttons in the second FAX restriction screen have been selected (NO in S174), the CPU 122 determines in S178 whether a predetermined time (e.g., 30 seconds) has elapsed since the second FAX restriction screen was displayed. If the CPU 122 determines that the predetermined time has elapsed (YES in S178), the CPU 122 proceeds to S180. That is, the second FAX restriction screen is automatically erased from the display unit 116. On the other hand, if the CPU 122 determines that the predetermined time has not elapsed (NO in S178), the CPU 122 returns to S174.

(Specific cases in Scan to Email; Figures 9 to 11)
9 to 11, a specific case of Scan to Email will be described. In this case, two email addresses MA1 and MA2 are stored as addresses for "Scan to Email", and an email address MA3 is stored as an email address for FAX. In the restriction table 34, three email addresses MA1 to MA3 are stored in association with the device ID "d01" of the MFP 100, and a restriction flag "OFF" is stored in association with each of the email addresses MA1 to MA3.

In T20, the MFP 100 accepts a program usage operation from the user (YES in S100 in FIG. 7). In T22, the MFP 100 sends an access request including the device ID "d01" to the server 10 (S102).

When the server 10 receives an access request from the MFP 100 in T22 (YES in S2 in FIG. 3), in T24, it identifies the restriction flag "OFF" stored in association with both the device ID "d01" and the FAX email address MA3 in the restriction table 34. The server 10 then determines that the identified restriction flag indicates "OFF" (NO in S4). In T26, the server 10 transmits menu screen data to the MFP 100 (S8).

When the MFP 100 receives the menu screen data from the server 10 in T26, it displays the menu screen in T28 (S106 in FIG. 7). In T30, the MFP 100 accepts the selection of the "Scan to Email" button in the menu screen (YES in S108). In T32, the MFP 100 transmits the "Scan to Email" selection information to the server 10 (S110).

When the server 10 receives "Scan to Email" selection information from the MFP 100 in T32 (YES in S10 in FIG. 3), in T34 it transmits to the MFP 100 scan screen data including the two "Scan to Email" addresses MA1 and MA2 stored in association with the device ID "d01" (S12).

When the MFP 100 receives the scan screen data from the server 10 in T34 (S112 in FIG. 7), it displays the scan screen in T36 (S114).

At T38, the MFP 100 accepts input of scan settings, selection of the address MA1 for "Scan to Email," and selection of the Scan button on the scan screen. At T40, the MFP 100 generates scan data SD1 according to the input scan settings.

At T42, the MFP 100 sends an email sending request including the "Scan to Email" address MA1, the scan data SD1, and the device ID "d01" to the server 10 (114).

When the server 10 receives an email transmission request from the MFP 100 in T42 (S14 in FIG. 3), it identifies the restriction flag "OFF" that is stored in association with both the device ID "d01" and the "Scan to Email" address MA1 (S20). In T44, the server 10 determines that the identified restriction flag is "OFF" (NO in S22).

Next, at T50 in FIG. 10, the server 10 generates the mail ID "m01" and the URL ID "u01" (S30 in FIG. 4).

At T52, the server 10 sends an email EM1 to the "Scan to Email" address MA1 (S32). The email EM1 includes a header in which the mail ID "m01" is written, a restriction URL including the URLID "u01", and a body including a deletion URL including the URLID "u01". The scan data SD1 is attached to the email EM1.

The server 10 also associates the device ID "d01", the "Scan to Email" address MA1, the mail ID "m01", the URL ID "u01", and the timestamp "2019.5.20.12:00" of the email EM1 in the sending table 32.

(Cases A1 to A3)
Next, specific cases A1 to A3 of an alert regarding the email EM1 will be described. Case A1 shows a case where the cause of the alert is "temporarily out of service" or "no address". In T54, the server 10 determines that a non-delivery notice for the email EM1 has been received (YES in S34 of FIG. 4). The non-delivery notice includes the email ID "m01" and the error code EC1 (or EC2).

At T56, the server 10 associates the cause information "temporarily unreachable" (or "no address") indicated by the error code EC1 (or EC2) included in the non-delivery notification with the mail ID "m01" and stores it in the sending table 32 (S36).

At T58, the server 10 changes the restriction flag stored in association with both the device ID "d01" stored in association with the mail ID "m01" and the "Scan to Email" address MA1, which is the destination of the email EM1, from "OFF" to "ON" (S38).

Case A2 shows a case where the cause of the alert is "block." In T74, the server 10 receives a block notification for the email EM1, for example, due to the mailer that received the email EM1 executing a process for blocking (YES in S40 of FIG. 4). The block notification includes the mail ID "m01."

In T76, the server 10 associates the cause information "block" with the mail ID "m01" and stores it in the sending table 32 (S42). T78 is the same as T58.

Case A3 shows a case where the cause of the alert is a "restriction request." At T80, the user clicks on the restriction URL in the email EM1 on the terminal device 500 where the email EM1 is being displayed. As a result, at T84, the server 10 receives a restriction request including the URL ID "u01" from the terminal device 500 (YES in S44).

In T86, the server 10 associates the cause information "restriction request" with the mail ID "m01" and stores it in the sending table 32 (S46). T88 is the same as T58. With this configuration, the user can restrict the sending of emails simply by clicking the restriction URL in the email EM1. This improves user convenience.

In case A3, the user further clicks on the delete URL in the email EM1. As a result, the server 10 receives a delete request from the terminal device 500 at T94 without going through the mail server. The delete request is a request to change the restriction flag stored in association with the destination of the email EM1 from "ON" to "OFF". The delete request includes the URL ID "u01".

At T96, the server 10 identifies the information stored in association with the URL ID "u01" included in the deletion request, namely the device ID "d01" and the "Scan to Email" address MA1. The server 10 then deletes the cause information "restriction request" stored in association with both the device ID "d01" and the "Scan to Email" address MA1.

In T98, the server 10 changes the restriction flag stored in association with both the device ID "d01" and the "Scan to Email" address MA1 from "ON" to "OFF." With this configuration, even if the user accidentally clicks on a restricted URL, the restriction flag "ON" can be deleted by clicking on the deletion URL in the email EM1. This makes it possible to prevent the sending of emails from being accidentally restricted.

(Continuation of Case A2)
Next, the continuation of case A2 will be described with reference to Fig. 11. In the continuation of case A2, the user uses the "Scan to Email" function again to send an email addressed to the "Scan to Email" address MA1. Therefore, the same processes as T20 to T38 in Fig. 9 are executed. In T140, the MFP 100 generates scan data SD2 according to the scan settings entered on the scan screen. T142 is the same as T42 in Fig. 9, except that the scan data SD2 is included in the email transmission request.

When the server 10 receives an email transmission request from the MFP 100 in T142 (S14 in FIG. 3), it identifies the restriction flag "ON" that is stored in association with both the device ID "d01" and the "Scan to Email" address MA1 (S20). In T144, the server 10 determines that the identified restriction flag is "ON" (YES in S22).

At T146, the server 10 determines that the cause information stored in association with both the device ID "d01" and the "Scan to Email" address MA1 is "blocked" (NO at S50 in FIG. 5). Then, at T148, the server 10 transmits to the MFP 100 scan restriction screen data for displaying on the MFP 100 a scan restriction screen including a cause message indicating the cause "blocked" (S54A).

When the MFP 100 receives the scan restriction screen data from the server 10 in T148 (YES in S120 in FIG. 7), it displays the scan restriction screen in T150 (S122). This allows the user to know that sending e-mail addressed to the "Scan to Email" address MA1 is restricted.

In addition, if the "Scan to Email" address MA2 is selected on the scan screen, the restriction flag stored in association with the "Scan to Email" address MA2 indicates "OFF" (NO in S22), so the Scan restriction screen is not displayed. That is, if the "Scan to Email" address MA1 is selected, the Scan restriction screen is displayed, but if the "Scan to Email" address MA2 is selected, the Scan restriction screen is not displayed. According to the configuration of this case, the Scan restriction screen can be appropriately displayed according to the "Scan to Email" address selected by the user.

At T152, the MFP 100 accepts the selection of the Delete button on the Scan restriction screen (YES at S124). At T154, the MFP 100 transmits the Delete selection information including the information associated with the Delete button (i.e., the device ID "d01" and the "Scan to Email" address MA1) to the server 10 (S126).

When the server 10 receives the deletion selection information from the MFP 100 in T154 (YES in S56 in FIG. 5), in T156, it deletes the "Scan to Email" address MA1 stored in association with the device ID "d01" from the mail table 30 (S58). This makes it possible to delete the email address MA1 that has been blocked by the mailer.

In addition, in this case, in the restriction table 34, the address MA1 for "Scan to Email" is stored in association with the device ID "d02" of the MFP 200, and the restriction flag "OFF" is stored in association with the device ID "d02" and the address MA1 for "Scan to Email."

T220 is the same as T20 in FIG. 9, except that MFP 200 accepts a program usage operation. T222 to T232 are the same as T22 to T32 in FIG. 9, except that MFP 200 is used instead of MFP 100. T234 is the same as T34 in FIG. 9, except that the scan screen data includes only the address MA1 for "Scan to Email." T236 and T238 are the same as T36 and T38 in FIG. 9, except that MFP 200 is used instead of MFP 100. T240 is the same as T40 in FIG. 9, except that scan data SD3 is generated by MFP 200.

At T242, the MFP 200 sends an email sending request including the "Scan to Email" address MA1, the scan data SD3, and the device ID "d02" to the server 10 (S114 in FIG. 7).

When the server 10 receives an email transmission request from the MFP 200 in T242 (S14 in FIG. 3), it identifies the restriction flag "OFF" that is stored in association with both the device ID "d02" and the "Scan to Email" address MA1 (S20). In T244, the server 10 determines that the identified restriction flag is "OFF" (NO in S22). In T252, the server 10 sends an email EM2 with the scan data SD3 attached to the "Scan to Email" address MA1 (S32).

For example, in T78 of case A2 in FIG. 10, a comparative example is assumed in which the restriction flag "ON" is stored in the restriction table 34 in association with the "Scan to Email" address MA1 without association with the device ID "d01". In this comparative example, when an email transmission request including the "Scan to Email" address MA1 is received from an MFP 200 different from the MFP 100, the server 10 determines that the restriction flag stored in association with the "Scan to Email" address MA1 indicates "ON" and executes the restriction process of FIG. 5. For example, even if the user of the MFP 100 wants to block the email address MA1, the user of the MFP 200 may not want to block the same email address MA1. In the configuration of the comparative example, even if the user of the MFP 200 does not want to block the email address MA1, the sending of email addressed to the email address MA1 may be unnecessarily restricted. In contrast, according to the configuration of this case, the server 10 stores the restriction flag in the restriction table 34 in association with each of the device IDs "d01" and "d02". When the server 10 changes the restriction flag stored in association with the device ID "d01" from "OFF" to "ON" (T78 in FIG. 10), the server 10 maintains the restriction flag stored in association with the device ID "d02" at "OFF". Therefore, when the server 10 receives an email transmission request including the device ID "d02" from the MFP 200 (T242 in FIG. 11), it transmits the email EM2 without executing the restriction process (T252). According to the configuration of this case, when the user of the MFP 200 does not want to block the email address MA1, it is possible to prevent unnecessary restriction on the transmission of emails addressed to the email address MA1.

(Specific case of FAX to Email; Figure 12)
A specific case of FAX to Email will be described with reference to Fig. 12. In this case, the mail table 30 stores the "FAX to Email" address MA3 in association with the device ID "d01" of the MFP 100. In addition, the restriction table 34 stores the restriction flag "OFF" in association with both the device ID "d01" and the "FAX to Email" address MA3. In this case, the MFP 100 stores the FAX setting information 130 indicating "FAX to Email".

At T310, the MFP 100 receives the fax data FD1 via the PSTN I/F 118 (S150 in FIG. 8).

At T312, the MFP 100 determines that the fax setting information 130 indicates "FAX to Email" (YES at S152). At T314, the MFP 100 sends a "FAX to Email" request including the fax data FD1 and the device ID "d01" to the server 10 (S154).

When the server 10 receives a "FAX to Email" request from the MFP 100 at T314 (YES in S60 in FIG. 6), it identifies the "FAX to Email" address MA3 stored in association with the device ID "d01" from the mail table 30 (S62).

At T316, the server 10 determines that the restriction flag stored in the restriction table 34 in association with both the device ID "d01" and the "FAX to Email" address MA3 indicates "OFF" (NO at S82).

T350 is the same as T50 in FIG. 10, except that a mail ID "m03" and a URL ID "u03" are generated. In T352, the server 10 sends an email EM3 to the "FAX to Email" address MA3 (S32). The email EM3 includes a header in which the mail ID "m03" is written, and a body including a restricted URL including the URL ID "u03", and a deletion URL including the URL ID "u03". FAX data FD1 is attached to the email EM3.

The server 10 also associates the device ID "d01", the "FAX to Email" address MA3, the mail ID "m03", the URL ID "u03", and the timestamp "2019.5.20.12:00" of the email EM3 in the sending table 32.

In this case, similar to case A2 in FIG. 10, the mailer that received email EM3 executes a process for blocking. At T374, the server 10 receives a block notification for email EM3 (YES in S40 in FIG. 4). The block notification includes the mail ID "m03".

T376 is the same as T76 in FIG. 10, except that the mail ID "m03" is used. In T378, the server 10 changes the restriction flag stored in association with both the device ID "d01" stored in association with the mail ID "m03" and the "FAX to Email" address MA3, which is the destination of the email EM3, from "OFF" to "ON" (S38).

Next, in T380, the MFP 100 receives the fax data FD2 via the PSTN I/F 118 (S150 in FIG. 8). T384 is similar to T314, except that the "FAX to Email" request includes the fax data FD2.

At T386, the server 10 determines that the restriction flag stored in the restriction table 34 in association with both the device ID "d01" and the "FAX to Email" address MA3 indicates "ON" (YES in S82 of FIG. 6).

At T384, the server 10 transmits second fax restriction screen data to the MFP 100 to cause the MFP 100 to display a second fax restriction screen including a cause message indicating the cause "blocked" (S54B).

T386 is the same as T150 in FIG. 11, except that the second FAX restriction screen is displayed. In this case, none of the buttons in the second FAX restriction screen are selected by the user. Therefore, in T388, the MFP 100 automatically erases the second FAX restriction screen after a predetermined time has elapsed (YES in S178 in FIG. 8, S180). Here, in the "Scan to Email" function, a request to send an email is sent to the server 10 (T142 in FIG. 11) triggered by the user selecting the scan button in the scan screen displayed on the MFP 100 (T36 in FIG. 9). Therefore, when the Scan restriction screen is displayed on the MFP 100 (T150), there is a high possibility that the user will see the Scan restriction screen. In contrast, in the "FAX to Email" function, the reception of the fax data FD2 (T380 in FIG. 12) is used as a trigger to send a "FAX to Email" request to the server 10 (T384). Therefore, when the second fax restriction screen is displayed on the MFP 100 (T392), the user is unlikely to see the second fax restriction screen. As described above, by automatically erasing the second fax restriction screen, it is possible to prevent the second fax restriction screen from continuing to be displayed unnecessarily.

Next, in T410, the MFP 100 accepts a program usage operation from the user (YES in S100 in FIG. 7). T412 is the same as T22 in FIG. 9.

When the server 10 receives an access request from the MFP 100 in T412 (YES in S2 in FIG. 3), in T414, it identifies the restriction flag "ON" stored in association with both the device ID "d01" and the FAX email address MA3 in the restriction table 34. The server 10 then determines that the identified restriction flag indicates "ON" (YES in S4).

At T416, the server 10 transmits the first fax restriction screen data to the MFP 100 (S6 in FIG. 3). As a result, the MFP 100 displays the first fax restriction screen at T420 (S105 in FIG. 7). The first fax restriction screen is displayed when a program use operation is executed in the MFP 100 as a trigger. Therefore, the user is likely to see the first fax restriction screen. According to the configuration of this case, even if the user does not see the second fax restriction screen, the user can be informed that sending email addressed to the "FAX to Email" address is restricted. In particular, the program use operation is a trigger for executing not only the "Scan to Email" function but also processing related to the "FAX to Email" function (e.g., S16 in S3). This allows users who use the "Fax to Email" function to be notified that sending emails to "Fax to Email" addresses is restricted.

(Deletion process; FIG. 13)
The deletion process executed by the CPU 22 of the server 10 will be described with reference to Fig. 13. The deletion process is executed periodically after the server 10 is powered on.

In S200, the CPU 22 determines whether or not a mail ID (hereinafter referred to as the "target mail ID") with no associated cause information exists in the sending table 32. If the CPU 22 determines that the target mail ID exists (YES in S200), the process proceeds to S202. On the other hand, if the CPU 22 determines that the target mail ID does not exist in the sending table 32 (NO in S200), the process skips S202 and subsequent steps and ends the process in FIG. 13.

In S202, the CPU 22 determines whether a predetermined valid time (e.g., one day) has elapsed since the date and time indicated by the timestamp stored in association with the target email ID. If the CPU 22 determines that the valid time has elapsed since the date and time (YES in S202), the CPU 22 proceeds to S204. On the other hand, if the CPU 22 determines that the valid time has not elapsed since the date and time (NO in S202), the CPU 22 skips S204 and ends the processing of FIG. 13.

In S204, the CPU 22 deletes the target mail ID and the URL ID stored in association with the target mail ID from the transmission table 32. If there are multiple target mail IDs, the processes of S202 and S204 are executed for each of the multiple target mail IDs. When S204 ends, the process of FIG. 13 ends.

The existence of a target mail ID means that no non-delivery notification or the like was received between the time the server mail was sent and the expiration time. In other words, the target mail ID indicates the mail ID of a server mail for which no alerts such as errors occurred. With the above configuration, unnecessary mail IDs can be deleted.

(Effects of this embodiment)
According to the configuration of this embodiment, when the server 10 receives a mail transmission request from the MFP 100 (T42 in FIG. 9), the server 10 transmits the email EM1 including the email ID "m01", and stores the device ID "d01" and the email ID "m01" in association with each other in the transmission table 32 (T52 in FIG. 10). Then, when the server receives a block notification including the email ID "m01" (T74), the server stores the device ID "d01" associated with the email ID "m01" in association with the restriction flag "ON" in the restriction table 34 (T78). This allows the server 10 to restrict the transmission of emails when the server 10 receives a mail transmission request from the MFP 100 again (T142 in FIG. 11) (T144). As a result, the server 10 can suppress unnecessary transmission of emails in the "Scan to Email" function.

When the server 10 receives a "FAX to Email" request from the MFP 100 (T314 in FIG. 12), it transmits an email EM3 including the mail ID "m03" and stores the device ID "d01" and the mail ID "m03" in association with each other in the transmission table 32 (T352 in FIG. 12). When the server receives a block notification including the mail ID "m03" (T374), it stores the device ID "d01" associated with the mail ID "m03" in association with the restriction flag "ON" in the restriction table 34 (T378). This allows the server 10 to restrict the transmission of emails when it receives a "FAX to Email" request from the MFP 100 again (T384) (T386). As a result, the server 10 can suppress unnecessary transmission of emails in the "FAX to Email" function. Furthermore, with the configuration of this embodiment, the "FAX to Cloud" function can also similarly prevent unnecessary sending of e-mails.

(Correspondence)
The server 10, the memory 24, the MFP 100, the MFP 200, and the terminal device 500 are examples of a "server", a "memory", a "first device", a "second device", and a "terminal device", respectively. The device ID "d01" and the device ID "d02" are examples of a "first device identification information" and a "second device identification information", respectively. The mail ID or the URL ID is an example of "mail identification information". Any of the non-delivery notification, the block notification, and the restriction request is an example of "alert information". The restriction flag "ON" is an example of "restriction information". The operation of selecting the Scan button in the menu screen and the operation of selecting an email address on the menu screen are examples of a "scan execution operation" and a "selection operation", respectively. The program use operation and the server program 128 are examples of a "predetermined operation" and a "predetermined program", respectively. The restriction URL and the deletion URL are examples of a "first URL" and a "second URL", respectively. The valid time is an example of a "predetermined time".

In the "Scan to Email" function, the "Scan to Email" address MA1 and the "Scan to Email" address MA2 are examples of a "first email address" and a "second email address", respectively. The scan data SD1, SD2, and SD3 are examples of "first image data", "second image data", and "third image data", respectively. The email transmission request T42 in FIG. 9, the email transmission request T142 in FIG. 11, and the email transmission request T242 are examples of "first transmission information", "second transmission information", and "third transmission information", respectively. The Scan restriction screen and the Scan restriction screen data are examples of a "notification screen" and "restriction notification information", respectively. Selecting the Scan button in the menu screen is an example of a "specific instruction".

In the "FAX to Email" function, the "FAX to Email" address MA3 is an example of a "first email address." The fax data FD1 and FD2 are examples of "first image data" and "second image data," respectively. The "FAX to Email" request of T314 in FIG. 12 and the "FAX to Email" request of T384 are examples of "first transmission information" and "second transmission information," respectively. The first and second fax restriction screens and the first and second fax restriction screen data are examples of "notification screens" and "restriction notification information," respectively. Receiving fax data is an example of a "specific instruction."

In the "FAX to Cloud" function, the "FAX to Cloud" address MA3 is an example of a "first email address". FAX data is an example of "first image data and second image data". The completion notification of T10 in FIG. 2 is an example of "first transmission information and second transmission information". The first and second FAX restriction screens and the first and second FAX restriction screen data are examples of "notification screens" and "restriction notification information", respectively. Receiving FAX data is an example of a "specific instruction".

S32 in FIG. 4 is an example of a process implemented by the "first mail sending unit and second mail sending unit." S32 and S38 are examples of a process implemented by the "first memory control unit" and the "second memory control unit," respectively.

In the "Scan to Email" function, S14 in FIG. 3 is an example of a process realized by the "first transmission information receiving unit and second transmission information receiving unit." S114 in FIG. 7 is an example of a process realized by the "first transmission information transmitting unit and second transmission information transmitting unit."

In the "FAX to Email" function, S60 in FIG. 6 is an example of a process realized by the "first transmission information receiving unit and second transmission information receiving unit." S154 in FIG. 8 is an example of a process realized by the "first transmission information transmitting unit and second transmission information transmitting unit."

In the "FAX to Cloud" function, S68 in FIG. 6 is an example of a process realized by the "first transmission information receiving unit and second transmission information receiving unit." S164 in FIG. 8 is an example of a process realized by the "first transmission information transmitting unit and second transmission information transmitting unit."

Second Example
In this embodiment, the mail table 30 and the restriction table 34 are stored in the memory 124 of the MFP 100. The mail table 30 and the restriction table 34 do not include a device ID. In this embodiment, the process of using the mail table 30 and the restriction table 34 is executed by the CPU 122 of the MFP 100.

(Specific cases in Scan to Email; Figs. 14 and 15)
A specific case of Scan to Email will be described with reference to Figures 14 and 15. In the initial state of this case, similar to the case of Figure 9, three email addresses MA1, MA2, and MA3 are stored in the email table 30, and the restriction flag "OFF" is stored in the restriction table 34 in association with each of the email addresses MA1 to MA3.

T520 is the same as T20 in FIG. 9. In T521, the MFP 100 identifies the restriction flag stored in the restriction table 34 in association with the fax email address MA3.

In this case, the MFP 100 determines that the identified restriction flag indicates "OFF" and sends an access request to the server 10 in T522. The MFP 100 then receives menu screen data from the server 10 in T526 and displays the menu screen in T528 (see S102 and S106 in FIG. 7). If it is determined that the identified restriction flag indicates "ON", the MFP 100 displays the first FAX restriction screen on the display unit 116 (see S105 in FIG. 7) and sends an access request to the server 10.

T530 to T538 are the same as T30 to T38 in Figure 9, except that the scan screen data of T534 does not include the email addresses MA1 and MA2.

In T539, the MFP 100 identifies the restriction flag stored in association with the address MA1 for "Scan to Email" selected in T538 from the restriction table 34 in the memory 124. In this case, the MFP 100 determines that the identified restriction flag is "OFF" and executes the processing from T540 onwards. Note that a case where the identified restriction flag is determined to be "ON" will be described later from T644 onwards in FIG. 15.

T540, T542, and T550, T552, T574, and T576 in FIG. 15 are the same as T40, T42 in FIG. 9, and T50, T52, T74, and T76 in FIG. 10. In other words, this is a case where the cause of the alert is "block." In T576, the server 10 associates the cause information "block" with the mail ID "m01" and stores it in the sending table 32.

The user then uses the "Scan to Email" function again to send an email addressed to the "Scan to Email" address MA1. This causes the same processing as T520 and T521 in FIG. 14 to be executed. Then, in T582, the MFP 100 sends an access request to the server 10.

When the server 10 receives an access request from the MFP 100 in T582, the server 10 determines whether or not cause information is stored in the transmission table 32 in association with the device ID "d01" in the access request. In this case, the cause information "block" is stored in association with the device ID "d01", so in T584, the server 10 transmits a restriction flag ON request to the MFP 100 to change the restriction flag in the MFP 100 from "OFF" to "ON". The restriction flag ON request includes the email address MA1 stored in association with the device ID "d01" in the access request. If cause information is not stored in association with the device ID "d01" in the access request, the server 10 skips the process of T584 and transmits menu screen data to the MFP 100 (see T526 in FIG. 14).

When the MFP 100 receives a restriction flag ON request from the server 10 at T584, it changes the restriction flag stored in the restriction table 34 in association with the email address MA1 in the restriction flag ON request from "OFF" to "ON" at T586.

Then, the same processing as T522 to T538 in FIG. 14 is executed. That is, the MFP 100 again sends an access request to the server 10.

In T644, the MFP 100 identifies the restriction flag stored in association with the "Scan to Email" address MA1 selected by the user from the restriction table 34 in the memory 124. In this case, the MFP 100 determines that the identified restriction flag is "ON." If it is determined that the identified restriction flag is "OFF," the process is the same as T539 in FIG. 14.

At T646, the MFP 100 sends the email address MA1 to the server 10 and queries the server 10 for cause information. Then, at T648, the MFP 100 receives from the server 10 the cause information "block" that is associated with the email address MA1 and stored in the transmission table 32.

At T650, the MFP 100 displays a scan restriction screen on the display unit 116, including a cause message indicating the cause "blocked" (see S122 in FIG. 7).

At T652, the MFP 100 accepts the selection of the Delete button on the Scan restriction screen. At T656, the MFP 100 deletes the email address MA1 from the email table 30 in the memory 124.

(Effects of this embodiment)
According to the configuration of this embodiment, when the MFP 100 accepts the selection of the email address MA1 on the scan screen, it transmits an email transmission request including the email address MA1 to the server 10 (T542 in FIG. 14). As a result, the server 10 transmits the email EM1 (T552 in FIG. 15). Then, when the server 10 receives a block notification including the email ID "m01" that identifies the email EM1 (T574), the MFP 100 receives a restriction flag ON request from the server 10 and associates the email address MA1 with the restriction flag "ON" and stores it in the restriction table 34 (T586). As a result, when the MFP 100 accepts the selection of the email address MA1 on the scan screen, it is possible to display the scan restriction screen and restrict the transmission of the email transmission request to the server (T650). As a result, the server 10 can suppress unnecessary transmission of emails in the "Scan to Email" function.

Figures 14 and 15 explain the case where the sending of e-mail is restricted when the cause of the alert is "blocked." In this embodiment, even if the cause of the alert is "temporarily out of service," "no address," or "restricted URL," the sending of e-mail can be restricted in the same way as in the cases of Figures 14 and 15.

In addition, in Figures 14 and 15, a case was described in which the sending of e-mail is restricted in the "Scan to Email" function. In this embodiment, the sending of e-mail can be restricted in both the "FAX to Email" function and the "FAX to Cloud" function, as in the cases of Figures 14 and 15.

(Correspondence)
The MFP 100 and the memory 124 are examples of a "communication device" and a "memory". T542 and T584 in Fig. 14 are examples of processing realized by a "first mail transmission request transmitting unit" and a "storage request receiving unit", respectively. In T644 in Fig. 15, if it is determined that the specified restriction flag is "OFF", the MFP 100 sends a mail transmission request to the server 10, which is an example of processing realized by a "second mail transmission request transmitting unit".

Although specific examples of the present invention have been described above in detail, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples given above. Modifications of the above examples are listed below.

(Variation 1) The "first device (and communication device)" is not limited to the MFP 100, but may be, for example, a scanner capable of performing only the scan function, or a fax device capable of performing only the fax function.

(Variation 2) In the first embodiment, the MFP 100 receives fax data via the PSTN I/F 118. Alternatively, the MFP 100 may receive fax data via the network I/F 112 from a terminal device capable of executing an Internet fax function. In this case, the fax data may be, for example, image data stored in the terminal device. In this variation, the fax data received via the network I/F 112 is an example of "first image data."

(Variation 3) The sending table 32 does not need to store the URL ID. In this case, the restricted URL and the deleted URL may include the email ID. In this variation, the email ID is an example of "email identification information."

(Variation 4) The Scan restriction screen may include a Send button for instructing the sending of an e-mail. Then, when the Send button in the Scan restriction screen is selected, the server 10 may send the e-mail even if the restriction flag indicates "ON." Generally speaking, "the sending of the second e-mail is restricted" includes sending the second e-mail on the condition that the Send button in the Scan restriction screen is selected.

(Variation 5) In the first embodiment, the restriction process is executed in the second server process (i.e., the process of the "FAX to Email" function, etc.) (S86 in FIG. 6). Alternatively, when the server 10 determines that the restriction flag indicates "ON" (NO in S82), the server 10 may end the process in FIG. 6 without executing the restriction process. That is, the server 10 may not need to send the second FAX restriction screen data to the MFP 100. Generally speaking, "the transmission of the second email is restricted" includes not sending the second email and not sending restriction notification information (e.g., the second FAX restriction screen data).

(Variation 6) In the first embodiment, the server 10 transmits the scan restriction screen data to the MFP 100 (S54A in FIG. 5). Alternatively, the server 10 may transmit text data indicating a cause message to the MFP 100. In this variation, the text data is an example of "restriction notification information."

(Variation 7) The "predetermined operation" is not limited to a program usage operation, but may also be an operation of selecting a setting button on a menu screen.

(Variation 8) In the first embodiment, when the server 10 receives an access request, it determines whether the restriction flag stored in association with the FAX email address indicates "ON" (S4 in FIG. 3). Alternatively, when the server 10 receives an access request, it may determine whether the restriction flag stored in association with the "Scan to Email" address indicates "ON". Then, when the server 10 determines that the restriction flag stored in association with the "Scan to Email" address indicates "ON", it may send the Scan restriction screen data to a specific MFP. Generally speaking, the "first email address" may indicate the destination of an email regarding the transmission of scan data.

(Variation 9) The processes of S6 and S26 in FIG. 3 and S86 in FIG. 6 do not have to be executed. In this variation, the "restriction notification transmission unit" can be omitted. Also, the processes of S26 and S28 can be executed, and the process of S6 does not have to be executed. In this variation, the "access request" can be omitted.

(Variation 10) The second FAX restriction screen does not have to be automatically erased. Generally speaking, the notification screen is erased from the display unit of the first device in response to the operation of a button in the notification screen. The second FAX restriction screen may also be the same as the first FAX restriction screen. The first FAX restriction screen may also be the same as the SCAN restriction screen.

(Variation 11) The transmission table 32 does not need to store cause information. In this variation, the "cause information" can be omitted.

(Variation 12) The process of S50 in FIG. 5 does not need to be executed. In this variation, the "first deletion unit" can be omitted.

(Variation 13) The server mail does not need to include the restricted URL and the deleted URL. In this variation, the "first URL" and "second URL" can be omitted.

(Variation 14) The deletion process in FIG. 13 does not need to be performed. In this variation, the "third deletion unit" can be omitted.

(Variation 15) In each of the above embodiments, the processes in Figures 2 to 13 are implemented by software (e.g., programs 26, 126, and 128), but at least one of these processes may be implemented by hardware such as a logic circuit.

(Variation 16) In the second embodiment, the mail table 30 and the restriction table 34 are stored in the memory 124 of the MFP 100. Alternatively, the restriction table 34 may be stored in the memory 124 of the MFP 100, and the mail table 30 may be stored in the memory 24 of the server 10. In this case, the mail transmission request in FIG. 14 may include information for the server 10 to identify the mail address MA1, instead of the mail address MA1.

(Variation 17) In the second embodiment, the restriction table 34 and the like are stored in the memory 124 of the MFP 100. Alternatively, the restriction table 34 and the like may be stored in a memory provided separately from the MFP 100. In this variation, the memory provided separately from the MFP 100 is an example of a "memory".

In addition, the technical elements described in this specification or drawings exert technical utility alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. In addition, the technologies exemplified in this specification or drawings achieve multiple objectives simultaneously, and achieving one of those objectives is itself technically useful.
The features of the technology disclosed in this specification are listed below.
(Item 1)
A server,
a memory that stores first device identification information for identifying the first device and a first email address in association with each other;
a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first electronic mail, from the first device, the first electronic mail being an electronic mail regarding transmission of a first image data;
a first mail sending unit that, when the first transmission information is received from the first device, sends the first electronic mail to the first mail address stored in association with the first device identification information that identifies the first device;
a first storage control unit that, when the first transmission information is received from the first device, stores in the memory the first device identification information that identifies the first device and the mail identification information that identifies the first electronic mail in association with each other;
a second storage control unit that, when alert information including the mail identification information is received after the first mail is sent, associates the first device identification information associated with the mail identification information with restriction information indicating that the sending of the mail is restricted, and stores the associated information in the memory;
a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail, from the first device, the second e-mail being an e-mail regarding the transmission of second image data;
a second mail sending unit that sends the second e-mail to the first mail address stored in association with the first device identification information that identifies the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are not stored in association with each other, and the second mail sending unit restricts the transmission of the second e-mail when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other;
A server comprising:
(Item 2)
The memory further stores second device identification information for identifying a second device different from the first device and the first email address in association with each other;
The server further comprises:
a third transmission information receiving unit that receives third transmission information, which is information for transmitting a third e-mail, from the second device in a state in which the first device identification information and the restriction information are stored in association with each other, the third e-mail being an e-mail regarding the transmission of third image data;
a third mail sending unit that, when the third transmission information is received from the second device in a state in which the first device identification information and the restriction information are stored in association with each other, sends the third electronic mail to the first mail address stored in association with the second device identification information that identifies the second device;
2. The server according to claim 1,
(Item 3)
The server further comprises:
3. The server according to claim 1 or 2, further comprising a restriction notification sending unit that sends restriction notification information to the first device to cause the first device to display a notification screen indicating that sending of e-mail addressed to the first e-mail address is restricted when the first device identification information and the restriction information are stored in association with each other.
(Item 4)
The server according to item 3, wherein the restriction notification sending unit sends the restriction notification information to the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other.
(Item 5)
The server described in item 4, wherein the second transmission information is either information transmitted from the first device as a result of a scan execution operation for generating the second image data, which is scan data, being executed by the first device, and information transmitted from the first device as a result of the second image data, which is fax data, being received by the first device.
(Item 6)
When the second transmission information is information transmitted from the first device as a result of the scan execution operation being performed on the first device, the notification screen is erased from the first device in response to an operation of a button on the notification screen;
The server described in item 5, wherein when the second transmission information is information transmitted from the first device due to the second image data, which is the FAX data, being received by the first device, the notification screen is erased from the first device even if the button in the notification screen is not operated.
(Item 7)
the restriction notification transmission unit transmits the restriction notification information to the first device when an access request including the first device identification information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other;
7. The server according to any one of claims 3 to 6, wherein the access request is information transmitted from the first device when a predetermined operation for accessing the server is executed on the first device.
(Item 8)
The first device stores a predetermined program,
The predetermined program is
A process of transmitting the second transmission information to the server for transmitting the second e-mail regarding the transmission of the second image data, which is scan data;
a process of transmitting the second transmission information to the server for transmitting the second e-mail regarding the transmission of the second image data, which is FAX data;
a program for causing the first device to execute a plurality of processes including
8. The server according to item 7, wherein the predetermined operation is an operation for utilizing the predetermined program.
(Item 9)
the first email address indicates a destination of an email regarding the transmission of the FAX data;
the second storage control unit, when receiving the alert information, stores the first device identification information, the restriction information, and the first email address in the memory in association with each other;
The server according to item 8, wherein the restriction notification sending unit sends the restriction notification information to the first device when the access request is received from the first device and the first device identification information, the restriction information, and the first email address are stored in association with each other.
(Item 10)
The memory further stores the first device identification information and a second email address different from the first email address in association with each other,
the second transmission information is information that is transmitted to the server when a selection operation for selecting the first email address from the first email address and the second email address is executed on the first device,
5. The server according to claim 4, wherein the second transmission information includes the first device identification information and the first email address.
(Item 11)
the second storage control unit stores in the memory the first device identification information, the restriction information, and cause information indicating a cause of the alert indicated by the alert information in association with each other;
11. The server according to any one of items 3 to 10, wherein the restriction notification information is information for causing the first device to display the notification screen indicating the cause indicated by the cause information stored in association with the first device identification information.
(Item 12)
the second transmission information includes the first device identification information;
The server further comprises:
Item 12. The server according to item 11, further comprising: a first deletion unit that deletes the restriction information associated with the first device identification information from the memory when the second transmission information is received from the first device and the cause information associated with the first device identification information indicates that the first email could not be temporarily sent to the destination in a state in which the first device identification information, the restriction information, and the cause information are stored in association with each other.
(Item 13)
a first URL (short for Uniform Resource Locator) for receiving an instruction to transmit the alert information, the first email body including the first URL,
The first URL includes the email identification information,
13. The server according to any one of claims 1 to 12, wherein the alert information is information received from a terminal device on which the first email is being displayed due to selection of the first URL included in the body of the first email.
(Item 14)
the body of the first e-mail includes the first URL and a second URL for receiving an instruction to delete the restriction information;
The second URL includes the email identification information,
The server further comprises:
The server described in item 13, further comprising a second deletion unit that deletes the restriction information associated with the email identification information from the memory when a deletion request including the email identification information is received from the terminal device due to the second URL included in the body of the first email being selected when the first device identification information and the restriction information are stored in association with each other.
(Item 15)
The server further comprises:
A server according to any one of items 1 to 14, comprising a third deletion unit that deletes the email identification information from the memory when a predetermined time has elapsed since the first email was sent when the first device identification information and the restriction information are not stored in association with each other.
(Item 16)
1. A communication system comprising:
The communication system includes a server and a first device;
The server,
a memory that stores first device identification information for identifying the first device and a first email address in association with each other;
a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first electronic mail, from the first device, the first electronic mail being an electronic mail regarding transmission of a first image data;
a first mail sending unit that, when the first transmission information is received from the first device, sends the first electronic mail to the first mail address stored in association with the first device identification information that identifies the first device;
a first storage control unit that, when the first transmission information is received from the first device, stores in the memory the first device identification information that identifies the first device and the mail identification information that identifies the first electronic mail in association with each other;
a second storage control unit that, when alert information including the mail identification information is received after the first mail is sent, associates the first device identification information associated with the mail identification information with restriction information indicating that the sending of the mail is restricted, and stores the associated information in the memory;
a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail, from the first device, the second e-mail being an e-mail regarding the transmission of second image data;
a second mail sending unit that sends the second e-mail to the first mail address when the second transmission information is received from the first device in a state where the first device identification information and the restriction information are not stored in association with each other, and the second mail sending unit restricts the transmission of the second e-mail when the second transmission information is received from the first device in a state where the first device identification information and the restriction information are stored in association with each other;
Equipped with
The first device comprises:
a first transmission information transmitting unit that transmits the first transmission information to the server when a specific instruction related to the first image data is input in the first device;
a second transmission information transmitting unit that transmits the second transmission information to the server when the specific instruction related to the second image data is input in the first device;
A communication system comprising:
(Item 17)
A computer program for a server, comprising:
the server includes a memory that stores first device identification information for identifying a first device and a first email address in association with each other;
The computer program controls the server computer to include the following units:
a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first electronic mail, from the first device, the first electronic mail being an electronic mail regarding transmission of a first image data;
a first mail sending unit that, when the first transmission information is received from the first device, sends the first electronic mail to the first mail address stored in association with the first device identification information that identifies the first device;
a first storage control unit that, when the first transmission information is received from the first device, stores in the memory the first device identification information that identifies the first device and the mail identification information that identifies the first electronic mail in association with each other;
a second storage control unit that, when alert information including the mail identification information is received after the first email is sent, associates the first device identification information associated with the mail identification information with restriction information indicating that the sending of the email is restricted, and stores the associated information in the memory;
a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail, from the first device, the second e-mail being an e-mail regarding the transmission of second image data;
a second mail sending unit that sends the second e-mail to the first mail address stored in association with the first device identification information that identifies the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are not stored in association with each other, and the second mail sending unit restricts the transmission of the second e-mail when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other;
A computer program that functions as a
(Item 18)
1. A communication device, comprising:
a first mail transmission request transmission unit that transmits a first mail transmission request to a server when a first instruction for transmitting a first mail is accepted, the first mail transmission request transmitting unit transmitting the first mail to a server, the first mail being an email regarding transmission of first image data;
a storage request receiving unit that receives a storage request from the server when the server receives alert information including email identification information for identifying the first email after the server transmits the first email in accordance with the first email transmission request, the storage request being a command requesting that restriction information indicating a restriction on the transmission of email be stored in a memory in association with an email address indicating a destination of the first email;
a second mail transmission request transmission unit that transmits a second mail transmission request to the server when a second instruction to transmit a second mail addressed to the mail address in the memory is accepted in a state where the restriction information is not stored in the memory, the second mail transmission request transmission unit transmitting the second mail transmission request to the server, the second mail transmission request being an email regarding the transmission of second image data, and when the restriction information is stored in the memory in association with the mail address and the second instruction is accepted, the second mail transmission request transmission unit restricts the transmission of the second mail transmission request to the server;
A communication device comprising:

2: Communication system, 6: Internet, 10: Server, 12: Network I/F, 20: Control unit, 22: CPU, 24: Memory, 26: Program, 30: Mail table, 32: Sending table, 34: Restriction table, 36: Cloud URL, 100: MFP, 112: Network I/F, 114: Operation unit, 116: Display unit, 118: PSTN I/F, 119: Scan execution unit, 120: Control unit, 122: CPU, 124: Memory, 126: OS program, 128: Server program, 130: FAX setting information, 200: MFP, 500: Terminal device, 600: Cloud server, EC1, EC2: Error code, EM1-EM3: Email, MA1-MA3: Email address, SD1-SD3: Scan data, FD1, FD2: FAX data

Claims (18)

A server,
a memory that stores first device identification information for identifying the first device and a first email address in association with each other;
a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first electronic mail, from the first device, the first electronic mail being an electronic mail regarding transmission of a first image data;
a first mail sending unit that, when the first transmission information is received from the first device, sends the first electronic mail to the first mail address stored in association with the first device identification information that identifies the first device;
a first storage control unit that, when the first transmission information is received from the first device, stores in the memory the first device identification information that identifies the first device and the mail identification information that identifies the first electronic mail in association with each other;
a second storage control unit that, when alert information including the mail identification information is received after the first mail is sent, associates the first device identification information associated with the mail identification information with restriction information indicating that the sending of the mail is restricted, and stores the associated information in the memory;
a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail, from the first device, the second e-mail being an e-mail regarding the transmission of second image data;
a second mail sending unit that sends the second e-mail to the first mail address stored in association with the first device identification information that identifies the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are not stored in association with each other, and the second mail sending unit restricts the transmission of the second e-mail when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other;
A server comprising: The memory further stores second device identification information for identifying a second device different from the first device and the first email address in association with each other;
The server further comprises:
a third transmission information receiving unit that receives third transmission information, which is information for transmitting a third e-mail, from the second device in a state in which the first device identification information and the restriction information are stored in association with each other and the second device identification information and the restriction information are not stored in association with each other , the third e-mail being an e-mail regarding the transmission of third image data;
a third mail sending unit that, when the third transmission information is received from the second device in a state in which the first device identification information and the restriction information are stored in association with each other and the second device identification information and the restriction information are not stored in association with each other, sends the third electronic mail to the first mail address stored in association with the second device identification information that identifies the second device;
The server of claim 1 . The server further comprises:
3. The server according to claim 1 or 2, further comprising a restriction notification sending unit that sends restriction notification information to the first device to cause the first device to display a notification screen indicating that the sending of e-mail addressed to the first e-mail address is restricted when the first device identification information and the restriction information are stored in association with each other. The server according to claim 3, wherein the restriction notification transmission unit transmits the restriction notification information to the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other. The server according to claim 4, wherein the second transmission information is either information transmitted from the first device as a result of a scan execution operation for generating the second image data, which is scan data, being executed by the first device, or information transmitted from the first device as a result of the second image data, which is FAX data, being received by the first device. When the second transmission information is information transmitted from the first device as a result of the scan execution operation being performed on the first device, the notification screen is erased from the first device in response to an operation of a button on the notification screen;
The server of claim 5, wherein when the second transmission information is information transmitted from the first device due to the second image data, which is the FAX data, being received by the first device, the notification screen is erased from the first device even if the button in the notification screen is not operated. the restriction notification transmission unit transmits the restriction notification information to the first device when an access request including the first device identification information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other;
The server according to claim 3 , wherein the access request is information transmitted from the first device when a predetermined operation for accessing the server is executed on the first device. The first device stores a predetermined program,
The predetermined program is
A process of transmitting the second transmission information to the server for transmitting the second e-mail regarding the transmission of the second image data, which is scan data;
a process of transmitting the second transmission information to the server for transmitting the second e-mail regarding the transmission of the second image data, which is FAX data;
a program for causing the first device to execute a plurality of processes including
The server according to claim 7 , wherein the predetermined operation is an operation for utilizing the predetermined program. the first email address indicates a destination of an email regarding the transmission of the FAX data;
the second storage control unit, when receiving the alert information, stores the first device identification information, the restriction information, and the first email address in the memory in association with each other;
The server according to claim 8, wherein the restriction notification sending unit sends the restriction notification information to the first device when the access request is received from the first device and the first device identification information, the restriction information, and the first email address are stored in association with each other. The memory further stores the first device identification information and a second email address different from the first email address in association with each other,
the second transmission information is information that is transmitted to the server when a selection operation for selecting the first email address from the first email address and the second email address is executed on the first device,
The server according to claim 4 , wherein the second transmission information includes the first device identification information and the first email address. the second storage control unit stores in the memory the first device identification information, the restriction information, and cause information indicating a cause of the alert indicated by the alert information in association with each other;
11. A server according to claim 3, wherein the restriction notification information is information for causing the first device to display the notification screen indicating the cause indicated by the cause information stored in association with the first device identification information. the second transmission information includes the first device identification information;
The server further comprises:
The server according to claim 11, further comprising a first deletion unit that deletes the restriction information associated with the first device identification information from the memory when the second transmission information is received from the first device and the cause information associated with the first device identification information indicates that the first email could not be temporarily sent to the destination, in a state in which the first device identification information, the restriction information, and the cause information are stored in association with each other. a first URL (short for Uniform Resource Locator) for receiving an instruction to transmit the alert information, the first email body including the first URL,
The first URL includes the email identification information,
13. The server according to claim 1, wherein the alert information is information received from a terminal device on which the first email is being displayed, as a result of the first URL included in the body of the first email being selected. the body of the first e-mail includes the first URL and a second URL for receiving an instruction to delete the restriction information;
The second URL includes the email identification information,
The server further comprises:
The server described in claim 13, further comprising a second deletion unit that deletes the restriction information associated with the email identification information from the memory when a deletion request including the email identification information is received from the terminal device due to the second URL included in the body of the first email being selected when the first device identification information and the restriction information are stored in association with each other. The server further comprises:
A server as described in any one of claims 1 to 14, comprising a third deletion unit that deletes the email identification information from the memory when a predetermined time has elapsed since the first email was sent when the first device identification information and the restriction information are not stored in association with each other. 1. A communication system comprising:
The communication system includes a server and a first device;
The server,
a memory that stores first device identification information for identifying the first device and a first email address in association with each other;
a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first electronic mail, from the first device, the first electronic mail being an electronic mail regarding transmission of a first image data;
a first mail sending unit that, when the first transmission information is received from the first device, sends the first electronic mail to the first mail address stored in association with the first device identification information that identifies the first device;
a first storage control unit that, when the first transmission information is received from the first device, stores in the memory the first device identification information that identifies the first device and the mail identification information that identifies the first electronic mail in association with each other;
a second storage control unit that, when alert information including the mail identification information is received after the first mail is sent, associates the first device identification information associated with the mail identification information with restriction information indicating that the sending of the mail is restricted, and stores the associated information in the memory;
a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail, from the first device, the second e-mail being an e-mail regarding the transmission of second image data;
a second mail sending unit that sends the second e-mail to the first mail address when the second transmission information is received from the first device in a state where the first device identification information and the restriction information are not stored in association with each other, and the second mail sending unit restricts the transmission of the second e-mail when the second transmission information is received from the first device in a state where the first device identification information and the restriction information are stored in association with each other;
Equipped with
The first device comprises:
a first transmission information transmitting unit that transmits the first transmission information to the server when a specific instruction related to the first image data is input in the first device;
a second transmission information transmitting unit that transmits the second transmission information to the server when the specific instruction related to the second image data is input in the first device;
A communication system comprising: A computer program for a server, comprising:
the server includes a memory that stores first device identification information for identifying a first device and a first email address in association with each other;
The computer program controls the server computer to include the following units:
a first transmission information receiving unit that receives first transmission information, which is information for transmitting a first electronic mail, from the first device, the first electronic mail being an electronic mail regarding transmission of a first image data;
a first mail sending unit that, when the first transmission information is received from the first device, sends the first electronic mail to the first mail address stored in association with the first device identification information that identifies the first device;
a first storage control unit that, when the first transmission information is received from the first device, stores in the memory the first device identification information that identifies the first device and the mail identification information that identifies the first electronic mail in association with each other;
a second storage control unit that, when alert information including the mail identification information is received after the first mail is sent, associates the first device identification information associated with the mail identification information with restriction information indicating that the sending of the mail is restricted, and stores the associated information in the memory;
a second transmission information receiving unit that receives second transmission information, which is information for transmitting a second e-mail, from the first device, the second e-mail being an e-mail regarding the transmission of second image data;
a second mail sending unit that sends the second e-mail to the first mail address stored in association with the first device identification information that identifies the first device when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are not stored in association with each other, and the second mail sending unit restricts the transmission of the second e-mail when the second transmission information is received from the first device in a state in which the first device identification information and the restriction information are stored in association with each other;
A computer program that functions as a 1. A communication device, comprising:
a first mail transmission request transmission unit that transmits a first mail transmission request to a server when a first instruction for transmitting a first mail is accepted, the first mail transmission request transmitting unit transmitting the first mail to a server, the first mail being an email regarding transmission of first image data;
a storage request receiving unit that receives a storage request from the server when the server receives alert information including email identification information for identifying the first email after the server transmits the first email in accordance with the first email transmission request, the storage request being a command requesting that restriction information indicating a restriction on the transmission of email be stored in a memory in association with an email address indicating a destination of the first email;
a second mail transmission request transmission unit that transmits a second mail transmission request to the server when a second instruction to transmit a second mail addressed to the mail address in the memory is accepted in a state where the restriction information is not stored in the memory, the second mail transmission request transmission unit transmitting the second mail transmission request to the server, the second mail transmission request being an email regarding the transmission of second image data, and when the restriction information is stored in the memory in association with the mail address and the second instruction is accepted, the second mail transmission request transmission unit restricts the transmission of the second mail transmission request to the server;
A communication device comprising:

Images