Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: David Engster <deng@randomsample.de>
To: info-gnus-english@gnu.org
Subject: Re: nnmairix question
Date: Fri, 02 Oct 2009 13:36:16 +0200	[thread overview]
Message-ID: <m2y6nuhvtb.fsf@gwdg-wxp-sek08.top.gwdg.de> (raw)
In-Reply-To: <1cf74430-5a14-4b45-90ae-68c8ef2ebc47@z24g2000yqb.googlegroups.com>

Francis Moreau <francis.moro@gmail.com> writes:
> I'm using nnmairix but unfortunately found that nnmairix-goto-original-
> article function doesn't work for me.
>
> In a nnmairix group I do '$ o' on a current article and got: "Couldn't
> find original article".
>
> But gnus doesn't tell me why it couldn't...

I agree that a little more debugging output would be neat...

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).

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!).

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).

Regards,
David

  reply	other threads:[~2009-10-02 11:36 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 [this message]
     [not found] ` <mailman.7899.1254483421.2239.info-gnus-english@gnu.org>
2009-10-02 11:48   ` Francis Moreau
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=m2y6nuhvtb.fsf@gwdg-wxp-sek08.top.gwdg.de \
    --to=deng@randomsample.de \
    --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).