Patrick Westenberg p...@wk-serv.de wrote on 20.11.2010 23:46:14:
Tim Traver schrieb:
Is there a quota setting that will let them move things to the trash
without error? this of course would be so they could decrease their disk
usage and become under quota again...
You can give additional
Miha Vrhovnik schrieb:
Patrick Westenbergp...@wk-serv.de wrote on 20.11.2010 23:46:14:
You can give additional space to e.g. Trash mailbox:
quota_rule2 = Trash:storage=100M
Patrick you sure, that doesn't mean that the trash quota is 100M?
Haven't tested your version, but for sure I know,
# ps auxwww|egrep -i imap-login
dovenull 11879 1.4 0.9 83484 77656 ?SNov20 19:12
dovecot/imap-login [822 connections (822 TLS)]
What exactly is TLS in this context?
All connections from imap - imap-login?
All clients connecting to an imap process?
--
Ralf Hildebrandt
I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs
it says that Maildirs are almost always located in ~/Maildir. I'm a
Linux end user, not a programmer, so I may be wrong in this; but isn't
the notation ~/ used for system users only to reference their home
page;
Glen Lee Edwards schrieb:
I'm trying to configure Dovecot 2.0.7. In the Dovecot Wiki for Maildirs
it says that Maildirs are almost always located in ~/Maildir. I'm a
Linux end user, not a programmer, so I may be wrong in this; but isn't
the notation ~/ used for system users only to reference
I previously had a static userdb and an ldap passdb. Everything's been
working fine, both 1.2 and 2.0 - but now I need to support the nightly
mdbox purge operation. I added the iterate params to my ldap
configuration, but (I'm guessing) that with a defined static userdb it
won't work.
How
Dear All,
I am currently using courier-imap which uses INBOX.
namespace configuration now i am willing to use dovecot instead of
courier-imap but without INBOX. namespace configuration means default
namespace of dovecot which helps me to sort out no of mail client
issues as well.
I
Hi all,
ok, I implemented the feature to allow 100 more MB in the trash, and it
appears to work for accounts that have a standard quota, but it appears
it doesn't work with an account that comes back with a 0 quota (meaning
unlimited).
So, I seemed to have fixed one issue, but then on accounts
ok, more info on this one. When I took out the quota_rule that added the
extra 100M to the trash quota, the unlimited accounts started working
properly again.
So you know, I retrieve the quota values from the userdb lookups instead
of having a default configured in the dovecot config files,
