Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Julien Cubizolles <j.cubizolles@free.fr>
To: info-gnus-english@gnu.org
Subject: Re: Is INBOX special in a Maildir?
Date: Wed, 11 Nov 2015 00:38:36 +0100	[thread overview]
Message-ID: <87bnb1tog3.fsf@free.fr> (raw)
In-Reply-To: <87io5920bp.fsf@free.fr>

Julien Cubizolles <j.cubizolles@free.fr> writes:


> I suspect it has to do with Gnus being confused about what INBOX really
> is: either the root of the Maildir, or the folder actually named
> INBOX. Do I need to change something in my offlineimap setup, or in
> Gnus' ?

I finally got it right. In case someone stumbles on the same problem:

I was using

--8<---------------cut here---------------start------------->8---
type = Maildir
localfolders = ~/email/Maildir/Free
--8<---------------cut here---------------end--------------->8---

in the local repository setting of .offlineimaprc

and

--8<---------------cut here---------------start------------->8---
(nnimap-shell-program "/usr/lib/dovecot/imap -o mail_location=maildir:$HOME/email/Maildir/Gmail:LAYOUT=fs")
--8<---------------cut here---------------end--------------->8---

so I guess that offlineimap was writing the INBOX messages in an actual
INBOX folder, whereas dovecot was expecting them at the root of the
Maildir.

Changing the .offlineimaprc setting to:

--8<---------------cut here---------------start------------->8---
type = IMAP
preauthtunnel = /usr/lib/dovecot/imap -o mail_location=maildir:$HOME/email/Maildir/Free:LAYOUT=fs
--8<---------------cut here---------------end--------------->8---

fixed it. Now only dovecot is writing messages in the Maildir, at least
that's my understanding.

Julien.



      reply	other threads:[~2015-11-10 23:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-10 18:09 Julien Cubizolles
2015-11-10 23:38 ` Julien Cubizolles [this message]

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=87bnb1tog3.fsf@free.fr \
    --to=j.cubizolles@free.fr \
    --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).