644131 - Meeting requests / event invitations to "local" users directly show up as unconfirmed events

Status: RESOLVED DUPLICATE of bug 1074513

(Calendar :: Provider: CalDAV, defect)

Description

[Nick Long]

User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10_6_6; en-US) AppleWebKit/533.4 (KHTML, like Gecko) Iron/5.0.381.0 Chrome/5.0.381 Safari/533.4
Build Identifier: Thunderbird 3.1.7 - Lightning 1.0b2 as well as latest night build

I'm using Darwin CalendarServer (Apple's CalDAV server) running on a Debian Squeeze server

When creating an event and inviting people who are local users on the same CalDAV server (i.e. no iMiP, availability and transmission of the invitation is handled internally by the server, no email is sent), it works perfectly on Apple's iCal client: invitees get a notification and are asked for Accept/Decline/Maybe.

On Thunderbird+Lightning clients, the events automatically appears on the invitee's calendar, without any notification/warning, no accept/decline/maybe, no way to accept the event.
The event in his calendar is set as "Available".

If the event is deleted by the invitee from his calendar, the event owner/organizer sees this invitee as 

Reproducible: Always

Steps to Reproduce:
1. Create an event on John's calendar (let's say a meeting)
2. Invite Robert and Danny (both users on the same CalDAV server) to this event (for example in iCal on a Mac)
3. Danny receives a warning and a request to accept/decline/maybe the event on iCal on his Mac
4. Robert sees a new event appearing in his Windows Lightning calendar, no warning, no accept/decline/maybe.

Actual Results:  
Our Windows users see events auto-magically appearing on their calendar and can't handle the meeting requests...

Expected Results:  
Notify for an incoming event invitation, ask for Accept/Decline/Maybe

Comment 1

[Philipp Kewisch [:Fallen][☁️📆]]

Do you get an "Invitations: NNN" item in the status bar? We should have an invitations manager, but since I don't have a server with auto-scheduling I haven't tried this in a long time.

Comment 2

[Nick Long]

Nope !

Comment 3

[Philipp Kewisch [:Fallen][☁️📆]]

Felix, you have an Apple server with auto-scheduling, right? Can you confirm this?

Comment 4

[Nick Long]

BTW I have an Apple Server with auto-scheduling on, but enabled only on the two "locations" (meeting rooms) calendars I have, and the problem is appearing on a user calendar (i.e. without any auto-scheduling option in the account configuration).

Comment 5

[Felix Möller]

(In reply to comment #4)
> BTW I have an Apple Server with auto-scheduling on, but enabled only on the two
> "locations" (meeting rooms) calendars I have, and the problem is appearing on a
> user calendar (i.e. without any auto-scheduling option in the account
> configuration).
Hi Nick, could you explain my what to do in configuration to set it that way?

What version of the Calendar Server are you running? Are you running current trunk or are you still on 2.4?

Philipp, I infact have a Calendar Server running. Sadly it through an exception at the moment when I inivite a second internal user it seems. :-(

Comment 6

[Philipp Kewisch [:Fallen][☁️📆]]

(In reply to comment #4)
> BTW I have an Apple Server with auto-scheduling on, but enabled only on the two
With auto-scheduling I was rather referring to the CalDAV Server capability calendar-auto-schedule that tells the client that the server will take care of sending emails and the client should not.

Comment 7

[Nick Long]

Hi,

I'm using 2.4, via the official Debian Squeeze package (on a very standard Debian Squeeze install).

I'm using most of the default settings.

For locations with auto-schedule (i.e. when someone books a meeting in a room which is available during the metting's timeslot, it's automagically booked/confirmed/writted in the location's calendar), I just add the option:

    <auto-schedule/>


in the accounts.xml file

For standard users (other entries in the same file), there's no such option.

Cheers,
Nick

Comment 8

[Philipp Kewisch [:Fallen][☁️📆]]

Possibly this is already "fixed" by the calendar.caldav.sched pref, but enabling that is currently broken per bug 760827.

Another possibility is that we are not setting SCHEDULE-AGENT=CLIENT if we want to handle the invitation ourselves.

Comment 9

[Philipp Kewisch [:Fallen][☁️📆]]

Unfortunately we are going to remove inbox polling for now since its been broken for multiple releases anyway. We will add this back in once we have a better implementation and have done some cleanup in the caldav provider.