Skip to content
Mint Service Desk Documentation centre

Accounts

Mint Service Desk 3.4.2 user manual.

Accounts

Use ‘Accounts’ to configure the email accounts used for incoming and outgoing messages.

The list shows all configured accounts.

To add an email account, click the button located on the right side of the search box.

In the ‘Create account’ view, fill in all required fields (those marked with an *).

Select at least one queue in ‘Outgoing queues’. When an agent sends a message in a ticket that belongs to one of the selected outgoing queues, the message will be sent using this email account. If an agent sends a message in a ticket whose queue is not assigned to any mailbox, the message will be sent from the mailbox designated as the ‘System account’. If no mailbox is designated as the ‘System account’, the message will not be sent.

After selecting the outgoing queues, choose one ‘Incoming queue’. Emails sent to this mailbox create tickets in that queue.

You can also mark a mailbox as the ‘System account’.

The system mailbox is used to send automatic notifications (e.g., new ticket creation, status updates) and will also handle tickets from queues that are not assigned to any other mailbox.

Select the email provider.

You can choose:

  • Gmail
  • Yahoo!
  • Microsoft Office 365
  • Other
  • Microsoft Graph Api

All mailboxes include predefined configuration settings specific to each email provider. The only exception is the Others section, where all parameters must be entered manually.

Choose an authentication method:

  • Credentials
  • OAuth2

The following sections describe Credentials, OAuth2, Microsoft Office 365 and Microsoft Graph API configuration.

Related articles

Credentials

Credentials authentication uses the mailbox username and password, plus the incoming and outgoing mail server addresses, ports and security settings.

Connection requirements

Requirements for successful mailbox configuration:

  • valid login credentials (email address and current password)
  • the address of the outgoing mail server (SMTP), including the correct port and security mechanism (e.g., SSL/TLS, STARTTLS)
  • the address of the incoming mail server (IMAP - recommended - or POP3), including the relevant port and security mechanism
  • enabled message retrieval and sending services within the mailbox settings (IMAP/POP3, SMTP)
  • awareness of whether Two-Factor Authentication (2FA) is enabled on the mailbox, as it may require an alternative login method (e.g., an application-specific password)
  • if necessary, confirmation that access to the above ports and protocols is not restricted by the network or firewall

The three tables below present the Credentials Authentication Support, SMTP server parameters, and IMAP server parameters for specific email providers.

Credentials support

Credentials Authentication Support

Mail ProviderCredentials SupportNotes
GmailLimitedApp password required and IMAP must be enabled. Standard account password does not work when 2FA is enabled.
YahooYesApp password required after enabling 2FA.
Microsoft Office 365LimitedBasic Auth over IMAP/SMTP may be disabled by the organization’s policy. Works only if Basic Auth is still enabled.
Microsoft Graph APINoOnly OAuth2 authentication is supported. IMAP/SMTP with user password is not available.

SMTP settings

SMTP Server Parameters (Credentials)

Mail ProviderSMTP ServerSMTP PortSMTP Security
Gmailsmtp.gmail.com465SSL/TLS
Yahoosmtp.mail.yahoo.com465SSL/TLS
Microsoft Office 365smtp.office365.com587STARTTLS
Microsoft Graph APINot applicableNot applicableNot applicable

IMAP settings

IMAP Server Parameters (Credentials)

Mail ProviderIMAP ServerIMAP PortIMAP Security
Gmailimap.gmail.com993SSL/TLS
Yahooimap.mail.yahoo.com993SSL/TLS
Microsoft Office 365outlook.office365.com993SSL/TLS
Microsoft Graph APINot applicableNot applicableNot applicable

Account configuration

The screenshot below shows the fields required for Credentials authentication in Mint Service Desk.

Complete the following fields:

FieldDescription
User name*The login username for the mailbox. In most cases this is the full email address, unless the provider requires a different format.
Password*The mailbox account password associated with the User name.
Send server address*The SMTP server address used for sending outgoing emails.
Send server port*The port used for SMTP communication (typically 465 or 587 depending on the security method).
Security (SMTP)The security protocol applied to the outgoing mail server connection (SSL/TLS or STARTTLS).
Receive protocol*The protocol for receiving email: IMAP (recommended) or POP3.
Receive server address*The mail server address for incoming email (IMAP or POP3 depending on the selected protocol).
Receive server port*The communication port for the incoming mail server (e.g., IMAP: 993, POP3: 995).
Security (IMAP/POP3)Encryption type for incoming communication (typically SSL/TLS).
Email address*The mailbox address associated with this configuration. Must match credentials for most providers.
Additional addressesOptional aliases or secondary addresses assigned to the same mailbox that should be handled in the system.

After completing the fields, click button to finish the process and save the new email account.

Connection and activation

If the connection fails, an error appears when you try to save.

After a successful save, the account appears on the Accounts list.

If any connection issues occur while using the mailbox (for example, if the password for the external mailbox connected to Mint has been changed), a warning icon will appear in the Error occurred column.

To activate your new account, press the button. If for some reason you want to deactivate it, you can easily do it, using button.

Once you have a working email account added to the system you can use the button in order to manually force the retrieval of messages from this email box.

Browse retrieved messages in Logs > Messages.

In the Accounts view, use the or in the Action column to update or remove a mailbox.

Oauth2

OAuth2 grants mailbox access using tokens issued by the provider, without storing the mailbox password in the application. Providers such as Gmail and Yahoo recommend this method.

NOTE: It is recommended to perform the configuration in your browser’s incognito/private mode. For example, in Office 365 configuration the final step requires you to authorize your Microsoft account. Otherwise, if you are signed in to a Microsoft account in your browser with the “stay signed in” option enabled (for example, through Outlook or OneDrive in the browser), the system may incorrectly use those credentials to authorize the connection.

Requirements for a successful OAuth2 connection

To ensure correct configuration, the user or administrator must:

  • possess an active mailbox with one of the supported providers
  • register the Mint Service Desk application with the email provider
  • obtain the Client ID and Client Secret
  • configure a valid Redirect URI pointing to Mint Service Desk (visible in the upper right section of the OAuth2 tab, for example https://mintsd.opgksoftware.com/admin/channels/accounts/create)
  • enable necessary API services if required (e.g., Gmail API)
  • ensure IMAP is enabled in the mailbox (if used for email retrieval)
  • verify that firewall/network settings do not block email communication
  • ensure the user grants consent during authentication using a browser pop-up flow

Details on Credentials authentication support, as well as SMTP and IMAP server parameters for specific email providers, are provided in the Credentials section of the Email chapter in this documentation.

To connect to an email account using OAuth2, select ‘OAuth2’ in the ‘Authorization type’ section. Depending on the previously selected operator, the data will be filled in accordingly (if the ‘Other’ option is selected, the user must enter all the data himself).

Below is a table describing each field using the Others provider as an example.

FieldDescription
Authorization typeSelected authentication method – in this case OAuth2.
Client ID*Unique identifier of the application assigned by the email provider (e.g., Google, Yahoo).
Client Secret*Application secret: a confidential key used to authorize the application during token exchange.
Authorization server*URL of the authorization server responsible for user login and issuing the authorization code.
Access token server*URL of the token endpoint where the Access Token and Refresh Token are obtained.
Scopes*Permission scopes requested by the application; these must allow mail access (send/read).
Send server address*SMTP server address used to send outgoing messages.
Send server port*SMTP port (typically 465 or 587).
Security (SMTP)Connection security method for SMTP (SSL/TLS or STARTTLS).
Receive protocol*Mail retrieval protocol: IMAP (recommended) or POP3.
Receive server address*IMAP/POP3 server address used for incoming mail.
Receive server port*Incoming mail server port (e.g., IMAP: 993).
Security (IMAP/POP3)Security settings for the mail retrieval connection (SSL/TLS).
Email address*Email address of the user whose mailbox is integrated with the system.
Additional addressesOptional aliases for additional addresses that should also receive mail.

After saving, the Redirect URL changes from the ‘create’ endpoint to an ‘edit’ endpoint containing the account’s UUID. Add this URL to the application’s redirect settings in your OAuth2 provider’s portal.

Office 365

IMPORTANT!

The outlook.office.com IMAP/SMTP with OAuth integration is based on a legacy model with limited and gradually restricted support. Microsoft recommends migrating to the Microsoft Graph API for improved reliability, security, and long-term compatibility. Continued use of IMAP/SMTP OAuth may result in reduced functionality or service disruptions in future updates.

Use the following example to configure Office 365. Open a private or incognito browser window first, as explained in the OAuth2 section.

Registering the application

To begin configuration, the user must register the application. To do this, go to ‘https://portal.azure.com/’ and then log in to your account. When the login process is successful, select ‘App registrations’ from the left menu. When the window opens click on ‘New registration’.

In order to configure your application correctly, you must first enter an application name. Then in the ‘Supported account types’ section select ‘Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)’ and in the ‘Redirect URI (optional)’ section select ‘Web’ and paste the Redirect Uri from the email account creation page.

Then you need to press the ‘Register’ button.

Once the button is pressed and the new application is successfully registered, the user will be taken to a summary page where he/she must copy the ‘Application (client) ID’

The copied code, the user must paste into the mint configuration in the ‘Client id’ field.

Permissions

The next step is to add permissions. To do this, the user must press the ‘API permissions’ option on the sidebar and then select ‘Add a permission’ on this window.

After pressing the button, press the ‘Microsoft Graph’ option.

Select ‘Delegated permissions’ and check these options:

  • IMAP.AccessAsUser.All
  • SMTP.Send
  • offline_access

And then press the ‘Add permissions’ button.

Client secret

The next step is to go to ‘Certificates & secrets’ which is located on the left sidebar. Then you need to press the ‘New client secret’ button.

Add a description and press the ‘Add’ button.

Remember to enable SMTP Authentication. More information at this link: https://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/authenticated-client-smtp-submission

