Administration Guide

Set Up Mail Connector Jobs

On this page

A Mail Connector job connects one mailbox and processes its messages on a schedule. You can create several jobs, each with its own mailbox, server type, operations, and preprocessing rules. The Mail Connector runs as a job of the Automation Server: each run signs in to the mailbox, processes the messages it finds, signs out, and ends, so the job's schedule sets how often the mailbox is checked. For jobs and schedules in general, see Jobs and Schedules.

A new 2026.1 database created with the Default Workflow (see Default Workflow Configuration) has no Mail Connector job, and the three preprocessing rules that configuration supplies are not selected for any job. An upgraded database need not match this.

The Admin Center and the Settings App edit the same jobs; where both show a setting, they edit one stored value, and the Settings App's editor is the deeper one. See Admin Center and Settings App. The Admin Center configures IMAP4, Exchange Online, and Google Mail jobs; POP3, EWS, and MAPI jobs are configured in the Settings App.

Before you begin

  • A job runs only while the Automation Server is set up and running.
  • Mail Connector jobs need the Notifications permission of the role ("Allows managing Notifications"). A role with Administrative Access has it.
  • In the Admin Center, this permission opens the E-mail Processing pages, Mail Connector among them, and the Notifications pages other than SSP E-mail Templates.
  • In the Settings App, opening a job without this permission shows "You do not have enough permissions to view this item."
  • In the Admin Center, Microsoft sign-in to a mailbox fails with an error when the Admin Center is opened over an HTTP connection.
  • An Exchange Online job with a custom application and a Google Mail job sign in with an OAuth client that you prepare in Microsoft Entra ID or in Google Cloud first (see Prepare the OAuth client).

Prepare the OAuth client

Exchange Online: Microsoft Entra ID

An Exchange Online job signs in with an application registered in Microsoft Entra ID. Its Client setting names the application:

  • Alloy Mail Connector (admin consent required) is the multi-tenant application that Alloy Software registered, so you register nothing. It can be chosen in the Settings App only.
  • Custom application registered in your Azure portal is an application that you register yourself.

To prepare a custom application:

  1. Register the application in Microsoft Entra ID as a single-tenant or a multi-tenant application. For the registration that a Mail Connector job needs, see Register an application in Microsoft Entra ID; for Microsoft's own steps, see How to register an app in Microsoft Entra ID on Microsoft Learn.
  2. On the application's Overview page, copy the Application (client) ID into the job's Client ID.
  3. For a single-tenant application, copy your tenant ID into the job's Tenant ID. Microsoft describes where to find it in Find your tenant ID. For a multi-tenant application, leave Tenant ID empty.

The permissions that the mailbox sign-in requests are listed under Sign in to the mailbox.

Google Mail: Google Cloud

A Google Mail job signs in with an OAuth client that you create in a Google Cloud project. The sign-in requests email and https://mail.google.com/, which is the scope Google requires for IMAP access to Gmail (see OAuth 2.0 Mechanism).

  1. In the Google Cloud console, create a project or select an existing one. See Create a Google Cloud project.
  2. Enable the Gmail API in the project, under APIs & Services > Library. See Enable Google Workspace APIs.
  3. Configure the OAuth consent screen. Choose the Internal user type when the app is used only within your Google Workspace organization, or External; for External with the publishing status Testing, add every Gmail account whose mailbox a job reads as a test user. See Configure the OAuth consent screen.
  4. Create an OAuth client ID of the application type Desktop app, or Web application with the authorized redirect URI http://127.0.0.1/authorize/, including the final slash. See Create access credentials.
  5. Copy the client ID and the client secret of the new client into the job's Client ID and Client Secret.

NOTE: For a consent screen with the External user type and the publishing status Testing, Google issues refresh tokens that expire in 7 days, unless the only scopes requested are name, e-mail address, and user profile. See Refresh token expiration.

Set up a job in the Admin Center

