Summary: | Expiry options on folder properties doesn't move mails | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Christian <cnngimenez> |
Component: | folders | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | montel, simonandric5 |
Priority: | NOR | ||
Version: | 4.14.4 | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Christian
2015-03-25 00:29:27 UTC
At first, I thought it was because KMail downloaded mails again because of my account configuration, so after posted this bug I checked for this matter. I tested again activating the "leave the message on the server 7 days", I downloaded the mails (KMail displayed the "deleting mails on server" status) and then try the expiry options clicking on the "Save preferences and expire now": same results, it just copy the mails and don't move anything. Work fine here. Do you have error in console ? (In reply to Laurent Montel from comment #2) > Work fine here. > Do you have error in console ? I get this: $ kmail --nofork libpng warning: iCCP: Not recognizing known sRGB profile that has been edited loaded the Generic plugin libpng warning: iCCP: too many profiles libpng warning: iCCP: too many profiles [almost 40 times the same libpng warning] ~StorageServiceJobConfigPrivate I think is not of much help. If there's a way to start some kind of "debug output", please tell me how. This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks (5.x). Those versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the oportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12, preferably more recent), please open a new one unless it already exists. Thank you for all your input. |