Gnus development mailing list
 help / color / mirror / Atom feed
From: "Georg C. F. Greve" <greve@fsfeurope.org>
To: David <de_bb@arcor.de>
Cc: ding@gnus.org
Subject: Re: released mairix backend nnmairix.el
Date: Sun, 07 Oct 2007 13:12:32 +0200	[thread overview]
Message-ID: <m3r6k7b2lb.fsf@cerebro.fsfeurope.org> (raw)
In-Reply-To: <kzhcl4vt7f.fsf@musil.physik3.gwdg.de> (David's message of "Sat, 06 Oct 2007 23:17:24 +0200")

[-- Attachment #1: Type: text/plain, Size: 1563 bytes --]

On Sat, 06 Oct 2007 23:17:24 +0200
David <de_bb@arcor.de> wrote: 

 d> This is because you specified the nnmaildir-server as your mail
 d> backend. However, mairix will put the search results under the path
 d> you specified with the 'base' variable in your .mairixrc.

Ah! This is the reason why it does not work for me.

In my concrete case, the mail archive is in the Archive data structure,
whereas the incoming mail structure is in Mail in my home directory.

Consequently, all search results (falsely) end up in my home directory,
where Gnus does not find them.


 d> This means, the 'base' path in .mairixrc and the base path of your
 d> mail folders have to be the same.

Considering that many people use different backends for archival and
incoming mail, I think that is not a safe assumption to make.

I think nnmairix should use 'nnml-directory' instead, which is where the
path for the mail folders are configured in Gnus, or the appropriate
variable for other backends.

As an added benefit, nnmairix should then also work in situations with
"mixed" backends, because they are not illegal, some people use them for
reasons that may not be entirely obvious, and nnmairix should not choke
on this, imho.

Regards,
Georg

-- 
Georg C. F. Greve                                 <greve@fsfeurope.org>
Free Software Foundation Europe	                 (http://fsfeurope.org)
Join the Fellowship and protect your freedom!     (http://www.fsfe.org)
What everyone should know about DRM                   (http://DRM.info)

[-- Attachment #2: Type: application/pgp-signature, Size: 306 bytes --]

  parent reply	other threads:[~2007-10-07 11:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-26 13:52 Getting rid of the zombies in dynamically created groups Georg C. F. Greve
2007-09-26 18:38 ` Reiner Steib
2007-09-26 22:38   ` Georg C. F. Greve
2007-09-27  6:12     ` Reiner Steib
2007-09-27 21:35       ` Georg C. F. Greve
2007-10-04  8:04 ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) David
2007-10-04 16:29   ` released mairix backend nnmairix.el Reiner Steib
2007-10-05  9:15     ` David
2007-10-05 16:41       ` Reiner Steib
2007-10-06 14:24       ` Georg C. F. Greve
2007-10-06 18:59         ` Bastien
2007-10-06 21:20           ` David
2007-10-06 23:19             ` Bastien
2007-10-07 16:09               ` David
2007-10-08  9:33                 ` Bastien
2007-10-06 21:17         ` David
2007-10-06 23:17           ` Bastien
2007-10-07 11:12           ` Georg C. F. Greve [this message]
2007-10-07 15:53             ` David
2007-10-08  9:33               ` Bastien
2007-10-04 16:48   ` released mairix backend nnmairix.el (was: Getting rid of the zombies in dynamically created groups) Bastien
2007-10-04 17:18     ` released mairix backend nnmairix.el Bastien
2007-10-05  9:46       ` David
2007-10-05 12:00         ` Bastien
2007-10-04 23:54   ` Bastien

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=m3r6k7b2lb.fsf@cerebro.fsfeurope.org \
    --to=greve@fsfeurope.org \
    --cc=de_bb@arcor.de \
    --cc=ding@gnus.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).