Configuration of the UMA's email server
New article with version: 3.3 (12.2022)
notempty
This article refers to a Resellerpreview
Introduction
The UMA allows various setup options for the external email server.
Email-Server
Remote email-server settings Remote email-server settings
| |||
| Caption | Value | Description |  |
|---|---|---|---|
| Email Domain: | » ✕ttt-point.de | The email domains for the remote email-server are entered | |
Remote smarthost settings Remote smarthost settings
| |||
| Server: | smtp.anyideas.de | The server name |  |
| Return address: | user@anyideas.de | The email address of the user account | |
| Username: | user | The user account name | |
| Password: | *********** | The user account password | |
| Port: | 25 | The connection port | |
| Connection security: | The security type of the connection. The associated default port is also displayed. | ||
| Trust all certificates: | |||
| Test email address: | When the button is clicked, a test email is sent to the entered email address | ||
Remote email accounts Remote email accounts
| |||
| Status: | Displays the status of the fetchmail service. The button stops the service. |  | |
| Enable debugging: | When activated debugging is enabled. The button opens the log window. | ||
For Auto, POP3 and IMAP protocolFor Auto, POP3 and IMAP protocol
| |||
| Name: | Journal account | Freely selectable name |  |
| Protocol: | used protocol | ||
| Servername: | imap.mailsever.anyideas.de | Mail server that hosts the journal address. | |
| Username: | tttpointcloud | User name for the Journal-email account | |
| Password: | ••••• | Password for the journal email account | |
| Fetch all emails: | Sets the time frame in which the emails are to be fetched | ||
| Keep mails: | Usually, emails are deleted after they have been picked up. Activating Keepmails prevents this deletion. | ||
| SSL: | Requires an SSL connection on activation | ||
| Max. email size | disabled | A size can be defined up to which the email is archived | |
| Email header evaluation: | default |
The recognition of the header entries "MS journal envelope" enables the UMA BCC recipient to recognize in the Exchange-own header and assign it to a user account. BCC recipients are not in the original mail header | |
| Uses the original header of the email to assign it to a user account | |||
| Uses only the X-Envelope-To entry from the original header of the email to assign it to a user account | |||
| Uses only the X-Original-To entry from the original header of the email to assign it to a user account | |||
| Uses only the Delivered-To entry from the original header of the email to assign it to a user account | |||
| A custom defined header part to be evaluated. Example: envelope-from | |||
For OAuth 2 protocolFor OAuth 2 protocol
| |||
| Name: | Journal account | Freely selectable name |  |
| Protocol: | used protocol | ||
| Servername: | outlook.office365.com | ||
| Tenant ID: | aaaabbbb-1111-2222-3333-… | In Microsoft Azure in the menu Azure Active Directory / Overview under Tenant ID | |
| Client ID: | 11111111-aaaa-bbbb-2222-… | In Microsoft Azure, in the menu Enterprise Applications / All Applications / Application name / Overview under Application ID | |
| Username: | ttt-point@anyideas.onmicrosoft.com | Username for the journal email account in Azure | |
| Client Secret: | 33334444-dddd-eeee-ffff-… | In Microsoft Azure in the menu Certificates & Secrets in the tab Client Secrets under Value | |
| Fetch all emails: | Specifies how often the external mail server is checked for new emails | ||
| Keep mails: | Usually, emails are deleted after they have been picked up. Activating Keepmails prevents this deletion. Keepmails should only be used temporarily for test purposes, or if it is otherwise ensured that the external mailbox does not reach its capacity limit. | ||
| SSL: | Requires an SSL connection on activation | ||
| Max. email size | disabled | A size can be defined up to which the email is archived | |
| Email header evaluation: | default |
The recognition of the header entries "MS journal envelope" enables the UMA BCC recipient to recognize in the Exchange-own header and assign it to a user account. BCC recipients are not in the original mail header | |
| Uses the original header of the email to assign it to a user account | |||
| Uses only the X-Envelope-To entry from the original header of the email to assign it to a user account | |||
| Uses only the X-Original-To entry from the original header of the email to assign it to a user account | |||
| Uses only the Delivered-To entry from the original header of the email to assign it to a user account | |||
| A custom defined header part to be evaluated. Example: envelope-from | |||