Your message dated Wed, 6 May 2026 13:26:01 +0800
with message-id <[email protected]>
and subject line Bug#1032772: fixed in mutt 2.2.12-0.1
has caused the Debian Bug report #1032772,
regarding mutt: Consider a narrower dictionary for message-id generation
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1032772: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032772
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mutt
Version: 2.2.9-1
Severity: important
control: tags -1 patch upstream fixed-upstream
control: forwarded -1
https://gitlab.com/muttmua/mutt/-/commit/5df86199463b5cf893fb6a37457fa02804d3b02a.patch
>From https://gitlab.com/muttmua/mutt/-/issues/400
| Currently, mutt message-id generation uses the base64 dictionary for random
| string generation. While this perfectly conforms to the RFC, the base64
| dictionary includes URL-unfriendly characters such as + and /. This
complicates
| message-id based lookups with services like public-inbox (e.g. on
| lore.kernel.org and similar sites).
The issue has been fixed upstream and a stable release with this fixed
is planned.
It would be helpful if this change could be added for the Bullseye
release.
Sebastian
--- End Message ---
--- Begin Message ---
Source: mutt
Source-Version: 2.2.12-0.1
Closing this as this change has already landed upstream in 2.2.10.
--
Best,
Tianyu Chen
--- End Message ---
