Summary: | Failure to read write-protected mbox files | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Volker Kuhlmann <bugz57> |
Component: | general | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | bugz57, kollix, montel |
Priority: | NOR | ||
Version: | 4.10.5 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/kdepimlibs/4a4a56b3d64d518a881a08c32dc51138909613b7 | Version Fixed In: | 4.14.5 |
Sentry Crash Report: |
Description
Volker Kuhlmann
2013-08-21 23:43:32 UTC
Will look at soon. but mixedmaildir is just for compatibility not necessary to use it for new account. Thanks! But especially for compatibility I would expect write-protected historic mbox files to be accessible easily. Confirmed with 4.14.3 The pending fix is here: https://git.reviewboard.kde.org/r/122255/ Git commit 4a4a56b3d64d518a881a08c32dc51138909613b7 by Martin Koller. Committed on 30/01/2015 at 19:00. Pushed by mkoller into branch 'KDE/4.14'. Fix handling of read-only mbox files Up till now a read-only mbox file could not be loaded, since load() always tried to open in read-write mode. Now it first tries to open the file readWrite and if that fails, it retries readOnly. Also one can now explicitely tell the class to open the file readOnly even if it could be written. Related: bug 138445 FIXED-IN: 4.14.5 REVIEW: 122255 M +19 -2 kmbox/mbox.cpp M +30 -4 kmbox/mbox.h M +11 -4 kmbox/mbox_p.cpp M +46 -0 kmbox/tests/mboxtest.cpp M +1 -0 kmbox/tests/mboxtest.h http://commits.kde.org/kdepimlibs/4a4a56b3d64d518a881a08c32dc51138909613b7 |