## Please enable JavaScript to view this site.

# MDaemon Email Server 25.5

- Zoom Window Out
- Larger Text | Smaller Text
- Hide Page Header
- Show Expanding Text
- Printable Version
- Save Permalink URL

MultiPOP | Scroll Prev Top Next More

Enable MultiPOP

Check this box to enabled the MultiPOP server. MultiPOP collects mail from POP servers on behalf of your users and stores it in the their local mailboxes. The MultiPOP feature allows you to create an unlimited number of POP3 host/user/password combinations for collection of mail messages from multiple sources. This is useful for your users who have mail accounts on multiple servers but would prefer to collect and pool all their email together in one place. Before being placed in the user's mailbox, MultiPOP collected mail is first placed in the local queue so that it can be processed like other mail having Autoresponders and Content filters applied to it. The scheduling options for MultiPOP are located at: Setup » Event Scheduling » Mail Scheduling » MultiPOP Collection.

MultiPOP always deletes mail from all servers after collection

Click this check box if you wish to override the Leave a copy of message on POP3 server option (located on the MultiPOP screen of the Account Editor) for all users. All messages will be deleted from each MultiPOP server after they are collected.

Send notification email after this many failures

By default, MDaemon sends a notification email after multiple failures when checking a MultiPOP account. Since temporary failures can be common, this option allows you to specify how many consecutive failures it takes to trigger the notification, and the option below allows you to choose how many days to wait between those notifications. The content and recipients of the notification emails can be customized by editing \MDaemon\App\MPOPFailureNotice.dat. By default the notifications are sent to the MultiPOP account owner after 5 failures, no more than once every 7 days.

Do not notify again for this many days

By default MultiPOP failure notifications are sent no more than once every seven days. Use this option if you wish to adjust that interval.

## MultiPOP OAuth

OAuth 2.0 is a modern authentication method that Gmail and Microsoft (Office) 365 are now requiring (or will soon require) as they disable support for legacy/basic authentication. In order for MDaemon's MultiPOP feature to use OAuth 2.0 to collect mail from Gmail or Office 365 on behalf of your users, you must register your MDaemon server with Google or Microsoft, respectively, creating an OAuth 2.0 application using the Google API Console or Microsoft's Azure Active Directory. This is similar to the procedure required for using MDaemon's Dropbox Integration for your Webmail users.

To set up MultiPOP to collect mail from Gmail or Microsoft (Office) 365 for your users:

1.Turn on the Enable MultiPOP option above.

2.Follow the instructions below for Creating and Linking Your MultiPOP OAuth App for Gmail or Office 365.

3.On the Account Editor's MultiPOP page, Enable MultiPOP for each user that you wish to allow to use MultiPOP to retrieve email from Gmail or Office 365.

4.Add the Gmail (pop.gmail.com:995) or Office 365 (outlook.office365.com:995) account for each of the users, and enable the Use OAuth option. Optionally you can have your users do this step for themselves in Webmail. Note: for Gmail accounts, each Gmail account must be added to the Test Users in your Gmail OAuth app (see the Publishing Status note in the Creating and Linking Your MultiPOP OAuth App instructions below).

5.On the Account Editor's Web Services page, enable the "...edit MultiPOP settings" option for each of those users.

