W dniu 12.09.2011 12:21, Timo Sirainen pisze:
Not exactly like that, but you should be able to have a field called
"userdb_import" that contains data like:
namespace=n1 n2namespace/n1/prefix=blah.etc. other fields
Thes would of course have to be actual tab characters.
Cool. I've changed field
On Fri, 2011-09-09 at 13:24 +0200, Marcin Mirosław wrote:
> Ok, maybe could it be possible to do it in other way:
>
> |user_id | namespace_full_definition |
> -
W dniu 08.09.2011 15:18, Timo Sirainen pisze:
Forget all of that. I just tried a few ways and looks like you can add
more namespaces by returning e.g. these fields (from SQL):
namespace=nsname
namespace/nsname/prefix=prefix/
namespace/nsname/location=maildir:/elsewhere
namespace/nsname/separato
On Thu, 2011-09-08 at 13:00 +0200, Marcin Mirosław wrote:
> W dniu 08.09.2011 11:40, Timo Sirainen pisze:
> > You can't have two namespaces with prefix="". So for example add:
> >
> > namespace test33 {
> >prefix = test33.
> > }
>
> I admit that I slightly lost me. Let me try to summarize:
> -
W dniu 08.09.2011 11:40, Timo Sirainen pisze:
You can't have two namespaces with prefix="". So for example add:
namespace test33 {
prefix = test33.
}
I admit that I slightly lost me. Let me try to summarize:
- i can't use db to keep completely definition of namespace(s)
-- e.g. user X has n
On Thu, 2011-09-08 at 11:26 +0200, Marcin Mirosław wrote:
> W dniu 07.09.2011 17:24, Timo Sirainen pisze:
> > On 7.9.2011, at 18.19, Marcin Mirosław wrote:
> > Actually I'm not completely sure if this is needed. Get it working first
> > with this template, and then see if it continues working afte
W dniu 07.09.2011 17:24, Timo Sirainen pisze:
On 7.9.2011, at 18.19, Marcin Mirosław wrote:
Actually I'm not completely sure if this is needed. Get it working first with
this template, and then see if it continues working after removing the template.
I did namespace template:
namespace test33
On 7.9.2011, at 18.19, Marcin Mirosław wrote:
>> I don't think you can add new ones via userdb lookup.. You'll basically have
>> to have a template in the config file first, like:
>>
>> namespace newspace {
>> }
>
> Hmm, it doesn't looks flexible ;) But probably should be enough for my
> purpo
W dniu 07.09.2011 17:09, Timo Sirainen pisze:
On 7.9.2011, at 17.59, Marcin Mirosław wrote:
namespace {
inbox = yes
list = yes
location =
prefix =
separator = .
subscriptions = yes
type = private
}
You want to modify this namespace, or add a completely new namespace?
I want to
On 7.9.2011, at 17.59, Marcin Mirosław wrote:
> namespace {
> inbox = yes
> list = yes
> location =
> prefix =
> separator = .
> subscriptions = yes
> type = private
> }
You want to modify this namespace, or add a completely new namespace? I don't
think you can add new ones via userdb loo
W dniu 07.09.2011 16:50, Timo Sirainen pisze:
dovecot -n output (with version number)?
Argh, i've forgot about it:( Dovecot-2.0.14
# 2.0.14: /etc/dovecot/dovecot.conf
# OS: Linux 3.1.0-rc4-git2 x86_64 Gentoo Base System release 2.0.3
auth_cache_size = 1 k
auth_debug = yes
auth_mechanisms = log
dovecot -n output (with version number)?
On 7.9.2011, at 17.42, Marcin Mirosław wrote:
> Hello!
> I'd like to set up dovecot to keep namespaces in database, keep more than one
> namespace per user.
>
> I try to create the simplest rule (even without tuple in db table) to get new
> namespace, u
12 matches
Mail list logo
