This documentation is for Dovecot v2.x, see wiki1 for v1.x documentation.
Differences between revisions 12 and 13
Revision 12 as of 2006-05-18 12:25:37
Size: 2130
Comment: name RFC-2342 in link text
Revision 13 as of 2007-03-18 20:38:31
Size: 2141
Editor: TimoSirainen
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
Dovecot 1.0 versions support fully configurable namespaces. Their original and primary purpose is to provide [http://www.faqs.org/rfcs/rfc2342.html Namespace IMAP extension (RFC 2342)] support, which allows giving clients hints about where to locate mailboxes and if they're private, shared or public. Unfortunately most IMAP clients don't support this extension. Dovecot supports fully configurable namespaces. Their original and primary purpose is to provide Namespace IMAP extension ([http://www.faqs.org/rfcs/rfc2342.html RFC 2342]) support, which allows giving IMAP clients hints about where to locate mailboxes and whether they're private, shared or public. Unfortunately most IMAP clients don't support this extension.
Line 4: Line 4:
With Dovecot namespaces can be used for a few other purposes too: Dovecot namespaces can be used for several other purposes too:
Line 71: Line 71:
Without the "hidden = yes" in the first namespace, clients see the #mbox namespace as a non-selectable mailbox named as #mbox and having submailboxes (ie. like a directory). Without the {{{hidden = yes}}} setting in the first namespace, clients see the "#mbox" namespace as a non-selectable mailbox named "#mbox" and having child mailboxes (ie. like a directory).

Namespaces

Dovecot supports fully configurable namespaces. Their original and primary purpose is to provide Namespace IMAP extension ([http://www.faqs.org/rfcs/rfc2342.html RFC 2342]) support, which allows giving IMAP clients hints about where to locate mailboxes and whether they're private, shared or public. Unfortunately most IMAP clients don't support this extension.

Dovecot namespaces can be used for several other purposes too:

  • Providing backwards compatibility when switching from another IMAP server
  • Provides support for public shared mailboxes
  • Allows having mails in multiple different locations with possibly different formats

See namespace sections in [http://dovecot.org/doc/dovecot-example.conf example configuration file] for more information.

Backwards Compatibility

When switching from UW-IMAP and you don't want to give users full access to filesystem, you can create hidden namespaces which allow users to access their mails using their existing namespace settings in clients.

# default namespace
namespace private {
  separator = /
  prefix =
  inbox = yes
}
# for backwards compatibility:
namespace private {
  separator = /
  prefix = mail/
  hidden = yes
}
namespace private {
  separator = /
  prefix = ~/mail/
  hidden = yes
}
namespace private {
  separator = /
  prefix = ~%u/mail/
  hidden = yes
}

For Courier-IMAP compatibility, use:

namespace private {
  separator = .
  prefix = INBOX.
  inbox = yes
}

Shared Mailboxes

See SharedFolders.

Multiple Mailbox Locations

INBOX in /var/mail/username, maildir in ~/Maildir, other mboxes in ~/mail under #mbox/ namespace:

namespace private {
  separator = /
  inbox = yes
  hidden = yes
  prefix = "#mbox/"
  location = mbox:~/mail:INBOX=/var/mail/%u
}
namespace private {
  separator = /
  prefix =
  location = maildir:~/Maildir
}

Without the hidden = yes setting in the first namespace, clients see the "#mbox" namespace as a non-selectable mailbox named "#mbox" and having child mailboxes (ie. like a directory).

None: Namespaces (last edited 2019-09-12 08:39:23 by MichaelSlusarz)