Overview
Parameter:EXRECIPIENTMAIL
Category: SMTP
Default value: log@etask.de
Product: eTASK.Other (SMTP)
What does this parameter do?
This parameter defines the email address to which automatic notifications regarding timer job results and technical errors (exceptions) are sent, provided that the corresponding notification functions are enabled.
What is this parameter used for?
Central recipient address for automated system notifications
Receiving error reports for critical system errors
Receiving timer job results and status messages
Monitoring of system operations via automatic email alerts
Technical Details (for Administrators)
Format: Email address (string)
Default value: log@etask.de
Important notes:
The address is only used if EXNOTIFYEMAILFLAG or SENDTIMERJOBMAILSTOEXRECIPIENT are enabled
For timer jobs, the address is also used for result notifications
A working SMTP configuration is required
Dependent parameters:
EXNOTIFYEMAILFLAG: Enables/disables email notifications for errors
SENDTIMERJOBMAILSTOEXRECIPIENT: Enables/disables email notifications for timer job results
When should you change this value?
Change the value to an internal email address when:
The system goes into production
You want to receive error notifications sent to your IT team
You want to monitor timer job results
You want to enable one of the notification functions (EXNOTIFYEMAILFLAG or SENDTIMERJOBMAILSTOEXRECIPIENT)
Leave the default value if:
You do not want automatic notifications
The dependent parameters are already disabled
An agreement has been made with eTASK Support
Important notes
Default value not suitable for production
use The default valuelog@etask.deis an internal eTASK address and should be changed to your own email address before activating the notification functions.Notifications must be activated separately
Simply changing this email address does not result in emails being sent. You must also set EXNOTIFYEMAILFLAG or SENDTIMERJOBMAILSTOEXRECIPIENT1.Note email volume
Depending on system activity and activated notifications, a large volume of emails could be generated in the event of an error. Ideally, use a dedicated monitoring address.
Security
Does changing this parameter affect security?
No, this parameter has no direct impact on security.
Changing the email address does not affect authentication or authorization mechanisms
No new access options are created
Data protection assessment:
The emails may contain technical error details, stack traces, and system information
In sensitive environments, it should be ensured that the recipient address is trustworthy
Error reports may potentially contain personal data from the error context
The recipient address should only be accessible to authorized IT personnel
Conclusion: The parameter is not security-relevant, but from a data protection perspective, the recipient address should be chosen carefully and access to it should be controlled.
Practical example
Initial situation:
A company wants to monitor its eTASK production system. The parameters EXNOTIFYEMAILFLAG and SENDTIMERJOBMAILSTOEXRECIPIENT are to be activated, but the notifications should not be sent to log@etask.de .
Configuration:
The administrator changes EXRECIPIENTMAIL from log@etask.de to etask-monitoring@firma.de and then activates EXNOTIFYEMAILFLAG (1) and SENDTIMERJOBMAILSTOEXRECIPIENT (1).
After the change:
If an error with LogLevel "Error" occurs,
etask-monitoring@firma.dea detailed error messageTimer jobs also send their results to
etask-monitoring@firma.deThe IT team can set up mailbox monitoring and trigger alerts for specific keywords
Errors are detected proactively without the need to manually check logs
Result:
Centralized monitoring of the eTASK system via a dedicated monitoring email address with full control over notifications.
Recommended setting
For standard installations: Dedicated email address (e.g., etask-monitoring@firma.de)
Reason:
The default value
log@etask.deis an external address and unsuitable for production useAn internal monitoring address enables controlled monitoring
Dedicated addresses simplify the filtering and processing of notifications
Tip for production environments:
Use a dedicated email address for system monitoring
Set up email rules to highlight critical notifications
Integrate the address into your monitoring system (e.g., forwarding to a ticketing system)
Regularly check whether notifications are arriving (e.g., by triggering test errors)
Caution: Do not forget to change EXRECIPIENTMAIL before activating EXNOTIFYEMAILFLAG or SENDTIMERJOBMAILSTOEXRECIPIENT to avoid unwanted emails being sent to the default address.