6.0.0-git
2019-05-25

[#14135] Email notifications from each meeting attendee when event is created via calDAV
Summary Email notifications from each meeting attendee when event is created via calDAV
Queue Kronolith
Queue Version 4.2.9
Type Bug
State Not A Bug
Priority 1. Low
Owners
Requester tim.odriscoll (at) lambrookschool (dot) co (dot) uk
Created 2015-10-12 (1321 days ago)
Due
Updated 2015-10-29 (1304 days ago)
Assigned 2015-10-28 (1305 days ago)
Resolved 2015-10-29 (1304 days ago)
Milestone
Patch No

History
2015-10-29 12:23:37 Michael Rubinsky Comment #8
State ⇒ Not A Bug
Reply to this comment
As I understand from the sources, an itip notification is sent, when 
the event is saved, regardless of any changes in its fields.
This is true. However, depending on the synchronization method, this 
might require quite a bit of extra processing - something that is 
probably not worth it considering this is to work around broken 
clients that trigger an event save when you press the "close" button 
and wouldn't help the main point of this ticket - that *clients* are 
sending the iTip notifications directly, not the server.

However, feel free to open an "Enhancement" request for this.
2015-10-29 05:16:43 Christopher (dot) Etz (at) time2bi (dot) de Comment #7 Reply to this comment
As I understand from the sources, an itip notification is sent, when 
the event is saved, regardless of any changes in its fields.
I'd be happy to have an additional check, that the event actually has 
been changed somewhere, before the notification is sent.

(I can read the sources, but I am not able to write PHP.)

Cheers
Christopher
2015-10-28 22:17:09 tim (dot) odriscoll (at) lambrookschool (dot) co (dot) uk Comment #6 Reply to this comment
This sounds like a client issue. There is no code in Horde that 
would iterate over attendees to send emails from them.
I agree - I believe it's to do with my DAV plugin (Bynari's WebDAV 
Collaborator) and OL. One of my users has just received an '<user> 
wishes to make you aware of' emails from an event in 2013, where 
<user> is the recipient.

As was mentioned before by Christopher, I believe OL2013 is 'updating' 
the event when it is opened/highlighted and that is causing the DAV 
plugin think it's changed and resync with Kronolith and then OL to 
notify all the attendee's.

Feel free to close this ticket - it's just another OL issue..

Tim
2015-10-28 16:23:56 Michael Rubinsky Comment #5 Reply to this comment
I cannot reproduce this.

I'm using OL2013 with the "Open Protocols" connector, craete a 
meeting request where I invite two other attendees. Each attendee, 
including myself,
Slight correction - the organizer does not receive any iTip email.

2015-10-28 16:22:35 Michael Rubinsky Comment #4
State ⇒ Feedback
Priority ⇒ 1. Low
Reply to this comment
I cannot reproduce this.

I'm using OL2013 with the "Open Protocols" connector, craete a meeting 
request where I invite two other attendees. Each attendee, including 
myself, receives one email from myself (the meeting organizer). WIthin 
that iTip email, the attendees are listed, but only one email is 
received.

This sounds like a client issue. There is no code in Horde that would 
iterate over attendees to send emails from them.
2015-10-14 13:24:16 tim (dot) odriscoll (at) lambrookschool (dot) co (dot) uk Comment #3 Reply to this comment
Hi Christopher,

You make a very good point..

I've investigated my situation further: A user logs onto two different 
PCs using Outlook 2013 with a calDAV connector. If she accepts a load 
of event invitations on one PC, the next time she logs onto the other 
PC (and the calDAV connector syncs the calendar) she'll get a load of 
'wishes to make you aware of' notifications from her own email address 
(as do other event attendee's).

The usual response I have to deal with is 'it never happened with 
Exchange'.. For now I've set up a mailbox filter to at least try and 
quiet down her inbox..

Tim
2015-10-12 13:38:36 Christopher (dot) Etz (at) time2bi (dot) de Comment #2 Reply to this comment
Hello,

every save operation of an event generates notifications to all 
participants. And, depending on the mail reader program, the save 
operation cannot be avoided or is hard to avoid.
Some generate save operations when the event is opened, others use 
popups which generate save operations when closed via "OK". Here, an 
"Abort" avoids saving the event. (But it's hard to teach all users to 
use the "Abort" button.)
Nevertheless, I definitively vote for generating notifications, only 
when event data have changed, or -- even better -- to make it 
configuarble.

Cheers,
Christopher
2015-10-12 13:20:45 tim (dot) odriscoll (at) lambrookschool (dot) co (dot) uk Comment #1
Type ⇒ Bug
State ⇒ Unconfirmed
Priority ⇒ 2. Medium
Summary ⇒ Email notifications from each meeting attendee when event is created via calDAV
Queue ⇒ Kronolith
Milestone ⇒
Patch ⇒ No
Reply to this comment
Hello,

This only occurs when the users are using calDAV. Our environment uses 
Outlook 2013 with a calDAV plugin for calendar access.

If a user creates an event and invites some other users, each one of 
those users will get an email notification ('<user> wishes to make you 
aware of <meeting>') from each one of the attendee's. For example:

User1 creates event, invites User2,User3,User4.
User1 gets an email notification from User1,User2,User3,User4 '<user> 
wishes to make you aware of <meeting>'
User2 gets an email notification from User1,User2,User3,User4 '<user> 
wishes to make you aware of <meeting>'
User3 gets an email notification from User1,User2,User3,User4 '<user> 
wishes to make you aware of <meeting>'
User4 gets an email notification from User1,User2,User3,User4 '<user> 
wishes to make you aware of <meeting>'

So in this example each user will get 4 notification emails as soon as 
the original event invite is received in each of the attendee's 
calendar (including their own).

Many thanks,

Tim

Saved Queries