Open manu-p opened 3 years ago
It looks like it is not allowed to assign the same email address to more than one resource.
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 Ref https://github.com/nextcloud/server/pull/16615
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.
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.
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: