Re: IMAP and meeting invitations

On Thursday 17 May 2007 20:32, Heiko Hund wrote:
> Hi everyone,
>
> at first I thought it is a straight bug in kmail that some (actually
> most of the) meeting invitations from my co-workers do not get
> displayed inline, but instead as "meeting.ics" attachments. If I open
> these attachments in kontact the meeting is not added to my calendar
> and the person who scheduled the meeting does not get a reply. If I
> press "v" to view the source code of the mail, the invitation
> suddenly gets displayed inline.
>
> After some diggin' I found out that it has actually to do with on
> demand attachment loading. If I turn it off in the IMAP account
> settings the invitations is displayed inline when I select the mail.
>
> It seems to me that the size of the attachment/mail matters. An
> invitation with only four attendees gets displayed inline, while
> another one with five doesn't. Difference between them in bytes is
> just ~250, but the bigger one is over 5000 bytes. Is there a magic
> threshold around 5k where the on demand loading kicks in?
>
> Is there a way to force fetching/display of text/calendar mime parts?
> I was thinking about developing a patch that adds an exception for
> meeting invitations. Any ideas where to look to get started?

In BodyVisitor::BodyVisitor() in bodyvisitor.cpp a list of mime-types 
that should always be loaded is created. I guess the mime-type used for 
invitations should be added to it.

This class is used in ImapAccountBase::handleBodyStructure() to 
determine the body parts that should be loaded. The only fallback from 
load-on-demand to load-everything I can see there is if "more than 50% 
of the parts have to be loaded". I can't see any indication of a 
threshold for the message size (but maybe I looked at the wrong spot).

Regards,
Ingo

_______________________________________________
KMail developers mailing list
[email protected]
https://mail.kde.org/mailman/listinfo/kmail-devel

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBGTK4XGnR+RTDgudgRAkT1AKCSV2mStKR/ZxH6o/AlIXNsc3w8RQCfU5b7
5LByUIySEcvRPDqeSLwgKRA=
=Hujg
-----END PGP SIGNATURE-----