Bug 284534

Summary:	my_user growing when archiving outside of /home/
Product:	[Applications] kmail2	Reporter:	Daniel Moyne <daniel.moyne>
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:
Sentry Crash Report:

Description Daniel Moyne 2011-10-20 09:58:48 UTC

Version:           1.99.0
OS:                Linux

I am archiving all my kmail data in an archive on a separate partition of my /home partition though this one is now full !

Reproducible: Didn't try

Steps to Reproduce:
archiving a huge kmail data

Actual Results:  
during archiving my /home partition is 100% occupation ; when the job is finished 91 %

Expected Results:  
a full control of kmail data location would avoid such situation ; before my kmail data was not in /home as I used folders[$ie] to indicate its location ; why not keep this feature or allow akonadi frontend to choose for such location for example) ; again with this new version data handling cannot be controlled by user 

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

Comment 1 Laurent Montel 2011-10-20 12:26:43 UTC

do you use migration ?
Because we look at old local folder

Comment 2 Daniel Moyne 2011-10-21 13:51:39 UTC

My data has been migrated from Kmail migration option starting initially with a new empty kmail setting ; now to reconfigure properly my kmail application know how to archive my existing data but how to clear everything like "inbox", "sent-mail" and "trash" folders that appear redundantly with their french equivalent names "boîte de réception" "boîte d'envoi" and "corbeille", before remigrating my data archive back in a normal folder architecture ?

Comment 3 Laurent Montel 2011-10-21 13:55:37 UTC

Duplicate system folder is a bug in kmail-migration that I fixed in 4.7.3.

Comment 4 Denis Kurz 2016-09-24 18:04:04 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 5 Denis Kurz 2017-01-07 21:25:39 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.