Bug#970526: marked as done ("mutt" is forced to use "utf-8" and "base64".)
Your message dated Fri, 18 Sep 2020 09:40:35 +0200 (CEST)
with message-id <92997871.15845.1600414835571@office.mailbox.org>
and subject line Re: Bug#970526: "mutt" is forced to use "utf-8" and "base64".
has caused the Debian Bug report #970526,
regarding "mutt" is forced to use "utf-8" and "base64".
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 owner@bugs.debian.org
immediately.)
--
970526: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970526
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: reportbug
Version: 7.7.0
Severity: normal
Dear Maintainer,
If an octet (8bit) character (mu, µ) is used in the body of a report,
"reportbug" changes the default encoding for "mutt" to "utf-8" and then
"mutt" encodes the body with "base64".
The bug tracker does not accept such mails, as the header of the
report is missing (concealed in the encoded text).
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.8.7-1 (SMP w/2 CPU threads)
Locale: LANG=is_IS.iso88591, LC_CTYPE=is_IS.iso88591 (charmap=ISO-8859-1), LANGUAGE not set
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Versions of packages reportbug depends on:
ii apt 2.1.10
ii python3 3.8.2-3
ii python3-reportbug 7.7.0
ii sensible-utils 0.0.12+nmu1
reportbug recommends no packages.
Versions of packages reportbug suggests:
pn claws-mail <none>
pn debconf-utils <none>
pn debsums <none>
pn dlocate <none>
pn emacs-bin-common <none>
ii exim4 4.94-7
ii exim4-daemon-light [mail-transport-agent] 4.94-7
ii file 1:5.38-5
ii gnupg 2.2.20-1
pn python3-urwid <none>
pn reportbug-gtk <none>
ii xdg-utils 1.1.3-2
Versions of packages python3-reportbug depends on:
ii apt 2.1.10
ii file 1:5.38-5
ii python3 3.8.2-3
ii python3-apt 2.1.3
ii python3-debian 0.1.37
ii python3-debianbts 3.0.2
ii python3-requests 2.23.0+dfsg-2
ii sensible-utils 0.0.12+nmu1
python3-reportbug suggests no packages.
-- no debconf information
--
Bjarni I. Gislason
--- End Message ---
--- Begin Message ---
Bjarni Ingi Gislason wrote:
> If an octet (8bit) character (mu, µ) is used in the body of a report,
> "reportbug" changes the default encoding for "mutt" to "utf-8" and then
> "mutt" encodes the body with "base64".
The encoding choice of base64 is done by python's email library.
Reportbug itself does not care about the encoding, and the
choice of MUA does not make any difference to the encoding
used by reportbug.
If you pass the message to a MUA like mutt for submission, then
the MUA is of course free to choose a different encoding on
submission (and I expect it to follow its own default settings then).
> The bug tracker does not accept such mails, as the header of the
> report is missing (concealed in the encoded text).
The bugtracker first decodes the text before looking for the
pseudoheader lines you are referring to, so there is no bug here.
Closing accordingly.
Please provide more evidence if something really is broken.
Thanks!
--- End Message ---
Reply to: