From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: David Bremner <david@tethera.net>,
Gaudenz Steinlin <gaudenz@debian.org>,
notmuch@notmuchmail.org, 810784@bugs.debian.org
Subject: Re: [Gaudenz Steinlin] Bug#810784: should match email adress case insensitive when sending encrypted mail
Date: Fri, 15 Jan 2016 13:47:51 -0500 [thread overview]
Message-ID: <874mee7k88.fsf@alice.fifthhorseman.net> (raw)
In-Reply-To: <87egdm4ujh.fsf@tesseract.cs.unb.ca>
On Tue 2016-01-12 11:44:18 -0500, David Bremner wrote:
> [gaudenz wrote:]
>> When sending encrypted mail the key lookup to encrypt to is done case
>> sensitive on the mail address. As mail addresses are case insensitive
>> this should be done case insensitive. Otherwise keys for users which for
>> some reason have uppercase letters in their email address in the key UID
>> are not found.
fwiw, i agree with gaudenz that this is the right thing to do, despite
being a gray area.
For the right-hand side of an e-mail address (the stuff after the @; the
e-mail domain), the DNS label there is case-insensitive by definition.
There may be some additional thinking to be done here when thinking
about non-ASCII DNS labels in the RHS, though -- should we be
normalizing the domain names in doing the search? using punycode?
The stuff before the @ is a bit more problematic.
According to the standards documents, the left-hand-side of an e-mail
address (the "domain-specific" part) is up to the mail domain to parse
and process. So it would not be a violation of the public
specifications for the operator of the MX for example.org to provide
three distinct mailboxes for alice@example.org and Alice@example.org and
ALICE@example.org.
However, i know of no mail providers that do so, and anyone proposing to
do such a thing should have their head examined.
Examining GnuPG's interface here, it looks like gpg already does
case-insensitive matching when searching for an e-mail address
surrounded by angle-brackets.
So where is the case-insensitive lookup happening? Is this a bug in
mml-mode, or in notmuch-emacs?
--dkg
next prev parent reply other threads:[~2016-01-15 18:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 16:44 [Gaudenz Steinlin] Bug#810784: should match email adress case insensitive when sending encrypted mail David Bremner
2016-01-15 18:47 ` Daniel Kahn Gillmor [this message]
2016-02-08 21:44 ` David Edmondson
2016-02-08 22:08 ` David Edmondson
2016-02-09 15:36 ` David Edmondson
2016-02-10 8:28 ` Tomi Ollila
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=874mee7k88.fsf@alice.fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=810784@bugs.debian.org \
--cc=david@tethera.net \
--cc=gaudenz@debian.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).