Mail Connector jobs are on the E-mail Processing > Mail Connector page. The same job pages are also reached from Services > Automation Server. The Automation Server list has no New button, so a new job is started from the Mail Connector page.

Create or edit a job

  1. Go to E-mail Processing > Mail Connector and open the job, or start a new one.
  2. On the Settings tab, enter the job's name, choose the Server Type, and fill in the settings of that type (see Server types).
  3. For Exchange Online and Google Mail, sign in to the mailbox (see Sign in to the mailbox).
  4. Set the schedule.
  5. Click Test Connection to check the settings (see Test the connection).
  6. On the Processing tab, choose the Create Persons action under Unmatched sender workflow, and set the Email attachment, Incoming email handling, and End of session options (see Processing and preprocessing rules).
  7. On the Preprocessing Rules tab, select the rules the job applies and drag them into the order they apply in.
  8. Click Ok.

The job form has the tabs Settings, Processing, Preprocessing Rules, and Sessions. The schedule is on the Settings tab, and Sessions is shown once the job exists. Ok refuses to save with The "<field>" field is mandatory, it can't be left blank. when the name, the Create Persons field of the Processing tab, or a required field of the server type is empty (see Server types).

A new job starts with these values:

  • Name: Mail Connector.
  • The job is enabled.
  • Server Type: Internet Message Access Protocol v4 (IMAP4), port 143, mailbox Inbox, and no secure connection.
  • OAuth client type: Custom application registered in your Azure portal.
  • Schedule: monthly, on day 1 of every month, once that day at 00:00, starting today.
  • The processing operations that Alloy Navigator supplies for a new job, shown in the Operations tree of the Processing tab.

Server types in the Admin Center

The Server Type list offers Internet Message Access Protocol v4 (IMAP4), Exchange Online with OAuth authentication, Google Mail (IMAP4), Post Office Protocol v3 (POP3), Exchange Web Services (EWS), and Messaging Application Programming Interface (MAPI). When you choose POP3, EWS, or MAPI, the form shows only "This feature is not yet available in the Admin Center. Please use the desktop Settings App." and has no other tabs and no Ok. The tabs and Ok are available for IMAP4, Exchange Online, and Google Mail jobs.

The settings of each server type:

  • IMAP4: the server, the port, the mailbox folder, the mailbox user name and password, and the secure connection: None, STARTTLS, if available, STARTTLS, or SSL/TLS. Server Name, Port, and Username are required; the password is not.
  • Exchange Online: the job signs in with OAuth. From top to bottom, the Mail Server group of the Settings tab shows:
    • API offers Microsoft Graph, selected for a new job, and Exchange Web Services (EWS). This is how the job reaches the mailbox.
    • Under Client, Custom application registered in your Azure portal is selected. The other client type, Alloy Mail Connector (admin consent required), is unavailable and shows "This feature is not yet available in the Admin Center. Please use the desktop Settings App."
    • Your organization uses Microsoft Cloud for US Government, a check box for the government cloud.
    • Client ID, required.
    • Tenant ID, optional: "Leave empty for a multi-tenant application".
    • Account, required, with its Sign in button (see Sign in to the mailbox).
    • Folder.
  • Google Mail: the job signs in with Google OAuth. Server Name and Port are filled in with imap.gmail.com and 993 and cannot be changed. Client ID, Client Secret, and Account are required.

Sign in to the mailbox

The account field shows the signed-in mailbox account and a Sign in button, which reads Change once an account is set.

For Exchange Online, Sign in opens a Microsoft sign-in window where you select the account. For the government cloud, sign-in goes to login.microsoftonline.us. The sign-in requests these permissions:

Mail access Permissions requested
Microsoft Graph Mail.ReadWrite, Mail.Send, openid, profile, offline_access
EWS EWS.AccessAsUser.All, openid, profile, offline_access

After sign-in, the field shows the user name of the signed-in account.

The field checks the access that was granted. A Microsoft grant for EWS must include EWS.AccessAsUser.All; a grant for Microsoft Graph must include both Mail.ReadWrite and Mail.Send; a Google grant must include https://mail.google.com/. When the access is missing, the field shows "Authorization failed. The requested access to {scope} was not granted. Please sign in again." and keeps its previous value.

Over an HTTP connection, Microsoft sign-in fails with an error.

When sign-in fails, an error dialog with OK and Help opens. When the sign-in service answers with one of these error statuses, the dialog shows:

Status Message
400 Your browser sent a request that this server didn't understand. Please try again later or contact your administrator.
401 Access is denied. Make sure the credentials you entered are correct and try again.
403 This action is unauthorized. Please contact your administrator.
404 The requested page was not found on this server. Please try again later or contact your administrator.
500 The server encountered an internal error and could not process your request. Please try again later or contact your administrator.

Failures without an error status show the sign-in service's own message, "id_token not found", or "Unknown error". When a failure carries no message, the details area of the dialog shows the sign-in service's response. Closing the sign-in window without finishing opens no dialog.

Test the connection

Test Connection tests the job's current settings in the form. The button is unavailable while a test runs, for an IMAP4 job without a server or a port, and when there is no mailbox user name. The result is one of these:

  • "Connection test completed successfully."
  • "Connection to the mail server failed. For details, see the session log at E-mail Processing > Mail Connector > Logs", where the last part links to the job's log.
  • "The connection to the server timed out. Please try again later.", with a Got it button.
  • The text of another error or success message that the test reports.

Processing and preprocessing rules

On the Processing tab, the Operations tree is shown for information only, with the text "The current logic is displayed for informational purposes only and can be configured using a dedicated desktop Settings application." The Unmatched sender workflow, Email attachment, Incoming email handling, and End of session options can be changed.

Under Unmatched sender workflow, the text "Specify workflow action to run when receiving new message for message senders that can't matched to a Person:" introduces one field, Create Persons. It is required: when it is empty, Ok refuses with The "Create Persons" field is mandatory, it can't be left blank.

The Preprocessing Rules tab lists the rules one per row, each with a check box and the rule's name. A new job lists every preprocessing rule, with its check box cleared.

  • Select a rule's check box to apply the rule to the job.
  • Drag a row up or down to change the order; the position of a row is the order in which the rule applies. The tab has no Move Up or Move Down buttons.
  • The order and the selection are saved with the job when you click Ok. When you save an existing job, only the order and the selection of the rules already linked to it change.

A rule's name on this tab does not open the rule. A rule itself is edited only on the E-mail Processing > Preprocessing page (see Incoming E-mail Processing Rules).

Schedule in Cloud

In Alloy Navigator Cloud, the schedule field does not accept an interval shorter than 5 minutes, and a new job saved with a shorter interval is set to 5 minutes (see Administering Alloy Navigator Cloud). Saving changes to an existing job does not make that adjustment.

Run, terminate, enable, and disable jobs

On the Mail Connector page, select the job or jobs and click the command:

  • Run needs one selected job and an active Automation Server.
  • Terminate also needs the job's last run to be still running.
  • Enable and Disable act on the whole selection.

A run or termination requested in the Admin Center goes through the database, so the Automation Server can take up to one refresh interval to pick it up. A run requested this way ignores the schedule and whether the job is enabled, so it also runs a disabled or expired job, and it does not change the next run date. It does not start while the Automation Server is not the active server or the job is already running. If a run is already queued, the Admin Center shows "Please wait until the job has completed, and then check the session log to make sure that it runs as expected." and refreshes the list instead of queuing it again. If a termination is already requested, it shows "Please wait, the job will be terminated soon." and refreshes the list. For jobs in general, see Jobs and Schedules.

Check the results

On the Automation Server list, a job's next run shows "Queued to run as soon as possible", "Queued for forced termination", "The job schedule is disabled.", "The job has not started yet.", or the date. Its last run status shows None when no status is recorded, and the status with its date when both are recorded.

The Sessions tab of a job lists the job's sessions, newest first, in the columns Run Date, Job Name, Comments, Duration, Messages in Box, Received Messages, Created, Updated, and Errors.

  • To open the log of a session, click its run date, double-click the row, or select one row and click View Log.
  • The refresh button reloads the list, and the Filter items box filters it.
  • Delete and Clear All are shown only to an account that is allowed to manage logs. Delete asks "Are you sure you want to delete the selected item?", or "Are you sure you want to delete <n> selected items?" for several rows. Clear All asks "You are about to delete all entries from the Service Log. Are you sure you want to proceed?"; Yes deletes the sessions of this job only.

The E-mail Processing section has a Logs page. When a connection test fails, its message links to the job's log. For logs in general, see Logs.

Set up a job in the Settings App

Mail Connector jobs have their own page in the navigation tree, E-mail Processing > Mail Connector, a grid of the Mail Connector jobs with New, Open, and Delete. They are also listed with the jobs of every other kind in Services > Automation Server > Job List, grouped by job type.

Create or edit a job

  1. Go to E-mail Processing > Mail Connector. Select the job and click Open, or click New to start a new job. A job can also be opened from the Job List. The job opens in a window titled Mail Connector, followed by the job name in brackets for an existing job. If the job is already open, its window comes to the front.
  2. On the Settings tab, enter the Name: and select or clear Enabled.
  3. In the Mail Server group, choose the Server Type: and fill in the fields of that type (see Server types). For Exchange Online and Google Mail, sign in to the mailbox (see Mailbox sign-in).
  4. In the Schedule group, which shows the schedule in words, click Change to set the schedule.
  5. On the Processing tab, choose the Create Persons: action and set up the operations (see The Processing tab).
  6. On the Preprocessing Rules tab, select the rules the job applies and set their order (see The Preprocessing Rules tab).
  7. Click Test Connection to test the settings in the window (see Connection test).
  8. Click OK.

The window has the tabs Settings, Processing, Preprocessing Rules, and Sessions. Sessions is unavailable until the job is saved. While the Automation Server is not running, the Settings tab shows "Warning. For this job to be executed, the Automation Server must be set up and running."

A new job is named Mail Connector, then Mail Connector (1) and so on, is enabled, runs every minute (every 5 minutes in Alloy Navigator Cloud), and has the server type Internet Message Access Protocol v4 (IMAP4). Its Processing tab starts with a default operation tree (see The Processing tab).

OK refuses to save with The "<field>" field is mandatory, it can't be left blank. when one of these is empty:

  • Always: the name, the schedule, and the Create Persons action.
  • POP3 and IMAP4: Server Name, Port, and Username.
  • MAPI: Mail Profile, unless Use default profile is selected.
  • EWS: the EWS URL or the e-mail address, and Username.
  • Exchange Online: Account.
  • Google Mail: Client ID, Client Secret, and Account.

Closing the window with unsaved changes asks "Do you want to save the changes?"

Server types in the Settings App

The Server Type: list offers six entries:

Server type Fields
Post Office Protocol v3 (POP3) Server Name:, Port:, the Secure connection options, Reject invalid certificates, Username:, Password:, Require Secure Password Authentication (SPA)
Internet Message Access Protocol v4 (IMAP4) The same fields as POP3, plus Folder:
Messaging Application Programming Interface (MAPI) A mail profile, or Use default profile, and the Profile account group
Exchange Web Services (EWS) EWS: or E-mail Address:, Username:, Password:, Version:, Reject invalid certificates, and a Folder: box of its own
Exchange Online with OAuth authentication API:, Client:, the settings of the OAuth client, Account:, and a Folder: box of its own (see Mailbox sign-in)
Google Mail (IMAP4 + OAuth) The IMAP4 fields preset to imap.gmail.com, port 993, and implicit SSL/TLS; the server and port boxes are unavailable, the Secure connection options are hidden, and Client ID:, Client Secret:, and Account: replace the user name and password

