Re: IMAP archive?
On 2015-03-05 16:02, Dan White wrote: > On 03/05/15 13:53 +0100, Marco wrote: >> I read in docs that with Cyrus-Imapd I can create a folder Archive >> with no quota for each user, using a dedicated partition. > > Assuming you have a quota root set for each user's INBOX, you would > need to > explicitly set a higher quota value for any such archive folder, if it > exists hierarchically underneath the INBOX. > More specifically, you need to create a quota root on the Archive folder (however it be named) so that it is no longer a part of the original INBOX quota root, and you could set the Archive folder's quota root storage quota to be '-1', aka. 'unlimited'. Separately, you could make the Archive folder (however it be named) end up on a separate partition or even a separate server/partition, so that it is abundantly less resource-rich than your average INBOX server(s)/partition(s). You would typically restrict your users to, say, 1GB of storage space, and hence force them to "archive" mail at a reasonable point in time -- or risk run out of storage quota. If the only place they can archive *to* just so happens to be this Archive folder that is located on a cheaper/slower set of disks, then maybe that's just what you wanted. Kind regards, Jeroen van Meeuwen -- Systems Architect, Kolab Systems AG e: vanmeeuwen at kolabsys.com m: +41 79 951 9003 w: https://kolabsystems.com pgp: 9342 BF08 Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsubscribe: https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
Re: The admins key on imapd.conf
On 2015-03-10 20:25, Niels Dettenbach wrote:
> Am Dienstag, 10. März 2015, 17:48:44 schrieb Manuel Vazquez:
>> I understand by the official documentation,this users described there
>> are
>> can see the mailboxes of the all the users present in the server.
>>
>> Do it is correct?
> Beside this, the admin user(s) are able to create mailboxes / folders
> and
> maintaining access rights and quotas including delete folders after
> setting
> the appropiate rights to it.
>
> It is important to understand the role of the admin user - without i
> assume it
> would be nearly impossible to set up and maintain a cyrus setup.
>
True, but for the autocreate feature set we have today ;-)
It needs to be understood that any user listed in `admins` setting has
-- implicitly -- the 'a' right on *all* mailboxes.
The 'a' right does not imply any other rights ('l', 'r', 's' most
prominently, though an "admin" doesn't require 'l' specifically in order
to be able to have a mailbox appear in a list of mailboxes), but does
impose the right to SETACL (including 'l', 'r' and 's', and whichever
other ones!).
`admins` should be limited very, *very* much, to a rather select group
of people/services with a proverbial ``$surname-admin`` account -- it is
the sysadmin/root equivalent of a system otherwise normally a sealed
system.
Kind regards,
Jeroen van Meeuwen
--
Systems Architect, Kolab Systems AG
e: vanmeeuwen at kolabsys.com
m: +41 79 951 9003
w: https://kolabsystems.com
pgp: 9342 BF08
Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus
