From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: mail vs news
Date: Sat, 19 Dec 2015 10:24:44 +0800 [thread overview]
Message-ID: <87lh8rrx8z.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m260zwnl2z.fsf@krugs.de>
Rainer M Krug <Rainer@krugs.de> writes:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Igor Sosa Mayor <joseleopoldo1792@gmail.com> writes:
>>
>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>
>>>> Igor Sosa Mayor <joseleopoldo1792@gmail.com> writes:
>>>>
>>>>> Rainer M Krug <Rainer@krugs.de> writes:
>>>>>
>>>>>> Maintenance: I use offlineimap to sync my gmail account to a local
>>>>>> dovecot imap server, and after each sync, "notmuch" -new is called - so
>>>>>> no maintenance on my side.
>>>>>
>>>>> sorry for the noise... but is it somehow possible to see your dovecot
>>>>> config? I never managed to run a local dovecot imap server in
>>>>> archlinux...
>>>>>
>>>>> many thanks in advance!
>>>>
>>>> Here's my output of "doveconf -n". This is all the configuration I've
>>>> got, apart from /etc/dovecot/passwd.
>>>>
>>>
>>> thanks! this is local imap server, isn't it?
>>
>> Right, then Gnus connects via (for instance, for this email address):
>>
>> (nnimap "EA"
>> (nnimap-address "localhost")
>> (nnimap-stream network)
>> (nnimap-authenticator login)
>> (nnimap-user "eric@ericabrahamsen.net"))
>>
>
> Or like this:
>
> (nnimap "Maildir"
> (nnimap-stream shell)
> (nnimap-shell-program "/usr/local/opt/dovecot/libexec/dovecot/imap -o mail_location=maildir:$HOME/Maildir")))
>
> If you do it like this, it is not necessary to run the imap server
> daemon - no worries about security. And if I am correc=ct, you don't
> need to configure dovecot with the conf file, as you specify the
> parameters in the commandline.
Right -- I was originally doing that (single dovecot invocations), and
wrote the blog post above because I thought that I needed an
always-running daemon in order for FTS indexing to work. Later on I
discovered it's not really necessary, but on the other hand the daemon
hasn't bothered me any, so...
next prev parent reply other threads:[~2015-12-19 2:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-15 22:53 Xavier Maillard
2015-12-16 0:13 ` Greg Troxel
2015-12-16 5:01 ` Xavier Maillard
2015-12-16 6:21 ` Glyn Millington
2015-12-16 9:22 ` Rainer M Krug
2015-12-16 22:11 ` Xavier Maillard
2015-12-17 8:33 ` Rainer M Krug
2015-12-17 10:31 ` Adam Sjøgren
2015-12-17 11:02 ` Igor Sosa Mayor
2015-12-17 11:13 ` Eric Abrahamsen
2015-12-17 11:17 ` Igor Sosa Mayor
2015-12-17 14:32 ` Rainer M Krug
2015-12-17 14:54 ` Igor Sosa Mayor
2015-12-17 23:34 ` Eric Abrahamsen
2015-12-18 9:48 ` Rainer M Krug
2015-12-18 15:19 ` Igor Sosa Mayor
2015-12-19 2:24 ` Eric Abrahamsen [this message]
2015-12-19 8:35 ` Erik Colson
2015-12-20 3:36 ` Eric Abrahamsen
2015-12-20 13:51 ` Erik Colson
2015-12-18 15:18 ` Igor Sosa Mayor
2015-12-17 14:31 ` Rainer M Krug
2015-12-16 22:08 ` Xavier Maillard
2015-12-16 13:07 ` Filipp Gunbin
2015-12-16 15:44 ` Tim Landscheidt
2015-12-16 22:06 ` Xavier Maillard
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=87lh8rrx8z.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).