From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Rainer M Krug <Rainer@krugs.de>
Cc: ding@gnus.org
Subject: Re: blog post on gnus, dovecot, and lucene
Date: Wed, 08 Oct 2014 00:47:36 +0800 [thread overview]
Message-ID: <87egujzv13.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <m2oatos5yt.fsf@krugs.de> (Rainer M. Krug's message of "Tue, 07 Oct 2014 09:18:34 +0200")
On 10/07/14 09:18 AM, Rainer M Krug wrote:
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>> Hi,
>>
>> I mentioned a bit ago that I had shifted my gnus/dovecot setup, and
>> would blog about it. I finally did that:
>>
>> http://ericabrahamsen.net/tech/2014/oct/gnus-dovecot-lucene.html
>>
>> The gist of it is how to move to an always-running dovecot daemon, fed
>> by isync, and incorporating lucene searches into that.
>
> Nice - thanks.
>
> The idea of using virtual users under dovecot is intriguing - it makes
> all the name translations I am doing in offlineimap to keep my accounts
> in different folder structures unneccessary. Could you please elaborrate
> a little bit on your setup in this regard and where the emails are
> actually stored? I might be implementing th same approach because it
> sounds so simple!
I can't claim to understand the entire configuration procedure, as I was
just diving "deep enough" into dovecot, but the trick is this bit from
the dovecot.conf file:
passdb {
driver = passwd-file
args = /etc/dovecot/passwd
}
userdb {
driver = static
args = uid=eric gid=users home=/home/eric/.mail/%d/%n
default_fields = mail=maildir:/home/eric/.mail/%d/%n/mail
}
Particularly the userdb section. I understand this to be saying: "each
virtual user should be run as uid "eric" and gid "users", and each user
will have their home directory under /home/eric/.mail, in a directory
that looks like domainname/username. Furthermore, the mail for each user
will be stored in maildir format, in a mail/ subdirectory in that user's
home directory." It's like making viritual home directories for each
virtual user.
So now my directory structure looks like:
~/.mail/ericabrahamsen.net/
└── eric
└── mail
├── cur
├── dovecot.index
[ more dovecot stuff]
├── lucene-indexes
├── new
├── subscriptions
└── tmp
~/.mail/paper-republic.org/
├── eric
│ └── mail
│ ├── cur
│ ├── dovecot.index
│ [ etc ]
│ ├── lucene-indexes
│ ├── new
│ ├── subscriptions
│ └── tmp
└── info
└── mail
├── cur
├── dovecot.index
[ more dovecot stuff]
├── lucene-indexes
├── new
├── subscriptions
└── tmp
So in cases where I have more than one user at the same domain name,
both users are nested under the domain name directory.
In hindsight the extra mail/ directory was probably unnecessary, I had
some idea that other files might go above that mail/ directory.
Hope that helps,
Eric
prev parent reply other threads:[~2014-10-07 16:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 5:43 Eric Abrahamsen
2014-10-07 5:51 ` Igor Sosa Mayor
2014-10-07 11:14 ` Feng Shu
2014-10-07 11:59 ` Rasmus
2014-10-07 10:09 ` Vincent Bernat
2014-10-07 16:30 ` Eric Abrahamsen
2014-10-08 5:12 ` Vincent Bernat
2014-10-08 14:15 ` Eric Abrahamsen
2014-10-09 5:30 ` Vincent Bernat
2014-10-09 8:23 ` Eric Abrahamsen
2014-10-09 8:30 ` Rainer M Krug
[not found] ` <m2oatos5yt.fsf@krugs.de>
2014-10-07 16:47 ` Eric Abrahamsen [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=87egujzv13.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=Rainer@krugs.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).