-
Notifications
You must be signed in to change notification settings - Fork 3
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
[RFC] personalize 'Message to All' #118
Comments
The email shows as from support@researchspace.com, because you're using a hosted version of RSpace which uses our email servers. The from address cannot be changed, however we can set a different reply to address. Please open a support ticket with us privately by emailing support@researchspace.com and we can set a custom reply to address |
Dear Ramon, |
RSpace has an option to have a "reply to" address which is different than the "from" address on emails sent by RSpace. This is a global server configuration so can only be changed by us on managed RSpace installs. As GitHub Issues is a public forum, if you have any other questions related to the configuration of your specific RSpace server, please follow up with a private support ticket. |
Dear Ramon,
|
The feature request can stay open for point 1, it would be a nice feature to set the subject of a "Request" and it's contents a bit more. Maybe, in it's current form, even just changing the word "request" to "message" in the current version would be a step in the right direction. Re: 2, I've sent you an email privately to follow this up |
'Message to All' generates a default email coming from 'support@researchspace.com' and with Subject containing the word 'Request'.
It would be really useful to be able to personalize the Subject of the message and/or its content a bit more.
It would be also useful to change the Sender of the message into our local email address so that we can receive replies.
As a SysAdmin I need to inform users about different matters (upgrades, new templates, regulations etc.) which, most of the times, are not considered as Requests
The text was updated successfully, but these errors were encountered: