unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Petter Reinholdtsen <pere@hungry.com>
Cc: notmuch@notmuchmail.org
Subject: Re: Incorrect parsing of email addresses (MIME with quotes)
Date: Mon, 24 Oct 2011 12:09:42 -0400	[thread overview]
Message-ID: <4EA58DC6.6090108@fifthhorseman.net> (raw)
In-Reply-To: <2flr522zju3.fsf@login2.uio.no>

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

On 10/24/2011 07:53 AM, Petter Reinholdtsen wrote:
> 
> The notmuch email frontend have a problem parsing email headers.
> The problem is headers like this
> 
>   From: "=?iso-8859-1?q?=D8yvind_Normann?=" <oyvind.norman@uio.no>
> 
> which my mailbox got a lot of.  The frontend show the address as 
> 
>   =?iso-8859-1?q?=D8yvind_Normann?=
> 
> instead of
> 
>   Øyvind Normann
> 
> The problem is the quotes around the MIME encoded string.  Mutt and
> Gnus handle these headers properly, but notmuch do not.


http://tools.ietf.org/html/rfc2047#page-8

states quite clearly:

   + An 'encoded-word' MUST NOT appear within a 'quoted-string'.

I'd argue that notmuch is doing the right thing here, and that MUAs that
wrap encoded words in quotes (or that apply decoding rules within quoted
strings) are the ones that need fixing.

Regards,

	--dkg


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 1030 bytes --]

  reply	other threads:[~2011-10-24 16:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-24 11:53 Incorrect parsing of email addresses (MIME with quotes) Petter Reinholdtsen
2011-10-24 16:09 ` Daniel Kahn Gillmor [this message]
2011-11-21 12:38   ` Petter Reinholdtsen
2011-11-22 23:30     ` David Bremner
2011-11-23  2:58       ` Austin Clements
2011-11-25  5:49       ` Petter Reinholdtsen

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=4EA58DC6.6090108@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    --cc=pere@hungry.com \
    /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).