On 31/10/2025 12:07, Stuart Henderson via dovecot wrote:
If you have logs, you can send those, along with doveconf -n. But this bug will not be fixed for 2.3. I can check if it's in 2.4 maybe if there is enough information how to reproduce this. ... This is already fixed inhttps://github.com/dovecot/core/commit/b3fcfa013a5d9a6eb28ff701ef5ddf45ba6d5... - so upgrading to 2.4 should fix it. it's already fixed in the 2.3 branch,
https://github.com/dovecot/core/commits/release-2.3/
2.3 is in maintenance mode, can you see try if this happens with 2.4? if it's still in maintenance, would it be possible to make a release rolling up the various post-2.3.21.1 fixes please? this would be easier to work with for stable OS distributions still using 2.3 than cherry- picking patches.
I think you'd need to raise the issue with Debian so their maintainer can update their packages.
On 31/10/2025 12:07, Stuart Henderson via dovecot wrote:
If you have logs, you can send those, along with doveconf -n. But this bug will not be fixed for 2.3. I can check if it's in 2.4 maybe if there is enough information how to reproduce this.
...
This is already fixed in [1]https://github.com/dovecot/core/commit/b3fcfa013a5d9a6eb28ff701ef5ddf45ba6d5... - so upgrading to 2.4 should fix it.
it's already fixed in the 2.3 branch,
[2]https://github.com/dovecot/core/commits/release-2.3/
2.3 is in maintenance mode, can you see try if this happens with 2.4?
if it's still in maintenance, would it be possible to make a release rolling up the various post-2.3.21.1 fixes please? this would be easier to work with for stable OS distributions still using 2.3 than cherry- picking patches.
I think you'd need to raise the issue with Debian so their maintainer can update their packages.
References
Visible links