Re: IMAP and meeting invitations

On Sunday 20 May 2007, Carsten Burghardt wrote:
> > > 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).
> >
> > Well, both invitations I was talking about had three mime
> > parts: "text/plain", "text/html" and "text/calendar". So that can't
> > be the reason for the different loading strategies. I'll take a
> > closer look to see if all of the working invitations had a size
> > less than ~5k when I get back to work.
>
> There is indeed no size threshold but only the 50% border as the
> loading of many single parts is slower than the complete message.

Then I don't get it. All invitations have the three parts mentioned 
above. So, where is the diffence? Could you please elaborate or point 
me to the code? Just to make me feel good. =)

Regards
Heiko