unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Matthieu Lemerre <racin@free.fr>
To: notmuch@notmuchmail.org
Subject: Warning when GMime is parsing broken email addresses
Date: Wed, 17 Nov 2010 23:20:26 +0100	[thread overview]
Message-ID: <87ipzvk2xh.fsf@free.fr> (raw)


Hi,

I just realized that GMime is not robust to some broken email addresses
sent by broken email clients. I received a mail, with the to field being

xxxx.yyyy <uuuu-vvvv@gmail.com>

The email client (Exchange) had forgotten to put a "" around
"xxxx.yyyy", which is necessary because `.' is a special character, and
this confused GMime. This resulted in notmuch storing xxxx.yyyy as the
email address, instead of using uuuu-vvvv@gmail.com. Because of that I
had trouble finding one of my mail using a to: in the search terms.

I have filed a bug report for GMime
(https://bugzilla.gnome.org/show_bug.cgi?id=545333), but I just wanted
to make people using notmuch aware of this problem, because I guess that
such problems might be extremely common.

Maybe it would also be interesting to add a warning/assertion to check
that all email adresses added to the database are correct email
addresses? I.e. check that the `addr' variable in _index_address_mailbox
always has a @. This check is in fact already done using the function
strchr, but a bad value is explicitly ignored...

Matthieu

             reply	other threads:[~2010-11-17 22:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 22:20 Matthieu Lemerre [this message]
2010-11-18 18:37 ` Warning when GMime is parsing broken email addresses Matthieu Lemerre
2010-11-18 18:51   ` Daniel Kahn Gillmor
2010-11-20 11:23     ` Matthieu Lemerre
2010-11-20 14:35       ` Daniel Kahn Gillmor
2011-04-25 22:23 ` Carl Worth
2011-04-27 16:30   ` Xavier Maillard
2011-04-27 19:59     ` Pieter Praet
2011-05-13 22:33       ` Matthieu Lemerre

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=87ipzvk2xh.fsf@free.fr \
    --to=racin@free.fr \
    --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).