Bug 284435

Summary:	Not all mails migrated to kmail2
Product:	[Applications] kmail2	Reporter:	karaluh <karaluh>
Component:	general	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	1.99.0
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:

Description karaluh 2011-10-19 07:27:29 UTC

Version:           1.99.0
OS:                Linux

As in summary, many e-mails weren't migrated from several local folders and IMAP account. It's not the problem with particular e-mails, entire folders are not migrated.

Reproducible: Didn't try

Steps to Reproduce:
Migrate my e-mail accounts.

Actual Results:  
Not all e-mails migrated.

Expected Results:  
All e-mails migrated.

OS: Linux (i686) release 3.0.0-12-generic
Compiler: gcc

Comment 1 Laurent Montel 2011-10-19 09:28:21 UTC

Do you have errors during migration ?

Comment 2 karaluh 2011-10-19 09:38:23 UTC

I don't recall any. Is there a log somewhere I can check?

Comment 3 karaluh 2011-10-20 12:14:36 UTC

The e-mails migrated, only they aren't shown. To see them you have to make some changes to the folder, like copying an e-mail to it.

Comment 4 karaluh 2011-10-20 12:15:30 UTC

Refreshing also works.

Comment 5 Laurent Montel 2011-10-20 12:45:36 UTC

Refresh all folder ?

Comment 6 karaluh 2011-10-20 13:01:42 UTC

(In reply to comment #5)
> Refresh all folder ?

Yes, but it should be done automatically after the migration, if it's realy needed. It's confusing, and I never had to refresh anything in kmail1.

Comment 7 Laurent Montel 2011-10-20 16:54:33 UTC

Not easy.
But will try to fix it.

Comment 8 Denis Kurz 2016-09-24 18:10:22 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 9 Denis Kurz 2017-01-07 22:01:58 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.