e7b24b112a44fdd9ee93bdf998c6ca0e

Edit file

File name : maildiracl.html

Content :

<?xml version="1.0"?>
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/><title>maildiracl</title><link rel="stylesheet" type="text/css" href="style.css"/><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"/><link rel="home" href="#idm255214213184" title="maildiracl"/><link xmlns="" rel="stylesheet" type="text/css" href="manpage.css"/><meta xmlns="" name="MSSmartTagsPreventParsing" content="TRUE"/><link xmlns="" rel="icon" href="icon.gif" type="image/gif"/><!--

--></head><body><div class="refentry"><a id="idm255214213184" shape="rect"> </a><div class="titlepage"/><div class="refnamediv"><h2>Name</h2>maildiracl — manage access control lists</div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><code class="command">maildiracl</code> {-reset} {<code>maildir</code>}</div><div class="cmdsynopsis"><code class="command">maildiracl</code> {-list} {<code>maildir</code>} {<code>INBOX[.folder]</code>}</div><div class="cmdsynopsis"><code class="command">maildiracl</code> {-set} {<code>maildir</code>} {<code>INBOX[.folder]</code>} {<code>[-]identifier</code>} {<code>[+/-]rights</code>}</div><div class="cmdsynopsis"><code class="command">maildiracl</code> {-delete} {<code>maildir</code>} {<code>INBOX[.folder]</code>} {<code>[-]identifier</code>}</div><div class="cmdsynopsis"><code class="command">maildiracl</code> {-compute} {<code>maildir</code>} {<code>INBOX[.folder]</code>} {<code>identifier</code>...}</div></div><div class="refsect1"><a id="idm255217010064" shape="rect"> </a><h2>DESCRIPTION</h2>
maildiracl
manages “access control lists” (or ACLs)
of the Courier IMAP server maildir folders.
Access control lists are used primarily to provide fine-grained control
for accessing virtual shared folders via IMAP.<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
The Courier IMAP server server implements
two types of shared folders:
filesystem permission-based shared folders,
as well as virtual shared folders based on IMAP access control lists.
Use the maildiracl
command to set up access control lists for virtual shared folders.
Use the
<a class="ulink" href="maildirmake.html" target="_top" shape="rect">maildirmake(1)</a>,
command
to implement shared folders based on
filesystem permissions.
See the Courier IMAP
server documentation for additional information
on setting up virtual shared folders.</div><div class="refsect2"><a id="idm255217002016" shape="rect"> </a><h3>ACL overview</h3>
ACLs provide a fine-grained mechanism for controlling
access to shared folders.
ACLs may be used to specify, for example, that
<code class="literal">user1</code> may only open and read the messages in the folder;
and <code class="literal">user2</code> can not only do that, but also delete messages,
and create subfolders.
Each folder maintains its own individual access control list, that specifies
who can do what to the folder.
An ACL is a list of “identifier” and “rights”
pairs.
Each “identifier” and “rights” pair means that an
entity called “identifier”
(using the <code class="literal">UTF-8</code> character set)
is allowed to do “rights”
on this folder.
“rights” consists of one or more letters, each letter
signifies a particular action:<div class="variablelist"><dl class="variablelist"><dt>a</dt><dd>
<code>identifier</code>
may modify this folder's ACLs.</dd><dt>c</dt><dd>
<code>identifier</code>
may create subfolders of this folder (this includes renaming another
folder as this folder's subfolders).</dd><dt>e</dt><dd>
<code>identifier</code>
may remove deleted messages from this folder.</dd><dt>i</dt><dd>
<code>identifier</code>
may add messages to this folder (either uploading them one by one,
or copying messages from another folder).</dd><dt>l</dt><dd>
<code>identifier</code>
may actually see that this folder exists.
If <code>identifier</code> does not have the “l”
right on this folder, the folder is effectively invisible to
<code>identifier</code>.</dd><dt>r</dt><dd>
<code>identifier</code>
may open this folder.
Note that if <code>identifier</code>
knows the name of this folder, it can open it even if
<code>identifier</code> does not the “l”
right on this folder.</dd><dt>s</dt><dd>
<code>identifier</code>
may mark messages in this folder as seen, or unseen.</dd><dt>t</dt><dd>
<code>identifier</code>
may mark messages in this folder as deleted, or undeleted.</dd><dt>w</dt><dd>
<code>identifier</code>
may change other status flags of messages in this folder.
May also add or remove custom keywords on individual messages.</dd><dt>x</dt><dd>
<code>identifier</code>
may delete this folder (which includes renaming this folder as another
mailbox's subfoler.</dd></dl></div><div class="refsect3"><a id="idm255213195776" shape="rect"> </a><h4>Negative rights</h4>
An ACL entry of “-identifier” and “rights”
is called a “negative right”, which
explicitly removes “rights” from “identifier”.
More than one “identifier” is usually used to determine the
actual rights someone has for the given folder.
The actual access rights are determined by taking all rights from all
applicable <code>identifier</code>, than subtracting any
negative rights, as specified in the following section.</div><div class="refsect3"><a id="idm255213191760" shape="rect"> </a><h4>Identifiers</h4>
Access rights on a given folder are computed by obtained the rights
on the following identifiers, then subtracting the negative rights on the
same identifiers:<div class="variablelist"><dl class="variablelist"><dt><code class="literal">owner</code></dt><dd>
The owner of the maildir containing this folder.
The maildir's INBOX's ACL defaults to all rights for its owner.
A new folder's ACL is the same as its parent's ACL.
In all cases, trying to remove the “a” right from the owner
(either directly or using a negative right) results in an error.</dd><dt><code class="literal">anyone</code></dt><dd>
This identifier refers literally to every userid.
The associated rights (or negative rights) are always used.</dd><dt><code class="literal">anonymous</code></dt><dd>
This is a synonym from “anyone”.</dd><dt><code class="literal">user=</code><code>loginid</code></dt><dd>
Rights (or negative rights) for IMAP account “loginid”.
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
“loginid” is what's logged to syslog after a succesful
login.
In some situations “loginid” is not exactly the actual login ID
used by the IMAP client.</div>
</dd><dt><code class="literal">group=</code><code>name</code></dt><dd>
Rights (or negative rights) for account group “name”.
Access rights are granted to an account group as a whole.
The account options feature of the Courier Authentication Library specifies
which account belongs to which account group.
See courier-authlib's documentation for more information.
</dd><dt><code class="literal">administrators</code></dt><dd>
This is an alias for “group=administrators”.
Accounts that are members of an account group called
“administrators” are considered administrative accounts, and
automatically receive all access rights on all accessible folders.</dd></dl></div>
Consider the following access control list:<div class="informalexample"><pre class="programlisting" xml:space="preserve">
owner aceilrstwx
anyone lr
user=john w
-user=mary r
administrators aceilrstwx
</pre></div>
This access control list specifies that the folder's owner has complete
control over the mailbox (as well as the administrators, which have complete
access to every folder); everyone else can see it and open it,
except for “mary” who can see that the mailbox exists, but
can't open it; additionally, “john” can change the status and
keywords of individual messages (but not mark them as deleted/undeleted or
seen/unseen, which requires additional rights).</div></div></div><div class="refsect1"><a id="idm255213770192" shape="rect"> </a><h2>OPTIONS</h2><div class="cmdsynopsis"><code class="command">maildiracl -reset <code>maildir</code></code> </div>
This command resets access control lists in
<code class="filename"><code>maildir</code></code>
which as a path to a maildir.
Under certain conditions, the files where a folder's ACLs are saved may
continue to exist after the folder is removed.
The <code class="literal">-reset</code> options goes through
<code>maildir</code>
and removes all stale ACL files for removed folders.<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
The Courier IMAP server
normally performs this maintenance
function automatically.
It is not necessary to run this command under normal conditions.</div><div class="cmdsynopsis"><code class="command">maildiracl -list
<code>maildir</code>
<code>folder</code>
</code> </div>
This command
lists the access control lists set for <code>folder</code>.
<code>folder</code> must be either
“INBOX” or “INBOX.folder.subfolder”, which is the
same naming convention for
the Courier IMAP server.<div class="cmdsynopsis"><code class="command">maildiracl -set
<code>maildir</code>
<code>folder</code>
<code>identifier</code>
<code>rights</code></code> </div>
Puts <code>identifier</code> (which may begin with a minus
sign to specify a negative right) and
<code>rights</code> in
<code>folder</code>'s access control list.
Existing rights for
<code>identifier</code>
(or <code>identifier</code>) are replaced by
<code>rights</code> unless “rights” begins with
“+” or “-”, which modifies the existing rights
by adding or removing from them accordingly.
Some examples:<div class="informalexample"><pre class="programlisting" xml:space="preserve">
maildiracl -set /home/user1/Maildir INBOX.Sent user=john lr

maildiracl -set /home/user2/Maildir INBOX.Notes anyone -r

maildiracl -set /home/user3/Maildir INBOX.Private -user=tom +r
</pre></div><div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
Observe that the last command revokes the “r”
right from “tom”, by adding it as a negative right.</div><div class="cmdsynopsis"><code class="command">maildiracl -delete
<code>maildir</code>
<code>folder</code>
<code>identifier</code></code> </div>
This command removes <code>identifier</code>
from
<code>folder</code>'s access control list, if it exists.
Use “-<code>identifier</code>” to remove
negative rights.<div class="cmdsynopsis"><code class="command">maildiracl -compute
<code>maildir</code>
<code>folder</code>
[<code>identifier</code>]+</code> </div>
This command takes a list of one or more
<code>identifier</code>s.
All access rights for the
<code>identifier</code>s are combined together, then
any appropriate negative rights are removed, and the result is printed
on standard output.
Use the following procedure to compute access rights the same way as they
are computed by
the Courier IMAP server:<div class="informalexample"><pre class="programlisting" xml:space="preserve">
maildiracl -compute /home/tom46/Maildir INBOX.Sent owner user=tom46
</pre></div>
This command computes access rights “tom46” has on
his own folder.<div class="informalexample"><pre class="programlisting" xml:space="preserve">
maildiracl -compute /home/john34/Maildir INBOX.Public user=tom46
</pre></div>
This command computes access rights “tom46” has on
“john34”'s folder.</div><div class="refsect1"><a id="idm255216399104" shape="rect"> </a><h2>IRREVOCABLE ACCESS RIGHTS</h2>
The owner of the mailbox must always have the “a” amd
“l” access rights.
The <code class="literal">administrators</code> group must always have all access
rights to all folders.
Attempts to set access control lists, that do not include these minimum
access rights, will be rejected.</div><div class="refsect1"><a id="idm255214994240" shape="rect"> </a><h2>BUGS</h2>
All identifiers are specified using the <code class="literal">UTF-8</code> character
set.
All non-Latin letters in folder names are specified using the
<code class="literal">modified-UTF7</code> coding as used in IMAP.
This implementation of access control lists is based on
version 2 (or “ACL2”) of IMAP
access control lists, which is a work-in-progress.
The existing IMAP ACL,
<a class="ulink" href="http://www.rfc-editor.org/rfc/rfc2086.txt" target="_top" shape="rect">RFC 2086</a>
is transparently implemented inside the ACL2 model.
If history's of any guidance, ACL2 is subject to change at any time.
Be sure to check the release notes
when upgrading to a newer version of this software.
The “ACL overview” portion of this manual page is a
very brief summary of ACL2, which leaves out optional
parts of ACL2 that are not implemented.</div><div class="refsect1"><a id="idm255214624736" shape="rect"> </a><h2>SEE ALSO</h2>
<a class="ulink" href="maildirmake.html" target="_top" shape="rect">maildirmake(1)</a>,
<a class="ulink" href="maildirkw.html" target="_top" shape="rect">maildirkw(1)</a>,</div></div></body></html>