The user will be taken to the summary. Remember to copy the ‘Value’ field because when you refresh the page, this field will be hidden.

The copied value should be pasted into the MINT configuration in the ‘Client secret’ field.

Saving the connection

To complete the configuration of MINT, select ‘IMAP’ in ‘Receive protocol’ and in the ‘Email address’ field enter the Microsoft Office 365 address from which the configuration was performed.

To complete the configuration process, press the ‘Save’ button. After pressing it the user will be redirected to Outlook login form. If all the information is correct, the system should connect to Microsoft Office 365 via OAuth2.

After saving, the Redirect URL changes from the ‘create’ endpoint to an ‘edit’ endpoint containing the account’s UUID. Add this URL to the application’s redirect settings in Azure or your OAuth2 provider’s portal.

The sample Redirect URL can look like this below:

Note:

Keep in mind that some OAuth2 providers only allow you to generate one refresh token per config. Because of this restriction, you may get an error that you cannot connect to the mailbox. In this case, review the documentation of the provider you are using.

Connection troubleshooting

Note:

If you are still unable to connect your mailbox despite applying the settings described above, ask your application administrator to perform the following steps:

Step 1: Navigate to the following section in Microsoft Entra ID:

Home > Manage > Enterprise applications

Then, go to Security > Consent and permissions.

Step 2: Configure User consent settings section

Under User consent settings, it may be necessary to select the following option: Allow user consent for apps from verified publishers, for selected permissions.

Step 3: Classify permissions

Under Permission classifications > Classify permissions, the administrator may need to classify the following permissions as Low:

  • offline_access
  • IMAP.AccessAsUser.All
  • SMTP.Send

Please note, that the solution described above is provided as an example. The specific settings required may vary depending on your organization’s security policies and configuration.

Microsoft Graph Api

Open the Microsoft Graph API mailbox configuration form.

Registering the application

First go to https://portal.azure.com Sign in and go to Microsoft Entra ID services.

Go to “App” and ‘App registration’

The following form will appear.

Complete the registration form:

  • in ‘Name’ field type your preferred name
  • ‘Supported Account Types’: leave it as it is
  • ‘Redirect URL’: Select “Web” option.

Copy Application (client) ID and Directory (tenant) ID

Paste them here:

API permissions

After the registration go to the Manage > API permissions located in the sidebar on the left.

Press the button. Then, from the window that slides out on the right side of the screen, select the “Microsoft Graph” option.

From the two available options, select the one on the right - Application permissions

In the Mail section, select the following options:

To save the rights, press the button.

You may see a request for administrator approval:

Domain administrator approval is required to grant permissions (read, write, send). It is recommended that domain administrators narrow Graph application access to only the required email addresses. By default, permissions will be granted to the entire domain (for each email address in the domain).

Application access policy

To configure an application access policy and limit the scope of application permissions:

Connect to Exchange Online PowerShell:

  • To require all PowerShell scripts that you download from the internet are signed by a trusted publisher, run the following command in an elevated Windows PowerShell window (a WindowsPowerShell window you open by selecting Run as administrator)

Set-ExecutionPolicy RemoteSigned

  • Install ‘ExchangeOnlineManagement’ tool for managing the Exchange Online Services

Install-Module -Name ExchangeOnlineManagement

  • Login to the Exchange Online Powershell (a login pop-up will prompt out)

Connect-ExchangeOnline -UserPrincipalName {your-admin-account@your-domain.com}

Identify the app’s client ID and a mail-enabled security group to restrict the app’s access to. Identify the app’s application (client) ID in the Azure app registration portal. Create a new mail-enabled security group or use an existing one and identify the email address for the group:

  • You must have Microsoft 365 admin permissions to access the Exchange admin center. For more information, see Permissions in Exchange Online.
  • sign in to Microsoft 365 or Office 365 using your work or school account, and then choose the Admin tile.
  • In the Microsoft 365 admin center, choose Admin centers > Exchange.
  • In the EAC, navigate to Recipients > Groups.
  • Click New > Security groups and fill all necessary fields.

Create an application access policy.

  • Run the following command, replacing the AppId, PolicyScopeGroupId, and Description arguments
  • New-ApplicationAccessPolicy -AppId e7e4dbfc-046f-4074-9b3b 2ae8f144f59b -PolicyScopeGroupId EvenUsers@contoso.com -AccessRight RestrictAccess -Description “Restrict this app to members of distribution group EvenUsers.”

Note: Changes to application access policies can take more than 1 hour to take effect in Microsoft Graph REST API calls.

Client secret and saving

Then go to the Certificates & secrets section.

Once you are in this section press the button.

Enter a recognisable name in Description. In Expires, keep the default of 6 months or choose another validity period.

To approve the operation press the button.

After saving, copy Value.

Client secret values cannot be viewed, except for immediately after creation. Be sure to save the secret when created before leaving the page.

Paste the copied value into MINT in the Client secret section

The configuration should look similar to this:

To save the mailbox configuration press the button.