Overview
The platform supports custom email integrations, which allows you to leverage your own email system for sending and receiving emails.
Configuring custom email
By default, all emails sent and received via the platform are routed through the platform's email server.
To reduce the chance of your emails being flagged as spam, it's better that all emails sent and received through the platform are routed through your own organization's email server.
- First, create an email account for your organization that will be used specifically for email integration with the platform.
- It is recommended to name this account "messages". For example, if your organization's domain is myorganization.com, create an account called messages@myorganization.com for the integration.
- The email used for the email integration should not be a personal email address or used for any other communication as the platform can delete emails in that account as part of the email syncing process.
- Additionally, contact your email provider to learn about any email volume limitations to prevent overloading when sending large numbers of emails.
To begin configuring custom email, you must first install the Custom email app. To install the app:
- Click Admin from the primary navigation menu.
- Click App center from the fly-out menu.
- Install the Custom email app in the Email section.
- After installing the app, click the Configure
icon on the Custom email tile.
The email Configure page displays.
- Select your email provider.
Configuration settings display for Outgoing emails and Incoming emails.
- Complete the form based on your email system. Additional information about the fields below:
- User: The user name of the email account without the domain. In this example, it would be "messages".
- Password: The password for the email account.
- Domain: The domain of the email account.
- SMTP server: The address of your SMTP server.
- SMTP port: The port of your SMTP server.
- SMTP authentication: The kind of authentication your SMTP server requires.
- Use TLS for SMTP?: Enable if your SMTP server requires TLS.
- POP3 server: The address of your POP3 server.
- POP3 port: The port of your POP3 server.
- POP3 polling: The number of minutes for your POP3 polling.
- Click Save.
The Configure page now displays your settings.
- Click Send test message to test your configuration settings. This will send an email via your SMTP server. If the configuration is correct, the message will be sent to your email account within a few seconds.
- Click Edit if you would like to edit your email integration settings.
- Click Disable to disable your email integration settings.
AWS-SES integration
The AWS-SES integration allows you to use AWS-SES to send emails, and a POP3 server to receive emails.
To set up an AWS-SES email integration:
- Click Admin from the primary navigation menu.
- Click Email from the fly-out menu.
- Click the Configure tab.
- Click AWS-SES.
The AWS-SES configuration settings display.
Some helpful information to complete the Outgoing emails section:
- Delivery method: Choose between AWS-SES and SMTP delivery methods.
- If you select AWS-SES as the Delivery method, the From email field will appear in the form. The address entered in this field is used to set the "from address" in the sent emails. The email address used in this field has to be verified in your AWS account.
- Click here to learn more about verifying email addresses.
- Information about SMTP credentials such as User and Password for AWS-SES can be found here.
- Domain: The domain defaults to amazonaws.com.
- SMTP server: The SMTP server defaults to email-smtp.us-east-1.amazonaws.com or equivalent depending on the region of your AWS account.
In the Incoming emails section, the Different POP3 account? option is selected by default.
- Complete the Incoming emails section with your POP3 email retrieval protocol information.
- Click Save.

