claws-mail-vcalendar-plugin displays previous viewed event

Bug #779757 reported by Tiger!P on 2011-05-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
claws-mail (Ubuntu)

Bug Description

Binary package hint: claws-mail

I have received 2 e-mails from a person with an event request. Claws only displays the information about the last event I received. I connect to an exchange server using imap.
The requests are sent with outlook 2010 client and are in the vcalender format. The event is a recurring event.

I would expect to be able to view every event with claws and see the event that is in the email.

 lsb_release -rd
Description: Ubuntu 11.04
Release: 11.04

apt-cache policy claws-mail-vcalendar-plugin
  Installed: 3.7.8-1ubuntu1
  Candidate: 3.7.8-1ubuntu1
  Version table:
 *** 3.7.8-1ubuntu1 0
        500 natty/universe i386 Packages
        100 /var/lib/dpkg/status

Colin Leroy-Mira (colin-colino) wrote :

I think Claws is displaying the same data for both, because they have the same event UID, and one has a greater SEQUENCE number than the other, which means one is an update of the other one.

Tiger!P (ubuntu-tigerp) wrote :

Even when it has the same event ID, I think that claws should display the information that the e-mail contains and not the information of the last seqence when I select the e-mail.
The calendar might display the information.

The problem that I have is that it is a recurring event which has some updates for single occurences. And now I can only see the last update.

Michael Gmelin (freebsd-z) wrote :

I'm experiencing this as well, there are invitations which are regularly changed by our back office team using outlook 2010 and I'm only seeing the first cached version (.claws-mail/vcalendar/<UID>) . The sequence number actually doesn't seem to matter at all. So it's two issues:

1. It would be good to see what has been in an actual appointment for a specific email without looking at the source (like Tiger!P suggested)
2. If appointments override each other the newer sequence number should win (I thought this was the case but it doesn't seem to work correctly).

Michael Gmelin (freebsd-z) wrote :

* by "newer" I mean "higher" of course...

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers