From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: info-gnus-english@gnu.org
Subject: Re: Trouble setting up Gnus + OfflineIMAP + dovecot
Date: Fri, 23 Oct 2015 19:57:02 +0200 [thread overview]
Message-ID: <87fv11v575.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <87mvv91x16.fsf@free.fr>
Julien Cubizolles writes:
> Thanks you for your answer Lluís.
>> I use a configuration file for dovecot:
>>
>> (setq gnus-secondary-select-methods
>> '((nnimap "FreeOffline"
>> (nnimap-stream shell)
>> (nnimap-shell-program "/usr/lib/dovecot/imap -c ~/.dovecot-free")))
>>
>> With the following contents:
>>
>> protocols = imap
>> log_timestamp = "%Y-%m-%d %H:%M:%S "
>> mail_location = maildir:~/Maildir/free
>> protocol imap {
>> mail_plugins = fts fts_lucene
>> }
>> plugin {
>> fts = lucene
>> fts_lucene = whitespace_chars=@
>> fts_autoindex = yes
>> }
> I tried it, it didn't help.
>> I vaguely remember having to switch from "-o" to "-c" for some reason I cannot
>> recall. If that does not work, I'd say the problem might be in your offlineimap
>> configuration. Did you check the contents of your "Maildir-free" directory?
> Here it is:
> /home/wilk/Maildir-free
> ├── cur
> ├── dovecot.index.log
> ├── dovecot.mailbox.log
> ├── dovecot-uidlist
> ├── dovecot-uidvalidity
> ├── dovecot-uidvalidity.5629f967
> ├── General
> │ ├── cur
> │ │ ├── 1445591380_0.15542.lago,U=152457,FMD5=0db377921f4ce762c62526131097968f:2,
> │ │ ├── 1445591381_0.15542.lago,U=152458,FMD5=0db377921f4ce762c62526131097968f:2,
> │ │ ├── 1445591381_1.15542.lago,U=152459,FMD5=0db377921f4ce762c62526131097968f:2,
> │ │ ├── 1445591381_2.15542.lago,U=137612,FMD5=0db377921f4ce762c62526131097968f:2,FS
> │ │ ├── 1445591382_0.15542.lago,U=142222,FMD5=0db377921f4ce762c62526131097968f:2,S
> many lines like this
> │ │ ├── 1445607543_0.15542.lago,U=152499,FMD5=0db377921f4ce762c62526131097968f:2,R
> │ │ ├── 1445607543_1.15542.lago,U=152500,FMD5=0db377921f4ce762c62526131097968f:2,
> │ │ └── 1445607543_2.15542.lago,U=152502,FMD5=0db377921f4ce762c62526131097968f:2,
> │ ├── new
> │ └── tmp
> ├── maildirfolder
> ├── new
> ├── subscriptions
> └── tmp
Hmmmm, your contents seem strange to me. General should not be there, since you
said you're only synchronizing INBOX. But since you said it's a gmail account,
maybe you need to synchronize it somewhat differently:
http://www.emacswiki.org/emacs/GnusGmail#toc9
Cheers,
Lluis
--
"And it's much the same thing with knowledge, for whenever you learn
something new, the whole world becomes that much richer."
-- The Princess of Pure Reason, as told by Norton Juster in The Phantom
Tollbooth
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2015-10-23 17:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-22 16:36 Julien Cubizolles
2015-10-23 4:41 ` Jeffrey DeLeo
2015-10-23 9:34 ` Julien Cubizolles
2015-10-23 13:32 ` britt
2015-10-23 14:02 ` Lluís Vilanova
2015-10-23 14:26 ` Julien Cubizolles
2015-10-23 17:57 ` Lluís Vilanova [this message]
2015-10-23 22:24 ` Julien Cubizolles
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=87fv11v575.fsf@fimbulvetr.bsc.es \
--to=vilanova@ac.upc.edu \
--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).