Server and computer program for the server

Abstract

To provide a server which, upon reception of an email with a plurality of addresses designated, allows proper switching regarding whether or not to cause a printer to print.SOLUTION: A server according to the present invention receives, from a first external apparatus, a first email having a first print address and a first general address as destination addresses, and transmits a first print request to a first printer. The server also receives a second email having the first print address and a second general address as destination addresses from a second external apparatus and transmits a second print request to the first printer when the server determines that the second email is not one generated by using the first email. If the server determines that the second email is one generated by using the first email, the server does not transmit the second print request to the first printer.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] This specification discloses a technique related to a server that receives email from an external device and sends a print request to a printer. [Background technology]

[0002] Patent Document 1 discloses a network system including an image forming device and a terminal device. When the image forming device receives an email, it extracts the address set as the destination of the email. If one address is extracted, the image forming device executes a print process based on the email, but if multiple addresses are extracted, the image forming device does not execute a print process based on the email. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2014-23019 Summary of the Invention [Problem to be solved by the invention]

[0004] In the above technique, even if a user desires to execute a print process based on an email containing multiple addresses as destination addresses, the print process is not executed. This specification provides a technology that allows a server to appropriately switch whether or not to cause a printer to execute printing when the server receives an email containing multiple addresses as destination addresses. [Means for solving the problem]

[0005] The server disclosed in this specification includes a memory that stores, for each of one or more email addresses, an email address associated with printer identification information that identifies a printer; a first receiving unit that receives a first email including a first image file from a first external device, the first email including, as destination addresses, a first print address that is an email address stored in the memory and a first general address that is an email address not stored in the memory; a first print request sending unit that, when the first email is received from the first external device, sends a first print request to a first printer, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, the first printer being identified by the first printer identification information stored in the memory in association with the first print address included in the first email; The electronic mail system includes: a second receiving unit that receives a second email including a second image file from a second external device after receiving the first email, the second email including the first print address and a second general address that is an email address not stored in the memory as destination addresses; a determining unit that determines whether the second email is an email generated using the first email when the second email is received from the second external device; and a second print request sending unit that sends a second print request to the first printer when it is determined that the second email is not an email generated using the first email, the second print request being a signal requesting printing of a second image corresponding to the second image file included in the second email; and the second print request sending unit may not be sent to the first printer when it is determined that the second email is an email generated using the first email.

[0006] According to the above configuration, when the server receives a first email from a first external device, the first email including a first print address and a first general address as destination addresses, the server sends a first print request to the first printer. Then, after receiving the first email from the first external device, the server receives a second email from a second external device, the second email including the first print address and a second general address as destination addresses. When the server determines that the second email was not generated using the first email, the server sends the second print request to the first printer. On the other hand, when the server determines that the second email was generated using the first email, the server does not send the second print request to the first printer. In this way, when the server receives a second email including multiple addresses as destination addresses, the server can appropriately switch whether to cause the first printer to perform printing depending on whether the second email was generated using the first email.

[0007] A control method for realizing the above-mentioned server, a computer program, and a computer-readable recording medium storing the computer program are also novel and useful. Also novel and useful is a communication system including the above-mentioned server and another device (e.g., a first printer, etc.). [Brief explanation of the drawings]

[0008] [Figure 1] 1 shows the configuration of a communication system. [Figure 2] A sequence diagram of the setup process is shown below. [Figure 3] 10 shows a flowchart of a server process. [Figure 4] 1 shows a flowchart of a printing process. [Figure 5] 10 shows a sequence diagram of Case A in which an email containing one print address as the destination address is sent. [Figure 6] The sequence of Case B in which the email printing function is executed after Case A is shown. [Figure 7] The sequences of cases C and D in which the mail printing function is not executed after case A are shown. [Figure 8] 10 shows a sequence diagram of Case E in which an email containing two print addresses as destination addresses is sent. [Figure 9] A sequence diagram of Case F in which an email containing an incorrect email address as the destination address is sent is shown. [Figure 10] 10 shows a sequence diagram of Case G in which the email printing function is not executed. DETAILED DESCRIPTION OF THE INVENTION

[0009] (First Example) (Configuration of communication system 2: Figure 1) 1, communication system 2 includes a plurality of printers 10A and 10B, a plurality of PCs 100A to 100C, and a server 200. Printers 10A and 10B are connected to a LAN (abbreviation of Local Area Network) 4. LAN 4 is connected to the Internet 6. PCs 100A to 100C and server 200 are connected to the Internet 6. Printers 10A and 10B, PCs 100A to 100C, and server 200 are capable of communicating with each other via the Internet 6.

[0010] (Configuration of printers 10A and 10B) The printer 10A is a peripheral device capable of executing a printing function (i.e., a peripheral device such as a PC 100A). The printer 10A may be a multi-function device capable of executing a scanning function, a fax function, etc. in addition to the printing function. The printer 10A is further configured to be capable of executing an email printing function. The email printing function is a function that executes printing of an image corresponding to an image file included in an email. In a modified example, the email printing function may be a function that executes printing of an image corresponding to an image file inserted in the body of an email. The printer 10A includes an operation unit 12, a display unit 14, a print execution unit 16, a communication interface (hereinafter, the interface will be referred to as "I / F") 20, and a control unit 30. The printer 10A is assigned a printer ID "pr1" that is information that identifies the printer 10A.

[0011] The operation unit 12 has a plurality of keys. A user can input various instructions to the printer 10A by operating the operation unit 12. The display unit 14 is a display for displaying various information. The display unit 14 also functions as a so-called touch panel (i.e., an operation unit). The print execution unit 16 is a printing mechanism such as an inkjet type or a laser type. The communication I / F 20 is connected to the LAN 4. The communication I / F 20 may be a wireless I / F or a wired I / F.

[0012] The control unit 30 includes a CPU 32 and a memory 34. The CPU 32 executes various processes in accordance with a program 36 stored in the memory 34. The memory 34 is composed of a volatile memory, a non-volatile memory, etc. The printer 10B is similar to the printer 10A except that the printer 10B is assigned the printer ID "pr2."

[0013] (PC100A~100C configuration) PCs 100A to 100C are PCs used by users who can use printer 10A. PC 100A is a PC used by a user who uses email address "u1@user.com". PC 100B is a PC used by a user who uses email address "u2@user.com". PC 100C is a PC used by a user who uses email address "u3@user.com". PCs 100A, 100B, and 100C are set to receive emails that include email addresses "u1@user.com", "u2@user.com", and "u3@user.com" as destination addresses, respectively.

[0014] (Configuration of Server 200) The server 200 is installed on the Internet 6 by the vendor of the printers 10A and 10B. In a modified example, the server 200 may be installed on the Internet 6 by a business entity other than the vendor. The server 200 executes communication to cause the printers 10A and 10B to execute the email printing function. The server 200 is configured to receive emails that include an email address containing the domain "print.com" of the server 200 as the destination address.

[0015] The server 200 includes a communication I / F 220 and a control unit 230. The communication I / F 220 is connected to the Internet 6. The control unit 230 includes a CPU 232 and a memory 234. The CPU 232 executes various processes in accordance with a program 236 stored in the memory 234. In addition to the program 236, the memory 234 also stores a notification list 238 and an address table 240.

[0016] Email addresses corresponding to users who are permitted to use the email printing function are stored in the notification list 238. The email addresses in the notification list 238 are registered by users who use the printers 10A and 10B and administrators of the printers 10A and 10B. In a modified example, the email addresses in the notification list 238 may be registered by an administrator of the server 200. Hereinafter, the email addresses in the notification list 238 may be referred to as "notification addresses."

[0017] The address table 240 stores a printer ID, an access token, a print address, and a priority order in association with each other. The access token is authentication information for establishing an XMPP (extensible Messaging and Presence Protocol) session with the corresponding printer. The print address is an email address for identifying the printer that should execute the email printing function. The print address is generated by the server 200. The priority order is information used to determine which printer should execute the email printing function when two or more printers are specified to execute the email printing function. In this embodiment, the priority order is set by the user of the printers 10A and 10B or by the administrator of the printers 10A and 10B. In a modified example, the administrator of the server 200 may set the priority order in the notification list 238. In another modified example, the priority order may be set in descending order of the number of times the printer has been specified as the printer that executes the email printing function. In another modified example, the server 200 is configured to periodically receive information indicating the status of each printer (such as "waiting," "error," or "printing"), and the priority order may be set according to the status of each printer. For example, the highest priority is set for a printer that indicates "standby."

[0018] (Setup process: Figure 2) 2, a setup process will be described in which information used for communication to execute the email printing function is registered in the server 200, and an XMPP session is established between the printers 10A and 10B and the server 200. Note that, in the following, for ease of understanding, the processes executed by each CPU of each device (e.g., CPU 232 of the server 200) will be described as being mainly each device (e.g., server 200) rather than each CPU. Also, in the following, communication is executed between the printers 10A and 10B and the server 200 via the LAN 4 and the Internet 6. Also, communication is executed between the PCs 100A to 100C and the server 200 via the Internet 6. In the following, unless otherwise specified, the terms "via the LAN 4" and "via the Internet 6" will be omitted.

[0019] When printer 10A receives an operation from the administrator of printer 10A to change the email printing setting of printer 10A from "disabled" to "enabled" at T10, printer 10A changes the email printing setting from "disabled" to "enabled." The email printing setting indicates whether or not execution of the email printing function is permitted. "Disabled" indicates that execution of the email printing function is prohibited, and "enabled" indicates that execution of the email printing function is permitted. The email printing setting indicates "disabled" by default. Next, printer 10A sends a registration request to server 200 at T12, requesting registration of information used for communication to execute the email printing function. The registration request includes the printer ID "pr1."

[0020] When the server 200 receives a registration request from the printer 10A in T12, it generates a print address "p1@print.com" in T14. The print address "p1@print.com" includes a local part "p1" and the domain name of the server 200, "print.com." Next, in T16, the server 200 associates the printer ID "pr1" with the print address "p1@print.com" and registers them in the address table 240. Next, in T20, the server 200 generates a PIN code C. The server 200 associates the printer ID "pr1" with the PIN code C and temporarily stores them in the memory 234. Next, in T22, the server 200 sends the PIN code C to the printer 10A.

[0021] When the printer 10A receives the PIN code C from the server 200 in T22, the printer 10A transmits an establishment request to the server 200 in T24 to request the establishment of an XMPP session. The establishment request includes the printer ID “pr1” and the PIN code C.

[0022] When the server 200 receives the establishment request from the printer 10A in T24, it authenticates the PIN code C in the establishment request. The server 200 determines that the authentication was successful because the printer ID "pr1" and PIN code C in the establishment request match the printer ID "pr1" and PIN code C in the memory 234 of the server 200. Next, the server 200 generates an access token AT1 in T30, and registers the access token AT1 in the address table 240 in association with the printer ID "pr1" in T32. Next, the server 200 sends the access token AT1 to the printer 10A in T34.

[0023] When printer 10A receives access token AT1 from server 200 in T34, it establishes an XMPP session with server 200 in T40 using access token AT1. By using the XMPP session, server 200 can send a request to the printer across a firewall (e.g., a firewall formed by a router) of LAN4 to which the printer belongs, even without receiving the request from the printer. Note that the mechanism for sending a request from server 200 to the printer may not be an XMPP session, but may be another method. For example, a session based on HTTPS (Hypertext Transfer Protocol Secure) may be established between the printer and server 200. Next, printer 10A sends a print address request including printer ID "pr1" to server 200 in T50. The print address request is a signal requesting the transmission of a print address corresponding to the printer ID in the print address request.

[0024] When the server 200 receives a print request from the printer 10A in T50, it identifies the print address "p1@print.com" associated with the printer ID "pr1" in the print request in the address table 240, and generates print data including the print address "p1@print.com" as a character string in T52. Next, the server 200 sends the print data including the print address "p1@print.com" as a character string to the printer 10A in T54.

[0025] When printer 10A receives print data from server 200 at T56, it prints an image corresponding to the print data. As a result, the print address "p1@print.com" is printed on the print paper. The administrator of printer 10A then notifies the print address "p1@print.com" to users who are permitted to use printer 10A to execute the email printing function. This enables execution of the email printing function using printer 10A. In the following, when communication is executed between printer 10A and server 200, access token AT1 is used, but description of "access token AT1" will be omitted.

[0026] Furthermore, when processes similar to those in T10 to T56 are executed between printer 10B and server 200, it becomes possible to execute the email printing function using printer 10B. Note that in T12, which is executed between printer 10B and server 200, a registration request including the printer ID "pr2" is communicated. In addition, in T14, server 200 generates a print address "p2@print.com" corresponding to printer 10B, and in T16, associates the printer ID "pr2" with the print address "p2@print.com" and registers them in the address table 240. In addition, in T30, server 200 generates an access token AT2, and in T32, associates the access token AT2 with the printer ID "pr2" and registers it in the address table 240. In addition, in T52, server 200 generates print data including the print address "p2@print.com" as a character string, and in T54, sends the print data including the print address "p2@print.com" as a character string to printer 10B. At T56, printer 10B prints an image corresponding to print data that includes the print address "p2@print.com" as a character string. The administrator of printer 10B then notifies the print address "p2@print.com" to users who are authorized to use printer 10B to execute the email printing function. This enables execution of the email printing function using printer 10B. In the following, when communication is executed between printer 10B and server 200, access token AT2 is used, but a description of "access token AT2" will be omitted.

[0027] (Server processing; Figure 3) Next, the server processing executed by the CPU 232 of the server 200 will be described with reference to Fig. 3. When the power supply of the server 200 is turned on, the processing of Fig. 3 starts.

[0028] In S10, the CPU 232 monitors whether an email with an image file attached has been received from the PC. If an email has been received from the PC, the CPU 232 determines YES in S10 and proceeds to S12.

[0029] In S12, the CPU 232 identifies one or more destination addresses included in the email received in S10 (hereinafter, sometimes referred to as "received email"). The destination address is the email address written in the destination address field (e.g., 304 in FIG. 5), which is the area indicating "to" of the email. In a modified example, the destination address may include the email address written in the area indicating "cc" of the email.

[0030] In S14, the CPU 232 determines whether the destination address identified in S12 (hereinafter, sometimes referred to as the "identified destination address") includes a general address. A general address is an email address that does not include the domain name "print.com" of the server 200, and is an email address that is assigned to a user, not a printer. If the identified destination address includes a general address (YES in S14), the CPU 232 proceeds to S20. On the other hand, if the identified destination address does not include a general address (NO in S14), the CPU 232 proceeds to S30.

[0031] In S20, the CPU 232 determines whether the received email is an email generated using an email that the server 200 has received in the past. In this embodiment, the CPU 232 determines whether a print address is written in the body field (e.g., 310 in FIG. 5), which is an area indicating the "body" of the received email. If a print address is written in the body field (YES in S20), the CPU 232 ends the processing of FIG. 3. On the other hand, if a print address is not written in the body field (NO in S20), the CPU 232 proceeds to S30.

[0032] In S30, the CPU 232 executes a print process. The print process is a process for causing the printer to execute an email print function. When S30 ends, the CPU 232 ends the process of FIG.

[0033] (Printing process; Figure 4) Next, the printing process executed in S30 of Fig. 3 will be described. In S40, CPU 232 determines whether the email address written in the sender address field of the received email (hereinafter, sometimes referred to as "sender address") is registered in notification list 238. If the sender address is registered in notification list 238 (YES in S40), CPU 232 proceeds to S50. On the other hand, if the sender address is not registered in notification list 238 (NO in S40), CPU 232 proceeds to S90.

[0034] In S90, the CPU 232 creates an email that includes the sender address included in the received email as the destination address, and sends the email. The email includes a reception completion message indicating that the server 200 has received the email. This allows the user to know that the email has been received. When the processing of S90 ends, the CPU 232 ends the processing of FIG. 4.

[0035] Furthermore, in S50, the CPU 232 determines whether the specified destination addresses include an unstored address. An unstored address is an email address that includes the domain name "print.com" of the server 200 but is not registered in the address table 240. For example, an unstored address is an email address that the user entered incorrectly. If the specified destination addresses include an unstored address (YES in S50), the CPU 232 proceeds to S52. On the other hand, if the specified destination addresses do not include an unstored address (NO in S50), the CPU 232 skips S52 and S54 and proceeds to S60.

[0036] In S52, the CPU 232 excludes the unstored addresses from the identified destination addresses.

[0037] In S54, the CPU 232 determines whether the specified destination address contains zero printing addresses. If the specified destination address contains zero printing addresses (YES in S54), the CPU 232 ends the processing of FIG. 4. On the other hand, if the specified destination address contains one or more printing addresses (NO in S54), the CPU 232 proceeds to S60. Note that the cases where YES is determined in S50 and YES is determined in S54 are when all email addresses included in the specified destination address are unstored addresses.

[0038] In S60, the CPU 232 determines whether the specified destination address includes two or more print addresses. If the specified destination address includes two or more print addresses (YES in S60), the CPU 232 proceeds to S62. On the other hand, if the specified destination address includes one print address (NO in S60), the CPU 232 proceeds to S70.

[0039] In S62, the CPU 232 identifies, in the address table 240, the priority associated with each of the two or more print addresses included in the identified destination addresses.

[0040] In S64, the CPU 232 uses the priority determined in S64 to identify a target printer. The target printer is a printer that will execute the email printing function. The CPU 232 identifies the printer ID corresponding to the print address with the highest priority in the address table 240, and identifies the printer corresponding to that printer ID as the target printer.

[0041] In S70, the CPU 232 identifies the printer ID corresponding to one print address included in the identified destination addresses in the address table 240, and identifies the printer corresponding to the printer ID as the target printer.

[0042] In S80, the CPU 232 converts the image file attached to the received email to generate print data and sends a print request to the target printer. After that, when the CPU 232 receives a print data request from the target printer, it sends the generated print data to the target printer.

[0043] In S82, the CPU 232 receives a print completion notification from the target printer. The print completion notification is a notification indicating that printing of the image corresponding to the print data sent to the target printer has been completed.

[0044] In S84, the CPU 232 creates an email containing the sender address as the destination address and sends the email. The email contains a print completion message indicating that printing has been completed. This allows the user to know that the email printing function has been executed. The notification received from the target printer in S82 may be an error notification indicating that printing of the image has failed. In this case, the CPU 232 sends an email containing an error message indicating that printing of the image has failed in S84. When S84 ends, the CPU 232 ends the processing of FIG. 4. In a modified example, the processing of S82 and S84 can be omitted.

[0045] (Specific cases: Figures 5 to 9) Next, specific cases realized by the processes of FIGS. 3 and 4 will be described with reference to FIGS.

[0046] (Case A; Figure 5) Referring to FIG. 5, case A will be described in which an email 300 including one printing address as a destination address is sent. The initial state of case A is the state after the setup process of FIG. 2 is completed. Therefore, the address table 240 of the server 200 stores a printer ID "pr1", an access token AT1, and a printing address "p1@printer.com" in association with each other. The address table 240 also stores a printer ID "pr2", an access token AT2, and a printing address "p2@printer.com" in association with each other. In the address table 240, the printer ID "pr1" is associated with a priority "1," and the printer ID "pr2" is associated with a priority "2." The notification list 238 also has registered therein the email addresses "u1@user.com" and "u2@user.com."

[0047] PC 100A creates email 300 upon receiving an operation to create an email, an operation to add email addresses "u2@user.com" and "p1@print.com" to the destination address field, an operation to enter the character string "aaa" in the subject field, an operation to enter the character string "Hello" in the body field, and an operation to attach an image file with the file name "zzz.pdf." Email 300 has the source address "u1@user.com" entered in source address field 302, the destination addresses "u2@user.com" and "p1@print.com" entered in destination address field 304, the title "aaa" entered in title field 306, the file name "zzz.pdf" entered in file name field 308, and the body "Hello" entered in body field 310. Next, upon receiving an operation to send email 300, PC 100A sends email 300 in T110. Since the email addresses "u2@user.com" and "p1@print.com" are included as destination addresses, email 300 is sent to PC 100B and server 200.

[0048] When server 200 receives email 300 from PC 100A at T110 (YES in S10 of FIG. 3), it identifies the destination addresses "u2@user.com" and "p1@print.com" of email 300 (S12). Next, server 200 determines that the identified destination addresses include the general address "u2@user.com" (YES in S14), and determines that a print address is not described in the body field 310 (NO in S20). Next, server 200 determines that the sender address "u1@user.com" of email 300 is registered in notification list 238 (YES in S40), determines that the identified destination addresses do not include an unstored address (NO in S50), and determines that the identified destination addresses include one print address, "p1@print.com" (NO in S60). Next, the server 200 identifies the printer ID "pr1" corresponding to the print address "p1@print.com" in the address table 240, and identifies the printer 10A corresponding to the printer ID "pr1" as the target printer (S70). Next, in T120, the server 200 converts the image file "zzz.pdf" attached to the email 300 to generate print data PD1. Next, in T122, the server 200 sends a print request to the printer 10A (S80), receives a print data request from the printer 10A in T124, and sends the print data PD1 to the printer 10A in T126.

[0049] When printer 10A receives print data PD1 from server 200 in T126, it prints an image corresponding to print data PD1 in T130. That is, the email printing function is executed. Next, printer 10A sends a print completion notification to server 200 in T132.

[0050] When the server 200 receives a print completion notification from the printer 10A in T132 (S82), it creates an email 320 and sends the email 320 in T140 (S84). The email 320 has the sender address "p1@print.com" written in the sender address field 322, the destination address "u1@user.com" written in the destination address field 324, the title "Re:aaa" written in the subject field 326, and a print completion message (the character string "Print has been completed") written in the body field 330. Because the email address "u1@user.com" is included as the destination address, the email 320 is sent to the PC 100A. By opening the email 320, the user of the PC 100A can know that the email printing function has been executed.

[0051] (Case B; Figure 6) Next, case B in which the email printing function is executed after the email 300 is sent from the PC 100A will be described with reference to Fig. 6. Case B is the state after case A. In other words, the PC 100B has already received the email 300.

[0052] When PC 100B receives an operation to create an email, an operation to add the email address "p1@print.com" to the destination address field, an operation to enter the character string "bbb" in the subject field, and an operation to attach an image file with the file name "yyy.pdf," it creates email 400. In email 400, the source address "u2@user.cm" is entered in source address field 402, the destination address "p1@print.com" is entered in destination address field 304, the title "bbb" is entered in subject field 406, and the file name "yyy.pdf" is entered in file name field 408. The body field 410 is "empty." Next, when PC 100B receives an operation to send email 400, it sends email 400 in T210. Because the email address "p1@print.com" is included as a destination address, email 400 is sent to server 200.

[0053] When server 200 receives email 400 from PC 100B at T210 (YES in S10 of FIG. 3), it identifies email address "p1@print.com" written in destination address field 404 of email 400 as a previously identified destination address (S12). Next, server 200 determines that the previously identified destination addresses do not include a general address (NO in S14), determines that the sender address "u2@user.com" of email 400 is registered in notification list 238 (YES in S40), and determines that the previously identified destination addresses do not include an unstored address (NO in S50 of FIG. 4). Next, server 200 identifies printer ID "pr1" corresponding to print address "p1@print.com" included in the previously identified destination addresses in address table 240, and identifies printer 10A corresponding to printer ID "pr1" as the target printer (NO in S60, S70). Next, in T220, server 200 converts the image file "yyy.pdf" attached to email 400 to generate print data PD2. T222 to T240 are similar to T122 to T140 in FIG. 5, except that print data PD2 and email 420 are communicated. The contents of sender address field 422, title field 426, and body field 430 of email 420 are the same as the contents of sender address field 322, title field 326, and body field 330 of email 320 in FIG. 5, respectively. The sender address "u2@user.com" is written in destination address field 424 of email 420.

[0054] (Case C; Figure 7) Next, case C, in which the email printing function is not executed after the email 300 is sent from the PC 100A, will be described with reference to Fig. 7. Case C is the state after case A. In other words, the PC 100B has already received the email 300.

[0055] When PC 100B receives an operation to reply to email 300 and an operation to attach an image file having the file name "yyy.pdf", it creates email 500. In this case, PC 100B creates email 500 in which the sender address "u2@user.com" is entered in sender address field 502, the destination addresses "u1@user.com" and "p1@print.com" are entered in destination address field 504, the title "Re:aaa" is entered in title field 506, and content related to email 300 (the sender address, destination address, and body of email 300) is entered in body field 510. In this case, the user of PC 100B wishes to use email 300 to send an image file having the file name "yyy.pdf" to PC 100A. Therefore, the user of PC 100B needs to perform an operation to delete the email address "p1@print.com" from the destination address field 504 and also perform an operation to delete the character string including "p1@print.com" written in the body field 510. However, in this case, the user of PC 100B performs an operation to send email 500 without performing an operation to delete the email address "u1@user.com" from the destination address field 504 or an operation to delete the content related to email 300 in the body field 510. When PC 100B accepts the operation to send email 500, it sends email 500 in T310. Because email 500 includes the email addresses "u1@user.com" and "p1@print.com" as destination addresses, email 500 is sent to PC 100A and server 200.

[0056] When the server 200 receives the email 500 from the PC 100B in T310 (YES in S10 of FIG. 3), it identifies the destination addresses "u1@user.com" and "p1@print.com" of the email 500 (S12). Next, the server 200 determines that the identified destination addresses include the general address "u1@user.com" (YES in S14) and that the print address "p1@print.com" is entered in the body field 510 (YES in S20). In this case, the server 200 does not send a print request to the printer 10A. In this way, when the user does not want the email print function to be executed but a print address is entered in the body field 510 of the email 500, the email print function can be prevented from being executed.

[0057] (Case D; Figure 7) Next, case D, in which the email printing function is not executed after the email 300 is sent from the PC 100A, will be described with reference to Fig. 7. Case D is the state after case A. In other words, the PC 100B has already received the email 300.

[0058] When PC 100B receives an operation to forward email 300 and an operation to add email addresses "u3@user.com" and "p1@print.com" to the destination address field, it creates email 600. The contents of columns 602 and 610 of email 600 are the same as the contents of columns 502 and 510 of email 500, respectively. The contents of file name column 608 are the same as the contents of file name column 308 of email 300 in FIG. 5 . Furthermore, in email 600, the destination addresses "u3@user.com" and "p1@print.com" are entered in destination address column 604, and "Fw:aaa" is entered in title column 606. In this case, the user of PC 100B wants to forward the image file attached to email 300 to the user of PC 100C. In this case, the user of PC 100B simply adds the email address "u3@user.com" to the destination address field. However, in this case, the user of PC 100B adds the email address "u3@user.com" to the destination address, and then adds the email address "p1@print.com", and then executes the operation to send email 600. When PC 100B accepts the operation to send email 600, it sends email 600 in T410. Because the email addresses "u3@user.com" and "p1@print.com" are included as destination addresses, email 600 is sent to PC 100C and server 200.

[0059] When the server 200 receives the email 600 from the PC 100B at T410 (YES in S10 of FIG. 3), it identifies the destination addresses "u3@user.com" and "p1@print.com" of the email 600 (S12). Next, the server 200 determines that the identified destination addresses include the general address "u3@user.com" (YES in S14), and determines that the print address "p1@print.com" is written in the body field 610 (YES in S20). In this case, the server 200 does not send a print request to the printer 10A.

[0060] (Case E; Figure 8) Next, case E in which an email 700 including two print addresses as destination addresses is sent will be described with reference to Fig. 8. The initial state of case E is the same as the initial state of case A.

[0061] When PC 100A receives an operation to create an email, an operation to add the email addresses "u2@user.com," "p1@print.com," and "p2@print.com" to the destination address field, an operation to enter the character string "aaa" in the title field, an operation to enter the character string "Hello" in the body field, and an operation to attach an image file with the file name "zzz.pdf," it creates email 700. The contents of columns 702, 706, 708, and 710 of email 700 are the same as the contents of columns 302, 306, 308, and 310 of email 300 in FIG. 5 . Furthermore, in email 700, the destination addresses "u2@user.com," "p1@print.com," and "p2@print.com" are entered in destination address column 704. Next, when PC 100A receives an operation to send email 700, it sends email 700 in T510. Since the email addresses "u2@user.com", "p1@print.com", and "p2@print.com" are included as destination addresses, email 700 is sent to PC 100B and server 200.