6.Each user must sign in to Webmail, go to their Mailboxes page under Options, add their Gmail or Office 365 account (if you didn't already do that for them), and then click Authorize to sign in to their Gmail or Office 365 account and proceed through the steps to authorize MDaemon to collect their mail from that location.

Gmail/Office 365

Client ID

This is the unique Client ID assigned to your MultiPOP OAuth 2.0 app when you create it in the Google API Console or Microsoft Azure Active Directory portal. After you create your app, copy its Client ID and paste it here.

Client Secret

This is the unique Client Secret assigned to your MultiPOP OAuth 2.0 app when you create it in the Google API Console or Microsoft Azure Active Directory portal. After you create your app, copy its Client Secret and paste it here. Note: when creating the Client Secret for an Azure app, you must copy it while creating the app because it will no longer be visible after that. If you fail to copy it at that time then you must delete the secret and create a new one.

Redirect URI

You must specify a Redirect URI when creating your OAuth 2.0 app for Gmail or Office 365. The Redirect URI displayed on the MultiPOP screen is an example built from your Default Domain's SMTP host name, which should work for that domain's users when signing in to Webmail. You should add additional Redirect URIs to your app for any additional MDaemon domains your users go to when signing in to Webmail. For example, "https://mail.example.com/WorldClient.dll?View=OAuth&AuthRequest=Office365" would work for any of your users who go to mail.example.com when signing in to Webmail. See: Creating and Linking Your MultiPOP OAuth App below for more information.

Redirect URI example:

https://mail.example.com/WorldClient.dll?View=OAuth&AuthRequest=Gmail

https://mail.example.com/WorldClient.dll?View=OAuth&AuthRequest=Office365

## Creating and Linking Your MultiPOP OAuth App

Step-by-step instructions for creating your MultiPOP OAuth 2.0 app.

For Google Gmail Follow the steps below to create a Google application to allow MultiPOP to authenticate using OAuth 2.0 when collecting mail from Gmail for your users. 1.In your browser, go to the Google API console. 2.If on the Project List, click NEW PROJECT, or if on the Manage Resources page, click (+) CREATE PROJECT. 3.Type a Project name, then click Edit if you wish to edit the Project ID, or leave it set to the default value. Note: the Project ID cannot be changed after the project is created. 4.In the left pane, go to APIs & Services | OAuth consent screen. 5.Select External, and click Create. 6.Enter the App name (e.g. MultiPOP OAuth 2.0 for Gmail), a Support email address for users to contact, and a Developer email address for Google to contact about changes to your project. That is all that's required on this page for setup, but depending on your particular organization or verification requirements, you can also enter your company logo and links to your Terms of Service and Privacy Policy. The Authorized domains fields will be filled in for you automatically when you add the Redirect URIs in a later step below. Note: This info is used for the Consent screen that will be presented to users for authorizing MultiPOP to collect from Gmail. 7.Click Save and Continue. 8.Click ADD OR REMOVE SCOPES, and under "Manually add scopes," enter https://mail.google.com/. Click ADD TO TABLE, then click Update. 9.Click Save and Continue. 10.Under Test Users, click ADD USERS, enter each Gmail account from which you will be collecting mail, and click ADD (see the note below about your app's Publishing Status). 11.Click Save and Continue. 12.On Summary, click BACK TO DASHBOARD at the bottom of the page. 13.Click Credentials in the left pane, click (+) Create Credentials, and select OAuth client ID. 14.In the "Application type" drop-down box, select Web application, and under "Authorized redirect URIs", click + ADD URIs. Enter the Redirect URI. The Redirect URI displayed on the MultiPOP screen is an example built from your Default Domain's SMTP host name, which should work for that domain's users when signing in to Webmail. You should add additional Redirect URIs to your app for any additional MDaemon domains your users go to when signing in to Webmail. For example, "https://mail.example.com/WorldClient.dll?View=OAuth&AuthRequest=Gmail" would work for any of your users who go to mail.example.com when signing in to Webmail. 15.Click CREATE. 16.Copy the values in Your Client ID and Your Client Secret to the Gmail Client ID and Client Secret boxes on the MultiPOP page.
| Publishing Status — These instructions are for creating a Google app with the Publishing Status set to "Testing". This requires you to add each specific Google account that will be using the app to collect their mail from Gmail, and it is limited to 100 users. Further, in Webmail when your users are asked to authorize MDaemon to collect their mail from Gmail, a warning message will be displayed "to confirm the user has test access to your project but should consider the risks associated with granting access to their data to an unverified app." Also, authorization expires after seven days, therefore each user would be required to reauthorize collection from Gmail every week. If you wish to remove these requirements and limitations then you must change your status to "In Production", which may or may not require you to go through a verification process. For more information on app verification and publishing status, see the following Google articles: Setting up your OAuth consent screen and OAuth API verification FAQs.
For Microsoft (Office) 365 Follow the steps below to create a Microsoft Azure application to allow MultiPOP to authenticate using OAuth 2.0 when collecting Office 365 email for your users. 1.Go to the Microsoft Azure Active Directory page at the Azure Portal and click App Registrations in the left pane (you must sign-up for a free or pay-as-you-go Azure account if you don't have one already). 2.Click + New Registration. 3.Enter an application name in the Name field (e.g. "Mailbox OAuth for Office 365"). 4.For "Supported account types" select Accounts in any organizational directory (Any Azure AD directory - Multitenant). 5.For "Redirect URI" select web and then enter your Office 365 Redirect URI. The Redirect URI displayed on the MultiPOP screen is an example built from your Default Domain's SMTP host name, which should work for that domain's users when signing in to Webmail. You should add additional Redirect URIs to your app for any additional MDaemon domains your users go to when signing in to Webmail. For example, "https://mail.example.com/WorldClient.dll?View=OAuth&AuthRequest=Office365" would work for any of your users who go to mail.example.com when signing in to Webmail. 6.Click Register. 7.Make note of the Application (client) ID (there is a copy to clipboard button beside it). You can find this ID later by clicking Overview in the left pane. 8.If you need to add additional Redirect URIs, click the Redirect URIs: 1 web link on the right. Click Add URI and enter the URI, repeating as necessary, and click Save. 9.Click API Permissions in the left pane. 10.Click + Add a permission. 11.Click Microsoft Graph. 12.Click Delegated Permissions. 13.Scroll down to POP and select POP.AccessAsUser.All, then under User select and User.Read (User.Read is already selected by default). 14.Click Add permissions. 15.In the left pane, click Certificates & Secrets. 16.Click + New Client Secret. 17.Enter a description (e.g. "Client secret for Office 365 MultiPOP OAuth app"). 18.Select how long before the client secret expires. 19.Click Add. 20.Make note of the generated client secret in the Value field (there is a copy to clipboard button beside it). NOTE: the client secret will not be viewable again on this page—there will be a Delete icon beside the entry so that you can delete it and create a new client secret when necessary. 21.Enter the Application (client) ID and Client Secret values into the Client ID and Client Secret fields under the Office 365 section of MDaemon's MultiPOP page under Server Settings.

See:

Account Editor | MultiPOP

Mail Scheduling | MultiPOP Collection

MDaemon v25.5.0 - October 2025. Copyright © 1996-2025. All rights reserved. MDaemon Technologies