Notification message should not be sent to resources if configured on a per-calendar basis

NEW
Unassigned

Status

Calendar
E-mail based Scheduling (iTIP/iMIP)
P5
enhancement
2 years ago
a year ago

People

(Reporter: sebastien.aubry31, Unassigned)

Tracking

Lightning 4.7.4

Details

(Reporter)

Description

2 years ago
User Agent: Mozilla/5.0 (X11; Linux i686 on x86_64; rv:45.0) Gecko/20100101 Firefox/45.0
Build ID: 20160407164938

Steps to reproduce:

- Create a new event involving a resource (meeting room).
- Manually click on the "user" icon next to the meeting room to make it look like a door.

I am asked if I want to send a notification email to all the attendees, which I accepted.


Actual results:

A notification email is sent to the meeting room, which does not have any valid address.



Expected results:

Lightning should know that resources will not read emails, though a dummy email address is needed for free/busy checks.
I do not know how Lightning can know that a principal is a resource: does it get it from the CalDAV server?

The Davical server documentation explains:
"using a non-existant address for scheduling e.g. rooms may be an option."
https://wiki.davical.org/index.php/Free_Busy
, which I did, leading to this problem.
Meeting rooms can also have valid addresses though and respond to them. If you send them a reply, they could track who will be coming. There are various smart systems and ideas for such, I don't think we should stop sending emails in this case.
(Reporter)

Comment 2

2 years ago
Thank you for your reply.
Then, do you think that emailing meeting rooms could at least be an optional behavior? In my case, it will induce email errors, which should be avoidable.
I'm confirming this as an enhancement. I could imagine adding a such pref on a per-calendar basis.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Component: General → E-mail based Scheduling (iTIP/iMIP)
Ever confirmed: true
Summary: Notification message should not be sent to resources → Notification message should not be sent to resources if configured on a per-calendar basis
Priority: -- → P5
You need to log in before you can comment on or make changes to this bug.