[0062] When the server 200 receives the email 700 from the PC 100A at T510 (YES in S10 of FIG. 3), it identifies the destination addresses of the email 700, "u2@user.com," "p1@print.com," and "p2@print.com" (S12). Next, the server 200 determines that the identified destination addresses include the general address "u2@user.com" (YES in S14), and determines that a print address is not described in the body field 710 (NO in S20). Next, the server 200 determines that the sender address "u1@user.com" of the email 700 is registered in the notification list 238 (YES in S40), determines that the identified destination addresses do not include an unstored address (NO in S50), and determines that the identified destination addresses include the two print addresses "p1@print.com" and "p2@print.com" (YES in S60). Next, the server 200 identifies the priorities "1" and "2" associated with the two print addresses "p1@print.com" and "p2@print.com" in the address table 240 (S62). Next, the server 200 identifies the printer ID "pr1" associated with the print address "p1@print.com" with the highest priority in the address table 240, and identifies the printer 10A corresponding to the printer ID "pr1" as the target printer (S64). Next, the server 200 generates print data PD1 in T520. T522 to T532 are the same as T122 to T132 in FIG. 5. The server 200 sends email 720 in T540. The contents of each column 722, 724, 726, and 730 of the email 720 are the same as the contents of each column 322, 324, 326, and 330 of the email 320.

[0063] (Effect of Case E) As shown in Case E, when an email 700 containing two print addresses, "p1@print.com" and "p2@print.com," as destination addresses is received, the server 200 sends a print request only to the printer 10A corresponding to the highest priority in the memory 234 (T522). This configuration can prevent the email print function from being executed by two printers when an email containing two print addresses is received. For example, when an email containing two print addresses is received from a third party who has learned the two print addresses, it can prevent the email print function from being executed by two printers. This can prevent unnecessary printing from being executed.

[0064] (Case F; Figure 9) Next, case F, in which email 800 containing an incorrect email address as the destination address is sent, will be described with reference to Figure 9. The initial state of case F is the same as the initial state of case A in Figure 5. In this case, we consider a case in which a user of PC 100A enters the email address "p3@print.com" when the email address should be "p1@print.com."

[0065] When PC 100A receives an operation to create an email, an operation to add the email addresses "u2@user.com," "p3@print.com," and "p2@print.com" to the destination address field, an operation to enter the string "aaa" in the title field, an operation to enter the string "Hello" in the body field, and an operation to attach an image file with the file name "zzz.pdf," it creates email 800. The contents of columns 802, 806, 808, and 810 of email 800 are the same as the contents of columns 302, 306, 308, and 310 of email 300 in FIG. 5 . Furthermore, the email addresses "u2@user.com," "p3@print.com," and "p2@print.com" are entered in destination address column 804 of email 800. Next, when PC 100A receives an operation to send email 800, it sends email 800 in T610. Since the email addresses "u2@user.com" and "p2@print.com" are included as destination addresses, email 800 is sent to PC 100B and server 200.

[0066] When server 200 receives email 800 from PC 100A at T610 (YES at S10 in FIG. 3), it identifies the destination addresses "u2@user.com," "p3@print.com," and "p2@print.com" of email 800 (S12). Next, server 200 determines that the identified destination addresses include the general address "u2@user.com" (YES at S14), and determines that a print address is not described in the body field 810 (NO at S20). Next, the server 200 determines that the sender address "u1@user.com" of the email 800 is registered in the notification list 238 (YES in S40), determines that the identified destination addresses include the unstored address "p3@print.com" (YES in S50), excludes the unstored address "p3@print.com" from the identified destination addresses (S52), and determines that one print address "p2@print.com" is included in the email 800 (NO in S54, NO in S60). Next, the server 200 identifies the printer ID "pr2" corresponding to the print address "p2@print.com" included in the identified destination addresses in the address table 240, and identifies the printer 10B corresponding to the printer ID "pr2" as the target printer (S70). Next, the server 200 generates print data PD1 in T620. T622 to T632 are the same as T122 to T132 in Fig. 5, except that the communication target is printer 10B. In T640, server 200 sends email 820. The email address "p2@print.com" is entered in a sender address field 822 of email 820. The contents of the subject field 826 and body field 830 of email 820 are the same as the contents of the subject field 326 and body field 310 of email 320 in Fig. 5, respectively.

[0067] (Effect of Case F) As shown in Case F, when email 800 is received, server 200 excludes "p3@print.com," which includes server 200's domain "print.com" and is not stored in memory 234, from the identified destination addresses "u2@user.com," "p3@print.com," and "p2@print.com." After "p3@print.com" has been excluded from the identified destination addresses, server 200 identifies "p2@print.com" from the identified destination addresses and sends a print request to printer 10B (T622). This configuration can reduce the time required to print data.

[0068] (Case G; Figure 10) Next, case G, in which the email printing function is not executed, will be described with reference to Fig. 10. The initial state of case G is the same as the initial state of case A, except that the email address "u1@user.com" is not registered in the notification list 238.

[0069] First, PC 100A creates email 900. The contents of each of columns 902, 904, 906, 908, and 910 of email 900 are the same as the contents of each of columns 302, 304, 306, 308, and 310 of email 300 in Fig. 5. Next, when PC 100A accepts an operation to send email 900, it sends email 900 in T710.

[0070] When server 200 receives email 900 from PC 100A in T710 (YES in S10 of FIG. 3), it identifies the destination addresses "u2@user.com" and "p1@print.com" of email 900 (S12). Next, server 200 determines that the identified destination addresses include the general address "u2@user.com" (YES in S14) and determines that a print address is not described in the body field 910 (NO in S20). Next, server 200 determines that the sender address of email 900, "u1@user.com," is not registered in notification list 238 (NO in S40), and creates email 920 including a reception completion message (the character string "Email has been received") indicating that email 900 has been received. The contents of fields 922, 924, and 926 of email 920 are the same as the contents of fields 322, 324, and 326 of email 320. A reception completion message is written in the body field 930 of the email 920. In T715, the server 200 sends the email 920 (S90). Since the email 920 includes the email address "u1@user.com" as a destination address, the email 920 is sent to PC 100A.

[0071] (Effects of Cases A and G) As shown in case A of Fig. 5, when the sender address "u1@user.com" of email 300 is stored in the notification list 238 and a print completion notification is received from printer 10A (T132), server 200 sends email 320 including email address "u1@user.com" as the destination address. On the other hand, as shown in case G of Fig. 10, when the sender address "u1@user.com" of email 900 is not stored in the notification list 238, server 200 sends email 920 including a reception completion message (T915 of Fig. 10). With this configuration, it is possible to appropriately switch between sending an email including a print completion message and sending an email including a reception completion message depending on whether the sender address is stored in the notification list 238.

[0072] 5, if the sender address "u1@user.com" of the email 300 is stored in the notification list 238, the server 200 sends a print request to the printer 10A (T122). On the other hand, as shown in case G of FIG. 10, if the sender address "u1@user.com" of the email 900 is not stored in the notification list 238, the server 200 does not send the print request. With this configuration, it is possible to appropriately switch whether or not to send a print request depending on whether or not the sender address is stored in the notification list 238. Therefore, the users of the printers 10A and 10B and the administrators of the printers 10A and 10B can appropriately manage the users who are permitted to use the email printing function.

[0073] 5, if the sender address "u1@user.com" of the email 300 is stored in the notification list 238, the server 200 sends a print request to the printer 10A (T122). If a print completion notification is received from the printer 10A (T132), the server 200 sends an email 320 including a print completion message (T140). On the other hand, as shown in case G of FIG. 10, if the sender address "u1@user.com" of the email 900 is not stored in the notification list 238, the server 200 sends an email 920 including a reception completion message (T915) and does not send a print request. With this configuration, the server 200 can appropriately switch between sending an email including a print completion message and sending an email including a reception completion message depending on whether the user using the sender address is authorized to use the email printing function. Furthermore, users corresponding to email addresses registered in the notification list 238 are authorized to use the email printing function. It is beneficial to provide information about the printers 10A and 10B to the users. On the other hand, users whose email addresses are not registered in the notification list 238 are users who are not authorized to use the email printing function. Such users may include users who use the printers 10A and 10B, as well as third parties other than the users who use the printers 10A and 10B. Providing information about the printers 10A and 10B to third parties is undesirable from a security perspective. According to the above configuration, when the server 200 receives an email containing an email address corresponding to a third party as the sender address (YES in S10 of FIG. 3), the server 200 determines that the email address is not registered in the notification list 238 (NO in S40 of FIG. 4), and sends an email containing a reception completion message (S90) without sending an email containing a print completion message. This improves the security of information about the printers 10A and 10B.

[0074] (Effects of cases A to G) When server 200 receives email 300 from PC 100A that includes the print address "p1@print.com" and the general address "u2@print.com" as destination addresses (T110 in FIG. 3), it sends a print request to printer 10A (T122 in FIG. 5). Then, after receiving email 300 from PC 100A, server 200 receives emails 400, 500, and 600 from PC 100B that include the print address "p1@print.com" and the general address "u2@user.com" as destination addresses (T210 in FIG. 6, T310, T410 in FIG. 7). When server 200 determines that email 400 was not generated using email 300, it sends a print request to printer 10A (T222 in FIG. 6). On the other hand, if the server 200 determines that the emails 500 and 600 were generated using the email 300, it does not send a print request to the printer 10A. In this way, when the server 200 receives emails 400, 500, and 600 with multiple addresses specified as destination addresses, it can appropriately switch whether to cause the printer 10A to print the emails, depending on whether the emails 400, 500, and 600 were generated using the email 300. In particular, in this embodiment, if the email address (i.e., the print address) stored in the address table 240 of the memory 234 is described in the body of the email 500 and 600 (see FIG. 7), the server 200 determines that the email 500 and 600 were generated using the email 300, and if the email address (i.e., the print address) stored in the address table 240 of the memory 234 is not described in the body of the email 400 (see FIG. 6), it determines that the email 400 was not generated using the email 300. As shown in the body field 510 of the email 500 in FIG. 7, when an operation to execute a reply to the email 300 is performed, the destination address of the original email 300 is included in the body field of the email.Therefore, it is possible to appropriately determine whether the emails 400 and 500 are emails generated using the email 300, depending on whether a print address is written in the body of the email. The same applies to forwarded emails.

[0075] (Correspondence) Printer 10A is an example of a "first printer." The printer ID is an example of "printer identification information." PC 100A and PC 100B are examples of a "first external device" and a "second external device," respectively. Memory 234 of server 200 is an example of a "memory." Email 300 in FIG. 5, email 700 in FIG. 8, and email 800 in FIG. 9 are examples of a "first email." An image file with the file name "zzz.pdf" is an example of a "first image file." The print address "p1@print.com" is an example of a "first print address." The general address "u2@user.com" is an example of a "first general address." The print request T122 in FIG. 5, the print request T522 in FIG. 8, and the print request T622 in FIG. 9 are examples of a "first print request." The printer ID "pr1" is an example of a "first printer identification information." Email 400 in FIG. 6 and emails 500 and 600 in FIG. 7 are examples of a "second email." An image file with the file name "zzz.pdf" and an image file with the file name "yyy.pdf" are examples of a "second image file." The general addresses "u2@user.com" and "u3@user.com" are examples of a "second general address." The print request of T222 in FIG. 6 is an example of a "second print request."

[0076] The domain "print.com" of the server 200 is an example of a predetermined domain. The email address "p3@print.com" in Figure 9 is an example of a "specific email address."

[0077] Printer 10B is an example of a "second printer." The printer ID "pr2" is an example of "second printer identification information." The printing address "p2@print.com" is an example of a "second printing address." In the address table 240, the priority "1" associated with the printing address "p1@print.com" and the priority "2" associated with the printing address "p2@print.com" are examples of a "first priority" and a "second priority," respectively. An email address registered in the notification list 238 is an example of a "notification address." "u1@user.com" listed in the sender address field 502 of email 500 in FIG. 5 and "u1@user.com" listed in the sender address field 902 of email 900 in FIG. 10 are examples of a "sender address." Email 320 in FIG. 5 is an example of a "third email." A print completion message is an example of "print completion information." Email 920 in FIG. 10 is an example of a "fourth email." The reception completion message is an example of "reception information."

[0078] S10 in Fig. 3 is an example of a process implemented by a "first receiving unit" and a "second receiving unit." S80 in Fig. 4 is an example of a "first print request transmitting unit" and a "second print request transmitting unit." S20 in Fig. 3 is an example of a process executed by a "determining unit."

[0079] (Second Example) In this embodiment, the process executed in S20 of Fig. 3 differs from that of the first embodiment. In S20 of Fig. 3, the CPU 232 of the server 200 determines whether the received email is an email generated using an email that the server 200 has previously received, by determining whether the subject line of the email received in S12 contains the character string "Re" or "Fw." If the subject line of the received email contains the character string "Re" or "Fw" (YES in S20), the CPU 232 ends the process of Fig. 3. On the other hand, if the subject line of the received email does not contain the character string "Re" or "Fw" (NO in S20), the CPU 232 proceeds to S30.

[0080] For example, in case B of FIG. 6, the server 200 determines that the subject field 406 of the email 400 does not contain the character string "Re" or "Fw" (NO in S20 of FIG. 3). In this case, as in the first embodiment, the server 200 sends a print request to the printer 10A in T222. On the other hand, in case C of FIG. 7, the server 200 determines that the subject field 506 of the email 500 contains the character string "Re" (YES in S20). In this case, as in the first embodiment, the print request is not sent to the printer 10A.

[0081] 7, when an operation to execute a reply to email 300 is performed, the character string "Re" is entered in the subject field of the email. Therefore, depending on whether the character string "Re" is entered in the subject field of the email, it is possible to appropriately determine whether emails 400 and 500 are emails generated using email 300. The same applies to forwarded emails.

[0082] (Third Example) In this embodiment, the process executed in S20 of FIG. 3 differs from that of the first embodiment. When receiving an email with an image file attached, the CPU 232 of the server 200 in this embodiment is configured to store the file name described in the file name field of the email in the memory 234. In S20 of FIG. 3, the CPU 232 determines whether the file name described in the file name field of the email received in S12 (hereinafter, sometimes referred to as the "target file name") matches the file name stored in the memory 234, thereby determining whether the received email is an email generated using an email previously received by the server 200. If the file names match (YES in S20), the CPU 232 terminates the process of FIG. 3. On the other hand, if the file names do not match (NO in S20), the CPU 232 proceeds to S30.

[0083] For example, in case A of FIG. 5, when server 200 receives email 300, it stores the file name "zzz.pdf." Then, in case B of FIG. 6, server 200 determines that the file name "yyy.pdf" written in file name field 408 of email 400 does not match the file name "zzz.pdf" stored in memory 234 (NO in S20 of FIG. 3). In this case, as in the first embodiment, server 200 sends a print request to printer 10A in T222. On the other hand, in case D of FIG. 7, server 200 determines that the file name "zzz.pdf" written in file name field 508 of email 500 matches the file name "zzz.pdf" stored in memory 234 (YES in S20). In this case, as in the first embodiment, the print request is not sent to printer 10A.

[0084] When an email is received with an attached image file similar to an image file received in the past, it is highly likely to be a forwarded email. Therefore, by determining whether the file name written in the file name field of the received email matches the file name stored in memory 234, it is possible to appropriately determine whether email 500 is an email generated using email 300.

[0085] 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 exemplified above. Modifications of the above-mentioned embodiments are listed below.

[0086] (First Modification) A "server" may be made up of two or more servers.

[0087] (Second Modification) In S20 of Fig. 3, the CPU 232 of the server 200 may determine whether a print address is written in the body field (e.g., 310 in Fig. 5), which is an area indicating the "body" of a received e-mail, and may also determine whether the character string "Re" or "Fw" is included in the subject field of the e-mail received in S12. The CPU 232 may execute a combination of two or more of the processes of S20 in the first to third embodiments.

[0088] (Third Modification) Steps S50 to S54, S60, S62, and S70 in FIG. 4 may be omitted. In this modification, in S64, the CPU 232 of the server 200 extracts a first email address listed at the top of the destination address field of the received email from among email addresses that include the server 200's domain "print.com." The CPU 232 then determines whether the first email address is an unstored address. If the first email address is not an unstored address (i.e., a print address), the CPU 232 identifies the printer ID associated with the first email address in the address table 240 and executes the processing from S80 onward. On the other hand, if the first email address is an unstored address, the CPU 232 extracts a second email address listed next to the first email address in the destination address field of the received email and determines whether the second email address is an unstored address. The CPU 232 repeats the above processing until a print address is identified. If it is determined that all email addresses including the domain "print.com" of server 200 are unstored addresses, CPU 232 executes the process of S90 and ends the process of FIG. 4. The order in which one email address is extracted from two or more email addresses written in the destination address field of a received email may be random. In this modification, the "exclusion unit" and the "address identification unit" can be omitted.

[0089] (Fourth Modification) Priority may not be stored in the address table 240 of the server 200. In this modification, in S64, the server 200 may identify all printers corresponding to two or more print addresses listed in the destination address field of the received email as target printers.

[0090] (Fifth Modification) Memory 234 of server 200 does not have to store notification list 238. In this modification, S40 and S90 in FIG. 4 can be omitted. In this modification, the "second email sending unit" can be omitted. Furthermore, S84 can be omitted. In this modification, the "first email sending unit" can be omitted.

[0091] (Sixth Modification) The notification list 238 of the server 200 may register email addresses corresponding to users who are prohibited from using the email printing function.

[0092] (Seventh Modification) After S90 in FIG. 4, processing similar to S50 to S82 may be executed. In this modification, the email address registered in the notification list 238 is the email address to which the email containing the print completion message should be sent.

[0093] (Eighth Modification) In a modification of the third embodiment, when the server 200 receives an email with an attached image file, the server 200 may store the sender address of the email and the general address written in the destination address field in association with the file name written in the file name field of the email. In this modification, the CPU 232 determines in S20 of Fig. 3 whether the target file name matches the file name stored in the memory 234 and whether the sender address of the received email matches the email address in the memory 234 associated with the target file name.

[0094] (Ninth Modification) It may be possible to set whether or not the server 200 is to execute the process (S40 in FIG. 4) using the notification list 238 (hereinafter, sometimes referred to as "notification list process"). In this modification, memory 234 of server 200 stores notification list information indicating either "ON," which indicates that execution of the notification list process is permitted, or "OFF," which indicates that execution of the notification list process is not permitted. The notification list information is set by the user of printer 10A, 10B or the administrator of printer 10A, 10B. In this modification, CPU 232 executes the processes of S40 to S90 when the notification list information is "ON." On the other hand, CPU 232 executes the processes of S50 to S84 when the notification list information is "OFF." With this configuration, when the notification list information is “ON,” the server 200 sends a print request to the printer 10A, 10B if it receives an email from the target PC containing an email address registered in the notification list 238 (i.e., an email address corresponding to a user who is authorized to use the email printing function) as a destination address. Also, when the notification list information is “ON,” the server 200 does not send a print request to the printer 10A, 10B if it receives an email from the target PC containing an email address not registered in the notification list 238 (i.e., an email address corresponding to a user who is not authorized to use the email printing function) as a destination address. Also, when the notification list information is “OFF,” the server 200 sends a print request to the printer 10A, 10B if it receives an email from the target PC containing an email address not registered in the notification list 238 (i.e., an email address corresponding to a user who is not authorized to use the email printing function). Therefore, the users of the printers 10A, 10B and the administrators of the printers 10A, 10B can more appropriately manage the users who are authorized to use the email printing function. It should be noted that the CPU 232 may omit S82 and S84 when the notification list information is "OFF." In this case, the CPU 232 executes S80 and S90 after S64 or S70.With this configuration, when the notification list information is "OFF," it is possible to prevent emails containing information about printers 10A and 10B (e.g., a print completion message) from being sent to users who use email addresses that are not registered in the notification list.

[0095] (Tenth Modification) The server 200 may store notification lists corresponding to the printers 10A and 10B. In this modification, the CPU 232 of the server 200 executes the same process as S40 after S64 and S70 in FIG. 4. That is, after the target printer is identified, the CPU 232 uses the notification list corresponding to the target printer to determine whether the sender address of the received email is registered in the notification list. In this modification, if the CPU 232 determines that the sender address of the received email is registered in the notification list, it executes the processes from S80 onward. On the other hand, if the CPU 232 determines that the sender address of the received email is not registered in the notification list, it executes S90. In a further modification, notification list information may be stored in the memory 234 of the server 200. In this modification, the CPU 232 determines whether the notification list information is "ON" after S64 and S70. If the notification list information is "ON," the CPU 232 executes the same process as S40. Then, if the sender address of the received email is registered in the notification list corresponding to the target printer, the CPU 232 executes the process from S80 onwards. On the other hand, if the sender address of the received email is not registered in the notification list corresponding to the target printer, the CPU 232 executes the process of S90. Furthermore, if the notification list information is "OFF", the CPU 232 executes the process from S80 onwards. Note that if the notification list information is "OFF", the CPU 232 may omit S82 and S84. Furthermore, if the CPU 232 omits S82 and S84, the CPU 232 may execute S90 after S64 or S70, and then execute S80.

[0096] (Eleventh Modification) In the above embodiment, a print address is written in the sender address field of an email sent from server 200. For example, the print address "p1@print.com" is written in sender address field 322 of email 320 in Fig. 5. In a modification, an email address for server 200 (for example, "server@print.com") may be written in the sender address field of an email sent from server 200.

[0097] (12th Modification) In each of the above embodiments, the processes in Figures 2 to 10 are realized by software (e.g., programs 36, 236), but at least one of these processes may be realized by hardware such as a logic circuit.

[0098] Furthermore, the technical elements described in this specification or drawings may exhibit technical utility either alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Furthermore, the technologies illustrated in this specification or drawings simultaneously achieve multiple objectives, and achieving one of those objectives is itself technically useful. [Explanation of symbols]

[0099] 2: Communication system, 4: LAN, 6: Internet, 10A, 10B: Printer, 12: Operation unit, 14: Display unit, 16: Print execution unit, 20: Communication I / F, 30: Control unit, 32: CPU, 34: Memory, 36: Program, 100A, 100B, 100C: PC, 200: Server, 220: Communication I / F, 230: Control unit, 232: CPU, 234: Memory, 236: Program, 238: Notification list, 240: Address table

Claims

1. a server, a memory that stores, for each of one or more email addresses, the email address and printer identification information that identifies the printer in association with each other; a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; each of the one or more email addresses stored in the memory includes a predetermined domain; The first email further includes, as a destination address, a specific email address that includes the predetermined domain and is not stored in the memory; The server further an address specifying unit that, when the first email is received from the first external device, specifies the first printing address, which is the destination address, and the first printing address that includes the predetermined domain and is stored in the memory from among the specific email addresses; the first printer is a printer identified by the first printer identification information stored in the memory in association with the identified first print address; The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The server further a first email sending unit that, when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, receives a print completion notification from the first printer indicating that printing of the first image has been completed, sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; a second email sending unit that, if the sender address is not the notification address, does not send the third email, and sends a fourth email that includes the sender address as a destination address and includes reception information indicating that the first email has been received, server.

2. a server, a memory that stores, for each of one or more email addresses, the email address and printer identification information that identifies the printer in association with each other; a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; the memory stores, for each of the one or more email addresses, the email address, the printer identification information, and a priority in association with each other; the first email further includes, as a destination address, a second print address that is an email address stored in the memory and that is different from the first print address; a first priority stored in the memory in association with the first printing address is higher than a second priority stored in the memory in association with the second printing address; the first print request sending unit sends the first print request only to the first printer corresponding to a higher priority among the first printer and the second printer; the second printer is a printer identified by second printer identification information stored in the memory in association with the second print address included in the first email, The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The server further a first email sending unit that, when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, receives a print completion notification from the first printer indicating that printing of the first image has been completed, sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; a second email sending unit that, if the sender address is not the notification address, does not send the third email, and sends a fourth email that includes the sender address as a destination address and includes reception information indicating that the first email has been received, server.

3. a server, a memory that stores, for each of one or more email addresses, the email address and printer identification information that identifies the printer in association with each other; a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; each of the one or more email addresses stored in the memory includes a predetermined domain; The first email further includes, as a destination address, a specific email address that includes the predetermined domain and is not stored in the memory; The server further an address specifying unit that, when the first email is received from the first external device, specifies the first printing address, which is the destination address, and the first printing address that includes the predetermined domain and is stored in the memory from among the specific email addresses; the first printer is a printer identified by the first printer identification information stored in the memory in association with the identified first print address; The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The server further a first email sending unit that, when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, receives a print completion notification from the first printer indicating that printing of the first image has been completed, sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; If the sender address is not the notification address, the third email is not sent; the first print request sending unit sends the first print request to the first printer when the first email is received from the first external device and the sender address is the notification address; When the first email is received from the first external device and the sender address is not the notification address, the first print request is not sent to the first printer. server.

4. a server, a memory that stores, for each of one or more email addresses, the email address and printer identification information that identifies the printer in association with each other; a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; the memory stores, for each of the one or more email addresses, the email address, the printer identification information, and a priority in association with each other; the first email further includes, as a destination address, a second print address that is an email address stored in the memory and that is different from the first print address; a first priority stored in the memory in association with the first printing address is higher than a second priority stored in the memory in association with the second printing address; the first print request sending unit sends the first print request only to the first printer corresponding to a higher priority among the first printer and the second printer; the second printer is a printer identified by second printer identification information stored in the memory in association with the second print address included in the first email, The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The server further a first email sending unit that, when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, receives a print completion notification from the first printer indicating that printing of the first image has been completed, sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; If the sender address is not the notification address, the third email is not sent; the first print request sending unit sends the first print request to the first printer when the first email is received from the first external device and the sender address is the notification address; When the first email is received from the first external device and the sender address is not the notification address, the first print request is not sent to the first printer. server.

5. A computer program for a server, comprising: the server includes a memory for storing, for each of one or more email addresses, the email address and printer identification information for identifying the printer in association with each other; The computer program controls the server computer to operate as follows: a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; It functions as each of the one or more email addresses stored in the memory includes a predetermined domain; The first email further includes, as a destination address, a specific email address that includes the predetermined domain and is not stored in the memory; The computer program further causes the computer to: When the first email is received from the first external device, the first external device functions as an address specifying unit that specifies the first printing address that is the destination address and that includes the predetermined domain and is stored in the memory from among the specific email addresses, the first printer is a printer identified by the first printer identification information stored in the memory in association with the identified first print address; The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The computer program further causes the computer to: a first email sending unit that, when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, receives a print completion notification from the first printer indicating that printing of the first image has been completed, sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; and a second email sending unit that, when the sender address is not the notification address, does not send the third email, and sends a fourth email that includes the sender address as a destination address and that includes reception information indicating that the first email has been received. Computer program.

6. A computer program for a server, comprising: the server includes a memory for storing, for each of one or more email addresses, the email address and printer identification information for identifying the printer in association with each other; The computer program controls the server computer to operate as follows: a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; It functions as the memory stores, for each of the one or more email addresses, the email address, the printer identification information, and a priority in association with each other; the first email further includes, as a destination address, a second print address that is an email address stored in the memory and that is different from the first print address; a first priority stored in the memory in association with the first printing address is higher than a second priority stored in the memory in association with the second printing address; the first print request sending unit sends the first print request only to the first printer corresponding to a higher priority among the first printer and the second printer; the second printer is a printer identified by second printer identification information stored in the memory in association with the second print address included in the first email, The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The computer program further causes the computer to: a first email sending unit that, when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, receives a print completion notification from the first printer indicating that printing of the first image has been completed, sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; and a second email sending unit that, when the sender address is not the notification address, does not send the third email, and sends a fourth email that includes the sender address as a destination address and that includes reception information indicating that the first email has been received. Computer program.

7. A computer program for a server, comprising: the server includes a memory for storing, for each of one or more email addresses, the email address and printer identification information for identifying the printer in association with each other; The computer program controls the server computer to operate as follows: a first receiving unit that receives a first email including a first image file from a first external device, the first email including a first print address that is an email address stored in the memory as a destination address; a first print request sending unit that sends a first print request to a first printer when the first email is received from the first external device, the first print request being a signal requesting printing of a first image corresponding to the first image file included in the first email, and the first printer being identified by first printer identification information stored in the memory in association with the first print address included in the first email; It functions as each of the one or more email addresses stored in the memory includes a predetermined domain; The first email further includes, as a destination address, a specific email address that includes the predetermined domain and is not stored in the memory; The computer program further causes the computer to: When the first email is received from the first external device, the first external device functions as an address specifying unit that specifies the first printing address that is the destination address and that includes the predetermined domain and is stored in the memory from among the specific email addresses, the first printer is a printer identified by the first printer identification information stored in the memory in association with the identified first print address; The memory further stores a notification address, which is an email address to which an email containing print completion information indicating that printing of the image has been completed is to be sent; The computer program further causes the computer to: when a sender address included in the first email is the notification address and, after the first print request is sent to the first printer, a print completion notification indicating that printing of the first image has been completed is received from the first printer, function as a first email sending unit that sends a third email that includes the sender address as a destination address, the third email including specific print completion information indicating that printing of the first image has been completed; If the sender address is not the notification address, the third email is not sent; the first print request sending unit sends the first print request to the first printer when the first email is received from the first external device and the sender address is the notification address; When the first email is received from the first external device and the sender address is not the notification address, the first print request is not sent to the first printer. Computer program.

Images