RE: NFC normalization rename errors after 2.3 to 2.4 upgrade (mdbox)

--===============2746474237041351758==
Content-Language: de-DE
Content-Type: multipart/alternative;
	boundary="_000_BE3P281MB579283ED81080385F439836DEFF92BE3P281MB5792DEUP_"

--_000_BE3P281MB579283ED81080385F439836DEFF92BE3P281MB5792DEUP_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi,

I tested the patch. The NFC error is gone.

I copied one affected user to a test user. The problem was reproducible on =
two different servers.
After running with the patched version, the NFC error disappeared. After mi=
grating the mailbox back to an unpatched server, the NFC error was still go=
ne.
So the patch seems to change something persistent.

However, I still get more subscribed mailbox names than real mailboxes.
Before the test on the unpatched server 'mailbox list -s=91 returned 50 mai=
lbox names and 9 errors.

Without -s I get 50 mailboxes.
With -s I get 68 names, but only 50 mailboxes really exist.
The additional names have a GUID-like suffix. I don't know if they are rela=
ted to this issue or if they are old subscription entries.

Would it make sense to remove the affected subscription entries automatical=
ly?

Regards,
Jens

Von: Timo Sirainen <[email protected]>
Datum: Freitag, 10. Juli 2026 um 16:28
An: Michael Goth <[email protected]>; [email protected] <[email protected]>=
; Jens Urban <[email protected]>
Betreff: Re: NFC normalization rename errors after 2.3 to 2.4 upgrade (mdbo=
x)

On 6. Jul 2026, at 21.53, Timo Sirainen via dovecot <[email protected]> w=
rote:
>
>   On 6. Jul 2026, at 8.39, Michael Goth via dovecot <[email protected]>
>   wrote:
>
>     So I think updating the mailbox name to NFC should also update any
>     matching subscriptions of the user. Otherwise, the subscription gets
>     lost and we get constant errors in the logs.
>
>   I thought this was already fixed, but looks like accidentally the test =
was
>   using mailbox_list_utf8=3Dyes. With the default =3Dno it was broken. At=
tached
>   a fix.

I guess nobody looked at the accidentally wrong diff :) But the fix is now =
committed:

--_000_BE3P281MB579283ED81080385F439836DEFF92BE3P281MB5792DEUP_
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"

   Hi,
   I tested the patch. The NFC error is gone.
   I copied one affected user to a test user. The problem was reproducible =
on
   two different servers.
   After running with the patched version, the NFC error disappeared. After
   migrating the mailbox back to an unpatched server, the NFC error was sti=
ll
   gone.
   So the patch seems to change something persistent.
   However, I still get more subscribed mailbox names than real mailboxes.
   Before the test on the unpatched server 'mailbox list -saEUR~ returned 50
   mailbox names and 9 errors.
   Without -s I get 50 mailboxes.
   With -s I get 68 names, but only 50 mailboxes really exist.
   The additional names have a GUID-like suffix. I don't know if they are
   related to this issue or if they are old subscription entries.
   Would it make sense to remove the affected subscription entries
   automatically?
   Regards,
   Jens
   Von: Timo Sirainen <[email protected]>
   Datum: Freitag, 10. Juli 2026 um 16:28
   An: Michael Goth <[email protected]>; [email protected]
   <[email protected]>; Jens Urban <[email protected]>
   Betreff: Re: NFC normalization rename errors after 2.3 to 2.4 upgrade
   (mdbox)
   On 6. Jul 2026, at 21.53, Timo Sirainen via dovecot <[email protected]>
   wrote:
   >
   >   On 6. Jul 2026, at 8.39, Michael Goth via dovecot
   <[email protected]>
   >   wrote:
   >
   >     So I think updating the mailbox name to NFC should also update any
   >     matching subscriptions of the user. Otherwise, the subscription ge=
ts
   >     lost and we get constant errors in the logs.
   >
   >   I thought this was already fixed, but looks like accidentally the te=
st
   was
   >   using mailbox_list_utf8=3Dyes. With the default =3Dno it was broken.
   Attached
   >   a fix.

   I guess nobody looked at the accidentally wrong diff :) But the fix is n=
ow
   committed:

--_000_BE3P281MB579283ED81080385F439836DEFF92BE3P281MB5792DEUP_--

--===============2746474237041351758==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
dovecot mailing list -- [email protected]
To unsubscribe send an email to [email protected]

--===============2746474237041351758==--