JP2008099162A - Undelivered mail notifying system, undelivered mail notification method and undelivered notification program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To improve the level of a mail service by notifying a receiver user of undelivered mail, which is not transmitted, at appropriate timing. <P>SOLUTION: Undelivered mail notification systems 1 and 2, for notifying a receiver user of undelivered mail which is not transmitted, are provided with an error management means 23 for counting transmission errors, for every mail address; a notification means 15 for notifying the user of a first message when a mail address whose error count does not exceed a predetermined threshold, and for notifying the user of a second message, when the error count of a mail address exceeds threshold; and a control means 13 for controlling mail transmission to the mail address whose error count exceeds the threshold. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a non-reachable mail notification technique for notifying a transmission destination user of an unreachable mail whose transmission has failed.

There are Web systems (Web sites) that provide various services to registered users via the Internet. Web systems often use electronic mail (hereinafter “mail”) as means for contacting registered users. By using e-mail, various types of information can be transmitted to registered users who do not access the Web system. In order to perform the notification by the e-mail, the Web system holds the e-mail address of the registered user. Patent Document 1 describes an automatic maintenance system that automatically maintains a database of email addresses.
JP 2004-5120 A

  Now, there are cases where an email sent from a Web system to a registered user does not reach the user for some reason. For example, when the mailbox on the receiving side cannot be used, the mail address does not exist, or the user changes the mail address.

  By receiving the mail, the user can know that the Web system has transmitted the mail. On the other hand, if the mail does not arrive, it is difficult for the user to know that the Web system has transmitted the mail.

  The present invention has been made in view of the above circumstances, and an object of the present invention is to notify a destination user of unreachable mail that has failed to be transmitted at an appropriate timing, and to improve the level of mail service. is there.

  In order to solve the above problems, the present invention is an unreached mail notification system for notifying unreached mail that has failed to be transmitted, and for each mail address, an error management means for counting the number of errors that have failed to be transmitted; A notification means for notifying a first message if the mail address does not exceed a predetermined threshold, and a second message if the mail address exceeds the threshold, and the error count is the threshold. Control means for controlling mail transmission to mail addresses exceeding.

  The present invention is also a non-reachable mail notification method for notifying unsuccessful mail that has failed to be transmitted, which is performed by the unreachable mail notification system. A count step for counting the number of times, a control step for controlling mail transmission to an email address in which the number of errors counted in the count step exceeds a predetermined threshold, and an email address in which the number of errors does not exceed a predetermined threshold Performs a notification step of notifying the first message and notifying the second message when the number of errors exceeds the threshold.

  In addition, the present invention is an unreached mail notification program for notifying an unreachable mail that has failed to be transmitted, executed by the unreached mail notification system, wherein the unreachable mail notification system has failed to transmit for each mail address. An error management means for counting the number of times, a first message is notified when the number of errors does not exceed a predetermined threshold, and a second message is notified when the number of errors exceeds the threshold. And control means for controlling mail transmission to a mail address whose number of errors exceeds the threshold.

  In the present invention, the unreachable mail that has failed to be transmitted can be notified to the user at the transmission destination at an appropriate timing, and the level of the mail service can be improved.

  Embodiments of the present invention will be described below.

  FIG. 1 is an overall configuration diagram of an unreached mail notification system to which an embodiment of the present invention is applied. The unreachable mail notification system shown in the figure has a business server 1 and a mail server 2, provides various services to the user terminal 3, and transmits various mails to the user terminal 3.

  The user terminal 3 is a terminal used by a registered user who has registered user attribute information and a mail address in the business server 1. The user terminal 3 is connected to the business server 1 and the mail server 2 via a network 9 such as the Internet. Note that the user terminal 3 is connected to the network 9 using a network connection provider (not shown). The user terminal 3 includes a Web browser 31 that requests various processes from the business server 1 and a mail transmission / reception unit 32 that transmits and receives mail.

  The business server 1 shown in the figure includes a transmission instruction unit 11, a message generation unit 12, a control unit 13, an authentication unit 14, a notification unit 15, a mail address management DB 16, a user attribute management DB 17, a message DB 18, Have The transmission instruction unit 11 receives a mail transmission instruction from an in-house terminal (not shown), generates a mailing list, and sends a mail transmission request to the mail server 2. The message generation unit 12 generates a personal message (message to an individual) that is notified to a user who has failed to send mail.

  The control unit 13 performs transmission control for an email address that exceeds a predetermined threshold and failed to send email. The authentication unit 14 authenticates whether or not the user accessed from the user terminal 3 is a valid registered user. The notification unit 15 transmits the personal message generated by the message generation unit 12 to the user terminal 3.

  The mail address management DB 16 stores the mail address of each registered user. The user attribute management DB 17 stores attribute information such as the registered user's user ID, name, address, telephone number, and FAX number. The message DB 18 stores personal messages generated by the message generator 12.

  The illustrated mail server 2 includes a mail transmission unit 21, a transmission determination unit 22, an error management unit 23, an error extraction unit 24, and an error management DB 25. The mail transmission unit 21 receives a mail transmission request from the business server 1 and transmits a mail to each mail address set in the mailing list. The transmission determination unit 22 determines whether or not the mail transmission has been successful. The error management unit 23 counts the number of mail transmission errors for each mail address, and sets it in the error management DB 25. The error management DB 25 stores the number of errors of the mail address that caused a transmission error.

  FIG. 2 is a diagram illustrating an example of the error management DB 25.

  The illustrated error management DB 25 is a table-type database, and includes a mail address 251 in which mail transmission has failed, an error count 252, an error date 253, and an error code 254. The error code 254 is set with an error code transmitted from a destination mail server (for example, a provider mail server). Note that, as an error code of the present embodiment, a response code of SMTP (Simple Mail Transfer Protocol) is used.

  The business server 1, the mail server 2, and the user terminal 3 described above all include, for example, a CPU 901, a memory 902, an external storage device 903 such as an HDD, and an input device such as a keyboard and a mouse as shown in FIG. A general-purpose computer system including 904, an output device 905 such as a display or a printer, and a communication control device 906 for connecting to a network can be used. In this computer system, the CPU 901 executes a predetermined program loaded on the memory 902, thereby realizing each function of each device.

  For example, the functions of the business server 1, the mail server 2, and the user terminal 3 are the CPU 901 of the business server 1 in the case of the program for the business server 1, and the CPU 901 of the mail server 2 in the case of the program for the mail server 2, In the case of a program for the user terminal 3, it is realized by the CPU 901 of the user terminal 3 executing it. Note that the memory 902 or the external storage device 903 of the business server 1 is used for the mail address management DB 16, the user attribute management DB 17, and the message DB 18 of the business server 1. The error management DB 25 of the mail server 2 uses the memory 902 or the external storage device 903 of the mail server 2.

  Note that the unreached mail notification system of this embodiment includes a business server 1 and a mail server 2 (see FIG. 1). However, the unreached mail notification system may be realized by a single computer system in which the business server 1 and the mail server 2 are integrated.

  Next, an outline of processing according to the present embodiment will be described.

  FIG. 4 is a diagram schematically showing the processing of this embodiment.

  First, the user uses the user terminal 3 to register a mail address in the unreached mail notification system (mail address management DB 16) (S11). The unreached mail notification system broadcasts a mail such as a notification of a new service to each mail address registered in the mail address management DB 16 (S12). However, mail transmission may fail due to unknown email address, mail server mailbox overflow, account suspension, spam filtering by a provider, and the like.

  The unreachable mail notification system of the present embodiment counts the number of times mail transmission has failed (number of errors) for each mail address. Then, when the number of errors is from the second time to the fourth time, the unreached mail notification system notifies the user having the mail address of a personal message that the mail transmission has failed (S13). When the number of errors is the first time, there is a possibility of a temporary transmission error, and therefore, notification of personal messages is not performed in this embodiment. The personal message is displayed on a Web page displayed on the user terminal 3 when the user accesses the business server 1.

  Further, when the number of errors is the fifth, the unreached mail notification system notifies the user having the mail address of a personal message that the transmission of the mail is stopped (S14). The unreached mail notification system sets a transmission stop flag for the mail address in the mail address management DB 16. As a result, transmission of mail to the mail address is stopped.

  Then, the user re-registers a valid mail address in the unreached mail notification system (mail address management DB 16) using the user terminal 3 (S15). Thereafter, the unreachable mail notification system transmits mail to the re-registered mail address.

  In the present embodiment, the threshold of the number of errors for determining whether or not to stop the transmission of mail is “4 times”, and when the number of errors exceeds “5” and exceeds the threshold, Stop sending.

  Next, the mail transmission process (FIG. 4: S12) of this embodiment is demonstrated in detail.

  5 and 6 are flowcharts of the mail transmission process.

  In FIG. 5, the transmission instruction unit 11 of the business server 1 first receives mail text data and a subject (hereinafter referred to as “mail text data, etc.”) from an in-house terminal (not shown) (S21).

  Then, the transmission instructing unit 11 creates a mailing list and a mail transmission stop list with reference to the mail address management DB 16 in which the registered user's mail address is registered (S22). In other words, the transmission instructing unit 11 creates a mailing list by extracting mail addresses without a transmission stop flag from the mail address management DB 16 and extracts mail addresses with a transmission stop flag from the mail address management DB 16. To create a transmission stop list.

  Then, the transmission instructing unit 11 transmits the mail body data received in S21 and the mailing list created in S12 to the mail server 2 (S23). Further, the transmission instruction unit 11 transmits the transmission stop list to a system administrator terminal or a branch office terminal (not shown) (S24). The system administrator manages the number of problematic email addresses based on the transmission suspension list. In addition, the sales office performs follow-up such as confirmation and inquiry of the mail address to the user of the mail address set in the transmission suspension list.

  Then, the mail transmission unit 21 of the mail server 2 receives the mail body data and the mailing list. Then, the mail transmitting unit 21 transmits mails including body data and the like via the network 9 with each mail address set in the mailing list as a transmission destination (S25). Note that the mail transmitting unit 21 retries (retransmits) a mail that has failed to be transmitted at a predetermined time interval for a predetermined time.

  Then, the transmission determination unit 22 determines whether the mail transmission has succeeded or failed for each mail address transmitted in S25 (S26). That is, the transmission determination unit 22 determines that the mail transmission has failed for the mail address that received the error message, and determines that the mail transmission has succeeded for the mail address that did not receive the error message. In addition, the transmission determination part 22 determines with the mail transmission of the said mail address having been successful, when mail transmission is successful while the mail transmission part 21 is retrying predetermined time. In addition, when an error message is received after retrying for a predetermined time, the transmission determining unit 22 determines that the mail transmission of the mail address has failed. Each mail address for which mail transmission has failed (S26: NO) will be described with reference to FIG.

  Then, the error management unit 23 initializes the number of errors of each mail address (S26: YES) that has been successfully transmitted by mail (S27). That is, the error management unit 23 determines whether or not the mail address exists in the error management DB 25 for each of the mail addresses, and if it exists, clears the error count of the mail address to “0”. Further, the error management unit 23 may delete the record of the mail address from the error management DB 25 instead of clearing the number of errors.

  Even if an e-mail address has failed to be sent for some reason in the past and the number of errors is set, the cause of the failure has been removed because the e-mail has been successfully sent at this time. Therefore, by clearing the previous number of errors at the timing of successful mail transmission, it is possible to prevent the number of errors from being accumulated unnecessarily, and to set an appropriate number of errors according to the current transmission status it can.

  Then, the transmission determination unit 22 creates a transmission success list that is a list of each mail address that has been successfully transmitted, and transmits it to the business server 1 (S28).

  The message generation unit 12 of the business server 1 receives the transmission success list. If the personal message corresponding to each mail address in the successful transmission list is stored in the message DB 18, the message generator 12 deletes the personal message (S29). As a result, it is possible to prevent an unnecessary personal message from being output to a user who has successfully transmitted the mail.

  The business server 1 registers each mail address set in the transmission success list in a transmission history DB (not shown) together with user attribute information acquired from the user attribute management DB 17 and a transmission date and time for use in marketing or the like. Also good.

  FIG. 6 is a flowchart showing the processing of each mail address (S26: NO) that failed to be sent. The error management unit 23 of the mail server 2 receives the error message after the retry is completed, and if the error message requires notification to the system administrator, the error message is transferred to the system administrator terminal (S31). The error management unit 23 determines whether or not notification to the system administrator is necessary based on the error code included in the error message. For example, in the case of an error message that is rejected from the provider by the spam filter, the error management unit 23 determines that notification to the system administrator is necessary.

  Then, the error management unit 23 determines whether or not the mail address included in the received error message exists in the error management DB 25 (S32). If it exists in the error management DB 25 (S32: YES), the error management unit 23 acquires the error date (previous error date) of the mail address set in the error management DB 25, and the current date from the acquired previous error date. It is determined whether or not a predetermined period (for example, 30 days) has passed (S33). When the predetermined period has not elapsed (S33: NO), the process proceeds to S35.

  If the predetermined period has elapsed (S33: YES), the error management unit 23 considers that the cause of the transmission error has been temporarily resolved within the predetermined period, and the error of the mail address set in the error management DB 25 The number of times is initialized (that is, cleared to “0”) (S34). In the present embodiment, for example, mail is transmitted to registered users at a rate of about twice a week. Therefore, if the cause of the transmission error has not been eliminated, the period from the previous error date to the current date will not exceed a predetermined period (30 days).

  Then, the error management unit 23 counts up the number of errors of the mail address in the error management DB 25 (S35). Further, the error management unit 23 updates the error date of the mail address in the error management DB 25 to the current date, and updates the error code included in the received error message.

  On the other hand, when it does not exist in the error management DB 25 (S32: NO), the error management unit 23 adds a record of the mail address specified in the error message to the error management DB 25 (S36). The error management unit 23 sets “1” as the number of errors in the record, sets the current date as the date, and sets the error code included in the error message as the error code.

  The error management unit 23 performs the above-described processing from S31 to S36 for each mail address for which mail transmission has failed. Then, the error extraction unit 24 extracts a record in which “5” is set as the number of errors from the error management DB 25 at a predetermined timing such as a night batch, and creates a stop error file. The error extraction unit 24 extracts records in which “2”, “3”, and “4” are set as the number of errors from the error management DB 25, and creates a notification error file. Then, the error extraction unit 24 transmits the stop error file and the notification error file to the business server 1 (S37).

  The business server 1 receives the stop error file and the notification error file, and performs processing according to each error file.

  For the error file for notification (number of errors: 2 to 4), the message generator 12 generates a personal message for the user who has the mail address for each mail address of the error file, and stores it in the message DB 18. (S38). That is, the message generation unit 12 acquires a user ID, a name, and the like corresponding to each mail address from the user attribute management DB 17. Further, the message generation unit 12 acquires the code content of the error code of each mail address included in the error file from an error code table stored in advance in the memory of the business server 1 or an external storage device.

  FIG. 7 is a diagram illustrating an example of an error code table. In the illustrated example, an SMTP response code and the content of the response code are set.

  Then, the message generation unit 12 uses the information to notify each user who has an email address that has been transmitted twice to four times to notify that the email transmission has failed. Generate customized personal messages. The personal message includes a user ID as a search key, and includes a personal message title, an e-mail address, an error code content, and a personal message posting deadline. The message generator 12 sets a date obtained by adding a predetermined period (for example, 30 days) from the current date as the posting deadline. A specific personal message will be described later.

  Note that the message generation unit 12 deletes a personal message whose posting deadline has passed from the message DB 18 at a predetermined timing.

  For the error file for stoppage (number of errors: 5), the message generator 12 generates a personal message for the user who holds the mail address for each mail address of the error file, and stores it in the message DB 18 (S39). ). That is, the message generation unit 12 acquires a user ID, a name, and the like corresponding to each mail address from the user attribute management DB 17. In addition, the message generation unit 12 acquires the code contents of the error code of each mail address included in the error file from the error code table described above.

  Then, the message generation unit 12 generates a personal message that notifies each user who has an email address that has received a transmission error five times to stop sending emails based on these pieces of information. The personal message includes a user ID as a search key and includes a title of the personal message, a mail address, and an error code content. A specific personal message will be described later.

  Further, the control unit 13 adds a transmission stop flag to each mail address of the error file registered in the mail address management DB 16 (S30). As a result, in the mailing list generation process of S22 of FIG. 5, the mail address to which the transmission stop flag is added is not extracted, and thereafter, the mail is not transmitted.

  Next, the message notification process (FIG. 4: S13, S14) of this embodiment will be described in detail.

  FIG. 8 is a flowchart of the message notification process.

  The user logs in to a predetermined service of the business server 1 using the user terminal 3. The Web browser 31 of the user terminal 3 receives the user instruction and transmits an access request to the business server 1 via the network 9 (S51). The authentication unit 14 of the business server 1 authenticates whether or not the user is a valid user registered in the business server 1 using a user ID and a password included in the access request (S52).

  In the case of a legitimate registered user, the notification unit 15 of the business server 1 generates a top page (Web page) including the title of the personal message of the user who has requested access and transmits it to the user terminal 3 that is the request source (S53). That is, when the personal message having the user ID specified by the access request exists in the message DB 18, the notification unit 15 sets the title of the personal message in the personal message display area on the top page. The Web browser 31 of the user terminal 3 receives the top page from the business server 1 and displays it on an output device such as a display (S54).

  FIG. 9A shows an example of the top page displayed on the user terminal 3 when the mail transmission error is 2 to 4 times. In the personal message display area 91 on the top page shown in the figure, the title “Request for confirmation of mail address” of the personal message is displayed.

  FIG. 10A shows an example of the top page displayed on the user terminal 3 when the mail transmission error is 5 times. In the personal message display area 101 of the top page shown in the figure, the personal message title “Notification of mail service stop” is displayed.

  In order to display the content of the personal message, the user clicks on the title in which link destination information (for example, URL) is embedded. The Web browser 31 accepts the user's click and transmits a personal message display request to the business server 1 (S55).

  The notification unit 15 of the business server 1 receives a request from the user terminal 3 and acquires a personal message of the user ID from the message DB 18. And the notification part 15 produces | generates the web page in which the content of the acquired personal message was described, and transmits to the user terminal 3 (S56). The Web browser 31 of the user terminal 3 displays the personal message transmitted from the business server 1 on the output device (S57).

  FIG. 9B is an example of a personal message when the mail transmission error is 2 to 4 times. In the illustrated personal message, a mail address confirmation request, an error mail address, the content of the error code, the posting deadline of the personal message, and the like are displayed.

  FIG. 10B is an example of a personal message when the mail transmission error is 5 times. In the personal message shown in the figure, a mail service stop notification and a mail address re-registration request, an error mail address, an error content, and the like are displayed.

  The user who browsed the personal message confirms the mail address, and inquires of the provider depending on the error content. The user re-registers a valid e-mail address in the business server 1 when the e-mail address is registered in error and when the e-mail transmission is stopped in FIG.

  Personal messages with two to four transmission errors are stored in the message DB 18 until the posting deadline has passed. Therefore, the notification unit 15 notifies the user of the personal message until the posting deadline elapses. In addition, when the user re-registers the mail address before the posting period of 2 to 4 personal messages has elapsed, the message generation unit 12 performs 2 to 4 times of the user stored in the message DB 18. The personal message shall be deleted.

  Further, it is assumed that the personal message with five transmission errors is deleted from the message DB 18 at the timing when the user re-registers the mail address. Therefore, the personal message is notified to the user indefinitely until the user re-registers the mail address.

  When a plurality of personal messages are stored in the message DB 18 for one user ID, the notification unit 15 notifies the user in order from the latest personal message based on the creation date and time of the personal message. Shall.

  In the present embodiment described above, the number of errors in which mail transmission has failed is counted, and a personal message indicating that mail could not be transmitted is notified to a user whose mail address is two or more. In other words, in the present embodiment, an unreachable mail that has failed to be transmitted can be notified to a transmission destination user at an appropriate timing, and the level of mail service can be improved.

  In addition, the user who has been notified of the personal message confirms the mail address in error, and re-registers a valid mail address if it is registered by mistake. Thereby, a valid mail address can be registered in the business server 1.

  In the present embodiment, when the transmission error reaches 5 times (when the threshold is exceeded), the transmission of the mail to the mail address is stopped and a personal message that prompts the re-registration of a valid mail address is notified. . Thereby, useless mail transmission can be prevented and a valid mail address can be registered in the business server 1.

  In the present embodiment, a personal message including the content of the error type (error code) that caused the transmission error is notified. Thereby, the user can deal with the content of the error, such as inquiring of the provider.

  In this embodiment, the previous number of errors is initialized at the timing when the mail transmission is successful. As a result, it is possible to prevent the number of errors from accumulating unnecessarily, and to set an appropriate number of errors according to the current transmission state (state in which the cause of the failure has been removed).

  Also, in this embodiment, when counting up the number of errors of a mail address that failed to be transmitted, if a predetermined period has elapsed since the previous transmission error date, the count is performed after initializing the previous number of errors. Up. If the specified period has passed, it is considered that the cause of the mail transmission error has been resolved within that period, so it is possible to prevent the number of errors from accumulating and set an appropriate number of errors. can do.

  In addition, this invention is not limited to said embodiment, Many deformation | transformation are possible within the range of the summary. For example, in the above embodiment, when the mail transmission error is 2 to 5 times, the personal message is notified to the user who has accessed the business server 1, but the following processing may be performed in addition to this. . That is, the attribute information of the target user is extracted from the user attribute management DB 17, and if a mail address other than the mail address in error is registered, a personal message is described for the other mail address. It is also possible to send an e-mail. Further, when the FAX number of the user is registered in the user attribute management DB 17, a FAX in which a personal message is described in the FAX number may be transmitted. As a result, it is possible to notify a user who has a low access frequency to the business server 1 that an error has occurred in the mail transmission.

1 is an overall configuration diagram of an unreached mail notification system to which an embodiment of the present invention is applied. It is a figure which shows an example of error management DB. It is a figure which shows the hardware structural example of each apparatus. It is a figure which shows typically the process outline | summary of this embodiment. It is a flowchart of a mail transmission process. It is a flowchart of a mail transmission process. It is a figure which shows an example of an error code table. It is a flowchart of a message notification process. It is an example of a screen of a personal message (second to fourth transmission error). It is an example of a screen of a personal message (fifth transmission error).

Explanation of symbols

  1: business server, 11: transmission instruction unit, 12: message generation unit, 13: control unit, 14: authentication unit, 15: notification unit, 16: mail address management DB, 17: user attribute management DB, 18: message DB 2: Mail server, 21: Mail transmission unit, 22: Transmission determination unit, 23: Error management unit, 24: Error extraction unit, 25: Error management DB, 3: User terminal, 31: Web browser, 32: Mail transmission / reception Part 9: Network

Claims (7)

An unreachable mail notification system that notifies unreachable mail that has failed to be sent,
For each email address, error management means that counts the number of errors that failed to send,
A notification means for notifying a first message in the case of a mail address whose number of errors does not exceed a predetermined threshold, and notifying a second message for a mail address in which the number of errors exceeds the threshold;
Control means for controlling mail transmission to an email address whose number of errors exceeds the threshold value.
An unreachable mail notification system characterized by The unreachable mail notification system according to claim 1,
The notification means notifies the first message and the second message according to an error type of mail that has failed to be transmitted. The unreachable mail notification system according to claim 1,
Mail address management storage means in which at least one mail address is stored;
The unreachable mail notification system, wherein the control means sets a transmission stop flag for stopping mail transmission to a mail address stored in the mail address management storage means and whose number of errors exceeds the threshold value. The unreachable mail notification system according to claim 1,
The unreached mail notification system, wherein the error management means initializes the number of errors of a mail address that has been successfully transmitted. The unreachable mail notification system according to claim 1,
When the error management means counts up the number of errors of an email address that failed to be transmitted, if a predetermined period has elapsed since the date and time of the previous transmission failure, after initializing the previous number of errors, Unreachable mail notification system characterized by counting up. An unreachable mail notification method for notifying unreachable mail that failed to be sent, performed by the unreachable mail notification system,
The unreachable email notification system includes:
For each email address, a counting step that counts the number of errors that failed to send,
A control step of controlling mail transmission to an email address in which the number of errors counted in the counting step exceeds a predetermined threshold;
A notification step of notifying the first message if the number of errors does not exceed a predetermined threshold and notifying the second message if the number of errors exceeds the threshold. An unreachable mail notification method characterized by this. An unreachable mail notification program that is executed by the unreachable mail notification system and notifies unsent mail that has failed to be sent,
The unreachable mail notification system,
Error management means that counts the number of errors that failed to send for each email address,
A notification means for notifying a first message if the mail address does not exceed a predetermined threshold, and a second message if the mail address exceeds the threshold; and
To function as a control means for controlling mail transmission to an email address whose number of errors exceeds the threshold value
An unreachable mail notification program.

Images