From: Francis Moreau <francis.moro@gmail.com>
To: info-gnus-english@gnu.org
Subject: Re: nnmairix question
Date: Fri, 2 Oct 2009 04:48:14 -0700 (PDT) [thread overview]
Message-ID: <95277d4a-20a8-4a1e-8526-20571029ca42@m38g2000yqd.googlegroups.com> (raw)
In-Reply-To: <mailman.7899.1254483421.2239.info-gnus-english@gnu.org>
Hello,
On Oct 2, 1:36 pm, David Engster <d...@randomsample.de> wrote:
>
> Finding the original article is a bit tricky. nnmairix will first try to
> use the registry. This will only work if you're actually using the
> registry (highly recommended), and if the article in question was
> already "seen" by the registry (the registry will register every article
> that is displayed in a summary buffer).
I finally end up to use registry, so now it works.
But just in case, you're interested in debugging my original issue...
>
> Now, if the registry did not work, it will do another mairix search,
> which looks like this:
>
> mairix -Q -r m:MESSAGE-ID
>
> (the MESSAGE-ID must be specified without the angle brackets!).
here is the ouptut of mairix:
/home/fmoreau/Mail/expired/953
>
> This is a search in 'raw mode', i.e., it will only display the full path
> to the found message(s). nnmairix will try to find the message from this
> path, based on some simple heuristics. It would be interesting to know
> how the output of the above search commands looks with your
> configuration, and what kind of backend server you're using for your
> mail (nnml, nnimap, or nnmaildir).
>
nnml.
Thanks
next prev parent reply other threads:[~2009-10-02 11:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 15:29 Francis Moreau
2009-10-02 11:36 ` David Engster
[not found] ` <mailman.7899.1254483421.2239.info-gnus-english@gnu.org>
2009-10-02 11:48 ` Francis Moreau [this message]
2010-08-30 4:49 ` oli
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=95277d4a-20a8-4a1e-8526-20571029ca42@m38g2000yqd.googlegroups.com \
--to=francis.moro@gmail.com \
--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).