For POP3 and IMAP4, changing the security mode switches a default port that you have not changed between 110 and 995 for POP3, and between 143 and 993 for IMAP4. Any other port stays as it is.

With EWS selected, choose Specify the Exchange Web Services URL or server name: and fill in EWS:, or choose Autodiscover the Exchange Web Services URL using this address: and fill in E-mail Address:. Then fill in Username: and Password:, which hides what you type. Version: offers "Autodetect the version of Microsoft Exchange Server", which is preselected, "Microsoft Exchange Server 2007 Service Pack 1", "Microsoft Exchange Server 2010", "Microsoft Exchange Server 2010 Service Pack 1", "Microsoft Exchange Server 2010 Service Pack 2", and "Microsoft Exchange Server 2013 or later".

When you open a job whose folder is empty, the folder boxes are filled with Inbox. If you clear a Folder: box after the window has opened, the folder is saved empty.

With MAPI selected, the Settings tab shows the Profile account group. Under "Specify a Windows account to access the MAPI profile:", choose The Automation Server startup account, or choose This account: and enter the user name and the password. The user name box has a Find... button. The tab also notes that the profile must be created with a 64-bit edition of Microsoft Outlook on the Automation Server computer, for the profile account.

  • A local Windows account is refused unless the database server and the Automation Server are on the same computer: "The Automation Server cannot use a local account to run the Mail Connector. Please specify a domain account."
  • When you change the profile account of a MAPI job, OK first runs a connection test, and the job is not saved when the test fails. When the Automation Server is stopped, the save is abandoned with "Now you need to start the Automation Server and then click "Test Connection" to confirm that the Mail Connector can use the specified Profile Account."
  • Missing rights of the account are reported as "Make sure that the Automation Server startup account belongs to the local Administrators group on the Automation Server computer." or "Make sure that this Windows account has the "Log on as a batch job" user right."

Mailbox sign-in

With Exchange Online with OAuth authentication selected, the Mail Server group shows, from top to bottom:

  • API: offers Microsoft Graph, selected for a new job, and Exchange Web Services (EWS). This is how the job reaches the mailbox.
  • Client: offers Alloy Mail Connector (admin consent required), selected for a new job, and Custom application registered in your Azure portal.
  • Your organization uses Microsoft Cloud for US Government, Client ID:, and Tenant ID: ("Leave empty for a multi-tenant application"). These are available only with Custom application registered in your Azure portal. The government cloud is used when the check box is selected and Client ID: is filled in.
  • Account:, with a Sign in... link that reads Change... once an account is signed in.
  • Folder:.

With Google Mail (IMAP4 + OAuth) selected, the group shows Client ID:, Client Secret:, and Account: with its Sign in... link.

To sign in to the mailbox:

  1. For a custom application, fill in Client ID:; leave Tenant ID: empty for a multi-tenant application. For Google Mail, fill in Client ID: and Client Secret:.
  2. Click Sign in.... For a custom application or Google Mail, an empty Client ID: shows "The Client ID is not specified". For Google Mail, an empty Client Secret: shows "The Client Secret is not specified".
  3. The Microsoft or Google sign-in page opens in a web browser, and the Settings App shows the Sign in window: "In a browser window, sign in with a Microsoft Account and configure client permissions. Once authorization is granted, the credentials will be saved automatically." For Google Mail, the window reads "a Google Account". The window has a Cancel button.
  4. In the browser, sign in and grant the permissions. The Sign in window closes, and Account: shows the name of the signed-in account.

Connection test

Test Connection runs the Mail Connector with the settings in the window, including changes you have not saved; the Automation Server runs the test. The button is available when the key fields of the server type are filled:

  • POP3 and IMAP4: the server, the port, and the user name.
  • MAPI: a profile, or Use default profile.
  • EWS: the user name, plus the URL or the Autodiscover address.
  • Exchange Online and Google Mail: a signed-in account.

The result is "Connection test completed successfully." or "Connection to the mail server failed.", with the error text available in an extended error view. When the list of MAPI profiles cannot be read, the window shows "Cannot receive a list of available e-mail profiles."

