Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Cc: info-gnus-english@gnu.org
Subject: Re: nnimap and searching articles by message-id
Date: Fri, 25 Sep 2009 16:05:38 -0500	[thread overview]
Message-ID: <87ocoyivkt.fsf@lifelogs.com> (raw)
In-Reply-To: <192987.27906.qm@web45214.mail.sp1.yahoo.com>

On Mon, 21 Sep 2009 16:25:11 -0700 (PDT) janko hrasko <jhrasko1@yahoo.com> wrote: 

jh> --- On Sat, 9/19/09, Reiner Steib <reinersteib+gmane@imap.cc> wrote:

>> > It turns out that the IMAP server I am using 
>> 
>> Which IMAP server software is it?

jh> It is a part of Oracle Beehive collaboration suite.

>> 
>> > requires the message-id be stripped of the enclosing
>> angle brackets
>> > when searching for messages like so:
>> >
>> > UID SEARCH HEADER Message-Id "xxxx.yyyy@foobar.com"
>> >
>> > Not sure who is not compliant here: Gnus/nnimap or the
>> IMAP server?
>> 
>> Cc-ing the developer list.  Maybe someone there
>> knows.

jh> It would be good to know.  What do people think?  A quick scan through the RFC2822 - Internet Message Format reveals the following, but I am not sure if that is enough to convince anyone. 

jh>    Semantically, the angle bracket characters are not part of the
jh>    msg-id; the msg-id is what is contained between the two angle bracket
jh>    characters.

jh> Thanks for the patch.  It didn't work for what I needed (e.g. fetch
jh> the parent article) until I applied analogous changes to the other
jh> occurrence of search by message-id in nnimap.el:
jh> nnimap-request-article-part.

Can you and Reiner put together a patch?  Should be a simple one.

I think stripping off the angle brackets MAY cost some efficiency in
other IMAP servers (maybe they hash by the full message ID), but I don't
know.  The SEARCH reference in RFC 3501
(http://www.ietf.org/rfc/rfc3501.txt) says that search by any field is
by contained string, so as far as the standard is concerned stripping
off the angle brackets is harmless.  I would make it a user option
unless we're sure Courier, Dovecot, Exchange, and UW IMAP will work the
same way with and without the change.

Ted




  reply	other threads:[~2009-09-25 21:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <loom.20090919T032021-30@post.gmane.org>
2009-09-19  9:12 ` Reiner Steib
2009-09-21 23:25   ` janko hrasko
2009-09-25 21:05     ` Ted Zlatanov [this message]
2009-09-25 23:41       ` Peter
2009-10-08 20:08         ` Ted Zlatanov

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=87ocoyivkt.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --cc=ding@gnus.org \
    --cc=info-gnus-english@gnu.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.
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 NNTP newsgroup(s).