Skip to content
This repository has been archived by the owner on Nov 21, 2024. It is now read-only.

Sender and Reply-To for emails #386

Open
NotSpecial opened this issue Apr 2, 2019 · 3 comments
Open

Sender and Reply-To for emails #386

NotSpecial opened this issue Apr 2, 2019 · 3 comments
Labels
unresolved Further discussion required.

Comments

@NotSpecial
Copy link
Contributor

NotSpecial commented Apr 2, 2019

Currently, all emails are sent from [email protected] and some uses use this address for replies. This is suboptimal, as the IT team and API devs, which receive mails aimed at [email protected], can rarely help with issues regarding events etc.

This raises two questions:

  1. Should we keep sending mails from [email protected], or should we switch to something like [email protected]?

  2. Should we add a reply-to address? If so, which address would be appropriate? Maybe [email protected]? (E.g. for the blacklist, a separate reply-to address might be used, e.g. [email protected])

@I98, @temparus, @hermannsblum , @cburchert -- what do you think?

@NotSpecial NotSpecial added the unresolved Further discussion required. label Apr 2, 2019
@hermannsblum
Copy link
Contributor

As stated in my comment to your PR, I think we need one of the two.
As users always have the option to answer to emails, it is unintuitive that your answer concerning e.g. your signup conformation is send to the api devs and not somebody responsible for the event.
Best option therefore would be to set reply-to to the email of the event moderator if existing, otherwise probably a per-resource fallback.

@temparus
Copy link
Member

temparus commented Apr 2, 2019 via email

@gingeneer
Copy link

I would suggest sending the emails from [email protected] and add a line to the message body along the lines of "If you have any questions, please write [email protected]".

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
unresolved Further discussion required.
Projects
None yet
Development

No branches or pull requests

4 participants