The Processing tab

The Processing tab holds the job's operations, two settings that apply to every message, and the Incoming e-mail handling group (see Incoming e-mail handling):

  • The Operations group holds the job's if/else tree. Its New menu starts with Create Object and Update Object, followed by "IF" Group, "ELSE" Group, and "ELSE IF" Group. The toolbar has Expand All, Collapse All, Move Up, and Move Down. An operation whose object class is not licensed cannot be opened or turned on again, and shows "Your license does not support this feature."
  • Create Persons: is the action that runs for a message whose sender cannot be matched to a Person. The tab explains it with the label "Specify workflow action to run when receiving new message for message senders that can't matched to a Person:". It offers the actions that create Persons; Delete or Backspace clears it.
  • Attach original e-mail message to object/activity is a check box.

Create Object and Update Object open the Operation window. A create operation (Create New:) names a licensed object class and the create action for it. An update operation also identifies the record to update, by a GUID field value or an expression. Its object box is labeled with the class name, for example Incident:, and its F(x) button opens Build Expression, where the E-mail Fields category lists the attributes of the message and the fields of the parsing rules (see Incoming E-mail Processing Rules); an entry you choose is inserted as %[EML <name>]%. Enable operation turns one operation off without deleting it, whether or not the job is enabled.

A new job starts with a default operation tree that depends on the licensed modules. When a message refers to an existing object, the branch for that object's class updates it:

  • With the ITSM module, the tree has branches for Incident, Change Request, Problem, Work Order, Service Request, Approval Request, and Task, plus Purchase Order when the ITAM module is also licensed. A message that refers to no object creates an Incident.
  • With only the ITAM module, the tree has branches for Purchase Order and Approval Request, and creates nothing.

Each branch uses the first enabled action, by rank, of the right kind for its class. A branch whose class has no such action is left out.

The Preprocessing Rules tab

The Preprocessing Rules tab lists every preprocessing rule: the rules linked to the job first, in their order, then the others. Each row has a check box and the rule's name, and the position of a row is its order.

  • Click a rule's check box, or press Space, to select or clear it.
  • Move Up and Move Down change the order.
  • Open shows the rule read-only.

Nothing is saved until you click OK. Rules themselves are created, edited, and deleted in the global Preprocessing Rules list, which is in the E-mail Processing group of the navigation tree; see Incoming E-mail Processing Rules.

Incoming e-mail handling

On the Processing tab, below the Operations group, the Incoming e-mail handling group sets what happens to a message after processing, which depends on whether the message was processed. A message counts as processed when at least one create or update operation ran for it.

  • When an object is created or modified successfully: choose Mark the message as read or Mark the message as deleted. A processed message is always marked as read, and is also deleted when Mark the message as deleted is chosen. Select Purge the deleted messages at the end of session to purge the deleted messages when the run ends.
  • When a workflow item rejects the message: select Mark the message as read (selected for a new job), Mark the message as deleted, or both.

For a POP3 job, the group shows the fixed, unavailable check box Delete the message from the mailbox for processed messages, and the rejected-message check box reads Delete the message from the mailbox. A processed POP3 message is always deleted, and a POP3 job does not purge.

Run a job now

  1. On the Mail Connector page or the Job List, select one job. Run is available while the page shows the Automation Server as running.
  2. Click Run.

The Automation Server starts the run at once, out of schedule, unless it is not the active server or the job is already running. A run started this way ignores the schedule and whether the job is enabled, so it also runs a disabled or expired job, and it does not change the next run date.

When the Settings App cannot reach the Automation Server directly, the request goes through the database, and the Settings App shows "Since your Settings App and the Automation Server are installed on separate computers, it may take some time to test your settings. Please wait until the job has completed, and then check the session log to make sure that it runs as expected." Any other failure shows "Cannot send request to the Automation Server. Make sure the Automation Server is configured and started."

Terminate a running job

  1. Select one job whose last run status is Running.
  2. Click Terminate, and confirm "Are you sure you want to terminate this job?".

The Automation Server stops the job's run. When the request goes through the database, the Settings App shows "Please wait, the job will be terminated soon. Since your Settings App and the Automation Server are installed on separate computers, it may take some time to complete."

Enable or disable jobs

  • In the job window, select or clear Enabled on the Settings tab.
  • On the Mail Connector page or the Job List, select one or more jobs, right-click the selection, and choose Enable or Disable. These two commands are on the right-click menu only. The list refreshes, and the Automation Server is told that the jobs changed.

For a disabled job, Next Run Date shows "The job schedule is disabled." Enabling the job again calculates its next run afresh.

On the Job List, which groups the jobs by type, a focused group row counts as two rows, so Open, Run, and Terminate are unavailable on it. For jobs in general, see Jobs and Schedules.

Job ID and log level

On the Mail Connector page, the right-click menu command Copy Job ID (GUID) to Clipboard copies the ID of the selected job.

To choose a job's log level, type debug in the grid of the Mail Connector page and confirm Enable debug mode?. A log-level column appears, and the right-click menu gains Log Level with Normal and Detailed. With Detailed, a run writes a debug trace for each message and, for MAPI, the messages of the MAPI engine.

Check the results

The Job List shows each job's name, last run status, next run date, and whether it is enabled. It refreshes itself every 10 seconds by default.

  • Last Run Status reads "Succeeded", "Failed", "Running", or "Unknown", followed by " at <last run date>" when a run is recorded.
  • Next Run Date shows the next run date, or one of these messages: "Queued to run as soon as possible", "Queued for forced termination", "The job schedule is disabled.", "The job has expired.", or "The job has not started yet."

The Sessions tab of the job window shows the job's Incoming Mail Log. The same log for all jobs is E-mail Processing > Logs. Each run records five counters: objects created, objects updated, messages, messages in the mailbox, and errors.

Schedule in Cloud

In Alloy Navigator Cloud, a new job starts with a schedule of every 5 minutes, and the scheduler that Change opens does not accept an interval shorter than 5 minutes, or shorter than one hour when the schedule is set in hours (see Administering Alloy Navigator Cloud).

How a job processes the mailbox

A job's operations form an if/else tree of two kinds of operation: one creates an object, and the other runs an action against an existing object.

A sender who matches no Person is created by the job's Person create action. A job without that action fails at the start of each run. When the action is not one of the enabled Mail Connector actions, the run fails before it processes any message, with "Person Create action not specified."; when it is a disabled Mail Connector action that creates Persons, the run reports that the action is disabled. For POP3, IMAP4, Google Mail, and Exchange Online over Microsoft Graph jobs, an empty mailbox ends the run before this check.

The mailbox folder

How a job uses its folder setting depends on the server type:

  • IMAP4 and Google Mail: the folder name is sent to the mail server exactly as it is typed. Whether a subfolder is written with a dot or a slash is the mail server's convention. When the server does not select the folder, the run stops with Cannot select folder <folder>.
  • EWS, and Exchange Online over EWS: the folder is a path from the root of the mailbox, split at each /. For example, Support/Escalations is the folder Escalations inside the folder Support. Write a slash that is part of a folder name as \/. An empty folder, or Inbox in any case, reads the Inbox. When a folder on the path is not found, the run fails with Folder <folder> not found.
  • Exchange Online over Microsoft Graph: Inbox in any case reads the Inbox. Any other folder is a path split at each /: the first folder is looked up by name among the top-level folders of the mailbox, and each next one among the subfolders of the one before. A first folder named Inbox is the Inbox, so Inbox/Support is the folder Support inside the Inbox. Write a slash that is part of a folder name as \/, and a backslash as \\. When a folder on the path is not found, the run fails with Folder <folder> not found. The job reads only the unread messages of the folder.
  • MAPI: the job always reads the Inbox of the mail profile.