From: rlane@club.cc.cmu.edu (Rich Lane)
Subject: [sup-talk] Fwd: xapian merged into next
Date: Sat, 01 Aug 2009 14:14:34 -0400 [thread overview]
Message-ID: <1249149855-sup-2211@pion.club.cc.cmu.edu> (raw)
In-Reply-To: <1e5fdab70908011044q6743d213o554a7bd039e237c2@mail.gmail.com>
Excerpts from Guillaume Quintard's message of Sat Aug 01 13:44:50 -0400 2009:
> E"name.surname at enst-bretagne.fr,
> my_name.my_surname at enst-bretagne.fr, name.surname at enst-bretagne.fr,
> name.surname at enst-bretagne.fr,
> name.surname at telecom-bretagne.eu,
> name.surname at telecom-bretagne.eu,
> name.surname at telecom-bretagne.eu, name.surname"@telecom-bretagne.eu
That's a very strange email address :). Could you track down the message
causing this and post the headers? It looks like it's getting parsed
incorrectly.
I think we'd be safe not adding terms for email addresses longer than
244 characters on the assumption that the user isn't going to want to
search for them.
next prev parent reply other threads:[~2009-08-01 18:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 16:13 [sup-talk] " William Morgan
2009-07-27 16:16 ` Guillaume Quintard
2009-07-27 16:27 ` William Morgan
2009-07-27 16:31 ` Guillaume Quintard
2009-07-27 16:44 ` William Morgan
2009-07-27 16:47 ` Guillaume Quintard
2009-07-27 16:50 ` William Morgan
2009-07-27 17:09 ` Guillaume Quintard
2009-07-27 17:34 ` William Morgan
[not found] ` <1e5fdab70908010934l30373447r4a405c5ca0e406f9@mail.gmail.com>
2009-08-01 17:44 ` [sup-talk] Fwd: " Guillaume Quintard
2009-08-01 18:14 ` Rich Lane [this message]
2009-08-01 18:31 ` Guillaume Quintard
2009-08-01 23:03 ` Rich Lane
2009-08-01 23:35 ` Guillaume Quintard
2009-07-27 20:04 ` [sup-talk] " Guillaume Quintard
2009-07-28 3:33 ` Rich Lane
2009-07-28 15:13 ` William Morgan
2009-07-28 0:33 ` Richard Heycock
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1249149855-sup-2211@pion.club.cc.cmu.edu \
--to=rlane@club.cc.cmu.edu \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox