From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Garjola Dindi <garjola@garjola.net>
Cc: info-gnus-english@gnu.org
Subject: Re: Configuration example for mbsync + dovecot + Gnus
Date: Mon, 25 Jan 2021 10:30:23 -0800 [thread overview]
Message-ID: <875z3k50ow.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87wnw0q449.fsf@pc-117-162.ovh.com> (Garjola Dindi's message of "Mon, 25 Jan 2021 19:11:33 +0100")
Garjola Dindi <garjola@garjola.net> writes:
> On Mon 25-Jan-2021 at 17:31:14 +01, Eric Abrahamsen
> <eric@ericabrahamsen.net> wrote:
>> Garjola Dindi <garjola@garjola.net> writes:
>>
>>> Hi,
>>>
>>> I would like to move from a nnmaildir + OfflineIMAP configuration to
>>> something which:
>>>
>>> 1. scales better for large number of messages than nnmaildir and
>>> 2. does not use OfflineIMAP (Python 2 based and sometimes slow).
>>>
>>> I understand that some Gnus users use a local IMAP server with dovecot
>>> and the nnimap backend.
>>>
>>> I found these interesting instructions here:
>>>
>>> https://ericabrahamsen.net/tech/2014/oct/gnus-dovecot-lucene.html
>>
>> I'm still using this setup! You didn't say what was going wrong, but
>> here's a sample config block for one of my IMAP accounts:
>
> Thanks for your answer!
>
> With respect to the 2014 post, for the mbsync part, I had to change
>
> ,----
> | UseIMAPS no
> | UseTLSV1 no
> `----
>
> to this
>
> ,----
> | SSLType IMAPS
> | SSLVersions TLSv1.2
> `----
>
> and also add the port as you have in the example you just gave.
>
> And now I also see that for the local dovecot, you have
>
> ,----
> | AuthMechs LOGIN
> `----
>
> which was not the case in the blog post. This may be why I was getting
> an authentication failure.
Looks like it's time to update the blog post...
> I will try again with this updated configuration (my next scheduled
> session to play with this is next week-end!).
>
> Do you remember having also updated dovecot.conf or other things?
I tried to keep dovecot as bog-standard as possible. The only changes I
made to dovecot.conf were to set the location of the password file and
where to store mail, and most importantly to turn on full-text search.
Then there was the passwd file itself.
I think that was it!
Eric
_______________________________________________
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:[~2021-01-25 18:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-25 11:01 Garjola Dindi
2021-01-25 16:31 ` Eric Abrahamsen
2021-01-25 18:11 ` Garjola Dindi
2021-01-25 18:30 ` Eric Abrahamsen [this message]
2021-01-31 10:56 ` Garjola Dindi
2021-01-25 21:01 ` Jeffrey DeLeo
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=875z3k50ow.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=garjola@garjola.net \
--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).