Basically the director is just another instance of Dovecot, and the
base_dir is where the dovecot instance stores its information, so if you
want 2 instances on 1 server you will need to separate them. You will
need to set up 2 configuration files, one for Director and one for
dovecot. When
The configuration and run/base_dir directories can be where ever you
like. The locations Eduardo stated are the most appropriate for dovecot
installed with an RPM. Mine were compiled and set in the home
directory, so they are in a slightly different location. As long as you
use the -c to
On 11/02/2013 08:32 AM, Timo Sirainen wrote:
On 26.9.2013, at 16.11, Chris Lasater vorg...@gmail.com wrote:
While testing some more I found out something else. I have an alias set for
doveadm so it was running with sudo and that ended up being part of the issue.
If doveadm is run
Just in case someone else has the same problem, I had to change the
following two variables
mail_home = /mnt/home/imapd/%d/%n
mail_location = dbox:/mnt/home/imapd/%d/%n
to
mail_home = /mnt/home/imapd/%d/%n
mail_location = dbox:~/
When mail_location begins with%h or~/, its permissions are
Hi everyone,
I feel like I am missing something obvious here. I have dovecot up
and running and every piece of mail is given user read/write
permission. I see the option mail_gid, but I do not see anyplace to set
the group permissions. I see the below wiki talking about new home
wrote:
On Thu, Sep 26, 2013 at 12:45:01AM -0400, Chris Lasater wrote:
I am trying to use 2 instances of Dovecot on the same server so I
can have a Director managing my connections, everything appears to
be working, but I can not use doveadm to control my 2nd instance,
but doveconf seems to work fine
Could this bug have reappeared or not been passed to the 2.2.x release?
On 09/26/2013 07:06 PM, Daniel Parthey wrote:
Hi,
this bug should have been fixed by Timo in some 2.1.x release. The
issue should be in the list archives too. Which version are you using?
BTW: I'm still using
doveadm -c
On 09/21/2013 08:48 PM, Timo Sirainen wrote:
On 4.9.2013, at 21.29, Chris vorg...@gmail.com wrote:
login_log_format_elements does not seem to change the login logs. I have it set to the
below setting and the word home does not even appear. Is there something I
have to do to for this? Also
While testing some more I found out something else. I have an alias set
for doveadm so it was running with sudo and that ended up being part of
the issue. If doveadm is run as a regular user then the problem goes away
[user@server ~]$ doveadm -i Director log find
Debug:
Hi Guys,
I am trying to use 2 instances of Dovecot on the same server so I can
have a Director managing my connections, everything appears to be
working, but I can not use doveadm to control my 2nd instance, but
doveconf seems to work fine.
[user@server logs]$ doveconf -i Director | grep
Hi,
I have just set up a new dovecot server with Dovecot 2.2.5. When I create
a new user and try to authenticate I get the following error
Sep 03 14:33:38 imap(test2): Error: user test2: Initialization failed:
Initializing mail storage from mail_location setting failed:
-errors {
group = user2
mode = 0620
user = user
}
}
On Mon, May 14, 2012 at 12:08 PM, Timo Sirainen t...@iki.fi wrote:
On Thu, 2012-05-10 at 14:43 -0400, Chris Lasater wrote:
Hi,
I just started using Dovecot and was trying to create separate logs
instead of using syslog
Hi,
I just started using Dovecot and was trying to create separate logs
instead of using syslog. Is there a way to get the file permission to be
something other then root? I have tried the below configuration and it
does not seem to change anything. The log process does change to a new
user,
13 matches
Mail list logo