Bug 20867

Summary:	Kmail is looking for the local folders in the wrong place
Product:	Mageia	Reporter:	Tom Cox <tomc>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	kdepim4-4.14.5-1.mga5.src.rpm	CVE:
Status comment:

Description Tom Cox 2017-05-16 05:11:00 CEST

One of the recent updates caused a problem with kmail.  The problem presented as follows:

1. Move mail in the sent-mail folder to the trash folder.
2. Empty the trash folder.
3. Click to the sent-mail folder and the mail was back.  Same for the trash folder.

After digging around for a while, I figured out the problem.

The Kmail Local Folders account is pointing to .local/share/local-mail/.  That is where all the sent-mail has been stored for a long time.

I discovered there is a new local mail directory structure.  There is a top level, where cur, new and tmp are are at .local/share and the rest of the folders, including inbox, are in .local/share/.local-mail.directory.  Experimenting showed the latter was now the directory in use.  I moved all the send-mail to that directory structure and everything started operating normally.

I tried pointing the Kmail Local Folders account the .local/share/ directory, but Kmail wasn't happy with that.  I discovered I can set the Local Folders account to either .local/share/local-mail or .local/share/.local-mail.directory and everything works, it always uses the .local-mail.directory path.  Currently I have Kmail still pointed at the original .local/share/local-mail directory, but it is none-the-less using the new directory structure.

Marja Van Waes 2017-05-16 08:01:36 CEST

CC: (none) => marja11
Assignee: bugsquad => kde

Comment 1 Marja Van Waes 2018-09-18 15:36:11 CEST

Hi Tom,

Thank you for having taken the needed time to report this issue!

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.

I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there.

Closing as OLD.

Please reopen this report and change its "Version:" at the top left to "6", if the same bug still exists in Mageia 6.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: NEW => RESOLVED
Resolution: (none) => OLD