JP2010009620A - Receiver, control method thereof, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a receiver for surely transmitting acknowledgment by adaptively selecting a transmitting/receiving path of the acknowledgment of e-mail in accordance with environment between devices, and to provide a control method thereof, and a program. <P>SOLUTION: E-mail from a transmitter is received, and it is determined whether an acknowledgment result for the received e-mail can be transmitted without passing through a mail server. When it is determined that the acknowledgment result for the received e-mail can be transmitted without passing through the mail server, as a result of the determination, the acknowledgment result is transmitted without passing through the mail server. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a communication system that transmits and receives electronic mail between a transmission device and a reception device via a network.

  In recent years, with the spread of computers and the networking of information, electronic mail that transmits and receives character information over a network has become widespread.

  It is possible to attach various types of files to the electronic mail in addition to the mail text as character information. For example, an Internet FAX (hereinafter abbreviated as IFAX) for transmitting and receiving images by attaching a TIFF (Tag Image File Format) file to this attached file has become widespread.

  IFAX converts the image read by the scanner of the transmitter into a TIFF format image and transmits it to the destination. The receiver restores the TIFF format image from the received data and prints it. Technology.

  In such a technique, Patent Document 1 discloses a configuration in which image data is transmitted directly to a receiver without relaying a mail server by an apparatus that transmits image data using an electronic mail protocol.

  Further, in Patent Document 2, in an apparatus that transmits image data using an e-mail protocol, data indicating whether image data is transmitted directly to a receiver without relaying a mail server for each address book destination is retained. Keep it. A configuration is disclosed in which data is directly transmitted to a receiver without going through a mail server to a destination that can be directly transmitted based on the data.

  In Non-Patent Document 1, the IFAX Full Mode standard is defined. In this standard, when image data is communicated from a transmitter to a receiver, a configuration for notifying the transmitter of the reception result by using MDN (Message Disposition Notification) from the receiver to the transmitter is defined. .

JP-A-2002-27193

JP 2003-233558 A

RFC2532

  In the configuration in which image data is transmitted from the transmitter to the receiver without going through the mail server in accordance with the Full Mode standard, according to the configuration disclosed in Patent Document 1 and Patent Document 2, an image is transmitted from the transmitter to the receiver. It is possible to send data directly.

  However, when the receiver transmits the MDN result to the transmitter, it cannot be determined whether the destination to which the MDN is transmitted is a destination that can be directly transmitted or a destination that cannot be directly transmitted.

  For this reason, the MDN always returns the mail server to perform communication, and the mail server has been indispensable.

  However, it is not easy to install and operate a mail server. Here, when operating only in an environment where communication is possible without going through a mail server, there is a case where image data is communicated according to an e-mail protocol without constructing a mail server. Also, even if a mail server exists, IFAX, which sends large image files, has a problem with the mail server load, so there is an increasing number of cases where the mail server is set not to use it. .

  Even if the receiver successfully receives e-mail data, in a system that analyzes e-mail data after extraction and extracts an image from the e-mail data, the data reception at the receiver is not always successful. The image formation is not always successful. For example, when a failure occurs such that a data storage device built in the receiver becomes full during processing, image formation at the receiver ends in failure.

  Therefore, in order to confirm whether communication has finally succeeded, confirmation by MDN is required. In an environment in which such a mail server is not installed or set, there is a problem that MDN communication is not performed and it is impossible to determine whether the transmitted e-mail data has normally arrived at the receiver.

  The present invention has been made in view of the above problems. An object of the present invention is to provide a receiving apparatus that can adaptively select a transmission / reception path for e-mail delivery confirmation according to the environment between the apparatuses and reliably transmit the delivery confirmation, and a control method and program thereof. It is in.

In order to achieve the above object, a receiving apparatus according to the present invention comprises the following arrangement. That is,
A receiving device for receiving e-mail via a network,
Receiving means for receiving e-mail from the transmitting device;
A determination unit that determines whether or not it is possible to transmit a delivery confirmation result related to the received e-mail without going through a mail server when the receiving unit receives the e-mail;
As a result of the determination by the determination means, when it is determined that the delivery confirmation result regarding the received electronic mail can be transmitted without going through the mail server, the delivery confirmation result is sent through the mail server. Transmission means for transmitting without making
Is provided.

  According to the present invention, it is possible to provide a receiving apparatus that can adaptively select a transmission / reception path for e-mail delivery confirmation according to the environment between the apparatuses, and to reliably transmit the delivery confirmation, and a control method and program therefor. it can.

It is a block diagram which shows the network connection structure of the communication apparatus of Embodiment 1 of this invention. 1 is a diagram illustrating a configuration of an MFP according to a first embodiment of the present invention. FIG. 3 is a diagram illustrating a configuration of a network program owned by the MFP according to the first embodiment of the present invention. 7 is a destination table registration screen for storing transmission destination information of the MFP according to the first embodiment of the present invention. It is a figure which shows the structural example of the email data of Embodiment 1 of this invention. It is a figure which shows the sequence flow of the SMTP protocol of Embodiment 1 of this invention. It is a flowchart which shows the SMTP reception process of Embodiment 1 of this invention. It is a figure which shows the structural example of the MDN data of Embodiment 1 of this invention. It is a flowchart which shows the MDN transmission process of Embodiment 1 of this invention. It is a flowchart which shows the MDN transmission process of Embodiment 2 of this invention. It is a figure which shows the structural example of the email data of Embodiment 3 of this invention. It is a flowchart which shows the email data analysis process of Embodiment 3 of this invention.

  Hereinafter, embodiments of the present invention will be described in detail with reference to the drawings.

<Embodiment 1>
FIG. 1 is a block diagram showing a network connection configuration of a communication apparatus according to Embodiment 1 of the present invention.

  Reference numerals 100 and 101 denote MFPs (Multi Function Peripherals). MFPs 100 and 101 are equipped with devices such as a scanner and a printer, so that multifunction copying including a scanner function, a copy function, a FAX transmission / reception function, and a printer function for printing data created on a computer is provided. Machine.

  For example, the MFP 100 and the MFP 101 have domain names xyz. co. It is connected to a network called jp and is connected to a plurality of computers and network devices such as the server 103 and the client PC 104.

  This network is further connected to the Internet network 110 that extends throughout the world.

  MFP 100 uses copy1. xyz. co. HOST name jp and ifax @ copy1. xyz. co. An e-mail mail address of a device called jp is given. The MFP 101 uses copy2. xyz. co. HOST name jp and ifax @ copy2. xyz. co. An e-mail address of a device called jp is given.

  The PC 104 has general-purpose e-mail software installed, and yamada @ xyz. co. A mail address of jp is given.

  The server 103 is a server having both a Mail server (SMTP server) function and a POP server function. xyx. co. The host name jp is assigned. It also has a DNS server function.

  It should be noted that a server having a Mail server function, a server having a POP server function, and a server having a DNS server function may be different terminals or may be integrated terminals as appropriate. Further, by collectively managing a server having a DNS server function as a terminal independent of MFP 100 as described above, a terminal that mutually converts a domain name and an IP address can be shared by various MFPs.

  If the domain name or IP address is changed, only this server needs to be changed. Of course, this DNS server function may be built in the MFP 100. In this case, since the communication via the network is not performed, an improvement in processing efficiency can be expected.

  The MFP 100 and the MFP 101 are configured with two types of transmission modes. One is an Email transmission mode in which an image received by a FAX / IFAX reception function and a monochrome / color image read by a scanner are transmitted on the assumption that the image is transmitted to a general electronic mail destination. The other is an IFAX transmission mode in which transmission is performed on the assumption that transmission is performed to a device in accordance with the IFAX standard.

  For data transmission / reception, for example, SMTP and POP3 protocols are used.

  In the Email transmission mode, when a color image is read by a scanner, an image of a file in JPEG format or PDF (Portable Document Format) format can be attached to an e-mail and transmitted. On the other hand, when a black and white image is read by the scanner, an image in TIFF or PDF format can be transmitted.

  For example, yamada @ xyz. co. When an e-mail is transmitted to the client 104 having a jp mail address, an e-mail with image data attached is transmitted to the server 103 using the SMTP protocol. Then, the client PC 104 can receive the electronic mail by the POP3 protocol and display the image attached by the general-purpose image viewer.

  In the IFAX transmission mode, an image read by the scanner function of the MFP or image data received by the FAX / IFAX reception function is transmitted as a TIFF format image according to RFC2301. The received image data is printed by the printer function of the receiving MFP.

  Next, the configuration of MFP 100 will be described with reference to FIG.

  In the following description, the configuration of the MFP 100 will be described as an example, but the same configuration as the MFP 100 is realized for the MFP 101 as well.

  FIG. 2 is a diagram showing a configuration of the MFP according to the first embodiment of the present invention.

  The CPU 130 executes control of the entire system using the program stored in the ROM 131 and the RAM 132.

  The operation unit 133 includes an LCD display panel and hard keys such as a start key and a numeric keypad, displays a soft button on the LCD, detects that the user touches the soft button with a finger, and executes a user operation. .

  The scanner 134 converts image data of a document into electrical data by photoelectric conversion. The scanner 134 transports a document from a document feeder (not shown) onto the platen glass. When the document is transported onto the platen glass, the lamp is turned on, and the document reading unit starts to move. Is scanned by exposure.

  Reflected light from the original is guided to a CCD image sensor by a mirror and a lens, converted into an electrical signal, and converted into digital data by an A / D conversion circuit. After the document reading operation is completed, the document on the platen glass is discharged.

  The printer 135 prints electrical image data on a recording sheet. Laser light corresponding to the electrical image data is emitted from the laser light emitting unit, and this laser light is applied to the photosensitive drum, and a latent image corresponding to the laser light is formed on the photosensitive drum.

  Developer is attached to the latent image portion of the photosensitive drum by the developing unit, and at the timing synchronized with the start of laser light irradiation, the recording paper is fed from the paper feeding cassette and conveyed to the transfer unit, and is attached to the photosensitive drum. The developed developer is transferred to recording paper. The recording paper to which the developer has been transferred is conveyed to the fixing unit, and the developer is fixed to the recording paper by the heat and pressure of the fixing unit. The recording paper that has passed through the fixing unit is discharged by a discharge roller, and the sorter stores the discharged recording paper in each bin and sorts the recording paper.

  The image processing circuit 136 includes various circuits such as a large-capacity image memory, an image rotation circuit, a resolution scaling circuit, and an encoding / decoding circuit such as MH, MR, MMR, JBIG, and JPEG, and includes shading, trimming, and masking. Various image processing such as these can be executed.

  The hard disk 137 is a large-capacity recording medium connected by an I / F such as SCSI or IDE.

  The network I / F 138 realizes a network data link for connecting to a network line such as Ethernet (registered trademark) represented by 10BASE-T and 100BASE-T or a token ring.

  The formatter unit 139 receives data from an external device (for example, the client PC 104) via the PC I / F 142 or the network I / F circuit 138 including a parallel interface conforming to IEEE 1284, and a serial interface such as USB. The formatter unit 139 creates image data from the received data (for example, PDL (Page Description Language)), performs image processing by the image processing circuit 136, and executes rendering for printing by the printer 135.

  The fax unit 140 is a fax I / F circuit that is connected to a telephone line and includes circuits such as an NCU (Network Control Unit) and a MODEM (Modulator / DEModulator).

  The fax unit 140 performs image processing on the image data read by the scanner 134 by the image processing circuit 136 and transmits the image data to another FAX apparatus via a telephone line. On the other hand, the fax unit 140 receives data transmitted from another FAX apparatus, performs image processing with the image processing circuit 136, and prints it with the printer 135.

  The scanner 134, the printer 135, the image processing circuit 136, the formatter unit 139, and the fax unit 140 are connected by a high-speed video bus different from the CPU bus 141 from the CPU 130, and are configured to transfer image data at high speed. .

  The image data read by the scanner 134 is subjected to image processing by the image processing circuit 136, and the image data after the image processing is operated to be printed by the printer 135, thereby realizing a copy function.

  Also, the image data read by the scanner 134 is subjected to image processing by the image processing circuit 136 and transmitted from the network I / F 138 to the network, thereby realizing a Send (data transfer / file transfer) function. Further, the image processing circuit 136 creates an image according to RFC2301, and transmits and receives data using an electronic mail protocol, thereby realizing the IFAX function.

  Next, the configuration of the network program owned by MFP 100 will be described with reference to FIG.

  FIG. 3 is a diagram illustrating the configuration of the network program owned by the MFP according to the first embodiment of the present invention.

  The configuration of the network program is roughly divided into three layers: an IP layer 200, a TCP / UDP layer 201, and an application layer 202.

  Here, IP is an abbreviation for “Internet Protocol”, TCP is a “Transmission Control Protocol”, and UDP is an abbreviation for “User Datagram Protocol”.

  The IP layer 200 is an Internet protocol layer that provides a service for sending and receiving messages in cooperation with a relay node such as a router from a source host to a destination host.

  The IP layer 200 manages the address of the transmission destination of data and the address of the destination of data reception, and executes a routing function for managing the route in the network to the destination host according to the address information. is doing.

  The TCP / UDP layer 201 is a transport layer that provides a service for delivering a message from a transmission application process to a reception application process.

  TCP is a connection-type service, and guarantees high communication reliability. On the other hand, UDP is a connectionless service and does not guarantee reliability.

  The application layer 202 defines a plurality of protocols. Examples of the protocols include the following.

  There is File Transfer Protocol (FTP) which is a file transfer service. There is also SNMP, which is a network management protocol. In addition, there is LPD which is a server protocol for printer printing. In addition, there is HTTPd which is a WWW (World Wide Web) server protocol.

  In addition, there is Simple Mail Transfer Protocol (SMTP) which is an e-mail transmission / reception protocol. There is also a mail download protocol POP3 (Post Office Protocol-Version 3). In addition, there is a Lightweight Directory Access Protocol (LDAP) that is a protocol for accessing a directory database that manages a user's e-mail address and the like. In addition, there is a Kerberos authentication program defined in RFC1510.

  Next, an operation screen example of the operation unit 133 of the MFP 100 will be described with reference to FIG.

  FIG. 4 is a destination table registration screen for storing transmission destination information of the MFP according to the first embodiment of the present invention.

  In this destination table registration screen, for example, various destinations such as the IFAX destination of the MFP 101 can be registered.

  In the destination table registration screen, the transmission type field 250 is an item for determining how to transmit to the transmission destination. This is composed of, for example, a pull-down menu, and one of FAX, IFAX, Email, and File can be selected. Here, IFAX is selected in the transmission type field 250.

  When IFAX is selected, information on address, via server, resolution, paper size, and compression method is displayed.

  The address field 251 is an item for inputting an address. Here, in the address field 251, ifax @ copy2. xyz. co. jp is input.

  The server via designation field 252 is a switch for selecting whether to send data to the mail server at the time of transmission and to transmit from the mail server to the target MFP 101 or directly to the MFP 101. Here, “No” indicating that the mail server is not passed is set. On the other hand, when going through the mail server, “Yes” is set.

  If the destination is via the Internet, there is a relay node such as a firewall, so direct transmission is not possible. However, if the destination is on the same network, send it without imposing a load on the mail server. Can do.

  The resolution designation fields 253 to 256 are switches that can designate a resolution that the MFP 101 can receive.

  The resolutions of 200 × 100 dpi and 200 × 200 dpi cannot be selected because they are usually resolutions that can be received by any device with IFAX. On the other hand, with respect to other resolutions, each time the corresponding field is operated, the display state is reversed to black and white, and the black display field indicates that the resolution is selected.

  4 shows that the resolution designation field 254 and the resolution designation field 255 are selected, and the MFP 101 can receive the resolutions of 200 × 400 dpi and 400 × 400 dpi.

  Here, for example, at the time of scanning, the MFP 101 cannot receive an image scanned at 600 × 600 dpi as it is. Therefore, in this case, the scanned image is converted in resolution to 400 × 400 dpi, which is the highest resolution that the MFP 101 can receive.

  Paper size designation fields 257 and 258 are switches for designating paper sizes that can be received by the MFP 101. Here, the paper size A4 cannot be selected because it is normally a resolution that can be received by any device.

  Here, since the MFP 101 can receive B4 and A3 size images, the paper size designation fields 257 and 258 are selected.

  Here, for example, at the time of scanning, an image read in A3 size is transmitted to the MFP 101 as an A3 size image. However, if the receiving side cannot receive an A3 size image, it is set to the maximum paper size that can be received by the receiving side. Send it after scaling.

  Compression method designation fields 259 and 260 are switches for selecting a compressed image format that can be received by the MFP 101. Here, it is possible to specify the MR or MMR system. In the case of a document image using characters or the like, the compression rate is high in the order of MH <MR <MMR.

  In addition, the MH system cannot be selected because it can be normally received by any device.

  Here, since the MFP 101 can receive MR and MMR images, the compression method designation fields 259 and 260 are selected.

  The MFP 101 transmits an MMR image with a high compression rate. If the receiver cannot receive an MMR image, the image is transmitted after being compressed to the compression method with the maximum compression rate that can be received by the receiving side. .

  In the destination table registration screen, when various settings are completed and the settings are confirmed, by operating the OK button 270, various setting values are stored as a destination table in the RAM 123, for example. On the other hand, when canceling the setting operation, various setting values can be reset by operating the cancel button 271.

  Next, a configuration example of the e-mail data according to the first embodiment will be described with reference to FIG.

  FIG. 5 is a diagram showing a configuration example of the e-mail data according to the first embodiment of the present invention.

  Here, a configuration of e-mail data when an image scanned by MFP 100 is attached to e-mail and transmitted to MFP 101 is shown.

  In the Date field 300, time information transmitted by the MFP 100 is input. In the From field 301, the e-mail address of the MFP 100 is input. In the To field 302, the e-mail address of the MFP 101 is input. In the Subject field 303, a character string “image” is input.

  The Disposition-Notification-To field 304 is a field for designating a mail address at which the MFP 100 requests delivery confirmation and sends a delivery confirmation mail (MDN data). Here, the mail address of MFP 100 is input.

  A Message-Id field 305 is a number indicating an ID unique to the mail. This is composed of data including a mail address and time data so that a mail with the same number does not exist. In the MIME-Version field 306, the MIME version number is input.

  The Content-Type field 307 indicates that the e-mail data is divided into a plurality of blocks by the character string “------_ 422E51E54FF704D75EF8_”.

  Fields 310 to 316 are one block. The field 311 indicates that this part is a character string written in Japanese JIS code, and the field 314 is a data character string, that is, the body of the e-mail data.

  The field 316 to 330 is another block, and the information in the fields 317 to 319 indicates that this part is a TIFF image file having a file name “GS2005.tif”. The data in the fields 321 to 328 indicates that this file is data obtained by BASE64 encoding.

  Next, a sequence flow based on the SMTP protocol when directly transmitting the e-mail data of FIG. 5 according to the first embodiment of the present invention from the MFP 100 to the MFP 101 will be described with reference to FIG.

  FIG. 6 is a diagram showing a sequence flow of the SMTP protocol according to the first embodiment of the present invention.

  As shown in FIG. 4, in the destination table of the MFP 100, when transmitting from the MFP 100 to the MFP 101, the server-directed specification field 252 indicates that direct transmission is possible without going through the mail server. "Is set.

  For this reason, when transmitting to the MFP 101, the MFP 100 performs an SMTP connection (400) directly to the MFP 101.

  The SMTP-connected MFP 101 returns a character string (401) including domain name information.

  When the MFP 100 issues an EHLO command (402), the MFP 101 notifies the SMTP extension command supported by the MFP 101 together with a character string starting from “250-” (403).

  Specific SMTP extended commands (commands indicating functions of the MFP 101) correspond to 404 to 406. Here, it is assumed that the MFP 101 has a reception function for receiving 8-bit e-mail data, an encryption function for encrypting a communication path using TLS encryption, and a direct response function for directly replying MDN.

  Therefore, in this case, the MFP 101 transmits to the MFP 100 an 8BITMIME command (404) indicating a reception function of 8-bit e-mail data, and a STARTTLS command (405) indicating a communication path encryption function using TLS encryption. Furthermore, the MFP 101 transmits a DIRECTMDN command (406) indicating the MDN direct response function (response method) to the MFP 100.

  Note that the MFP 101 has a switch of “Respond directly to MDN” / “Do not reply” as a device setting. Therefore, when the MDN direct response function is provided, the MDN direct response is executed in response to the DIRECT MDN command (407) from the MFP 100 only when “Yes” is set. On the other hand, when “NO” is set, the direct response of the MDN is not executed in response to the DIRECTMDN command (407) from the MFP 100.

  Here, the DIRECTMDN command (407) from the MFP 100 is a command for requesting an MDN direct response. Further, the direct response of the MDN means that the MDN is directly returned to the transmission destination without going through the mail server.

  In addition, when the destination table of the MFP 100 is registered in the destination table in the MFP 101, the setting contents (“pass / do not pass through the server”) of the via-server designation field 252 (FIG. 4) can be acquired from the destination table. It is. Therefore, in such a case, whether or not the MDN direct reply can be executed may be determined according to the setting contents. That is, when “not via server” is set in the setting content, a direct response of MDN may be executed.

  Returning to the description of FIG.

  When the DIRECTMDN command (407) is normally received from the MFP 101, the MFP 101 returns a normal response message (408) starting from “250”.

  Next, the MFP 100 transmits a MAIL command (409) indicating the mail sender to the MFP 101. When the MFP 101 normally receives this, the MFP 101 returns a normal response message (410) starting from “250”. Next, the MFP 100 transmits an RCPT command (411) indicating the mail recipient. When the MFP 101 normally receives this, the MFP 101 returns a normal response message (412) starting from “250”.

  Next, after transmitting a DATA command (413) indicating that e-mail data is to be transmitted from MFP 100, e-mail data (300 to 329 in FIG. 5) is transmitted. Thereafter, “.” (414) indicating the end of the e-mail data is transmitted.

  When the e-mail data is normally received from the MFP 100, the MFP 101 returns a normal response message (415) starting from “354”.

  Next, the MFP 100 transmits a QUIT command (416) for disconnecting the connection. In response, the MFP 101 returns a message (417) starting from “221”.

  With the above processing, the SMTP connection between the MFP 100 and the MFP 101 ends.

  Next, SMTP reception processing by the SMTP reception function of the MFP 101 will be described with reference to FIG.

  FIG. 7 is a flowchart showing SMTP reception processing according to the first embodiment of the present invention.

  Note that the SMTP reception here may be, for example, receiving e-mail data transmitted by SMTP from the MFP 100 or the client PC 104.

  When power is supplied, the SMTP reception function is activated, and a connection waiting state is entered in step S501.

  When the SMTP connection is started, the process proceeds from step S501 to step S502, and a connection response reply process (401 in FIG. 6) for returning an SMTP connection response operates.

  After the connection response is returned, the received command is examined, and it is determined in step S503 whether the command is an EHLO command. If there is an EHLO command (YES in step S503), the process proceeds to step S506. On the other hand, if it is not an EHLO command (NO in step S503), it is determined in step S504 whether it is a HELO command.

  If it is a HELO command (YES in step S504), the process proceeds to step S515. On the other hand, if it is not a HELO command (NO in step S504), the process proceeds to step S505, and a new command reception is waited for as a command error.

  If the received command is a HELO command in step S504, a HELO command response return process is executed in step S515, and the process proceeds to step S516.

  In step S503, if the received command is an EHLO command, in step S506, a response return process for the EHLO command is executed with a message including the SMTP extended function included in the own device as an EHLO command response.

  The message here is 8BITMIME, STRTTLS, DIRECTMDN, etc. shown in 404 to 406 in FIG.

  Next, a command that can be generated by the SMTP extended function of the own device is investigated. First, in step S507, it is determined whether it is an 8BITMIME command. If it is not an 8BITMIME command (NO in step S507), the process proceeds to step S509. If the command is an 8BITMIME command (YES in step S507), the process advances to step S508 to execute an OK reply process in which a character string “250 OK” is returned.

  In step S509, it is determined whether the command is a DIRECTMDN command. If it is not a DIRECTMDN command (NO in step S509), the process proceeds to step S512. On the other hand, if the command is a DIRECTMDN command (YES in step S509), the process advances to step S510 to execute an OK reply process in which a character string “250 OK” is returned. In step S 511, the IP address of the issuer that issued the connection request is stored in the RAM 132.

  In step S512, it is determined whether the command is a STRTTLS command. If it is not a STRTTLS command (NO in step S512), the process proceeds to step S516. On the other hand, if the command is a STRTTLS command (YES in step S512), the process proceeds to step S513, and an OK reply process for returning a character string of “250 OK” is executed. In step S514, TLS encryption processing is executed.

  In step S516, MAIL command processing is executed. This is because the mail address information of the sender set in the MFP 101 is received by the MAIL command (409 in FIG. 6) and a response to the MAIL command (410 in FIG. 6) that is a character string starting from “250”. Send.

  In step S517, RCPT command processing is executed. This receives an RCPT command (411 in FIG. 6) including the mail address information of the transmission destination, and transmits an RCPT command response (412 in FIG. 6) consisting of a character string starting from “250”.

  In step S518, DATA command processing is executed. This receives a DATA command (413 in FIG. 6) indicating that the e-mail data in FIG. 5 is to be transmitted. Thereafter, the next e-mail data (300, 329, and 414 in FIG. 6) is received, and a DATA command response that is a character string starting from “354” is transmitted (415 in FIG. 6).

The end of the e-mail data is determined by detecting a character string 414 consisting only of “.”, And a series of operations ends. In step S519, a QUIT command process is executed. This terminates transmission, receives a QUIT command (416 in FIG. 6) for disconnecting, returns a QUIT command (417 in FIG. 6) starting from the character string “221”, and disconnects the SMTP connection. When the process is completed, the SMTP reception ends.

  Thereby, the MFP 101 receives e-mail data shown in FIG. 5, for example. Then, the mail body data (314) in the e-mail data is converted from JIS code to text information of SJIS code, and then rasterized and converted to image data.

  The image data portion (321 to 328) in the e-mail data is decoded in the BASE64 format and converted into a TIFF file. Next, image data for each page is cut out from the TIFF file, and image decoding processing is performed on the cut out data. Then, when the image decoding process for all pages is completed normally, the MDN data shown in FIG. 8 is created.

  Next, a configuration example of the MDN data according to the first embodiment will be described with reference to FIG.

  FIG. 8 is a diagram illustrating a configuration example of the MDN data according to the first embodiment of the present invention.

  A portion from 600 to 607 in FIG. 8 is a mail header of this mail.

  In the Date field 600, time information at the time of data transmission is input. In the From field 601, the e-mail address of the MFP 101 that is the transmission source of the mail is input. In the Subject field 602, a character string “Message Disposition Notification” is input.

  In the To field 603, the destination set in the Disposition-Notification-To field 304 of the mail attached with the image described in FIG. 5 is set. As a result, the MDN data is transmitted to this destination.

  The Message-ID field 604 is a character string including the transmission time, host name, domain name, and user name information, and is created so that no other data with the same ID exists.

  In the MIME-Version field 605, a MIME version number is input. In the Content-Type field 606, it is entered that this mail is a report type notification mail.

  In the field 607, it is input that the mail is delimited by the boundary of “xiSCzkWI5qcO + uiWI6qaM + ueTIB6”. Here, the fields are divided by fields 609, 615, and 622. The fields 610 to 614 are divided into the first part of the mail, and the fields 616 to 621 are divided into the second part of the mail.

  A field 610 indicates that the first portion is data in text format, and fields 612 and 613 are the data character strings.

  A field 616 indicates that the second part is a notification message, and a field 618 describes the host name and domain name of the MFP 101 that created this message.

  In the Original-Message-ID field 619, the Message-Id 304 of the mail attached with the image described in FIG. 5 is input, and it is possible to determine which mail is the notification mail.

  The Disposition field 620 indicates that this notification mail is automatically responded, and the result indicates that it has been processed normally.

  Next, an MDN transmission process for transmitting MDN data by the MFP 101 will be described with reference to FIG.

  FIG. 9 is a flowchart showing the MDN transmission processing according to the first embodiment of the present invention.

  This process starts when the MDN is transmitted.

  In step S701, referring to the contents of the DIRECTMDN command (407 in FIG. 4), it is determined whether or not “MDNDIRECT” is designated by the sender. If “MDNDIRECT” is specified (YES in step S701), the process advances to step S702, the MDN data of FIG. 8 is transmitted to the destination corresponding to the IP address stored in step S511, and the process ends.

  On the other hand, if “MDNDIRECT” is not designated (NO in step S701), the process proceeds to step S703, MDN data is transmitted to the mail server (for example, the server 103), and the process is terminated. The MDN data transmitted to the mail server is finally transmitted via the mail server to the destination of the Disposition-Notification-To of the mail attached with the image described in FIG.

  As described above, according to the first embodiment, in an environment in which communication by the electronic mail protocol is possible without going through the mail server, the MDN data for delivery confirmation is also communicated without returning the mail server. On the other hand, in an environment in which communication is not possible without going through the mail server, MDN data for delivery confirmation is communicated through the mail server.

  As described above, the MDN data can be reliably transmitted by adaptively selecting the transmission / reception path of the MDN data according to the environment between the apparatuses. In addition, the transmission side can determine whether or not the transmitted mail and the image data attached thereto have normally arrived at the reception side.

<Embodiment 2>
In the second embodiment, an application example of the MDN transmission process of the first embodiment will be described.

  FIG. 10 is a flowchart showing the MDN transmission processing according to the second embodiment of the present invention.

  This process starts when the MDN is transmitted.

  In step S801, referring to the contents of the DIRECTMDN command (407 in FIG. 4), it is determined whether or not “MDNDIRECT” is designated by the sender. If “MDNDIRECT” is designated (YES in step S801), the process advances to step S802. In step S802, the DNS server (server 103) is inquired about the destination of the Disposition-Notification-To of the mail attached with the image described in FIG. 5, and the IP address of the destination to be transmitted is acquired.

  At this time, the DNS server acquires the IP address of the destination using the A record of the HOST name or the MX (Mail eXchange) record dedicated for mail delivery.

  In step S803, the MDN data in FIG. 8 is transmitted to the destination corresponding to the IP address acquired in step S802 using the SMTP protocol, and the process ends.

  On the other hand, if “MDNDIRECT” is not designated (NO in step S801), the process proceeds to step S804, where the MDN data is transmitted to the mail server (for example, the server 103), and the process ends. The MDN data transmitted to the mail server is finally transmitted via the mail server to the destination of the Disposition-Notification-To of the mail attached with the image described in FIG.

  As described above, according to the second embodiment, the transmission destination of the MDN data is specified by inquiring the transmission destination of the MDN data to the DNS server. As a result, even when the transmission destination of the MDN data cannot be specified from the e-mail data, the MDN data can be reliably transmitted to the correct destination.

