MAILFROMADDRESS - Detailed description

Overview

Parameter:MAILFROMADDRESS
Category: SMTP
Default value: eTASK-FM-Portal@etask.de
Product: eTASK.Other (SMTP)

What does this parameter do?

This parameter specifies the email sender address used for all emails automatically sent by the eTASK portal. This address appears in the "From" field of emails sent by the system, such as notifications, workflow messages, or password resets.

What is this parameter used for?

• Central sender address: Uniform email sender for all messages sent by the portal

• Workflow notifications: Sender for automated emails from approval processes and ticket systems

• System notifications: Sender for password resets, invitations, and reminders

• Professional communication: Corporate identity through a consistent sender address

• Reply control: Receiving address for replies to portal emails

Technical Details (for Administrators)

Format: Email address (string)
Default value: eTASK-FM-Portal@etask.de

Valid values:

• Full email address: portal@firma.de

• With company domain: noreply@unternehmen.com

• Department-specific: facility-management@firma.de

Important notes:

• The address should actually exist and be reachable

• Recipients can reply to this address

• The address is used for all automatic emails from the portal

• If the address does not exist, replies will be lost

• The address should match the company domain

Interaction with other parameters:

• MAILFROMNAME: Defines the display name that appears alongside this address

• SMTPSERVER: Specifies the mail server through which emails are sent

• IGNOREDDOMAINS: Filters specific domains from email delivery

When should you change this value?

Change the value to your company email if:

• You want emails to appear as coming from your official company domain

• Recipients should recognize the sender address as trustworthy

• You want replies to portal emails to go to your company

• Spam filters might block the default address

• Corporate identity guidelines require a company-specific sender address

Leave the default value if:

• You are in a test or development environment

• No company-specific email address has been set up for the portal yet

• The configuration is temporary

• You want to test the functionality first

• The mail server has not yet been fully configured

Important Notes

1. The email address must exist
   Use only email addresses that actually exist and are actively monitored. Recipients might reply to portal emails, and these replies should not be lost.

2. Be
   mindful of spam filters Ensure that the selected sender address is authorized by the SMTP server. Many email servers check whether the sender address belongs to the sending domain and reject emails if it does not.

3. Consider using "noreply@"
   addresses If you use a "noreply@" address, users cannot reply to portal emails. Consider whether this is desirable or if a monitored address would be more appropriate.

4. Consistency with display names
   Combine this address appropriately with the MAILFROMNAME parameter to achieve a professional and clear sender display.

5. Prepare for
   production deployment Change the default address to a company-specific address at the latest before going live to avoid confusion and demonstrate professionalism.

Security

Does changing this parameter affect security?

Yes, the correct configuration has a significant impact on email security and trustworthiness.

Positive aspects:

• A correct sender address prevents emails from being marked as spam

• A company domain increases trustworthiness with the recipient

• Genuine addresses enable legitimate communication

• SPF/DKIM authentication only works with a correct sender address

• Reduces phishing risk through unique sender identification

Note:

• Incorrect configuration can block emails: SMTP servers reject emails if the sender address is not authorized

• Risk of spoofing: Incorrectly configured addresses could be interpreted as a spoofing attempt

• Data protection: The sender address should not contain any personal data unless specifically desired

• Replies may contain sensitive data: Ensure that the mailbox is securely monitored

Recommendation: Use an official email address from your company domain that is authorized by the SMTP server. Configure SPF and DKIM records in your domain’s DNS to prevent emails from being marked as spam. Monitor the mailbox regularly or set up a dedicated NoReply address if replies are not desired.

Practical example

Initial situation: A facility management company uses eTASK in production and sends automatic emails daily for workflow notifications and ticket updates. Currently, the default sender address is still configured eTASK-FM-Portal@etask.de is still configured. Recipients are confused because the emails do not originate from the familiar company domain, and some spam filters block the messages.

Configuration: The administrator changes MAILFROMADDRESS to portal@fm-beispiel-gmbh.de and ensures that this address exists and that the SMTP server authorizes it as the sender. Additionally, MAILFROMNAME is set to "eTASK Portal FM-Example Inc."

After the change:

• All portal emails now originate from portal@fm-beispiel-gmbh.de

• Recipients immediately recognize that the emails come from the company portal

• Spam filters accept the emails because they originate from a verified company domain

• Employees can reply to the emails received in their inbox if they have any questions

• A professional public image is ensured

Result: The delivery rate of portal emails rises to nearly 100% since spam filters no longer block them. Recipients have greater trust in the messages and respond more quickly to workflow notifications. The IT team can process replies centrally in the portal inbox and provide additional support as needed.

Alternative scenarios:

Scenario A – Use a NoReply address:

• Set MAILFROMADDRESS on noreply@fm-gmbh.de

• Prevents unwanted replies to automated emails

• Additional note in email signature: "Please do not reply to this email"

Scenario B - Department-specific address:

• Set MAILFROMADDRESS to facility-management@firma.de

• Direct assignment to the responsible department

• Replies are automatically routed to the correct team mailbox

Recommended setting

For standard installations: Company email address (e.g., portal@unternehmen.de)

Reason:

• Professional public image through company domain

• Higher delivery rate by avoiding spam filters

• Trustworthiness among recipients

• Ability to communicate via a real mailbox

Exceptions (temporarily retain default address):

• Test and development environments without production email sending

• Initial setup phase prior to full SMTP configuration

• Proof-of-concept installations

• Training and demonstration systems

Tip: Create a dedicated email address specifically for the eTASK portal (e.g., etask@unternehmen.de or portal@unternehmen.de). Set up automatic forwarding for this address to the relevant support team so that replies do not go unanswered. After configuration, thoroughly test email delivery to ensure that both internal and external recipients receive the emails.