On Sun, 2022-06-26 at 09:28 +0100, Matthew Smith wrote:
> Add a news item explaining a maildir corruption bug in the mu/mu4e
> mail reader.
> ---
> .../2022-06-06-mu-corruption.en.txt | 26 +++++++++++++++++++
> 1 file changed, 26 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..6603b5e
> --- /dev/null
> +++ b/2022-06-26-mu-corruption/2022-06-06-mu-corruption.en.txt
> @@ -0,0 +1,26 @@
> +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.
> +
> +Users can check for corruption by checking to see if the following
> +command produces any output:
> +
> + find ~/Maildir -name '*:2,*:*'
> +
> +Users can correct the corruption by running the following commands:
> +
> + find ~/Maildir -name '*:2,*:*' |
> + sed "s/\(\([^:]*\)\(:2,\)\{1,\}\(:2,.*$\)\)/mv '\0' '\2\4'/" \
Would be nice to explain what the expression does in human way. Also, I
think using `sed -E` would make this more readable.
> + > rename.sh
> + # review rename.sh
> + sh rename.sh
> +
> +Upstream issue: https://github.com/djcb/mu/issues/2268
--
Best regards,
Michał Górny
