Displaying 4 results from an estimated 4 matches for "16hu".
2011 Nov 08
2
Multiple Patitions with with mdbox
Having > 10 TByte mailstore filesystem-checks takes too much time.
At the moment we have four different partitions, but I don't like to set
symlinks or LDAP-flags to sort customers and their domains to there
individual mount-point. I'd like to work with mdbox:/mail/%d/%n to calculate
the path automatically.
How do you handle >> 10 TB mailstore?
I'm very interested in the
2012 Nov 19
0
upgrade 1.0.15 -> 2.1.7: MBOX index compatibility and performance
...just upgraded our mailserver from Dovecot 1.0.15 to Dovecot 2.1.7.
We use MBOX format (due to legacy compatibility), system users,
PAM+GSSAPI auth, filesystem quotas, and indexes located on a separate
filesystem:
mail_location =
mbox:~/mail:INBOX=~/mail/INBOX:INDEX=/var/cache/dovecot/indexes/%16Hu/%u
The 2.1.7 configuration files have been rewritten based on default
templates instead of converting it from 1.0.15.
The server has ~8000 mailboxes and about ~2000 simultaneous IMAP/POP
active connexions.
The problem is:
- indexes seem to be rebuilt: first IMAP/POP connexion for each user
t...
2008 Mar 04
4
Security issue #5: mail_extra_groups setting is often used insecurely
mail_extra_groups=mail setting is often used insecurely to give Dovecot
access to create dotlocks to /var/mail directory. If you don't use
mboxes in /var/mail, make sure this setting is cleared.
If you do use /var/mail mboxes and Dovecot gives permission errors
without it, do one of the following (in the preferred order):
a) Upgrade to v1.0.11 and use the new mail_privileged_group setting
2008 Mar 04
4
Security issue #5: mail_extra_groups setting is often used insecurely
mail_extra_groups=mail setting is often used insecurely to give Dovecot
access to create dotlocks to /var/mail directory. If you don't use
mboxes in /var/mail, make sure this setting is cleared.
If you do use /var/mail mboxes and Dovecot gives permission errors
without it, do one of the following (in the preferred order):
a) Upgrade to v1.0.11 and use the new mail_privileged_group setting