<Embodiment 3>
In the first embodiment, the MDN data request is transmitted to the transmission destination according to the SMTP protocol. However, the present invention is not limited to this. For example, information indicating a request for MDN data may be described in the e-mail data.

  Therefore, in the third embodiment, a configuration in the case of using an e-mail in which information indicating the request for MDN data is described will be described.

  FIG. 11 is a diagram showing a configuration example of e-mail data according to the third embodiment of the present invention.

  Here, a configuration of e-mail data when an image scanned by MFP 100 is attached to e-mail and transmitted to MFP 101 is shown.

  In the Date field 900, time information transmitted by the MFP 100 is input. In the From field 901, the e-mail address of the MFP 100 is input. In the To field 902, the e-mail address of the MFP 101 is input. In the Subject field 903, a character string “image” is input.

  A Disposition-Notification-To field 904 is a field for designating a mail address at which the MFP 100 requests delivery confirmation and sends a delivery confirmation mail (MDN data). Here, the mail address of MFP 100 is input.

  An X-MDNDIRECT field 905 indicates that the sender wishes to have the delivery confirmation mail sent directly to the MFP 100 as a transmitter without passing through the mail server.

  A Message-Id field 906 is a number indicating an ID unique to the mail. This is composed of data including a mail address and time data so that a mail with the same number does not exist. In the MIME-Version field 907, the MIME version number is entered.

  The Content-Type field 908 indicates that the e-mail data is divided into a plurality of blocks by the character string “------_ 422E51E54FF704D75EF8_”.

  Fields 911 to 916 are one block. Field 911 indicates that this part is a character string written in Japanese JIS code, and field 915 is a data character string.

  The portion of fields 917 to 931 is another block, and the information of fields 917 to 920 indicates that this portion is a TIFF image file having a file name “GS2005.tif”. The data in the fields 922 to 929 indicates that this file is data obtained by BASE64 encoding.

  In the e-mail data of the third embodiment, in addition to the configuration of the e-mail data of the first embodiment, a request for a delivery confirmation mail is explicitly described.

  Next, e-mail data analysis processing when the MFP 101 receives the e-mail data of FIG. 11 will be described with reference to FIG.

  FIG. 12 is a flowchart showing e-mail data analysis processing according to the third embodiment of the present invention.

  When the e-mail data is received, image extraction processing is executed in step S951. Here, the mail body data (915 in FIG. 11) is converted from the JIS code to the text information of the SJIS code, and then rasterized and converted to image data.

  Further, the image data portion (922 to 929 in FIG. 11) in the e-mail data is decoded in the BASE64 format and converted into a TIFF file. Next, image data for each page is cut out from the TIFF file, and image decoding processing is performed on the cut out data.

  Next, in step S952, it is determined whether or not a destination exists in the Disposition-Notification-To field (904 in FIG. 11).

  If the destination exists (YES in step S952), the process proceeds to step S953, and destination information (here, ifax@copy1.xyz.co.jp) for transmitting the MDN data is extracted. In step S954, MDN data for the destination information is created and transmitted.

  On the other hand, if the destination does not exist (NO in step S952), the process advances to step S955 to determine whether or not the X-MDNDIRECT field (905 in FIG. 11) exists.

  If it is determined in step S952 that there is no destination in the Disposition-Notification-To field and the process proceeds to step S955, the process proceeds to step S959. This is because, in the absence of the Disposition-Notification-To field, no MDN is requested, so that the X-MDNDIRECT field does not exist in principle. In other words, a Disposition-Notification-To field is added when an MDN request is made.

  If the X-MDDNDIRECT field exists (YES in step S955), the process advances to step S956 to inquire the DNS server about the destination of the Disposition-Notification-To, and obtain the IP address of the destination to be transmitted.

  At this time, the DNS server acquires the IP address of the Disposition-Notification-To by using the A record of the HOST name or the MX (Mail eXchange) record dedicated for mail delivery. In step S957, the MDN data is transmitted to the destination corresponding to the IP address acquired in step S956 using the SMTP protocol.

  On the other hand, if the X-MDNDIRECT field does not exist (NO in step S955), the MDN data is transmitted to the mail server (eg, server 103) in step S958.

  In step S959, it is determined whether there is a print setting for the image data extracted from the received e-mail data. If there is a print setting (YES in step S959), the process advances to step S960 to execute printing according to the print setting. On the other hand, if there is no print setting (NO in step S959), the process advances to step S961 to determine whether there is a transfer setting.

  If there is a transfer setting (YES in step S961), the process proceeds to step S962, and the transfer is executed according to the transfer setting. Note that the transfer destinations by this transfer setting include file transfer destinations such as FAX, IFAX, FTP, and SMB.

  On the other hand, if there is no transfer setting (NO in step S961), the process ends.

  Note that the presence / absence of print settings and transfer settings in step S959 and step S961 is determined according to attribute information set in the e-mail data, for example, when e-mail data is received.

  In addition, although the e-mail receiving method has been described using SMTP and POP reception, it may be configured to receive e-mail using another predetermined communication protocol such as IMAP.

  As described above, according to the third embodiment, the MDN data request is not transmitted according to the SMTP protocol, but the information indicating the MDN data request is described in the e-mail data.

  According to this configuration, for example, if a request for MDN data is transmitted directly to a destination according to the SMTP protocol and is erroneously transmitted via a mail server, the MDN data request may be lost. It becomes possible to prevent sex.

  Although the embodiment has been described in detail above, the present invention can take an embodiment as, for example, a system, apparatus, method, program, or storage medium. Specifically, the present invention may be applied to a system composed of a plurality of devices, or may be applied to an apparatus composed of a single device.

  The present invention can also be realized by executing the following processing. That is, software (program) that realizes the functions of the above-described embodiments is supplied to a system or apparatus via a network or various storage media, and a computer (or CPU, MPU, or the like) of the system or apparatus reads the program. It is a process to be executed.

