-
Notifications
You must be signed in to change notification settings - Fork 14
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
Duplicate entry 'email' for key 'calresources_resources_eml' #22
Comments
The email is not a real email. It identifies the resource. Hence it has to be unique. |
It's also the email address that receives the invitation when the resource is being booked, and from which the booking is accepted or not. Isn't it? |
It's not. Nextcloud will schedule them automatically. Ref https://docs.nextcloud.com/server/latest/admin_manual/groupware/calendar.html#resources-and-rooms |
OK. How can an email not be a 'real email'? When I book a resource, I can see an email is sent to the email address (or alias) that's been associated to the resource. Is there not a relation between 'contact_person_user_id' and 'email'? I think I'll wait for a documentation before continuing the tests. |
This is still the behaviour I observe in 0.5.0 with NC27. It floods the mailaddress specified in the NC settings with "can not deliver" responses, when the email address for the ressource not exists. |
Hi,
It looks like it is not allowed to assign the same email address to more than one resource.
Let's say I want to set up "hotspots" resources, we get more than one and they're all under the responsibility of the same guy.
So here's what I enter:
Right, here's for the 1st one.
Then:
And here's what I get:
The text was updated successfully, but these errors were encountered: