KDEPIM 4.6 prob^Wimpressions

[Duncan]

Kevin Krammer posted on Fri, 01 Jul 2011 09:19:59 +0200 as excerpted:

> [Duncan wrote...]

>> (every time a mail comes in, I get a warning about two copies...[)]

> I don't have a bug number at hand but I think this is a know one.
> Something triggering the change collision detection when there is none.

Thanks.  I can probably find it in the filed bugs then, when I decide to 
investigate it.

>> > Ah, so you were referring to the mail importer (executable kmailcvt),
>> > not the migrator (executable kmail-migrator).
>> 
>> Yes.  By that point the migrator had finished

> Yeah, the best thing at that point would have been to simply create a
> KMail Folders resource and point it to the KMail mail directory.

> The kmailcvt tools is a very old one and should probably be replaced at
> some point.

Very useful information to know.  Had I known that...

>> What I found interesting was that it wasn't /all/ messages unread or
>> all read, it was /mostly/ unread.  If there wasn't support for the
>> index files at all, they should all be unread (or all read, arbitrary
>> choice of the importer).
> 
> Maildir messages also carry their read/unread status as part of their
> filename, so maybe the importer interpreted that for some of them.
> It could also be a bug in the interaction between the importer and
> Akonadi, or the importer and KMail (no idea if it has been ported to
> work with Akonadi or still works through KMail).

Yes, by the sound if it, perhaps I was lucky it worked as well as it did.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

___________________________________________________
This message is from the kde mailing list.
Account management:  https://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.