Claims (8)

A receiving device for receiving e-mail via a network,
Receiving means for receiving e-mail from the transmitting device;
A determination unit that determines whether or not it is possible to transmit a delivery confirmation result related to the received e-mail without going through a mail server when the receiving unit receives the e-mail;
As a result of the determination by the determination means, when it is determined that the delivery confirmation result regarding the received electronic mail can be transmitted without going through the mail server, the delivery confirmation result is sent through the mail server. Transmission means for transmitting without making
A receiving apparatus comprising: If it is determined that it is not possible to transmit the delivery confirmation result regarding the received e-mail without passing through the mail server as a result of the determination by the determination unit, the transmission unit determines the delivery confirmation result, The receiving apparatus according to claim 1, wherein the receiving apparatus transmits the mail via a mail server. Request information for requesting the receiving device to transmit the delivery confirmation result without passing through a mail server as one of commands transmitted and received by a communication protocol used when the receiving unit receives an e-mail. The determination means determines that it is possible to transmit a delivery confirmation result relating to the received electronic mail without going through a mail server. The receiving device described in 1. The receiving apparatus according to claim 3, wherein the communication protocol used when the receiving unit receives an electronic mail is the SMTP protocol. When the e-mail received by the receiving unit includes request information for requesting the receiving device to transmit the delivery confirmation result without going through a mail server, the determining unit The receiving apparatus according to claim 1 or 2, wherein it is determined that a delivery confirmation result relating to the received electronic mail can be transmitted without going through a mail server. For each of a plurality of external devices including the transmission device, further comprising a registration means for registering a setting indicating whether to transmit an e-mail without going through a mail server,
The determination unit, when a setting indicating that an e-mail is transmitted to the transmitting device without going through a mail server is registered in the registration unit, a delivery confirmation result regarding the received e-mail The receiving apparatus according to claim 1 or 2, wherein it is determined that transmission is possible without going through a mail server. A method of controlling a receiving device that receives an email via a network,
A receiving step for receiving an e-mail from a transmitting device;
A determination step of determining whether it is possible to transmit a delivery confirmation result related to the received e-mail without going through a mail server when an e-mail is received in the receiving step;
As a result of the determination in the determination step, when it is determined that the delivery confirmation result regarding the received electronic mail can be transmitted without going through the mail server, the delivery confirmation result is sent through the mail server. A transmission step for transmitting without
A method for controlling a receiving apparatus.   The program for making a computer perform the control method of the receiver of Claim 7.

Images