On Wed, Nov 16, 2011 at 5:23 PM, Bambero wrote:
> On Wed, Nov 16, 2011 at 3:59 PM, Timo Sirainen wrote:
>> On Wed, 2011-11-16 at 15:54 +0100, Bambero wrote:
>>> >> Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No
>>> >> such file or directory
>>> >
>>> > This is done because you
On Wed, Nov 16, 2011 at 3:59 PM, Timo Sirainen wrote:
> On Wed, 2011-11-16 at 15:54 +0100, Bambero wrote:
>> >> Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No
>> >> such file or directory
>> >
>> > This is done because you used %%h, to look up home directory from
>> > userdb. I
On Wed, 2011-11-16 at 15:54 +0100, Bambero wrote:
> >> Error: userdb lookup: connect(/var/dovecot/auth-userdb) failed: No
> >> such file or directory
> >
> > This is done because you used %%h, to look up home directory from
> > userdb. If you don't use %%h, it's not done.
> >
>
> Thanks but my db
On Tue, Nov 15, 2011 at 8:44 PM, Timo Sirainen wrote:
> On Sun, 2011-11-13 at 17:25 +0100, Bambero wrote:
>
>> all maildirs are located in: /var/mail/j...@example.com/Maildir
>
> So this is /var/mail/%u/Maildir template.
>
>> namespace {
>> type = shared
>> separator = /
>> prefix = shared/%
On Sun, 2011-11-13 at 17:25 +0100, Bambero wrote:
> all maildirs are located in: /var/mail/j...@example.com/Maildir
So this is /var/mail/%u/Maildir template.
> namespace {
> type = shared
> separator = /
> prefix = shared/%%u/
> location = maildir:%%h/Maildir:INDEX=~/Maildir/shared/%%u
Hello,
I have successfully setup dovecot with chroot but there are two things yet
1. submission_host problem (I posted message 2 days ago)
2. Problem with acl's and sharing:
all maildirs are located in: /var/mail/j...@example.com/Maildir
so:
mail_chroot=/var/mail
I setup acls with:
10-mail.conf
On 2011年06月07日 22:15, Timo Sirainen wrote:
On Tue, 2011-06-07 at 22:02 +0800, johnw wrote:
On 2011年06月07日 21:13, Timo Sirainen wrote:
On Tue, 2011-06-07 at 19:19 +0800, johnw wrote:
Couldn't drop privileges: Process is already chrooted, can't un-chroot
for this user
and lmtp can not delivery
On Tue, 2011-06-07 at 22:02 +0800, johnw wrote:
> On 2011年06月07日 21:13, Timo Sirainen wrote:
> > On Tue, 2011-06-07 at 19:19 +0800, johnw wrote:
> >> Couldn't drop privileges: Process is already chrooted, can't un-chroot
> >> for this user
> >>
> >> and lmtp can not delivery mail
> > This'll fix it
On 2011年06月07日 21:13, Timo Sirainen wrote:
On Tue, 2011-06-07 at 19:19 +0800, johnw wrote:
Couldn't drop privileges: Process is already chrooted, can't un-chroot
for this user
and lmtp can not delivery mail
This'll fix it: http://hg.dovecot.org/dovecot-2.0/rev/ed05316ed441
Also remove the pro
On Tue, 2011-06-07 at 19:19 +0800, johnw wrote:
> Couldn't drop privileges: Process is already chrooted, can't un-chroot
> for this user
>
> and lmtp can not delivery mail
This'll fix it: http://hg.dovecot.org/dovecot-2.0/rev/ed05316ed441
Also remove the protocol !lmtp {} around mail_chroot. Lo
On 2011年06月07日 02:41, Timo Sirainen wrote:
On 6.6.2011, at 19.59, johnw wrote:
yes, i did it (put the mail_chroot inside the protocol !lmtp { mail_chroot =
/var/vmail/ }
and no mail_chroot anywhere.
but the both doveconf mail_chroot and doveconf -f protocol=lmtp mail_chroot
result is same emp
On 6.6.2011, at 19.59, johnw wrote:
> yes, i did it (put the mail_chroot inside the protocol !lmtp { mail_chroot =
> /var/vmail/ }
> and no mail_chroot anywhere.
>
> but the both doveconf mail_chroot and doveconf -f protocol=lmtp mail_chroot
> result is same empty: mail_chroot =
Oh, looks like
On 2011年06月07日 00:42, Timo Sirainen wrote:
On 6.6.2011, at 19.32, johnw wrote:
Is there another mail_chroot setting elsewhere? The important thing is
that when you do:
doveconf mail_chroot
it shows the chroot, but when you do:
doveconf -f protocol=lmtp mail_chroot
the result should be empty
On 6.6.2011, at 19.32, johnw wrote:
>> Is there another mail_chroot setting elsewhere? The important thing is
>> that when you do:
>>
>> doveconf mail_chroot
>>
>> it shows the chroot, but when you do:
>>
>> doveconf -f protocol=lmtp mail_chroot
>>
>> the result should be empty.
>>
> when i h
On 2011年06月07日 00:09, Timo Sirainen wrote:
On Tue, 2011-06-07 at 00:02 +0800, johnw wrote:
i already config mail_chroot, should i remove it?(mail_chroot)
any how-to document is for lmtp chroot?
protocol !lmtp {
mail_chroot = /somewhere
}
i added it to 20-lmtp.conf, is it correct?
It doe
On Tue, 2011-06-07 at 00:02 +0800, johnw wrote:
> i already config mail_chroot, should i remove it?(mail_chroot)
> any how-to document is for lmtp chroot?
> >>> protocol !lmtp {
> >>> mail_chroot = /somewhere
> >>> }
> >>>
> i added it to 20-lmtp.conf, is it correct?
It doesn't matte
On 2011年06月06日 23:39, Timo Sirainen wrote:
On Mon, 2011-06-06 at 23:36 +0800, johnw wrote:
On 2011年06月06日 23:28, Timo Sirainen wrote:
On Mon, 2011-06-06 at 23:20 +0800, johnw wrote:
(lmtp) Couldn't drop privileges: Process is already chrooted, can't
un-chroot for this user
i already config ma
On Mon, 2011-06-06 at 23:36 +0800, johnw wrote:
> On 2011年06月06日 23:28, Timo Sirainen wrote:
> > On Mon, 2011-06-06 at 23:20 +0800, johnw wrote:
> >> (lmtp) Couldn't drop privileges: Process is already chrooted, can't
> >> un-chroot for this user
> >>
> >> i already config mail_chroot, should i rem
On 2011年06月06日 23:28, Timo Sirainen wrote:
On Mon, 2011-06-06 at 23:20 +0800, johnw wrote:
(lmtp) Couldn't drop privileges: Process is already chrooted, can't
un-chroot for this user
i already config mail_chroot, should i remove it?(mail_chroot)
any how-to document is for lmtp chroot?
protocol
On Mon, 2011-06-06 at 23:20 +0800, johnw wrote:
> (lmtp) Couldn't drop privileges: Process is already chrooted, can't
> un-chroot for this user
>
> i already config mail_chroot, should i remove it?(mail_chroot)
> any how-to document is for lmtp chroot?
protocol !lmtp {
mail_chroot = /somewhere
On Mon, 06 Jun 2011 17:46:31 +0300, Timo Sirainen wrote:
On Sat, 2011-06-04 at 21:48 +0800, johnw wrote:
i want to chroot lmtp with sieve, but have some problem, look like
lmtp
can not load sieve's lib or something.
the error message like this:
dovecot: lmtp(12799): Fatal: opendir(/usr/local/l
On Sat, 2011-06-04 at 21:48 +0800, johnw wrote:
> i want to chroot lmtp with sieve, but have some problem, look like lmtp
> can not load sieve's lib or something.
> the error message like this:
>
> dovecot: lmtp(12799): Fatal: opendir(/usr/local/lib/dovecot) failed: No
> such file or directory
>
i want to chroot lmtp with sieve, but have some problem, look like lmtp
can not load sieve's lib or something.
the error message like this:
dovecot: lmtp(12799): Fatal: opendir(/usr/local/lib/dovecot) failed: No
such file or directory
all is work fine, when not config lmtp chroot.
can i config lm
Timo Sirainen wrote:
> I did several fixes now. These should fix them:
http://www.dovecot.org/list/dovecot-cvs/2007-March/008412.html
http://www.dovecot.org/list/dovecot-cvs/2007-March/008413.html
Seems everything works well now.
On 28.3.2007, at 13.34, Michal Soltys wrote:
I'm not sure if it's even intended to work in this particular
case, but there's a problem when chroot is explicitely defined
and rawlogging is used. Rawlog respects chroot point, without
being actually chrooted.
I did several fixes now. These should
I'm not sure if it's even intended to work in this particular
case, but there's a problem when chroot is explicitely defined
and rawlogging is used. Rawlog respects chroot point, without
being actually chrooted.
Consider configurtion as below, with two cases (dovecot.rawlog
dir is of course creat
26 matches
Mail list logo
