Re: Namespace configuration over SQL

2014-09-26 Thread Ain
Sorry, using NULL indeed works correctly. My previous test with NULL was little bit flawed. Thanks for help! Ain > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thu, 25 Sep 2014, Ain wrote: > >> I had working setup, where namespace settings (including prefix) was >> queried over SQL. N

Re: Namespace configuration over SQL

2014-09-26 Thread Ain
Thanks for reply! Answer below: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > On Thu, 25 Sep 2014, Ain wrote: > >> I had working setup, where namespace settings (including prefix) was >> queried over SQL. Now, after installing new Dovecot to new server (using >> same configuration), this i

Re: Namespace configuration over SQL

2014-09-26 Thread Steffen Kaiser
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, 25 Sep 2014, Ain wrote: I had working setup, where namespace settings (including prefix) was queried over SQL. Now, after installing new Dovecot to new server (using same configuration), this is not working anymore. Log shows following erro

Re: Namespace configuration over SQL

2014-09-26 Thread Ain
I tried few different dovecot versions. 2.1.16 is working, 2.2.2 is broken. Because I use FreeBSD, in-between versions aren't available (I can use source of course, but ports tree don't include them). Probably some bigger change from 2.1 to 2.2 is affecting SQL output handling, any fix or workarou

Namespace configuration over SQL

2014-09-25 Thread Ain
Hello! I had working setup, where namespace settings (including prefix) was queried over SQL. Now, after installing new Dovecot to new server (using same configuration), this is not working anymore. Log shows following error: """ Initialization failed: namespace configuration error: list=yes req