The iService MailPopper Monitor is used to monitor the status of the mail processor and other threads within the iService application. The mail processor runs as a Windows Service that checks tenant mailboxes, retrieves those messages, and gets the messages into iService appropriately. The monitor provides a real-time view of the status of mailboxes including the number of messages being processed.
By default, it's executable is located in the same directory as the iService Mail Popper service and iService Mail Monitor (the default location is C:\Program Files\1To1Service\iService).
The location of the MailPopper Monitor
When opened, the monitor provides details for every tenant in the installation as shown below.
The MailPopper Monitor Screen
For each tenant, the monitor displays the following information. History is retained for the number of messages retrieved, sent, and processed until the mail popper service is restarted, at which time the count returns to zero.
1.Processor – After messages are retrieved and saved in the iService database (see All Mailboxes below), a mail processor thread is run to convert the raw message into an interaction. This line shows the number of emails that were successfully converted into interactions, and the number of emails that failed processing. Emails that failed processing can be extracted from the Management Console.
2.SMTP Out – Outbound email processing (SMTP) is managed separately from mail popping. The SMTP thread takes messages from the SMTPOUT table and delivers them to the appropriate SMTP mail server for delivery. Messages that failed SMTP processing are shown as mailbox errors in the iService web interface (Settings - Tenant - Mailboxes page and the Buitin Forms - SMTP OUT Monitor page). See the User Guide for more details.
3.Mass Mailing – The mass mailing process selects the appropriate contact based upon list and criteria specified, and generates the SMTP message to be delivered. These messages are saved in the SMTPOUT table and then processed by the SMTP Out thread. See the User Guide for more details.
4.Campaigns – Campaigns function identically to Mass Mailings, but are based on a series of predefined message that process based upon a schedule. See the User Guide for more details.
5.Alerts – The Alerts thread monitors your iService tenant and takes actions, such as sending notification messages to managers for unresolved questions.
6.All Mailboxes - The status of mail popping is listed for all mailboxes within each tenant. the All Mailboxes line will not be shown if mail popping is disabled for the tenant.
