INBOUNDEMAILUSER - Detailed description

Overview

Parameters:INBOUNDEMAILUSER
Category: Custom
Default value: String.Empty
Product: eTASK.Other (Custom)

What does this parameter do?

INBOUNDEMAILUSER defines the username for accessing incoming email inboxes. This parameter is used together with INBOUNDEMAILPASSWORD to retrieve emails from configured incoming mailboxes.

What is this parameter used for?

• Authentication with the email inbox for incoming emails

• Retrieving emails from configured inbox mailboxes via timer jobs

• Connecting to Exchange servers or Outlook 365 for email processing

• Automatic email processing in the eTASK system

Technical Details (for Administrators)

Format: Text string (email address or username)
Default value: String.Empty (empty)

Valid values:

• Email address (e.g., "service@ihr-unternehmen.de")

• Username for the email account

• Empty (String.Empty) if email retrieval is not configured

Important notes:

• The username is stored unencrypted in the database (UpdateDatabase: false)

• Used in combination with INBOUNDEMAILPASSWORD for authentication

• The value is used directly for logging in to the email server

Interaction with other parameters:

• INBOUNDEMAILPASSWORD: The encrypted password

• EWSURL: The URL of the Exchange Web Services for mail retrieval

When should you change this value?

Set the value (enter the username) if:

• An incoming email mailbox needs to be configured for automatic mail retrieval

• A new mailbox is being set up for email processing

• A migration to a new email system with different login credentials is taking place

• The service account’s email address has been updated

Leave the value blank (String.Empty) if:

• No automatic email retrieval is required

• The email functionality is not used

• Only outgoing emails are to be sent

Important Notes

1. Unencrypted storage
   Unlike the password, the username is stored unencrypted. This is common practice, as usernames are generally not as security-critical as passwords.

2. Email Address vs. Username
   Depending on the email system, either the full email address (e.g., "service@firma.de") or just the username (e.g., "service") may be required here. Check the requirements of your email server.

3. Timer Job Dependency
   This parameter is used by timer jobs that regularly check the mailbox. Incorrect usernames can lead to authentication errors.

4. No Spaces
   Avoid leading or trailing spaces in the username, as these can cause authentication issues.

Security

Does changing this parameter affect security?

Yes, although the username itself is less critical than the password, it is part of the authentication data and has security-related implications.

Positive aspects:

• Enables the use of dedicated service accounts

• Transparent storage facilitates troubleshooting

• Allows for separate accounts for different functions

Note:

• The username is visible to anyone with access to the system configuration

• In combination with a compromised password, this allows access to the email inbox

• If changed, INBOUNDEMAILPASSWORD must also be re-encrypted

• Should only be accessible to authorized administrators

• Authentication attempts will fail if the username is incorrect

Data protection assessment:

• The username itself usually does not contain any personal data (except in cases of naming conventions such as "firstname.lastname")

• Changes should be documented

• When using personal usernames, GDPR requirements must be observed

Recommendation: Use dedicated email accounts for automatic mail retrieval with functional usernames (e.g., "service," "tickets," "support") instead of personal names. Restrict access to the system configuration to authorized administrators.

Practical example

Initial situation: Your company wants to automatically capture incoming service requests via email in the eTASK system. To do this, a dedicated mailbox "service@ihr-unternehmen.de" with the username "service@ihr-unternehmen.de" was set up.

Configuration:

1. INBOUNDEMAILUSER = "service@ihr-unternehmen.de"

2. Generate INBOUNDEMAILPASSWORD

After the change:

• Timer job uses "service@ihr-unternehmen.de" as the username

• The system authenticates itself with the email server using these credentials

• New emails are retrieved from the mailbox

• Service tickets are automatically created from emails

• Automated processing runs continuously

Result: Email-based ticket intake works automatically. Service requests are transferred directly from the mailbox to eTASK, which reduces processing time and eliminates manual data entry.

Recommended setting

For standard installations:String.Empty(empty, no email retrieval configured)

Reason:

• Email inbox processing is optional

• Requires additional configuration of mailbox and timer jobs

• Not every installation requires automatic email retrieval

Exceptions (email retrieval required):

• Set INBOUNDEMAILUSER to the email address or username of the service account

• Use descriptive names (e.g., "service@firma.de", "tickets@firma.de")

• Configure INBOUNDEMAILPASSWORD in parallel

• Configure EWSURL for email server access

• Test the connection before going live

note90757168-9e1d-4de1-8a12-17743debb358

Tip: Use dedicated service accounts with functional names for email retrieval. Avoid personal usernames. Securely document the username. If the username changes, remember to reset the password.