Email Connectors

Adding an Email Connector

To add a new email connector click on the ‘+’ icon at the top right of the Email Connectors page, select 'Email Connector' and fill out the details in the resulting popup.

The attributes to configure are:

Attribute

Comments

Email Connector Name

Your Enate-friendly name – you can enter anything you like here as a name.

Email Service

List of available email Services which can be used for email connectors. Options available are:

  • Gmail (POP3)

  • Gmail (IMAP)

  • Office 365 (POP3)

  • Office 365 (IMAP)

  • Office 365 (Graph)

  • Other - if you select the ‘Other’ option for Email Service, you will need to specify the incoming and/or outgoing email server information, including server address, port and SSL

Username

The email address / username

Password

The email address password. Maximum of 50 characters.

Primary Email Address

The email address of your connector. If you have multiple email addresses linked to the same mailbox, you must note the primary email address.

Can access additional mailbox

If you want to access an additional mailbox which has the same login information as this, tick the box and add the mailbox name here

Use for

Options are:

  • Incoming: Emails create new Tickets / Cases or link to existing.

  • Outgoing: Mails can be sent OUT from the system via this mailbox. If you want to reference this email connector in e.g. ‘from email address’ settings etc. within Ticket/Case configuration, you must set it as ‘outgoing/ both’ for this to work.

  • Both

Setting a Fallback Email Route

You must also set a fallback email route for the primary email address of each email mailbox in your system.

This will ensure that any mails arriving to that connector which don't get handled by the various email routes configured will at least be handled by this fallback and will kick off the Case or Ticket it routes to.

When setting a fallback route you must define the work item that should be created for an email coming into that connector (if not picked up by any other email routes), i.e. the specific Ticket or Case.

You can also choose whether you want to send automatic emails (such as request acknowledgement emails) to the work item's contact when a work item has been created via the fallback route by selecting the 'Send Automated Emails' option.

You can also choose whether you want your fallback email route to only create work items in test mode by selecting the 'Only create work in test mode' option.

Behaviour After Upgrade to v2022.5

After your system has been upgraded to v2022.5, Email Connectors which do not yet have a fallback route defined will still work, and as such would still potentially allow some incoming emails to be unprocessed if they are not picked up by any of the existing email routes. However, you should be aware of the following when configuring Email Connectors after upgrade:

  • Any NEW Connectors which you create MUST have a fallback route specified in order to be saved and set live.

  • Any EXISTING Connectors which you EDIT MUST also have a fallback route specified in order for you to save your changes. The Save option will be disabled until you have specified a fallback route.

Auto-Selection of Fallback Routes during Upgrade

During the upgrade to 2022.5, Enate will assess all the existing Email Routes for each Connector in your system attempt to automatically set one of these for each Connector as its fallback route. In order to qualify as an acceptable fallback route, the email route must meet the following criteria:

  • Its email must match the primary email address or be set as a catch-all '*' wildcard.

  • No additional Routing Rules must exist for the Email Route.

  • It must have a Ticket or Case route already defined for it.

  • It must already be the last route in the ordered set of Routes for that Connector.

  • It must already be Enabled.

If an Email Route for a connector meets the above criteria, its route settings will be added to the Connector (displaying in the Connector details popup), and certain aspects of the Route's configuration will become locked down, in order to ensure it remains as the fallback route. See section below for details of this.

How Fallback Routes Subsequently Display in 'Routes' Section

Whether it be as a result of auto-selecting during upgrade, or manual definition of the email route afterwards within the Connector, the email routes which have been specified will then show in your Email routes section with some specific impacts.

Details of this are as follows:

  • These routes will always display at the foot of the Email Routes list

  • The Routing Rule will be set to read-only

  • The Email Connector will be set to read-only

  • The 'Enable' setting is set to ON, and is read-only

Testing a Connector & Setting it Live

Once you have configured the required information you must then test the connection. To do this, click on the 'Test Connection' button.

Once the connection has been tested successfully, you can then enable the connector by switching on the 'Enable' toggle.

The connection will not run with unless 'Enable' is switched on.

Editing an Email Connector

You can edit an email connector by clicking on the ellipsis and choosing 'Edit'.

When editing an email connector, you are also able to see its activity history by clicking on the Show Activity button. You can see when the email connector was created and by who, as well as if any edits have been made to the email connector, when they were made and by who.

Default Email Connector for Outgoing emails

The system has a default outgoing email Connector called ‘System Default SMTP Gateway’ for standard system activities e.g. User Welcome emails etc.

Last updated