Template:Dovecot:Main Page Information - Revision history

TeemuHuovila: /* Dovecot Object Storage */

2017-08-11T07:28:10Z

Dovecot Object Storage

← Older revision		Revision as of 07:28, 11 August 2017
Line 54:		Line 54:
	'''Overview'''		'''Overview'''

	Dovecot supports ~~different~~ object ~~storages as mail~~ storage~~, where~~ the ~~mails can be stored~~ to cloud ~~services~~ such as ~~but not limited to~~ Amazon S3~~, or Microsoft Azure~~ or to ~~local “in house”~~ object storage ~~olution~~ such as ~~but not limited to Scality, Ceph or Openstack Swift or using mixture of both (storing spam to cloud, actual mails to local object storage).~~ Scality ~~is well integrated to Dovecot and allows use of generic low cost x86 servers instead of NAS/SAN devices~~.		Dovecot Pro supports mail storage to several object storage solutions. These solutions include the ability to host on a managed cloud storage service such as Amazon S3 or to locally hosted object storage solutions such as Scality.

	If mails are stored to Object Storage, they can be accessed from any Backend, which are totally stateless as well as the other servers. All sessions of the same user are directed to the same Backend by Dovecot Director to prevent data corruption. As the user session reaches the Dovecot Backend the user’s indexes are loaded from object storage to local cache of the Backend. As the session is over, the indexes are loaded back to object storage. In the unlucky event of Backend failure the next Backend can continue where the other Backend left off since there are no locking problems (in comparison to NFS) and the indexes can be merged and updated by Dovecot Backend as soon as the servers are back on-line.		If mails are stored to Object Storage, they can be accessed from any Backend, which are totally stateless as well as the other servers. All sessions of the same user are directed to the same Backend by Dovecot Director to prevent data corruption. As the user session reaches the Dovecot Backend the user’s indexes are loaded from object storage to local cache of the Backend. As the session is over, the indexes are loaded back to object storage. In the unlucky event of Backend failure the next Backend can continue where the other Backend left off since there are no locking problems (in comparison to NFS) and the indexes can be merged and updated by Dovecot Backend as soon as the servers are back on-line.

	NFS storage is also supported, but this does not require Dovecot Object Storage plug-in~~. More about how to setup NFS storage can be found from section Object Storage Cluster setup~~.		NFS storage is also supported, but this does not require Dovecot Object Storage plug-in.

	'''Object Storage Advantages'''		'''Object Storage Advantages'''

	~~Dovecot Object Storage usage~~ is optimized for cloud technologies~~. The Dovecot Object Storage Plugin enables your Dovecot email service to store the~~ email data into ~~cost efficient~~ cloud storage ~~solution~~.		The obox plugin is optimized for cloud technologies by enabling long-term email data storage into cloud storage solutions.
	~~Object storage~~ plugin ~~keeps track of~~ which ~~users' and mailboxes'~~ index files have been ~~opened~~ locally and uploads / downloads them to object storage as necessary.		The obox plugin tracks which index files have been altered or are needed locally and uploads / downloads them to object storage only as necessary. This usage pattern most efficiently leverages the object storage paradigm, as opposed to a more traditional black storage strategy.
	~~Object Storage is using~~ the ~~same Dovecot index files~~, ~~which are already proven~~ to ~~be stable and efficient~~. The ~~object storage~~ plugin consists of three major components:		The obox plugin consists of three major components. The first component is a sdbox-like mailbox format. Each message is stored in its own “file” (a discrete object)I. Indexes are bundled into separate discrete objects stored in objects storage. The second component is a collection of drivers, that implement support for various object storages, such as Amazon S3 and Scality sproxyd. There is additionally a "fscache" driver that implements a local filesystem cache for mail objects. The third component is metadata storage for index files and and other metadata, such as Sieve scripts. It synchronizes these files between a local cache and the object storage.

	*The ~~actual obox plugin, which implements an~~ sdbox-like mailbox format~~, which is accessed via the lib-fs API (instead of POSIX filesystem API)~~. ~~Each~~ message is stored in its own ~~file~~ (object). ~~The index files~~ are ~~still accessed using the POSIX FS API~~.

	*lib-fs Backends that implement support for various object storages, such as Amazon S3~~, Windows Azure~~ and ~~Dropbox~~. ~~There~~ is ~~also~~ a "fscache" ~~Backend~~ that implements local filesystem cache for mail objects.

	*metacache processes, which implement synchronizing Dovecot index files (and other metadata ~~files~~, ~~like~~ Sieve scripts) between ~~the~~ local ~~filesystem~~ and object storage.

	=='''Dovecot Full Text Search'''==		=='''Dovecot Full Text Search'''==

Kmujunen: /* Dovecot Object Storage */

2016-04-13T07:20:59Z

Dovecot Object Storage

← Older revision		Revision as of 07:20, 13 April 2016
Line 58:		Line 58:
	If mails are stored to Object Storage, they can be accessed from any Backend, which are totally stateless as well as the other servers. All sessions of the same user are directed to the same Backend by Dovecot Director to prevent data corruption. As the user session reaches the Dovecot Backend the user’s indexes are loaded from object storage to local cache of the Backend. As the session is over, the indexes are loaded back to object storage. In the unlucky event of Backend failure the next Backend can continue where the other Backend left off since there are no locking problems (in comparison to NFS) and the indexes can be merged and updated by Dovecot Backend as soon as the servers are back on-line.		If mails are stored to Object Storage, they can be accessed from any Backend, which are totally stateless as well as the other servers. All sessions of the same user are directed to the same Backend by Dovecot Director to prevent data corruption. As the user session reaches the Dovecot Backend the user’s indexes are loaded from object storage to local cache of the Backend. As the session is over, the indexes are loaded back to object storage. In the unlucky event of Backend failure the next Backend can continue where the other Backend left off since there are no locking problems (in comparison to NFS) and the indexes can be merged and updated by Dovecot Backend as soon as the servers are back on-line.

	NFS storage is also supported, but this does not require Dovecot Object Storage plug-in. More about how to setup NFS storage can be found from section ~~8.4~~ Object Storage Cluster setup.		NFS storage is also supported, but this does not require Dovecot Object Storage plug-in. More about how to setup NFS storage can be found from section Object Storage Cluster setup.

	'''Object Storage Advantages'''		'''Object Storage Advantages'''

Kmujunen: /* Dovecot Migration Framework */

2016-03-17T12:54:24Z

Dovecot Migration Framework

← Older revision		Revision as of 12:54, 17 March 2016
Line 127:		Line 127:
	Emails stored in the archive namespace can be encrypted using the “mail-crypt” plugin. Encryption will be done using Elliptic Curve Cryptography.		Emails stored in the archive namespace can be encrypted using the “mail-crypt” plugin. Encryption will be done using Elliptic Curve Cryptography.

	= Dovecot Migration Framework =		=='''Dovecot Migration Framework'''==

	'''Overview'''		'''Overview'''

Kmujunen: /* Dovecot Pro Vault */

2016-03-17T12:54:07Z

Dovecot Pro Vault

← Older revision		Revision as of 12:54, 17 March 2016
Line 105:		Line 105:
	http://wiki.dovecot.org/Tools/Doveadm/SearchQuery		http://wiki.dovecot.org/Tools/Doveadm/SearchQuery

	= Dovecot Pro Vault =		=='''Dovecot Pro Vault'''==

	'''Overview'''		'''Overview'''

Kmujunen: /* =Dovecot Full Text Search */

2016-03-17T12:53:44Z

=Dovecot Full Text Search

