Bug 381366

Summary:	keep folder specific configuration after adjustements to mail server
Product:	[Applications] kmail2	Reporter:	m.eik michalke <bugs.kde.org>
Component:	folders	Assignee:	kdepim bugs <kdepim-bugs>
Status:	CONFIRMED ---
Severity:	normal	CC:	jjm
Priority:	NOR
Version:	5.2.3
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description m.eik michalke 2017-06-18 14:41:48 UTC

for me, one of the most annoying things in this great mail client is its inability to keep the folder settings (also in filters and identities) when something changes in the mail server configuration (i.e., same account but new URL). i have a *lot* of filters, configured various folders so they move mail to local folders after a certain time, and use custom folders for sent mail and drafts -- and all of that is silently "forgotten" when you reconfigure the mail server. the filters are still present, but inactive since they lost all target folder information, and i have to manually reconfigure each and every filter, folder, and identity.

there certainly are cases where it is preferable to remove all folder specific configuration. but when a user applies changes *within* a configured account, i would assume it's supposed to remain that same account.

the current behaviour is a bad way to deal with it: resetting various folder settings without even informing the user. at the very least, kmail should *ask* you if it's ok to lose all folder specific configuration. it could check whether the same folder structure is present and suggest to leave everything as it was configured before. i wouldn't even mind to be presented with a short dialog for each folder/filter/identity that is affected, so that i can confirm that the new folder remains the old one, or adjust some config only if it is really necessary (e.g., if some folders are no longer there).

Comment 1 Justin Zobel 2022-11-06 09:25:25 UTC

Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!

Comment 2 Bug Janitor Service 2022-11-21 05:13:44 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 m.eik michalke 2022-11-28 12:05:00 UTC

i currently don't see how i could check this without the risk of losing my configuration again, or setting things up in a new VM which unfortunately i don't have the time to ATM.

however, assuming that kmail still behaves the same so the issue persists, i'd propose a different approach to it. currently the import/export dialog for KDE-PIM data only offers a very general selection of data to store. if there was an option to store configuration data on a per-account basis, so that you could export all relevant configuration before changing the server and import your config again, that would do it for me.

i'll set this to REPORTED as it is likely still a thing.

Comment 4 Jonathan Marten 2022-11-28 15:40:47 UTC

Confirmed still an issue with current PIM.  The problem is that internally and in config files folders are identified by Akonadi ID, which can change if the mail server or configuration is changed, even if it is still effectively the same as far as the user sees.  See also bugs 311112 and 332358.