After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 557341 - Does not recognize valid vCal
Does not recognize valid vCal
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
2.22.x (obsolete)
Other All
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2008-10-22 00:12 UTC by Filip Keller
Modified: 2010-12-02 09:25 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22



Description Filip Keller 2008-10-22 00:12:42 UTC
Please describe the problem:
If I receive an email with a valid vCal, evolution.

1. makes a note: "The message says, it includes calendar, but calendar is not a valid iCalendar" (text translated might differ slightly) if there is no specific time (only date)

2. describes the event correctly but does not let to add to the Calendar.

Steps to reproduce:
1. sending an email with this valid code (no time specified):

BEGIN:VCALENDAR
PRODID:-//Evangnet o.s.//NONSGML Evangnet//CZ
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:/evangnet.cz/Europe/Prague
X-LIC-LOCATION:Europe/Prague
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
X-EPOCAGENDAENTRYTYPE:EVENT
X-EVCAL-ID:1127-evolution_conference_without_time
UID:evangcal-1127-evolution_conference_without_time@evangnet.cz
DTSTART;VALUE=DATE:20081028
DURATION:P1D
X-FUNAMBOL-ALLDAY:1
SUMMARY:Evolution conference without time
DESCRIPTION:Would be whole day.
LOCATION:Prague
DTSTAMP:20081022T020600Z
LAST-MODIFIED:20081022T020600Z
CLASS:PUBLIC
CATEGORIES:Evangnet
ORGANIZER;CN=Správci Evangnetu:MAILTO:spravci@evangnet.cz
URL:http://www.evangnet.cz/kalendar/1127-evolution_conference_without_time
PRIORITY:5
END:VEVENT
END:VCALENDAR


2. Sending an email with this valid code (time specified):

BEGIN:VCALENDAR
PRODID:-//Evangnet o.s.//NONSGML Evangnet//CZ
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:PUBLISH
BEGIN:VTIMEZONE
TZID:/evangnet.cz/Europe/Prague
X-LIC-LOCATION:Europe/Prague
BEGIN:DAYLIGHT
TZOFFSETFROM:+0100
TZOFFSETTO:+0200
TZNAME:CEST
DTSTART:19700329T020000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=3
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:+0200
TZOFFSETTO:+0100
TZNAME:CET
DTSTART:19701025T030000
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
X-EPOCAGENDAENTRYTYPE:EVENT
X-EVCAL-ID:1126-evolution_conference
UID:evangcal-1126-evolution_conference@evangnet.cz
DTSTART;TZID=/evangnet.cz/Europe/Prague:20081118T140000
DTEND;TZID=/evangnet.cz/Europe/Prague:20081118T235959
X-FUNAMBOL-ALLDAY:0
SUMMARY:Evolution conference
DESCRIPTION:Evolution conference on importing iCalendar
LOCATION:Los Angeles
DTSTAMP:20081022T020400Z
LAST-MODIFIED:20081022T020400Z
CLASS:PUBLIC
CATEGORIES:Evangnet
ORGANIZER;CN=Správci Evangnetu:MAILTO:spravci@evangnet.cz
URL:http://www.evangnet.cz
PRIORITY:5
END:VEVENT
END:VCALENDAR



Actual results:


Expected results:


Does this happen every time?
Yes, with this type of vCal

Other information:
Comment 1 André Klapper 2008-10-22 10:43:29 UTC
I'm still generally wondering how stuff is expected to work without any charset specification but having special letters in CN, like á.
Comment 2 Petr Tomasek 2008-10-22 22:05:39 UTC
Hi, I'm the author of the system, that generated this vCalendar (www.evangnet.cz). The email, the vCalendar was attached to, has a correct charset specified in the MIME header.

The RFC states:

  "There is not a property parameter to declare the character set used
   in a property value. The default character set for an iCalendar
   object is UTF-8 as defined in [RFC 2279].

   The "charset" Content-Type parameter can be used in MIME transports
   to specify any other IANA registered character set."

(RFC 2554, section 4.1.4)

So, I don't see any other way, how otherwise to specify the charset (which is UTF-8 anyway, so it shouldn't be problem even if the file would be processed without having access to the MIME headers!). 
Comment 3 Petr Tomasek 2008-10-22 22:19:12 UTC
Ooops, I meant of course RFC2445, (sorry for spamming)...
Comment 4 Milan Crha 2010-12-02 09:15:18 UTC
Thanks for a bug report. The problem is not with the DATE format, but with the first component, as it doesn't have specified DTEND property, it is not mandatory, somehow, though evolution requires it when importing through an invitation. As it's not neccessary and Evolution can handle it, then I'll fix it.
Comment 5 Milan Crha 2010-12-02 09:25:49 UTC
Heh, OK, I cannot fix it, because it's already fixed, I can open an email which has your event as an attachment and I can accept the invitation and it is added to my On This Computer/Personal calendar as a whole day event.

Thi sis with 2.91.3, though 2.32.0 should work the same.