Add a news item explaining a maildir corruption bug in the mu/mu4e
mail reader.
v2, following feedback from mgorny: Added a short explanation on what
the issue actually is and how it is fixed. Left the sed incantation
as-is because it comes from upstream and I do not want to break it.
---
.../2022-06-06-mu-corruption.en.txt | 22 +++++++++++++++++++
1 file changed, 22 insertions(+)
create mode 100644
2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
diff --git a/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
new file mode 100644
index 0000000..2108c99
--- /dev/null
+++ b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
@@ -0,0 +1,22 @@
+Title: Mu 1.7.23 Causing Maildir Corruption
+Author: Matthew Smith <matt...@gentoo.org>
+Posted: 2022-06-26
+Revision: 1
+News-Item-Format: 2.0
+Display-If-Installed: net-mail/mu-1.7.23
+
+Development versions of mu between 1.7.18 and 1.7.25 have a bug causing
+mail file names to sometimes get mangled after moving messages between
+directories. Symptoms include unread messages never being marked as
+read.
+
+Affected messages have the ':2,' flag appended multiple times. Using the
+following commands, users can remove the extra flags.
+
+ find ~/Maildir -name '*:2,*:*' |
+ sed "s/\(\([^:]*\)\(:2,\)\{1,\}\(:2,.*$\)\)/mv '\0' '\2\4'/" \
+ > rename.sh
+ # review rename.sh. empty file indicates that you are unaffected
+ sh rename.sh
+
+Upstream issue: https://github.com/djcb/mu/issues/2268
--
2.35.3