← Older revision		Revision as of 12:53, 17 March 2016
Line 72:		Line 72:
	*metacache processes, which implement synchronizing Dovecot index files (and other metadata files, like Sieve scripts) between the local filesystem and object storage.		*metacache processes, which implement synchronizing Dovecot index files (and other metadata files, like Sieve scripts) between the local filesystem and object storage.

	=='''Dovecot Full Text Search'''=		=='''Dovecot Full Text Search'''==

	'''Overview'''		'''Overview'''

Kmujunen: /* Dovecot Full Text Search */

2016-03-17T12:53:34Z

Dovecot Full Text Search

← Older revision		Revision as of 12:53, 17 March 2016
Line 72:		Line 72:
	*metacache processes, which implement synchronizing Dovecot index files (and other metadata files, like Sieve scripts) between the local filesystem and object storage.		*metacache processes, which implement synchronizing Dovecot index files (and other metadata files, like Sieve scripts) between the local filesystem and object storage.

	= Dovecot Full Text Search =		=='''Dovecot Full Text Search'''=

	'''Overview'''		'''Overview'''

Kmujunen: /* 'Dovecot Object Storage */

2016-03-17T12:53:05Z

'Dovecot Object Storage

← Older revision		Revision as of 12:53, 17 March 2016
Line 50:		Line 50:
	As an user is connecting to Dovecot for reading the mails the user’s mail indexes are fetched from the mail storage. The mail indexes are updated as long as the session is valid. This makes fetching of the user’s mail perform fast. As the session validity expires or the user logs off, the updated index is stored back to storage waiting for the next login. Dovecot Backends are stateless, making it possible for user connections to be connected to any Backend.		As an user is connecting to Dovecot for reading the mails the user’s mail indexes are fetched from the mail storage. The mail indexes are updated as long as the session is valid. This makes fetching of the user’s mail perform fast. As the session validity expires or the user logs off, the updated index is stored back to storage waiting for the next login. Dovecot Backends are stateless, making it possible for user connections to be connected to any Backend.

	=='''Dovecot Object Storage''==		=='''Dovecot Object Storage'''==

	'''Overview'''		'''Overview'''

Kmujunen: /* Dovecot Object Storage */

2016-03-17T12:52:51Z

Dovecot Object Storage

← Older revision		Revision as of 12:52, 17 March 2016
Line 50:		Line 50:
	As an user is connecting to Dovecot for reading the mails the user’s mail indexes are fetched from the mail storage. The mail indexes are updated as long as the session is valid. This makes fetching of the user’s mail perform fast. As the session validity expires or the user logs off, the updated index is stored back to storage waiting for the next login. Dovecot Backends are stateless, making it possible for user connections to be connected to any Backend.		As an user is connecting to Dovecot for reading the mails the user’s mail indexes are fetched from the mail storage. The mail indexes are updated as long as the session is valid. This makes fetching of the user’s mail perform fast. As the session validity expires or the user logs off, the updated index is stored back to storage waiting for the next login. Dovecot Backends are stateless, making it possible for user connections to be connected to any Backend.

	= Dovecot Object Storage =		=='''Dovecot Object Storage''==

	'''Overview'''		'''Overview'''

Kmujunen: /* Dovecot Pro Mai */

2016-03-17T12:51:51Z

Dovecot Pro Mai

← Older revision		Revision as of 12:51, 17 March 2016
Line 20:		Line 20:
	*Dovecot Migration Framework		*Dovecot Migration Framework

	='''Dovecot Pro ~~Mai~~'''=		=='''Dovecot Pro Mail'''==

	'''Overview'''		'''Overview'''

Kmujunen: /* Dovecot Pro Mail */

2016-03-17T12:51:36Z

Dovecot Pro Mail

← Older revision		Revision as of 12:51, 17 March 2016
Line 20:		Line 20:
	*Dovecot Migration Framework		*Dovecot Migration Framework

	= Dovecot Pro ~~Mail~~ =		='''Dovecot Pro Mai'''=

	'''Overview'''		'''Overview'''