[Dovecot] question on quota configuration on 2.0.5
Hi,
On dovecot 1.2 i had the following configuration on my
dovecot-sql.conf file:
password_query = select endereco as user, password, '/var/spool/mail/%u' as userdb_home, 'maildir:/var/spool/mail/%u' as userdb_mail, 8 as userdb_uid, 12 as userdb_gid, concat('*:storage=', quota) as userdb_quota_rule, 'Trash:storage=100M' as userdb_quota_rule2 from emails where endereco = '%u' and ativa = '1'
special attention to
'Trash:storage=100M' as userdb_quota_rule2
after migrating to 2.0.5, i got this warning on the logs:
Oct 3 16:06:41 ns2 dovecot: imap(user@domain.com), rip=127.0.0.1, lip=127.0.0.1: Warning: quota root User quota rule Trash:storage=100M: obsolete configuration for rule 'storage=100M' should be changed to 'storage=+100M' Oct 3 16:08:09 ns2 dovecot: imap(user@domain.com), rip=127.0.0.1, lip=127.0.0.1: Error: quota: Unknown namespace: Trash
about changing 100M to +100M, that's OK, no problem .... but even
after changing that, i still keep getting the 'unknown namespace' message.
question: what's the correct way of doing this configuration on
dovecot 2.0 ? The idea of this configuration is to give plus 100M of the user's quota on the Trash folder, thus avoiding problems with out webmail which copies messages to trash before erasing from the actual folder.
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Minha armadilha de SPAM, NÃO mandem email
gertrudes@solutti.com.br
My SPAMTRAP, do not email it
On Sun, 2010-10-03 at 16:09 -0300, Leonardo Rodrigues wrote:
password_query = select endereco as user, password, '/var/spool/mail/%u' as userdb_home, 'maildir:/var/spool/mail/%u' as userdb_mail, 8 as userdb_uid, 12 as userdb_gid, concat('*:storage=', quota) as userdb_quota_rule, 'Trash:storage=100M' as userdb_quota_rule2 from emails where endereco = '%u' and ativa = '1'
You have only one user? Maybe you should be using passwd-file instead of SQL..
Oct 3 16:08:09 ns2 dovecot: imap(user@domain.com), rip=127.0.0.1, lip=127.0.0.1: Error: quota: Unknown namespace: Trash
about changing 100M to +100M, that's OK, no problem .... but even
after changing that, i still keep getting the 'unknown namespace' message.
What kind of namespace configuration do you have? (dovecot -n)
question: what's the correct way of doing this configuration on
dovecot 2.0 ? The idea of this configuration is to give plus 100M of the user's quota on the Trash folder, thus avoiding problems with out webmail which copies messages to trash before erasing from the actual folder.
Are you sure it worked in v1.2? I'm rather guessing that v1.2 just didn't give an error about it.
Hi Timo,
Em 04/10/2010 11:19, Timo Sirainen escreveu:
On Sun, 2010-10-03 at 16:09 -0300, Leonardo Rodrigues wrote:
password_query = select endereco as user, password, '/var/spool/mail/%u' as userdb_home, 'maildir:/var/spool/mail/%u' as userdb_mail, 8 as userdb_uid, 12 as userdb_gid, concat('*:storage=', quota) as userdb_quota_rule, 'Trash:storage=100M' as userdb_quota_rule2 from emails where endereco = '%u' and ativa = '1' You have only one user? Maybe you should be using passwd-file instead of SQL..
No, i have a lot of users .... users are replaced bu the %u
variable and are stored on my column field named 'endereco'
Oct 3 16:08:09 ns2 dovecot: imap(user@domain.com), rip=127.0.0.1, lip=127.0.0.1: Error: quota: Unknown namespace: Trash
about changing 100M to +100M, that's OK, no problem .... but even
after changing that, i still keep getting the 'unknown namespace' message. What kind of namespace configuration do you have? (dovecot -n)
on 1.2 it was:
namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes
on 2.0 with that same configuration, i got the errors i posted before.
question: what's the correct way of doing this configuration on
dovecot 2.0 ? The idea of this configuration is to give plus 100M of the user's quota on the Trash folder, thus avoiding problems with out webmail which copies messages to trash before erasing from the actual folder.
Are you sure it worked in v1.2? I'm rather guessing that v1.2 just didn't give an error about it.
you seem to be completly right .... things wasnt working as
expected on 1.2 altough there were no errors and warnings.
to get things working on 2.0 as they were working on 1.2, i had to
configure like this:
namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = . type = private } namespace { inbox = no location = prefix = separator = . }
and now things are working exactly as i expected and exactly they
worked on 1.2.
--
Atenciosamente / Sincerily,
Leonardo Rodrigues
Solutti Tecnologia
http://www.solutti.com.br
Minha armadilha de SPAM, NÃO mandem email
gertrudes@solutti.com.br
My SPAMTRAP, do not email it
On 5.10.2010, at 14.13, Leonardo Rodrigues wrote:
you seem to be completly right .... things wasnt working as expected on 1.2 altough there were no errors and warnings.
to get things working on 2.0 as they were working on 1.2,
Didn't you just say they weren't working in 1.2? :)
namespace { hidden = no inbox = yes list = yes location = prefix = INBOX. separator = . type = private } namespace { inbox = no location = prefix = separator = . } and now things are working exactly as i expected and exactly they worked on 1.2.
That's not a very good configuration. Now all the mailboxes show up twice in LIST, once on root level and once under INBOX. Setting hidden=yes and list=no for the INBOX. namespace would make it a better configuration, but even simpler would be to not add any namespaces and use INBOX.Trash as the mailbox name in quota_rule2.
participants (2)
-
Leonardo Rodrigues
-
Timo Sirainen