unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: UTF-8 in mail headers (namely FROM) sent by bugzilla
Date: Mon, 29 Jul 2013 15:46:26 -0400	[thread overview]
Message-ID: <51F6C692.5090104@fifthhorseman.net> (raw)
In-Reply-To: <87d2q5wrre.fsf@nikula.org>

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

On 07/26/2013 06:16 AM, Jani Nikula wrote:
> I'm experiencing a similar problem with the Subject: headers in bugzilla
> mail. Per RFC 2047,
> 
>     Ordinary ASCII text and 'encoded-word's may appear together in the
>     same header field.  However, an 'encoded-word' that appears in a
>     header field defined as '*text' MUST be separated from any adjacent
>     'encoded-word' or 'text' by 'linear-white-space'.
> 
> In the problematic mails, the encoded-word begins immediately after
> preceding text, i.e. without linear-white-space. Manually adding that
> space in the message file makes the subject display as expected.
> 
> The decoding is done in the cli using g_mime_message_get_subject(). I'm
> not sure if there's much that can be done about it within notmuch.

I think asking gmime to deliberately mis-parse the subject line would
probably be a bad idea, because that would cause some strings to be
impossible to represent in the subject.

So Jani's report here sounds like a bug in bugzilla itself.  Jani, have
you reported this problem to that project?  I don't see it on their
bugtracker [0], though maybe my scan of the list wasn't as thorough as
it should be.

Regards,

	--dkg

[0]
https://bugzilla.mozilla.org/buglist.cgi?product=Bugzilla&component=Email%20Notifications&resolution=---


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

  reply	other threads:[~2013-07-29 19:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23  8:55 UTF-8 in mail headers (namely FROM) sent by bugzilla Franz Fellner
2013-07-23  9:30 ` Eric Abrahamsen
2013-07-23 10:55   ` Franz Fellner
2013-07-23 11:39     ` David Bremner
2013-07-26 10:16       ` Jani Nikula
2013-07-29 19:46         ` Daniel Kahn Gillmor [this message]
2013-07-29 19:46       ` Daniel Kahn Gillmor
2013-07-24  6:44     ` Eric Abrahamsen
2013-10-05 10:43 ` Jani Nikula
2013-10-05 13:38   ` Daniel Kahn Gillmor
     [not found] <289881190.1977918.1376058260231.JavaMail.root@sz0152a.westchester.pa.mail.comcast.net>
2013-08-09 18:04 ` Jani Nikula
2013-08-09 18:38   ` Jeffrey Stedfast

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=51F6C692.5090104@fifthhorseman.net \
    --to=dkg@fifthhorseman.net \
    --cc=jani@nikula.org \
    --cc=notmuch@notmuchmail.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).