Closed Bug 551140 Opened 15 years ago Closed 4 years ago

Outlook replies "Unsupported Calendar Format" while sending repeated events

Categories

(Calendar :: E-mail based Scheduling (iTIP/iMIP), defect)

Lightning 1.0b1
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: thomas.urbitsch, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.8) Gecko/20100202 Firefox/3.5.8 Build Identifier: Lightning 1.0b1 While setting up repeated events and sending invitations for Outlook users, the format of the event is not supported by Outlook Reproducible: Always Steps to Reproduce: 1) Create a new event 2) In the "Repeat" list choose "Custom" 3) In the "Edit Recurrence" choose "Monthly" (for example, I did not try other) 4) Tick the "Repeat Until" in the Range recurrence" 5) Enter a date, e.g. end of current month 6) In the "Recur on Day(s)" click a few days 7) Invite attendees and notify somebody who uses Outlook 8) The invitee receives an unsupported calendar event for the Outlook calendar Actual Results: Unsupported Outlook calendar event is emitted Expected Results: Create Outlook compatible calendar events None, works if done one by one
Version: unspecified → Lightning 1.0b1
Which Outlook version is the receiver using? Each Outlook version has problems with some variant, so it won't be possible to support them all.
(In reply to comment #1) > Which Outlook version is the receiver using? Each Outlook version has problems > with some variant, so it won't be possible to support them all. Hi and thanks for taking into account this request It happens with Outlook 2007 / SP2 It can also be reproduced on Outlook 2003, not knowing which SP It precisely says the following: "not supported calendar message.ics"
Please find hereafter details of the generated ics: Sections, #1 by Lightning, Section #2 equivalent by Outlook By the way: -- when sent by Thunderbird, only the first event is mentioned in the Event Invitation Box -- when sent with Outlook all events are displayed in the box -- Outlook does not have the (nice) CUSTOM feature with choice of any day in recurrence, you can only select days of week always in same order (may be the issue is here??) -- when sending with the CUSTOM option, there's always issue If I can help more, please let me know Cheers Part #1: as generated by Lightning: BEGIN:VCALENDAR PRODID:-//Mozilla.org/NONSGML Mozilla Calendar V1.1//EN VERSION:2.0 METHOD:REQUEST BEGIN:VTIMEZONE TZID:Europe/Paris X-LIC-LOCATION:Europe/Paris BEGIN:DAYLIGHT TZOFFSETFROM:+0100 TZOFFSETTO:+0200 TZNAME:CEST DTSTART:19700329T020000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=3 END:DAYLIGHT BEGIN:STANDARD TZOFFSETFROM:+0200 TZOFFSETTO:+0100 TZNAME:CET DTSTART:19701025T030000 RRULE:FREQ=YEARLY;BYDAY=-1SU;BYMONTH=10 END:STANDARD END:VTIMEZONE BEGIN:VEVENT CREATED:20100315T151058Z LAST-MODIFIED:20100315T151239Z DTSTAMP:20100315T151239Z UID:419f0d20-b0bf-42a4-9796-db4ad16f4b69 SUMMARY:Ultimate trial ORGANIZER;RSVP=TRUE;CN=thomas urbitsch;PARTSTAT=ACCEPTED;ROLE=CHAIR:mailto :thomas.urbitsch@stericsson.com ATTENDEE;RSVP=TRUE;CN=Gregory GOSCINIAK;PARTSTAT=NEEDS-ACTION;ROLE=REQ-PAR TICIPANT:mailto:gregory.gosciniak@stericsson.com RRULE:FREQ=MONTHLY;UNTIL=20100331T110000Z;BYMONTHDAY=16,24,26,27,30,31 DTSTART;TZID=Europe/Paris:20100316T130000 DTEND;TZID=Europe/Paris:20100316T131500 LOCATION:In my office DESCRIPTION:This doesn't work SEQUENCE:1 END:VEVENT END:VCALENDAR Part #2 equivalent by Outlook 2007 SP2 BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2007 VERSION:2.0 BEGIN:VTIMEZONE TZID:Romance Standard Time BEGIN:STANDARD DTSTART:16010101T030000 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T020000 TZOFFSETFROM:+0100 TZOFFSETTO:+0200 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3 END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT ORGANIZER;CN=Gregory GOSCINIAK:MAILTO:gregory.gosciniak@stericsson.com ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Thomas URB ITSCH:MAILTO:thomas.urbitsch@stericsson.com DESCRIPTION;LANGUAGE=en-US:When: Occurs every Monday and Tuesday effective 3/15/2010 until 4/13/2010 from 5:00 PM to 5:30 PM (GMT+01:00) Brussels\, C openhagen\, Madrid\, Paris.\nWhere: room\n\nNote: The GMT offset above doe s not reflect daylight saving time adjustments.\n\n*~*~*~*~*~*~*~*~*~*\n\n test\n\n RRULE:FREQ=WEEKLY;UNTIL=20100412T220000Z;INTERVAL=1;BYDAY=MO,TU;WKST=MO SUMMARY;LANGUAGE=en-US:test DTSTART;TZID=Romance Standard Time:20100315T170000 DTEND;TZID=Romance Standard Time:20100315T173000 UID:040000008200E00074C5B7101A82E0080000000010D702325DC4CA01000000000000000 0100000002060E1763587C1438B9A6C55B7C5A048 CLASS:PUBLIC PRIORITY:5 DTSTAMP:20100315T153308Z TRANSP:OPAQUE STATUS:CONFIRMED SEQUENCE:0 LOCATION;LANGUAGE=en-US:room X-MICROSOFT-CDO-APPT-SEQUENCE:0 X-MICROSOFT-CDO-OWNERAPPTID:1882142682 X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY X-MICROSOFT-CDO-ALLDAYEVENT:FALSE X-MICROSOFT-CDO-IMPORTANCE:1 X-MICROSOFT-CDO-INSTTYPE:1 BEGIN:VALARM ACTION:DISPLAY DESCRIPTION:REMINDER TRIGGER;RELATED=START:-PT15M END:VALARM END:VEVENT END:VCALENDAR
Again me This actually works between 2 Lightning applications
As you've mentioned, Outlook doesn't seem to support selecting by days. Could you try importing the Lightning event into Outlook (not as an invitation, but normally into an existing calendar) ? There's probably not much we can fix about this bug. You could try stripping information from the ics data (i.e removing CLASS, PRIORITY, etc attributes...leave the RRULE there) and then importing into outlook to see if there is some other property that is in the way. If its just the RRULE that fails, if it works with a more standard type rule, then there's nothing we can do about this bug (not our bug).
Component: Lightning Only → E-mail based Scheduling (iTIP/iMIP)

Resolving as INVALID per comment#5, and hopefully Outlook is smarter these days.

Status: UNCONFIRMED → RESOLVED
Closed: 4 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.