Patent Grant
11172078
This application claims priority to Japanese Patent Application No. 2019-120345 filed on Jun. 27, 2019 and Japanese Patent Application No. 2020-77711 filed on Apr. 24, 2020, the contents of which are hereby incorporated by reference into the present application.
The present disclosure relates to the art related to a device comprising a function of sending an email.
A multi-function peripheral which sends an email with attached image data is known. The multi-function peripheral sends the email with the attached image data created by its scan executing unit to a designated recipient in a case where such a specific recipient is designated by a user from among a plurality of recipients stored in the multi-function peripheral. Here, the email includes a unique message ID. In a case where an error email including such message ID is received after having sent the email, the multi-function peripheral uses this message ID to specify which email recipient address the error has occurred with. The multi-function peripheral registers error information in association with the specified recipient address. Thereafter, the multi-function peripheral executes display based on the error information when that specified recipient address is designated as a recipient address for a new email by the user.
In the aforementioned technique, the multi-function peripheral needs to have a function of sending an email. For example, a configuration may be assumed in which a server that is communicable with the multi-function peripheral sends an email on behalf of the multi-function peripheral. The above technique has not given any consideration to such a configuration.
The present disclosure provides an art configured to suitably execute processes according to an alert related to an email in a configuration in which a server sends an email.
A server disclosed herein may comprise: a processor; a memory storing a first email address in association with first device identification information identifying a first device and storing computer-readable instructions therein, wherein the computer-readable instructions, when executed by the processor, cause the server to: receive first sending information from the first device, the first sending information being for sending a first email, and the first email being related to sending of first image data; in a case where the first sending information is received from the first device, send the first email with the first email address as destination stored in association with the first device identification information identifying the first device; in the case where the first sending information is received from the first device, store email identification information identifying the first email in the memory in association with the first device identification information identifying the first device; in a case where alert information including the email identification information is received after the first email has been sent, store restriction information in the memory in association with the first device identification information associated with the email identification information, the restriction information indicating restriction on sending of an email; receive second sending information from the first device, the second sending information being for sending a second email, and the second email being related to sending of second image data; and in a case where the second sending information is received from the first device in a state where the restriction information is not stored in association with the first device identification information, send the second email with the first email address as destination stored in association with the first device identification information identifying the first device, wherein in a case where the second sending information is received from the first device in a state where the restriction information is stored in association with the first device identification information, the sending of the second email is restricted.
A communication device further disclosed herein may comprise: a processor; a second memory storing computer-readable instructions therein, wherein the computer-readable instructions, when executed by the processor, cause the communication device to: in a case where a first instruction for sending a first email is accepted in the communication device, send a first email sending request to a server, the first email sending request being for requesting a sending of the first email which is related to sending of first image data; in a case where the server receives alert information including email identification information identifying the first email after the server has sent the first email in accordance with the first email sending request, receive a storing request from the server, the storing request being for requesting to store restriction information in a third memory in association with an email address indicating a destination of the first email, the restriction information indicating restriction on sending of an email: and in a case where a second instruction for sending a second email with the email address in the third memory as destination is accepted in the communication device in a state where the restriction information is not stored in the third memory, send a second email sending request to the server, the second email sending request being for requesting a sending of the second email which is related to sending of second image data, wherein in a case where the second instruction is accepted in the communication device in a state where the restriction information is stored in the third memory in association with the email address, the sending of the second email, sending request to the server is restricted.
A control method and a computer program for realizing the aforementioned server, as well as a computer-readable recording medium storing the computer program are also novel and useful. Further, a communication system provided with the aforementioned server and another device (such as a first device) is also novel and useful.
As shown in
The server 10 is a server configured to send an email in accordance with an instruction from the MFP 100. The server 10 is installed on the Internet 6 by a vendor of each MFP 100 for example. Alternatively, in a variant, the server 10 may be installed on the Internet 6 by an entity different from the vendor.
The server 10 comprises a network interface 12 and a controller 20. Each of the units 12, 20 is connected to a bus line (not given a reference sign). Hereafter, an interface will be described as “I/F”. The network I/F 12 is an interface configured to execute communication through the Internet 6, and is connected to the Internet 6. The controller 20 comprises a CPU 22 and a memory 24. The CPU 22 executes various processes in accordance with a program 26 stored in the memory 24. The memory 24 is constituted of a volatile memory, a non-volatile memory, and/or the like. The memory 24 stores an email table 30, a sending table 32, a restriction table 34, and a Cloud uniform resource locator (URL) 36 in addition to the program 26. The cloud URL 36 is a URL indicating a location of the Cloud server 600. Alternatively in a variant, each of the tables 30, etc. may be stored in an external memory communicably connected to the server 10. In the present variant, a system including the server 10 and the external memory is an example of a “server”.
The email table 30 is a table configured to manage email addresses. The email table 30 stores, for each of the plural MFPs, a device ID (abbreviation of identifier) identifying the MFP, an address for “Scan to Email” (hereafter “Scan to Email” address), an address for “Fax to Email” (hereafter “Fax to Email” address), and an address for “Fax to Cloud” (hereafter “Fax to Cloud” address) in association with each other. The “Scan to Email” address is an address indicating a destination of an email related to a “Scan to Email” function. The “Fax to Email” address is an address indicating a destination of an email related to a “Fax to Email” function. The “Fax to Cloud” address is an address indicating a destination of an email related to a “Fax to Cloud” function. Hereafter, the “Scan to Email” function, the “Fax to Email” function, and the “Fax to Cloud” function will be collectively termed an “email function”. The email function will be described below with reference to
The sending table 32 is a table configured to manage information related to entails which the server 10 has sent (hereafter, “server emails”). The sending table 32 stores, for each of the plural server entails, the device ID identifying the MFP which instructed the sending of the server email, an email address indicating a destination of the server email, an email ID identifying the server email, a URL ID identifying URLs included in a body of the server email, a timestamp indicating date and time at which the server email was sent, and causation information related to the server email in association with each other. The aforementioned URLs comprise a restriction un and a deletion URL. The restriction URL is a URL that is clicked by a user in a case where the user rejects reception of the server email. The deletion URL is a URL that is clicked by the user in a case where the user allows the reception of the server email after the user has rejected the reception of the server email.
The causation information is information indicating causation of an alert with regard to the server email. The causation information indicates one of plural causations including “Temporary Disconnection”, “Inexistent Address”, “Blocked”, and “Restriction Request”. Here, the “Temporary Disconnection” indicates a temporary error that the server email cannot be sent to its destination. The temporary error takes place, for example, when an email server that corresponds to a domain name of the email address indicating the destination of the server email is temporarily disconnected from the Internet 6. The “Inexistent Address” indicates an error that the server email cannot be sent to its destination due to an email address indicating the server email destination not existing. The “Blocked” indicates that although the server email can be sent to the destination, the server email is blocked by that destination (such as an email server or a mailer). For example, if the server email is determined as a junk email, that server email is blocked. Once the server email has been blocked, the server email can no longer be sent to that destination. The “Restriction Request” indicates that the restriction URL, which will be described below, was clicked by the user, and the reception of the server email, has been rejected.
The restriction table 34 is a table configured to manage a restriction flag. The restriction flag indicates one of values including “ON” indicating a restriction on sending an email and “OFF” indicating un-restriction of sending the email. The restriction table 34 stores, for each of plural restriction flags, the device ID, the email address, and the restriction flag in association with each other.
The MFP 100 is a peripheral device (i.e. a peripheral of the terminal device 500) configured to execute multiple functions including a print function, a scan function, and a facsimile (FAX) function. The MFP 100 comprises a network I/F 112, an operation unit 114, a display unit 116, a Public Switched Telephone Network (PSTN) I/F 118, a scan executing unit 119, and a controller 120. Each of the units 112 to 120 is connected to a bus line (reference sign omitted). The network I/F 112 is connected to the Internet 6. The operation unit 114 comprises numeric keys. The user may input various types of instructions to the MFP 100 by operating the operation unit 114. The display unit 116 is a display for displaying various types of 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 configured to execute FAX communication.
The controller 120 comprises a CPU 122 and a memory 124. The CPU 122 is configured to execute various types of processes in accordance with programs 126, 128 stored in the memory 124. The memory 124 is constituted of a volatile memory, a non-volatile memory, and/or the like. The memory 124 stores the operating system (OS) program 126 for realizing basic processes, the server program 128 for accessing the server 10, and FAX setting information 130. The FAX setting information 130 indicates one of values including “FAX to Email” indicating use of the “FAX to Email” function, “FAX to Cloud” indicating use of the “FAX to Cloud” function, and “Regular FAX” indicating using neither the “FAX to Email” nor “FAX to Cloud”. The FAX setting information 130 is inputted by the user operating the operation unit 114. The FAX setting information 130 is set to the “Regular FAX” in its default setting.
A device ID “d01” is assigned to the MFP 100. The MFP 200 comprises a similar configuration to that of the MFP 100. A device ID “d02” is assigned to the MFP 200.
With reference to
In T0, the user operates the operation unit 114 of the MFP 100 to perform a “Scan to Email” operation. The “Scan to Email” operation includes an operation of selecting the “Scan to Email” address MA1 from among the “Scan to Email” addresses MA1, MA2 and an operation of instructing to execute the scan function.
The MFP 100 creates scan data (i.e. image data) by scanning a document in T0 in response to accepting the “Scan to Email” operation. Then, the MFP 100 sends the created scan data and the “Scan to Email” address MA1 to the server 10.
When the server 10 has received the scan data and the “Scan to Email” address MA1 from the MFP 100 in T1, the server 10 sends an email with an attachment of the scan data in T2 with the “Scan to Email” address MA1 as a destination.
When the MFP 100 has received FAX data via the PSTN I/F 118 in T3, the MFP 100 sends the FAX data to the server 10 in T4. The FAX data is image data that is sent from a FAX device different from the MFP 100 to the MFP 100 via FAX communication. The FAX data is created by the FAX device scanning a document.
When the server 10 has received the FAX data from the MFP 100 in T4, the server 10 sends an email with an attachment of the FAX data in T5 with the “FAX to Email” address MA3 as a destination.
When the MFP 100 has received the FAX data via the PSTN I/F 118 in T6, the MFP 100 sends a Cloud URL request requesting the Cloud URL 36 to the server 10 in T7. Due to this, in T8, the MFP 100 receives the Cloud URL 36 from the server 10.
In T9, the MFP 100 sends the FAX data received in T6 to the Cloud server 600 indicated by the Cloud URL 36 received in T8. Due to this, the FAX data is stored in the Cloud server 600.
In T10, the MFP 100 sends a completion notification indicating that the sending of the FAX data to the Cloud server 600 has completed to the server 10.
When the server 10 has received the completion notification from the MFP 100 in T10, the server 10 sends an email in T11 including a completion message indicating that the sending of the FAX data to the Cloud server 600 has been completed, with the “Fax to Cloud” address MA3 as a destination.
With reference to
In S2, the CPU 22 monitors reception of an access request from a specific MFP (such as 100) via the network I/F 12. The access request is information that is sent from the specific MFP in a case where a program use operation for using the server program 128 is performed on the specific MFP. The access request includes a device ID of the specific MFP (such as “d01”). The CPU 22 proceeds to S4 in a case of receiving the access request from the specific MFP (YES to S2).
In S4, the CPU 22 specifies, from the email table 30, a FAX email address that is stored in association with the device ID included in the access request. Here, the “FAX email address” indicates a “FAX to Email” address and a “Fax to Cloud” address. The CPU 22 specifies the restriction flag stored in association with both the device ID included in the access request and the specified FAX email address from the restriction table 34. Then, the CPU 22 determines whether or not the specified restriction flag indicates “ON”. The CPU 22 proceeds to S6 in a case of determining that the specified restriction flag indicates “ON” (YES to S4). Contrary to this, the CPU 22 skips S6 and proceeds to S8 in case of determining that the specified restriction flag indicates “OFF” (NO to S4).
In S6, the CPU 22 sends first FAX restriction screen data for causing the specific MFP to display a first FAX restriction screen to the specific MFP via the network I/F 12. The first FAX restriction screen indicates that the sending of an email with the FAX email address as a destination has been restricted.
In S8, the CPU 22 sends menu screen data for causing the specific MFP to display a menu screen to the specific MFP via the network I/F 12. The menu screen is a screen for using the email function. The menu screen includes a “Scan to Email” button for executing a scan in accordance with the “Scan to Email” function and a setting button for inputting information for using the email function (such as the “FAX to Email” address and the FAX setting information 130).
In S10, the CPU 22 determines whether or not “Scan to Email” selection information is received from the specific MFP via the network I/F 12. The “Scan to Email” selection information is information which indicates that the “Scan to Email” button has been selected in the menu screen. The CPU 22 proceeds to S12 in a case of determining that the “Scan to Email” selection information has been received from the specific MFP (YES to S10). Meanwhile, in a case where the setting button has been selected in the menu screen and a storing request including a “FAX to Email” address has been received, for example (NO to S10), the CPU 22 proceeds to S16. In S16, for example, the CPU 22 stores the “Fax to Email” address included in the storing request in accordance with the aforementioned storing request in the email table 30. When S16 is completed, the process of
In S12, the CPU 22 sends scan screen data for causing the specific MFP to display a scan screen to the specific MFP via the network I/F 12. The scan screen data includes one or mote “Scan to Email” addresses stored in association with the device ID of the specific MFP. The scan screen includes an input box for inputting scan setting (such as data format, size, and resolution), a selection box for selecting one from among the one or more “Scan to Email” email addresses, and a Scan button for instructing to execute the scan function.
In S14, the CPU 22 receives an email sending request from the specific MFP via the network I/F 12. The email sending request is a command for requesting the sending of an email in accordance with information in the email sending request. The email sending request includes an email address that has been selected in the selection box in the scan screen, scan data that has been created in accordance with the scan setting inputted in the input box in the scan screen, and the device ID of the specific MFP. Here, the process of T1 in
In S20, the CPU 22 specifies, from the restriction table 34, the restriction flag stored in association with the information included in the email sending request, that is, with both the device ID and the email address.
In S22, the CPU 22 determines whether the specified restriction flag indicates “ON”. In a case of determining that the specified restriction flag indicates “OFF” (NO to S22), the CPU 22 executes an email sending process that is to be described below (see
With reference to
In S32, the CPU 22 creates an email which includes a header in which the email ID created in S30 is described and a predetermined body, and with the scan data in the email sending request received in S14 of
In S34, the CPU 22 determines whether an unsent notification in response to the email sent in S32 (i.e., server email) has been received. The unsent notification is information for notifying an error that the server email cannot be sent to the destination. The unsent notification includes an error code indicating a causation of the error why the server email cannot be sent to the destination. The unsent notification is received via an email server (not shown). For example, in a case where the server email cannot be sent to the destination due to the causation “Temporary Disconnection”, the unsent notification includes an error code EC1. Further, in a case where the server email cannot be sent to the destination due to the causation “Inexistent Address”, the unsent notification includes an error code EC2 different from the error code EC1. Further, the unsent notification includes the email ID included in the header of the server email. The CPU 22 proceeds to S36 in a case of determining that the unsent notification has been received (YES to S34).
In S36, the CPU 22 stores causation information indicated by an error code included in the unsent notification (such as “Temporary Disconnection”) in association with the email ID included in the unsent notification in the sending table 32.
In S38, the CPU 22 specifies, from the sending table 32, information stored in association with the email ID included in the unsent notification. Then, the CPU 22 changes the restriction flag stored in association with both the device ID and the email address from “OFF” to “ON” in the specified information in the restriction table 34. When S38 is completed, the process of
Further, in a case of determining that the unsent notification has not been received (NO to S34), the CPU 22 determines whether a blocked notification in response to the server email has been received in S40. The blocked notification indicates that the server email has been blocked by the destination of the server email. The blocked notification includes the email ID included in the header of the server email. The blocked notification is received via the email server (not shown). In a case of determining that the blocked notification has been received (YES to S40), the CPU 22 proceeds to S42.
In S42, the CPU 22 stores the causation information indicated by the blocked notification (i.e., “Blocked”) in association with the email ID included in the blocked notification in the sending table 32. When S42 is completed, the CPU 22 proceeds to S38. In S38 executed after S42, the CPU 22 uses the email ID included in the blocked notification to specify information from the sending table 32 and changes the restriction flag stored in association with the specified information from “OFF” to “ON”.
Further, in a case of determining that the blocked notification has not been received (NO to S40), the CPU 22 determines whether a restriction request in response to the server email has been received in S44. The restriction request is information that is received without an intervention of an email server from a terminal device (such as 500) at which the server email is being displayed in a case where the restriction URL in the body of the server email is clicked. The restriction request is a request for changing the restriction flag stored in association with the destination of the server email from “OFF” to “ON”. The restriction request includes the URL ID included in the restriction URL. In a case of determining that the restriction, request has been received (YES to S44), the CPU 22 proceeds to S46.
In S46, the CPU 22 stores the causation information indicated by the restriction request (i.e. “Restriction Request”) in association with the URL ID included in the restriction request in the sending table 32. When S46 is completed, the CPU 22 proceeds to S38. In S38 executed after S46, the CPU 22 uses the URL ID included in the restriction request to specify information from the sending table 32 and changes the restriction flag stored in association with the specified information from “OFF” to “ON”.
Further, in a case of determining that the restriction request has not been received (NO to S44), the CPU 22 skips S38 and terminates the process of
With reference to
In S53, the CPU 22 determines whether the restriction process has been executed in the first server process of
In S54A, the CPU 22 sends Scan restriction screen data for causing the specific MFP to display a Scan restriction screen to the specific MFP via the network I/F 12. The Scan restriction screen indicates that the sending of an email with a “Scan to Email” address as a destination has been restricted. The Scan restriction screen includes a causation message indicating a causation why the sending of the email is restricted, a deletion button for instructing deletion of the email address, and a NO button. The deletion button is associated with the information included in the email sending request received in S14 of
The causation message is a message indicating a causation indicated by the causation information specified in S50. That is, as shown in
The CPU 22 proceeds to S54B in a case of determining that the restriction process has been executed in the second server process to be described later (i.e. process for “FAX to Email” function and “FAX to Cloud” function) (NO for S53). In S54B, the CPU 22 sends second FAX restriction screen data for causing the specific MFP to display a second FAX restriction screen to the specific MFP via the network I/F 12. The second FAX restriction screen indicates that the sending of an email with a FAX email address as a destination has been restricted. The second FAX restriction screen is different from the first FAX restriction screen of S6 in
In S56, the CPU 22 determines whether deletion selection information is received from the specific MFP via the network I/F 12. The deletion selection information is information indicating that the deletion button has been selected in the Scan restriction screen or the second FAX restriction screen. The deletion selection information includes information associated with the deletion button (i.e. device ID and email address). The CPU 22 proceeds to S58 in a case of determining that the deletion selection information has been received from the specific MFP (YES to S56), while the CPU 22 skips the process of S58 and terminates the process of
In S58, the CPU 22 deletes an email address that matches the email address in the deletion selection information among the email addresses stored in the email table 30 in association with the device ID in the deletion selection information from the email table 30. Further, the CPU 22 deletes the same email address stored in association with the device ID in the deletion selection information from the restriction table 34. When the process of S58 is completed, the process of
With reference to
In S60, the CPU 22 monitors reception of a “FAX to Email” request from the specific MFP via the network I/F 12. The “FAX to Email” request is information which is sent from the specific MFP in a case where the specific MFP receives FAX data. The “FAX to Email” request includes the FAX data and the device ID of the specific MFP. T4 of
In S62, the CPU 22 specifies the “FAX to Email” address stored in association with the device ID included in the “FAX to Email” request from the email table 30. The CPU 22 proceeds to S80 when the process of S62 is completed.
Further, in addition to the monitoring of S60, the CPU 22 monitors reception of a Cloud URL request from the specific MFP via the network I/F 12 in S64. In a case of receiving the Cloud URL request from the specific MFP (YES to S64), the CPU 22 sends the Cloud URL 36 in the memory 24 to the specific MFP via the network I/F 12 in S66. Subsequently, in S68, the CPU 22 receives a completion notification indicating that the sending of the FAX data to the Cloud server 600 has been completed from the specific MFP via the network I/F 12. The completion notification includes the device ID of the specific MFP. Here, the processes of T7, T8, and T10 of
In S70, the CPU 22 specifies the “FAX to Cloud” address stored in association with the device ID included in the completion notification from the email table 30. When the process of S70 is completed, the CPU 22 proceeds to S80.
In S80, the CPU 22 specifies a restriction flag from the restriction table 34. Specifically, in S80 executed after S62, the CPU 22 specifies the restriction flag stored in association with both the device ID included in the “FAX to Email” request and the “FAX to Email” address specified in S62 from the restriction table 34. On the other hand, in S80 executed after S70, the CPU 22 specifies the restriction flag stored in association with both the device ID included in the completion notification and the “FAX to Cloud” address specified in S70 from the restriction table 34.
S82 to S86 are similar to S22 to S26 of
With reference to
In S100, the CPU 122 monitors the program use operation being performed on the operation unit 114. The CPU 122 proceeds to S102 in accordance with the server program 128 in a case where the program use operation is performed (YES to S100).
In S102, the CPU 122 sends the access request to the server 10 via the network I/F 112 (see S2 of
In S104, the CPU 122 determines whether the first FAX restriction screen data is received from the server 10 via the network I/F 112 (see S6 of
In S106, the CPU 122 displays a menu screen in accordance with the menu screen data on the displaying unit 116.
In S108, the CPU 122 determines whether a “Scan to Email” button is selected in the menu screen. In a case of determining that the “Scan to Email” button has been selected (YES to S108), the CPU 122 proceeds to S110, whereas in a case of determining that a setting button in the menu screen has ben selected (NO to S108), the CPU 122 proceeds to S116. In S116, the CPU 122 displays an inputting screen for inputting information for using the email function (such as “FAX to Email” address), for example. When the process of S116 is completed, the process of
In S110, the CPU 122 sends the “Scan to Email” selection information to the server 10 via the network I/F 112 (see S10 of
In S112, the CPU 122 receives the scan screen data from the server 10 via the network I/F 112 (see S12 of
In S114, the CPU 122 displays the scan screen in accordance with the scan screen data on the displaying unit 116. In a case where the inputting of the scan setting, the selection of email address, and the selection of the Scan button have been performed in the scan screen, the CPU 122 causes the scan executing unit 119 to execute a scan in accordance with the inputted scan setting. Then, the CPU 122 sends the email sending request including the selected email address, the scan data created by the scan executing unit 119 and the device ID “d01” of the MFP 100 to the server 10 (see S14 of
In S120, the CPU 122 determines whether the Scan restriction screen data is received from the server 10 via the network I/F 122 (see S54A of
In S122, the CPU 122 displays the Scan restriction screen in accordance with the Scan restriction screen data on the displaying unit 116.
In S124, the CPU 122 determines whether the deletion button in the Scan restriction screen has been selected. In a case of determining that the deletion button has been selected (YES to S124), in S126 the CPU 122 sends the deletion selection information to the server 10 via the network I/F 112 (see S56 of
With reference to
In S150, the CPU 122 monitors reception of the FAX data via the PSTN I/F 118. The processes of T3 and T6 of
In S152, the CPU 122 determines whether the FAX setting information 130 in the memory 124 indicates the “FAX to Email”. In a case of determining that the FAX setting information 130 indicates the “FAX to Email” (YES to S152), the CPU 122 proceeds to S154.
In S154, the CPU 122 sends the “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 of
Contrary to this, in a case of determining that the FAX setting information 130 does not indicate the “FAX to Email” (NO to S152), the CPU 122 determines whether the FAX setting information 130 indicates the “FAX to Cloud” in S156. In a case of determining that the FAX setting information 130 indicates the “FAX to Cloud” (YES to S156), the CPU 122 proceeds to S158.
In S158, the CPU 122 sends the Cloud URL request to the server 10 via the network I/F 112 (see S66 of
In S162, the CPU 122 sends (i.e. uploads) the FAX data to the Cloud server 600 indicated by the Cloud URL 36. Here, the process of T9 of
In S164, the CPU 122 sends a completion notification including the device ID “d01” the server 10 via the network I/F 112 (see S68 of
On the other hand, in a case of determining that the FAX setting information 130 indicates the “Regular FAX” (NO to S156), the CPU 122 proceeds to S168. In S168, the CPU 122 causes a print executing unit (not shown) of the MFP 100 to print an image corresponding to the FAX data. When the process of S168 is completed, the process of
In S170, the CPU 122 determines whether the second FAX restriction screen data has been received from the server 10 via the network I/F 112 (see S54B of
In S172, the CPU 122 displays the second FAX restriction screen n the displaying unit 116 in accordance with the second FAX restriction screen data.
In S174, the CPU 122 determines whether the deletion button in the second FAX restriction screen has been selected. In a case of determining that the deletion button has been selected (YES to S174), the CPU 122 proceeds to S176. S176 is similar to S126 of
Further, in a case of determining that none of the buttons in the second FAX restriction screen has been selected (NO to S174), the CPU 122 determines in S178 whether a predetermined time (e.g., thirty seconds) has elapsed since the display of the second FAX restriction screen. In a case of determining that the predetermined time has elapsed (YES to S178), the CPU 112 proceeds to S180. That is, the second FAX restriction screen is automatically deleted from the displaying unit 116. On the other hand, in a case of determining that the predetermined time has not elapsed (NO to S178), the CPU 122 returns to S174.
With reference to
In T20, the MFP 100 accepts the program use operation by the user (YES to S100 in
When the access request is received from the MFP 100 in T22 (YES to S2 of
When the menu screen data is received from the server 10 in T26, the MFP 100 displays the menu screen in T28 (S106 of
When the “Scan to Email” selection information is received from the MFP 100 in T32 (YES to S10 of
When the scan screen data is received from the server 10 in T34 (S112 of
In T38, the MFP 100 accepts an input of a scan setting, a selection of the “Scan to Email” address MA1, and a selection of the Scan button in the scan screen. In T40, the MFP 100 creates scan data SD1 in accordance with the inputted scan setting.
In 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 (S114).
When the email sending request is received from the MFP 100 in T42 (S14 of
Subsequently, in T50 of
In T52, the server 10 sends an email EM1 with the “Scan to Email” address MA1 as a destination (S32). The email EM1 includes a header in which the email ID “m01” is described and a body which includes a restriction URL including the URL ID “u01” and a deletion URL including the URL ID “u01”. The scan data SD1 has been attached to the email EM1.
Further, the server 10 stores the device ID “d01” the “Scan to Email” address MA1, the email ID “m01”, the URL ID “u01”, and the timestamp of the email EM1 “2019.5.20.12:00” in association with each other in the sending table 32.
Subsequently, specific cases A1 to A3 regarding the email EM1 will be described. Case A1 indicates a case in which the causation of the alert is “Temporary Disconnection” or “Inexistent Address”. In T54, the server 10 determines that an unsent notification in response to the email EM1 has been received (YES to S34 of
In T56, the server 10 stores the causation information “Temporary Disconnection” (or “Inexistent Address”) indicated by the error code EC1 (or EC2) included in the unsent notification in association with the email ID “m01” in the sending table 32 (S36).
In T58, the server 10 changes the restriction flag stored in association with both the device ID “d01” associated with the email ID “m01” and the “Scan to Email” address MA1 being the destination of the email EM1 from “OFF” to “ON” (S38).
Case A2 indicates a case in which the causation of the alert is “Blocked”. In T74, the server 10 receives the blocked notification in response to the email EM1 due to, for example, a process for blocking being executed by a mailer which received the email EM1 being executed (YES to S40 of
In T76, the server 10 stores the causation information “Blocked” in association with the email ID “m01” in the sending table 32 (S42). T78 is similar to T58.
Case A3 is a case in which the causation of the alert is “Restriction Request”. In T80, in the terminal device 500 displaying the email EM1, the user clicks the restriction URL in the email EM1. Due to this, the server 10 receives the restriction request including the URL ID “u01” from the terminal device 500 in T84 (YES to S44).
In T86, the server 10 stores the causation information “Restriction Request” in association with the email ID “m01” in the sending table 32 (S46). T88 is similar to T58. Such a configuration enables the user to restrict sending of an email simply by clicking the restriction URL in the email EM1. Convenience for the user is improved.
Further, in Case A3, the user further clicks the deletion URL in the email EM1. Due to this, in T94, the server 10 receives the deletion request from the terminal device 500 without an intervention of any email server. The deletion request is a request to change the restriction flag stored in association with the destination of the email EM1 from “ON” to “OFF”. The deletion request includes the URL ID “u01”.
In T96, the server 10 specifies the information stored in association with the URL ID “u01” included in the deletion request, that is, the device ID “d01” and the “Scan to Email” address MA1. Then, the server 10 deletes the causation 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”. Such a configuration enables the user to delete the restriction flag “ON” by clicking the deletion URL in the email EM1 even when the user has erroneously clicked the restriction URL. An inadvertent restriction on the sending of an email can be suppressed.
Subsequently, with reference to
When the email sending request is received from the MFP 100 in T142 (S14 of
In T146, the server 10 determines that the causation information stored in association with both the device ID “d01” and the “Scan to Email” address MA1 is “Blocked” (NO to S50 of
When the Scan restriction screen data is received from the server 10 in T148 (YES to S120 in
Further, the Scan restriction screen is not displayed in a case where the “Scan to Email” address MA2 is selected in the scan screen, because the restriction flag stored in association with the “Scan to Email” address MA2 indicates “OFF” (NO to S22). That is, in the case where the “Scan to Email” address MA1 is selected, the Scan restriction screen is displayed, but in the case where the “Scan to Email” address MA2 is selected, the Scan restriction screen is not displayed. According to the configuration of the present case, the Scan restriction screen can be appropriately displayed depending on which “Scan to Email” address has been selected by the user.
In T152, the MFP 100 accepts a selection of the deletion button in the Scan restriction screen (YES to S124). In T154, the MFP 100 sends deletion selection information including information associated with the deletion button (i.e. the device ID “d01” and the “Scan to Email” address MA1) to the server 10 (S126).
When the deletion selection information is received from the MFP 100 in T154 (YES to S56 of
Further, in the present case, in the restriction table 34, the “Scan to Email address” MA1 has been stored in association with the device ID “d02” of the MFP 200, and the restriction flag “OFF” has been stored in association with both the device ID “d02” and the “Scan to Email” address MA1.
T220 is similar to T20 of
In 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 of
When the email sending request is received from the MFP 200 in T242 (S14 of
For example, a comparative example may be assumed in which in T78 of Case A2 in
With reference to
The MFP 100 receives FAX data FD1 via the PSTN I/F 118 in T310 (S150 of
In T312, the MFP 100 determines that the FAX setting information 130 indicates “FAX to Email” (YES to S152). In 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 “FAX to Email” request is received from the MFP 100 in T314 (YES to S60 of
In T316, the server 10 determines that the restriction flag stored in association with both the device ID “d01” and the “FAX to Email” address MA3 indicates “OFF” in the restriction table 34 (NO to S82).
T350 is similar to T50 of
Further, the server 10 stores the device ID “d01”, the “FAX to Email” address MA3, the email ID “m03”, the URL ID “u03”, and the timestamp of the email EM3 “2019.5.20.12:00” in association with each other in the sending table 32.
In the present case, similar to Case A2 of
T376 is similar to T76 of
Subsequently, the MFP 100 receives FAX data FD2 via the PSTN I/F 118 in T380 (S150 of
In T386, the server 10 determines that the restriction flag stored in association with both the device ID “d01” and the “FAX to Email” address MA3 in the restriction table 34 indicates “ON” (YES to S82 of
In T384, the server 10 sends second FAX restriction screen data for causing the MFP 100 to display second FAX restriction screen including the causation message indicating the causation “Blocked” to the MFP 100 (S54B).
T386 is similar to T150 of
Subsequently, the MFP 100 accepts the program use operation from the user in T410 (YES to S100 of
When the access request is received from the MFP 100 in T412 (YES to S2 of
In T416, the server 10 sends the first FAX restriction screen data to the MFP 100 (S6 of
With reference to
In S200, the CPU 22 determines whether an email ID not related to any causation information (hereafter, “target email ID”) exists in the sending table 32. In a case of determining that the target email ID exists (YES to S200), the CPU 22 proceeds to S202. On the other hand, in a case of determining that the target email ID does not exist in the sending table 32 (NO to S200), the CPU 22 skips processes from S202, and terminates the process of
In S202, the CPU 22 determines whether a predetermined valid time (e.g. one day) has elapsed since a date and time indicated by a time stamp stored in association with the target email ID. In a case of determining that the valid time has elapsed since the date and time (YES to S202), the CPU 22 proceeds to S204. On the other hand, in a case of determining that the valid time has not elapsed since the date and time (NO to S202), the CPU 22 skips S204, and terminates the process of
In S204, the CPU 22 deletes the target email ID and the URL ID stored in association with the target email ID from the sending table 32. Here, in a case where there is a plurality of target email IDs, the process of S202 and S204 is executed for each of the target email IDs. When S204 is completed, the process of
The existence of the target email ID means that the unsent notification was not received during a period from when the server email was sent to when the valid time has elapsed. That is, the target email ID indicates the email ID of the server email for which an alert such as an error has not occurred. According to the aforementioned configuration, the unnecessary email ID can be deleted.
According to the configuration of the present embodiment, in the case of receiving the email sending request from the MFP 100 (T42 of
Further, in the case of receiving the “FAX to Email” request from the MFP 100 (T314 of
The server 10, the memory 24, the MFP 100, the MFP 200, the terminal device 500, and the memory 124 are examples of a “server” “memory (and first memory)”, “first device”, “second device”, “terminal device”, and “second memory”, respectively. The device ID “d01” and the device ID “d02” are examples of “first device identification information” and “second device identification information”. The email ID or the URL ID is an example of “email identification information”. One of the unsent notification, the blocked notification, and the restriction request is an example of “alert information”. The restriction flag “ON” is an example of the “restriction information”. The operation of selecting the Scan button in the menu screen and the operation of selecting an email address in the menu screen are examples of “scan executing operation” and “selection operation”, respectively. The program use operation and the server program 128 are examples of a “predetermined operation” and a “predetermined program”. 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 sending request of T42 of
In the “FAX to Email” function, the “FAX to Email” address MA3 is an example of the “first email address”. The FAX data FD1, FD2 are examples of the “first image data” and the “second image data”, respectively. The “FAX to Email” request of T314 of
In the “FAX to Cloud” function, the “FAX to Cloud” address MA3 is an example of the “first email address”. The FAX data is an example of the “first image data and the second image data”. The completion notification of T10 of
S32 of
In the “Scan to Email” function, S14 of
In the “FAX to Email” function, S60 of
In the “FAX to Cloud” function, S68 of
In the present embodiment, the email table 30 and the restriction table 34 are stored in the memory 124 of the MFP 100. The email table 30 and the restriction table 34 do not include device IDs. Further, processes using the email table 30 and the restriction table 34 are executed by the CPU 122 of the MFP 100.
With reference to
T520 is similar to T20 of
In the present case, the MFP 100 determines the specified restriction flag indicates “OFF”, and sends an access request to the server 10 in T522. Then, the MFP 100 receives menu screen data from the server 10 in T526, and displays a menu screen in T528 (see S102, S106 of
T530 to T538 are similar to T30 to T38 of
In T539, the MFP 100 specifies the restriction flag stored in association with the “Scan to Email” address MA1 selected in T538 from the restriction table 34 in the memory 124. In the present case, the MFP 100 determines the specified restriction flag as “OFF”, and executes processes from T540. If the specified restriction flag is determined as “ON”, that case will be described in processes after T644 of
T540, T542, and T550, T552, T574, T576 of
Subsequently, the user uses the “Scan to Email” function again in order to send an email with the “Scan to Email” address MA1 as a destination. Due to this, processes similar to T520, T521 of
When the access request has been received from the MFP 100 in T582, the server 10 determines whether or not the causation information is stored in association with the device ID “d01” in the access request in the sending table 32 in T582. Since the causation information “Blocked” is stored in association with the device ID “d01” in the present case, the server 10 sends a restriction flag ON request for changing the restriction flag in the MFP 100 from “OFF” to “ON” to the MFP 100 in T584. The restriction flag ON request includes the email address MA1 stored in association with the device ID “d01” in the access request. Here, if any causation information is not stored in association with the device ID “d01” in the access request, the server 10 skips processes from T584, and sends menu screen data to the MFP 100 (see T526 of
When the restriction flag ON request is received from the server 10 in T584, the MFP 100 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” in T586.
Subsequently, processes similar to T522 to T538 of
In T644, the MFP 100 specifies 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 the present case, the MFP 100 determines the specified restriction flag as “ON”. If the specified restriction flag is determined as “OFF”, the process is similar to T539 of
In T646, the MFP 100 sends the email address MA1 to the server 10, and inquires the server 10 of the causation information. Then, the MFP 100 receives the causation information “Blocked” stored in the sending table 32 in association with the email address MA1 from the server 10 in T648.
In T650, the MFP 100 displays a Scan restriction screen including a causation message indicating the causation “Blocked” on the displaying unit 116 (see S122 of
In T652, the MFP 100 accepts a selection of the deletion button in the Scan restriction screen. In 656, the MFP 100 deletes the email address MA1 from the email table 30 in the memory 124.
According to the configuration of the present embodiment, the MFP 100 sends the email sending request including the email address MA1 in the case where the selection of the email address MA1 in the scan screen is accepted (T542 of
The case where the sending of an email is restricted if the causation of the alert is “Blocked” has been described in relation to
Further, the case where the sending of an email is restricted in the “Scan to Email” function has been described in relation to
The MFP 100, the memory 124 are examples of a “communication device”, a “second memory” and “third memory”, respectively. T542, T584 of
The “first device (and communication device)” are not limited to the MFP 100, but may be a scanner configured to execute only the scan function and a FAX device configured to execute only the FAX function.
In the first embodiment, the MFP 100 receives the FAX data via the PSTN I/F 118. Instead of this, the MFP 100 may receive the FAX data via the network I/F 112 from a terminal device configured to execute an Internet FAX function. In this case, the FAX data may be image data stored in the terminal device. In the present variant, the FAX data received via the network I/F 112 is an example of the “first image data”.
URL ID(s) may not be stored in the sending table 32. In this case, the restriction URL and the deletion URL may include an email ID. In the present variant, the email ID is an example of the “email identification information.”
The Scan restriction screen mays include a sending button for instructing to send an email. In a case where the sending button in the Scan restriction screen is selected, the server 10 may send an email irrespective to the restriction flag indicating “ON”. In general terms, “the sending of the second email is restricted” includes sending the second email on a condition that the sending button in the Scan restriction screen is selected.
In the first embodiment, the restriction process is executed (S86 of
In the first embodiment, the server 10 sends the Scan restriction screen data to the MFP 100 (S54A of
The “predetermined operation” is not limited to the program use operation, but may be an operation of selecting the setting button in the menu screen.
In the first embodiment, in the case of receiving the access request, the server 10 determines whether the restriction flag stored in association with the FAX email address indicates “ON” (S4 of
The processes of S6, S26 of
The second FAX restriction screen may not be automatically deleted. In general terms, a notifying screen may be deleted from the displaying unit of the first device in response to a button in the notifying screen being operated. Further, the second FAX restriction screen may be same as the first FAX restriction screen. Moreover, the first FAX restriction screen may be same as the Scan restriction screen.
The sending table 32 may not store the causation information. In the present variant, the “causation information” may be omitted.
The process of S50 of
The server email may not include the restriction URL and the deletion URL. In the present variant, the “first URL” and the “second URL” may be omitted.
The deletion process of
In the respective embodiments, each process of
In the second embodiment, the email table 30 and the restriction table 34 are stored in the memory 124 of the MFP 100. Instead of this, the restriction table 34 may be stored in the memory 124 of the MFP 100, and the email table 30 may be stored in the memory 24 of the server 10. In this case, the email sending request of
In the second embodiment, the restriction table 34 and the like are stored in the memory 124 of the MFP 100. Instead of this, the restriction table 34 and the like may be stored in a memory arranged separately from the MFP 100. In the present variant, the memory arranged separately from the MFP 100 is an example of the “third memory”.
| Number | Date | Country | Kind |
|---|---|---|---|
| JP2019-120345 | Jun 2019 | JP | national |
| 2020-077711 | Apr 2020 | JP | national |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6823367 | Wakasugi et al. | Nov 2004 | B1 |
| 8792118 | Vendrow | Jul 2014 | B2 |
| 20020194553 | Okamoto et al. | Dec 2002 | A1 |
| 20160227051 | Hanada | Aug 2016 | A1 |
| 20190281189 | Watts | Sep 2019 | A1 |
| Number | Date | Country |
|---|---|---|
| H10-308766 | Nov 1998 | JP |
| 2001-265675 | Sep 2001 | JP |
| 2002-297506 | Oct 2002 | JP |
| 2003-281060 | Oct 2003 | JP |
| 2009-100200 | May 2009 | JP |
| Number | Date | Country | |
|---|---|---|---|
| 20200412886 A1 | Dec 2020 | US |