Microsoft 365 email integration
Enabling SMTP
To integrate with Microsoft 365, you must first enable SMTP to send emails from your Microsoft 365 account.
- To enable SMTP with Microsoft 365, please follow the directions provided here.
Configuring Email
Once SMTP is enabled with your Microsoft 365 account, you can set up the integration:
- Click Admin from the primary navigation menu.
- Click Email from the fly-out menu.
The Email page displays.
- Click the Configure tab.
- Click Office 365.
In the Outgoing emails section, enter your Office 365 account credentials:
- User: The user name before @yourOfficeDomain.com.
- Password: Your Microsoft account password.
- Domain: yourdomain.com.
Scroll to the bottom of the page:
- Click Save.
After saving your credentials:
- Click Edit on the Configure tab.
In the Incoming emails section:
- Click Configure OAuth 2.0 for POP3.
The Configure authentication page displays.
- Keep the Configure authentication page open, as you will need the Redirect URI information when registering the application with Microsoft Entra ID in another browser window or tab.
Microsoft Entra ID
In order to obtain the OAuth 2.0 credentials for incoming email, you have to create an application with Microsoft Entra ID. To create the application:
- Log into Microsoft Azure with your Office 365 account credentials.
The Welcome to Azure page displays.
- Click View in the Manage Microsoft Entra ID section.
In the left menu:
- Click App registrations.
The App registrations page displays.
- Click + New registration.
The Register an application page displays.
- Name: Enter a name for the application. In the example below, the name Test POP3 access is used.
- Supported account types: Select Accounts in this organizational directory only - the default setting.
- Redirect URI: From the dropdown menu, select Web.
- In the URI field, enter the Redirect URI from the Configure authentication page in your platform.
- You can find this information on your platform at Admin > Email > Configure > Office365 > Edit > Configure OAuth 2.0 for POP3.
- Click Register.
On the App registrations page, the application name and details display.
- Copy the Application (client) ID and Directory (tenant) ID for future use.
From the left navigation menu:
- Click Certificates & secrets.
The Certificates & secrets page displays.
- Click + New client secret.
The Add a client secret pop-up displays.
- Enter a Description.
- Click Add.
A Client secret Value and Secret ID are created.
- Click the Copy
icon to copy the Value.
- The newly created Value is the Client secret, which you will use in the learning platform to authenticate.
Configuration Page
Now that you have a Microsoft Entra ID application and authentication information, you can complete the email configuration.
- Return to the Configure authentication screen in your platform.
Complete the form based on information gathered from the Microsoft Entra ID application. Note that you will need to replace the information in italics below with your specific application information:
- Authorization URL: https://login.microsoftonline.com/[Directory (tenant) ID]/oauth2/v2.0/authorize
- Token URL: https://login.microsoftonline.com/[Directory (tenant) ID]/oauth2/v2.0/token
- Scope: https://outlook.office.com/POP.AccessAsUser.All offline_access
- Client ID: Application (client) ID.
- Client secret: The Client secret Value.
- Click Save.
Next, you will configure OAuth 2.0 POP and authenticate your email credentials. To ensure you are asked to authenticate in a new window, you will need a new session.
It is recommended that you open a new browser window in Incognito mode to create a new session before proceeding with the following steps.
In Incognito or Private mode in a new browser:
- Click Admin from the primary navigation menu.
- Click Email from the fly-out menu.
- Click the Configure tab.
- Click Edit.
- Click Configure OAuth 2.0 for POP3 in the Incoming Emails section.

