nextcloud / nextcloud/calendar
Appointments: eMail Sender/'From' Field is misleading - should use 'Reply to'
Open
@SebastianKrupinski is already working on this.
Since Nov 18, 2024.
1. to develop
enhancement
Feature: Appointments
feature: iMip
- Dominant language
- JavaScript
- Stars
- 1.2k
- Forks
- 332
- Avg merge
- 16h 13m
- Merged PRs (30d)
- 137
Description
Is your feature request related to a problem? Please describe.
Currently, there are four different e-mails sent from the server:
- verification of the booker e-mail address
- confirmation of the booking to the booker
- confirmation of the booking to the organizer
- cancelation / date change to the booker
All three e-mails have the problem that the sender/From: field is misleading, because the name of a person is combined with the e-mail address of the server:
From: Organizer Name <noreply@yourserver.org>From: Organizer Name <noreply@yourserver.org>From: Booker Name <noreply@yourserver.org>Form: Organizer Name via Nextcloud instance Name <noreply@yourserver.org>
This causes problems like
- server address getting flagged as spam
- replies that end up going to the noreply address of the server or
- false address association inside mail clients. For example my Apple Mail suggests me now to wite e-mails to a client (that once used the appointment booking) via noreply@ourserver.org.
Describe the solution you'd like
We should use the name of the Nextcloud instance in the From: field and add a Reply to: field with the name and matching e-mail address of the person:
From: Nextcloud Instance Name <noreply@yourserver.org>,Reply to: Organizer Name <organizer@mail.org>From: Nextcloud Instance Name <noreply@yourserver.org>,Reply to: Organizer Name <organizer@mail.org>From: Nextcloud Instance Name <noreply@yourserver.org>,Reply to: Booker Name <booker@sample.com>From: Nextcloud Instance Name <noreply@yourserver.org>,Reply to: Organizer Name <organizer@mail.org>
Describe alternatives you've considered
No response
Additional context
We should then also remove the sentence in the bottom of the e-mails, saying Please don't anser to this e-mail.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.