unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jakub Wilk <jwilk@jwilk.net>
To: submit@bugs.debian.org
Subject: Bug#1021614: notmuch: RFC2047-encoded special characters in display-name show up unquoted
Date: Tue, 11 Oct 2022 22:02:31 +0200	[thread overview]
Message-ID: <20221011200231.53rzm7divs25dr5k@jwilk.net> (raw)

[-- Attachment #1: Type: text/plain, Size: 962 bytes --]

Package: notmuch
Version: 0.37-1

The attached message has a bunch of RFC-2047-encoded special characters 
in the display-name part of the From field:

    $ grep ^From: weird-from.eml
    From: =?UTF-8?Q?=3Cfoo=40example.org=3E=2C?= <bar@example.org>

When you show this message in notmuch, the special characters show up 
unquoted (and unencoded), so that it looks like there are two addresses 
in the From field:

    $ ./notmuch-show-from < weird-from.eml
    From: <foo@example.org>, <bar@example.org>

I initially thought this is a GMime bug, but it seems GMime gets this 
right:

    $ ./gmime-show-from < weird-from.eml
    From: "<foo@example.org>," <bar@example.org>


-- System Information:
Architecture: i386

Versions of packages notmuch depends on:
ii  libnotmuch5     0.37-1
ii  libc6           2.35-3
ii  libglib2.0-0    2.74.0-2
ii  libgmime-3.0-0  3.2.13+dfsg-2
ii  libtalloc2      2.3.4-1
ii  zlib1g          1:1.2.11.dfsg-4.1

-- 
Jakub Wilk

[-- Attachment #2: weird-from.eml --]
[-- Type: message/rfc822, Size: 64 bytes --]

From: "<foo@example.org>," <bar@example.org>



[-- Attachment #3: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2022-10-14 11:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-11 20:02 Jakub Wilk [this message]
2022-10-11 20:28 ` Bug#1021614: notmuch: RFC2047-encoded special characters in display-name show up unquoted Jakub Wilk

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20221011200231.53rzm7divs25dr5k@jwilk.net \
    --to=jwilk@jwilk.net \
    --cc=1021614@bugs.debian.org \
    --cc=submit@bugs.debian.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).