Open
Bug 1221918
Opened 9 years ago
Updated 2 years ago
Shared calendar invitation invalid ics format
Categories
(Calendar :: Provider: ICS/WebDAV, defect)
Tracking
(Not tracked)
UNCONFIRMED
People
(Reporter: jan.kraljic, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:41.0) Gecko/20100101 Firefox/41.0 Build ID: 20151015172656 Steps to reproduce: External reference: http://www.sogo.nu/bugs/view.php?id=3368 by bear-cave Adding event to shared calendar does not necessarily send invitations If a user creates an event with invitees in a shared calendar they have permission to access but do not own using a CalDAV connected device, SOGo may not send emails to the invitees, depending on the device. iOS 9, Android via DMFS CalDAV Sync, Mozilla Lightning: No email sent. Mac OS 10.10.1: Email sent. I have reports that a Blackberry device works. I am checking this. Steps To Reproduce Given regular SOGo accounts sogo1, sogo2 and sogo3. As sogo1, share personal calendar with sogo2 and sogo3, giving them write access. Actual results: According to bear-cave: After examining the .ics sent by the above devices, it looks like a Mac works because it sets the ORGANIZER to be the *owner* of the shared calendar, sogo1. iOS, Android and Lightning set the ORGANIZER to be the arranger of the meeting, sogo2. The web interface sets the ORGANIZER to be the calendar owner sogo1, but adds a SENT-BY clause specifying the arranger, sogo2. A quick read of RFC2445 suggests that, strictly speaking, the web interface may have the balance of right on its side. In which case all the above clients are wrong... Expected results: ICS should be generated according to RFC2445 and define "SENT-BY".
Comment 1•9 years ago
|
||
Lightning sets the organizer to the email identity configured for the respective calendar. Which do you have set in your scenario? Is the user1 also allowed to sent emails on behave if the organizer?
Reporter | ||
Comment 2•9 years ago
|
||
a) In Example when user2 is using shared calender user1. The Email that is set is user2. b) I would expect that then user2 is sending email, since user2 is organizer. c) I would get back to you when I recheck ACL for sending.
Comment 3•9 years ago
|
||
OT: RFC2445 is obsolete. Use RFC5545 instead.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•