1 |
Add a news item explaining a maildir corruption bug in the mu/mu4e |
2 |
mail reader. |
3 |
--- |
4 |
.../2022-06-06-mu-corruption.en.txt | 26 +++++++++++++++++++ |
5 |
1 file changed, 26 insertions(+) |
6 |
create mode 100644 |
7 |
2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
8 |
|
9 |
diff --git a/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
10 |
b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
11 |
new file mode 100644 |
12 |
index 0000000..6603b5e |
13 |
--- /dev/null |
14 |
+++ b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt |
15 |
@@ -0,0 +1,26 @@ |
16 |
+Title: Mu 1.7.23 Causing Maildir Corruption |
17 |
+Author: Matthew Smith <matthew@g.o> |
18 |
+Posted: 2022-06-26 |
19 |
+Revision: 1 |
20 |
+News-Item-Format: 2.0 |
21 |
+Display-If-Installed: net-mail/mu-1.7.23 |
22 |
+ |
23 |
+Development versions of mu between 1.7.18 and 1.7.25 have a bug causing |
24 |
+mail file names to sometimes get mangled after moving messages between |
25 |
+directories. Symptoms include unread messages never being marked as |
26 |
+read. |
27 |
+ |
28 |
+Users can check for corruption by checking to see if the following |
29 |
+command produces any output: |
30 |
+ |
31 |
+ find ~/Maildir -name '*:2,*:*' |
32 |
+ |
33 |
+Users can correct the corruption by running the following commands: |
34 |
+ |
35 |
+ find ~/Maildir -name '*:2,*:*' | |
36 |
+ sed "s/\(\([^:]*\)\(:2,\)\{1,\}\(:2,.*$\)\)/mv '\0' '\2\4'/" \ |
37 |
+ > rename.sh |
38 |
+ # review rename.sh |
39 |
+ sh rename.sh |
40 |
+ |
41 |
+Upstream issue: https://github.com/djcb/mu/issues/2268 |
42 |
-- |
43 |
2.35.3 |