The Configure authentication pop-up displays.
- Click Get access token.
Because you have accessed the page with a new session, you will be prompted to pick an account.
- Log in with your Office 365 account (the account used for the integration).
Accept the requested permissions.
The page refreshes and the access token and expiration date are available. Your Microsoft 365 email has been authenticated.
Gmail email integration
To set up a Gmail email integration, first, ensure you are using App passwords:
- You must use App passwords with Gmail to provide the platform with permission to access your Google account. More information can be found here.
- Note that in order to use App passwords, you must enable 2-Step Verification on your account. To learn more, visit the 2-Step Verification documentation from Google.
To set up an Gmail email integration:
- Click Admin from the primary navigation menu.
- Click Email from the fly-out menu.
- Click the Configure tab.
- Click Google.
The Google configuration settings display.
- No changes are needed for the default selections in the Outgoing emails section.
- In the Incoming emails section:
- POP3 user: Enter your gmail account name (the name before the @).
- POP3 domain: Enter gmail.com.
- Click Save.
After saving, you must configure Oath 2.0 for POP3. On the Configure tab:
- Click Edit.
The edit configuration settings page displays.
- Click Configure OAuth2.0 for POP3 in the Incoming emails section.
The Configure authentication page displays.
- Keep the Configure authentication page open, as you will need the Redirect URI information when setting up the application with Gmail in another browser window or tab.
Google Cloud Console
Next, you will set up a new project with Google Cloud Console. To begin:
- Log-in to the Gmail account you will be using to set up the integration.
- Then, access the Google Cloud Console.
- Click Select a project on the top menu.
- Click New Project.
- Name your new project. In this example, the organization will be named Google POP.
- Click Create.
- Select your new project.
After selecting the project, enable the Gmail API:
- Click the Google Cloud
navigation menu in the upper left corner.
- Click APIs & Services.
- Click Library.
- Click Gmail API.
- Click Enable.
Next, you must configure the OAuth consent screen.
- Click the Google Cloud
navigation menu in the upper left corner.
- Click APIs & Services.
- Click OAuth Consent Screen.
- Click Get Started.
The Project configuration page displays.
- Create an App name.
- Add a User support email, for users that contact you with questions about their consent.
- Click Next.
- Select External in the Audience section.
- Click Next.
- Add a Contact email address so Google can notify you about any changes to your project.
- Agree to the Google API Services: User Data Policy.
- Click Create.
Next, you will create credentials for the project.
- Click the Google Cloud
navigation menu in the upper left corner.
- Click APIs & Services.
- Click Credentials.
- Click Create credentials.
- Click OAuth client ID from the drop-down menu.
The Create Oauth client ID page displays.
- Application type: Select Web application.
- Name: Enter a name for your OAuth 2.0 client. Platform client is used in the example below.
- Click Add URI in the Authorized redirect URIs section.
- Enter the Redirect URI
- You can find the Redrect URI on the Configure authentication page in your learning platform.
- Click Create.
The OAuth client created pop-up displays.
- Copy the Client ID and Client secret, as both will be needed when setting up the integration in your learning platform.
Next, you will update your Data access scopes.
- Click Credentials on the left menu.
- Click the OAuth 2.0 Client ID you just created (Platform client was the example used in the previous screenshots).
- Click Data Access on the left menu.
- Click Add or Remove Scopes.
- Use the search filter to locate the https://mail.google.com/ scope.
- Select the Gmail API checkbox.
- Click Update.
Now, you will add your integration email.
- Click Audience on the left menu.
- Click + Add Users in the Test users section.
- Add the e-mail account you have been using for the integration.
- Click Save.
Enable POP in Gmail
To enable POP in Gmail:
- Access the Gmail account you are using to set up the integration.
- Click the Settings
icon in the upper right corner of your Gmail screen.
- Click See all settings.
- Click the Forwarding and POP/IMAP tab.
- You can select either Enable POP for all mail or Enable POP for mail that arrives from now on, depending on your preference.
- Click Save Changes.
Configuration Page
Now that you have Gmail client information, you can complete the email configuration.
- Return to the Configure authentication screen in your platform. If you closed your browser window, to access the page again:
- Click Admin from the primary navigation menu.
- Click Email from the fly-out menu.
- Click the Configure tab.
- Click Edit.
- Click the Configure OAuth 2.0 for POP3 button in the Incoming emails section.
The Configure authentication page displays. Complete the fields using the following information:
- Authorization URL: https://accounts.google.com/o/oauth2/auth?access_type=offline&prompt=consent
- Token URL: https://oauth2.googleapis.com/token
- Scope: https://mail.google.com/
- Client ID: Enter the Client ID you saved from the OAuth Client created pop-up in the Google Cloud Console.
- Client secret: Enter the Client secret you saved from the OAuth Client created pop-up in the Google Cloud Console.
- Click Save.
To complete the authentication, you must get an access token. To get the access token:
- Click Configure OAuth 2.0 for POP3 in the Incoming Emails section.
- Click Get access token.
An authentication window from Google will display.
- Select the Google account used for the integration.
- If prompted, login to the account.
- Click Continue to verify that you trust the learning platform and provide access for the platform to read, compose, send, and delete email from Gmail.
Once authentication has been granted, the Configure authentication page refreshes and the access token and expiration date display.
- Click Save to save your updates.
Your Gmail account has been authenticated.
Common email errors
Below are common errors you may encounter when integrating your email account with the platform, along with steps to troubleshoot them.
- "Net:SMTPUnknownError: could not get 3xx (550)": This error will occur when the Google email sending limit was exceeded. To keep the system healthy and accounts safe, Google limits the number of email messages users can send per day and the number of recipients per message. For more details, visit this Google support article. If you need further assistance, please contact Google support.
- "Net:SMTPAuthenticationError: 454 4.7.0 Too many login attempts, please try again later": This error can occur when Gmail can't handle the high email volume. If you encounter this error, please contact Google support. If you have a very high email volume, you may want to set up an AWS-SES integration.
- "Timeout::Error": Connection time-out means that your email server cannot be reached anymore. In this case, please your e-mail provider to check if they have enabled a firewall that blocks connections, or if they made changes that require updating your integration and authentication settings.
- "POPAuthenticationError: -ERR Login failure: unknown user name or bad password"; "Error: 535 5.7.3 Authentication unsuccessful"; "Incorrect authentication data:Authentication failed": These errors will occur when the credentials used for authentication are incorrect.
- When using Gmail, Error 535 5.7.3 occurs when you use the configured password. You must, instead, configure Google App Passwords in order to authenticate email.