Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use support email in the 'closing' text of the system email message #10287

Closed
PaulBoon opened this issue Jan 31, 2024 · 0 comments · Fixed by #10504
Closed

Use support email in the 'closing' text of the system email message #10287

PaulBoon opened this issue Jan 31, 2024 · 0 comments · Fixed by #10504
Milestone

Comments

@PaulBoon
Copy link
Contributor

Overview of the Feature Request
Emails sent by the system contain a 'closing' text that states You may contact us for support at followed by the system email.
However there is an optional JVM setting; dataverse.mail.support-email which can be different from the system email. Using that allows you to prevent problems when the system email is not used for handling support questions.

What kind of user is the feature intended for?
Sysadmins can configure this and all users will get their system emails with improved closing text.

What inspired the request?
We have our system email set as noreply@datastations.nl; clearly not intended for asking support, but now it is used in those emails as suggestion to sent support requests.

What existing behavior do you want changed?
Instead of always using the system email it should use the support email when it is specified by the JVM option.
The existence of the JVM option and the wording in the code; BrandingUtil.getSupportTeamEmailAddress, suggest that using a support email address was intended at some point.

Any open or closed issues related to this feature request?
The installer now can not set the dataverse.mail.support-email option:
#9962

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants