Configuration of the email accounts that receive all journal emails of a mail server
Last adaptation to the version: 3.3.1 (03.2023)
New:
- Connection Security Options for POP3/IMAP and OAuth 2
- Authentication in Azure possible with OAuth2 (New from v.3.3.0)
Remote email accounts
Remote email accounts
Remote email accounts receive all journal emails from a mail server.
This usually includes several individual user email accounts.
The remote email accounts must be created in the Mail Server as journal accounts, so that all associated mails (outgoing and incoming mails of the mail server) can be received here.
Archiving only takes place if the following settings have been made under System settings / Email accounts users with a corresponding email address can be created.
Add / remove account
Add new accounts with the ,
Remove with the button
Protocol: POP3 / IMAP
| Caption | Value | Description |  |
|---|---|---|---|
| Name: | Journal Account | Freely selectable name | |
| Protocol: | IMAP | used protocol | |
| Servername: | imap.mailsever.anyideas.de | Mail server that hosts the journal address. | |
| Username: | tttpointcloud | User name for the Journal-emai account | |
| Password: | ••••• | Password for the journal email account | |
| Keep Mails: | Usually, emails are deleted after they have been picked up. Activating Keepmails prevents this deletion. | ||
| Connection Security: New as of UMA v3.3.1 |
STARTTLS is used for connection encryption. Default | ||
| SSL is used for connection encryption | |||
| The connection is not encrypted. Should only be used temporarily if the remote station does not support encrypted communication! An update of the remote station is urgently required! E-mails and Passwords are sent in plain text.
Use is not recommended. Use of this option is a security risk | |||
| Max. email size | disabled | A size can be defined up to which the email is archived | |
| Email header evaluation: | Enable MS Journal-Envelope autodetection 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 | |
| Disable MS Journal-Envelope autodetection | Uses the original header of the email to assign it to a user account | ||
| X-Envelope-To | Uses only the X-Envelope-To entry from the original header of the email to assign it to a user account | ||
| X-Original-To | Uses only the X-Original-To entry from the original header of the email to assign it to a user account | ||
| Delivered-To | Uses only the Delivered-To entry from the original header of the email to assign it to a user account | ||
| Custom Recipient Header | A custom defined header part to be evaluated. Example: envelope-from | ||
Protocol: OAuth (IMAP)
New as of UMA NG v3.3
Requirement: Configured apps in Azure with OAuth (→Wiki)
| Caption | Value | Description |  |
|---|---|---|---|
| Name: | Journal Account | Freely selectable name | |
| Protocol: | OAuth 2 (IMAP) | 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 emails every: | 1 minute | 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. | ||
| Connection Security: New as of UMA v3.3.1 |
STARTTLS is used for connection encryption. | ||
| SSL is used for connection encryption. Default | |||
| The connection is not encrypted. Should only be used temporarily if the remote station does not support encrypted communication! An update of the remote station is urgently required! E-mails and Passwords are sent in plain text.
Use is not recommended. Use of this option is a security risk | |||
| Max. email size | disabled | A size can be defined up to which the email is archived | |
| Email header evaluation: | Enable MS Journal-Envelope autodetection 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 | |
| Disable MS Journal-Envelope autodetection | Uses the original header of the email to assign it to a user account | ||
| X-Envelope-To | Uses only the X-Envelope-To entry from the original header of the email to assign it to a user account | ||
| X-Original-To | Uses only the X-Original-To entry from the original header of the email to assign it to a user account | ||
| Delivered-To | Uses only the Delivered-To entry from the original header of the email to assign it to a user account | ||
| Custom Recipient Header | A custom defined header part to be evaluated. Example: envelope-from | ||