Skip to content
Toggle navigation
Toggle navigation
This project
Loading...
Sign in
John McEleney
/
mailutils
Go to a project
Toggle navigation
Toggle navigation pinning
Projects
Groups
Snippets
Help
Project
Activity
Repository
Pipelines
Graphs
Issues
0
Merge Requests
0
Wiki
Network
Create a new issue
Builds
Commits
Issue Boards
Files
Commits
Network
Compare
Branches
Tags
Commit
06480352
...
0648035219293c028b88b5bcb0c08b5c0d541e4e
authored
2017-01-26 12:40:51 +0200
by
Sergey Poznyakoff
Browse Files
Options
Browse Files
Tag
Download
Email Patches
Plain Diff
Improve description of variables useful in namespace directory statements
1 parent
24a868b2
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
54 additions
and
6 deletions
doc/texinfo/programs.texi
doc/texinfo/programs.texi
View file @
0648035
...
...
@@ -7591,9 +7591,9 @@ be run either as a standalone program or from @file{inetd.conf} file.
@cindex IMAP4 namespace
GNU @command{imap4d} supports a notion of @dfn{namespaces} defined
in RFC 2342. A namespace can be regarded as a list of
triplet
s,
in RFC 2342. A namespace can be regarded as a list of
entitie
s,
defining locations to which the user has certain access rights. Each
triplet defin
es the @dfn{prefix}, under which the mailboxes can be
entity includ
es the @dfn{prefix}, under which the mailboxes can be
found, @dfn{hierarchy delimiter}, a character used to delimit parts of
a path to a mailbox, and a @dfn{directory} on the file system on the
server, which actually holds the mailboxes. Among these three values,
...
...
@@ -7679,8 +7679,17 @@ determines their mappings to the server's file system. The @var{pfx}
argument defines the prefix which will be visible to the IMAP client.
The @code{directory} statement defines the directory in the file
system to which @var{pfx} is mapped. Its argument can contain
references to the following variables(@pxref{Variables}):
system to which @var{pfx} is mapped. Exactly one @code{directory}
statement must be present in each @code{prefix} block. The
inerpretation of its argument depends on the namespace in which it
occurs.
When used in the @samp{namespace shared} block, the argument to this
statement is interpreted verbatim, as an absolute pathname.
When used in @samp{namespace personal} the argument to
@code{directory} statement can contain references to the following
variables (@pxref{Variables}):
@table @asis
@item user
...
...
@@ -7690,8 +7699,47 @@ Login name of the user.
Home directory of the user.
@end table
Exactly one @code{directory} statement must be present in each
@code{prefix} block.
For example, the following statement maps the default personal
namespace to the directory @samp{imap} in the user's home directory:
@example
@group
namespace personal @{
prefix "";
directory "
$
home
/
imap
";
@}
@end group
@end example
If the @samp{directory} statement is used within the @samp{namespace
other} block, its value can contain the @samp{$user} and
@samp{$home} variables as well, but their meaning is different. For
the @samp{other} namespace, the @samp{$user} variable is expanded
to the part of the actual reference contained between the prefix and
first hierarchy delimiter (or the end of the reference, if no
delimiter occurs to the right of the prefix). Correspondingly,
@samp{$home} expands to the home directory of that user. Consider,
for example, the following statement:
@example
@group
namespace other @{
prefix "
~
";
directory "
/
var
/
imap
/
$
user
";
@}
@end group
@end example
If the client issues the following statement:
@example
1 LIST "
~
smith
" "
%
"
@end example
@noindent
then @samp{$user} will expand to the string @samp{smith} and the
server will look for all mailboxes in the directory
@file{/var/imap/smith}.
The @code{delimiter} statement defines the folder hierarchy delimiter
for that prefix. It is optional, the default value being @samp{"
/
"}.
...
...
Please
register
or
sign in
to post a comment