Overview - Revision history

Dweuthen at 14:32, 16 July 2020

2020-07-16T14:32:23Z

Dweuthen at 13:49, 29 June 2020

2020-06-29T13:49:13Z

Dweuthen at 07:20, 10 April 2019

2019-04-10T07:20:55Z

Dweuthen at 13:01, 19 March 2019

2019-03-19T13:01:37Z

Bmeyn at 12:58, 8 March 2019

2019-03-08T12:58:04Z

Bmeyn at 10:51, 7 March 2019

2019-03-07T10:51:28Z

Bmeyn at 16:35, 26 February 2019

2019-02-26T16:35:17Z

Dweuthen at 11:23, 6 February 2019

2019-02-06T11:23:20Z

Dweuthen: /* MailStore Gateway as Server */

2019-02-06T11:23:00Z

MailStore Gateway as Server

Dweuthen: /* MailStore Gateway as Proxy */

2019-02-06T11:22:44Z

MailStore Gateway as Proxy

@@ Line 10: / Line 10: @@
 == MailStore Gateway as Server ==
-Many email servers allow the creation of copies of all in- and outbound emails for the purpose of archiving. While on-premises email servers generally allow to deliver these copies into local mailboxes, most cloud based services (e.g. Microsoft Office 365, Google G Suite) do not, neither technically nor license-wise, and thus require external mailboxes to be used as a journal or archiving mailboxes. For those services, third-party archiving solutions, such as MailStore Server and MailStore Service Provider Edition, must either pull the emails from those external mailboxes, or, to circumvent that, be able to receive emails via SMTP directly.
+Many email servers allow the creation of copies of all in- and outbound emails for the purpose of archiving. While on-premises email servers generally allow to deliver these copies into local mailboxes, most cloud based services (e.g. Microsoft 365, Google G Suite) do not, neither technically nor license-wise, and thus require external mailboxes to be used as a journal or archiving mailboxes. For those services, third-party archiving solutions, such as MailStore Server and MailStore Service Provider Edition, must either pull the emails from those external mailboxes, or, to circumvent that, be able to receive emails via SMTP directly.
 As direct SMTP archiving is generally preferred over using yet another third-party mailbox provider, MailStore Gateway provides this functionality for MailStore Server and MailStore Service Provider Edition without changing their basic concept of pull-only archiving.

@@ Line 37: / Line 37: @@
 # A MailStore Gateway [[Management Console#Create Mailbox|mailboxes is created]]. Each MailStore Gateway mailbox has a unique identifier.
-# On the email client, the in- (POP3) and outbound (SMTP) server must be replaced by the MailStore Gateway's IP address or host name. Additionally, the user name needs to be modified to '''remote_username%target_server%mailbox_id''' where
+# On the email client, the in- (POP3) and outbound (SMTP) server must be replaced by the MailStore Gateway's host name. Additionally, the user name needs to be modified to '''remote_username%target_server%mailbox_id''' where
 #* ''remote_username'' is the user name (e.g. jdoe@example.com) to login to a mailbox on ''target_server''
-#* ''target_server'' is the IP address or host name of the original email server (e.g. mail.example.com)
+#* ''target_server'' is the host name of the original email server (e.g. mail.example.com). It also needs to match the common name of the TLS/SSL certificate used by the original email server to ensure full confidentiality.
 #* ''mailbox_id'' is the unique identifier of the MailStore Gateway mailbox into which copies of the sent or received emails are to be stored.
 # Afterwards copies of all sent and received emails on that particular client are stored in the given MailStore Gateway mailbox. MailStore Gateway encrypts all stored emails with a key unique to the mailbox.

← Older revision		Revision as of 07:20, 10 April 2019
Line 1:		Line 1:
−	~~__NOINDEX__~~
	This article gives an high level overview of the basic concepts behind MailStore Gateway. It should help to understand in which scenarios to use MailStore Gateway in combination with MailStore Server or MailStore Service Provider Edition. Further instructions can be found in the corresponding articles of this help or the help of MailStore Server and MailStore Service Provider Edition.		This article gives an high level overview of the basic concepts behind MailStore Gateway. It should help to understand in which scenarios to use MailStore Gateway in combination with MailStore Server or MailStore Service Provider Edition. Further instructions can be found in the corresponding articles of this help or the help of MailStore Server and MailStore Service Provider Edition.

← Older revision		Revision as of 13:01, 19 March 2019
Line 1:		Line 1:
		+	__NOINDEX__
	This article gives an high level overview of the basic concepts behind MailStore Gateway. It should help to understand in which scenarios to use MailStore Gateway in combination with MailStore Server or MailStore Service Provider Edition. Further instructions can be found in the corresponding articles of this help or the help of MailStore Server and MailStore Service Provider Edition.		This article gives an high level overview of the basic concepts behind MailStore Gateway. It should help to understand in which scenarios to use MailStore Gateway in combination with MailStore Server or MailStore Service Provider Edition. Further instructions can be found in the corresponding articles of this help or the help of MailStore Server and MailStore Service Provider Edition.

← Older revision		Revision as of 12:58, 8 March 2019
Line 49:		Line 49:

	Additionally, MailStore Gateway does not allow usernames or passwords to be transferred over an unencrypted connection. The remote server for proxied connections must support implicit (SMTPS, POP3S) or explicit (SMTP+STARTTLS, POP3+STARTTLS) encryption.		Additionally, MailStore Gateway does not allow usernames or passwords to be transferred over an unencrypted connection. The remote server for proxied connections must support implicit (SMTPS, POP3S) or explicit (SMTP+STARTTLS, POP3+STARTTLS) encryption.
		+
		+	[[de:Übersicht]]
		+	[[en:Overview]]

@@ Line 41: / Line 41: @@
 #* ''target_server'' is the IP address or host name of the original email server (e.g. mail.example.com)
 #* ''mailbox_id'' is the unique identifier of the MailStore Gateway mailbox into which copies of the sent or received emails are to be stored.
-# Once such changes have been made, copies of all send and received emails on that particular client are stored in the given MailStore Gateway mailbox. MailStore Gateway encrypts all stored emails with a key unique to the mailbox.
+# Afterwards copies of all sent and received emails on that particular client are stored in the given MailStore Gateway mailbox. MailStore Gateway encrypts all stored emails with a key unique to the mailbox.
-# Repeat step 2 in all email clients where the user's emails should be archived.
+# Repeat step 2 for all email clients where the users' emails should be archived.
-# In the last step, MailStore Server and MailStore Service Provider Edition  will archive the messages from MailStore Gateway mailboxes via the corresponding email archiving profile.
+# MailStore Server or MailStore Service Provider Edition will then archive those emails from MailStore Gateway mailboxes via the corresponding archiving profile.
 == Security ==
-All emails stored in the MailStore Gateway mailboxes are protected by strong hybrid encryption. The mailbox passwords represent the passphrase for the private key of the asymmetric part of the hybrid encryption. This means that without the correct mailbox password, no data can ever be decrypted. Therefore it is highly recommended to keep the password in a safe place (i.e. enterprise password manager).
+All emails stored in MailStore Gateway mailboxes are protected by strong hybrid encryption. The mailbox passwords represent the passphrase for the private keys of the asymmetric part of the hybrid encryption. This means that without the correct mailbox password, no data can ever be decrypted. Therefore it is highly recommended to keep the password in a safe place (i.e. enterprise password manager).
-Additionally, MailStore Gateway does not allow usernames or passwords to be transferred over an unencrypted connection, requiring that the remote server for proxies connection must support implicit (SMTPS, POP3S) or explicit (SMTP+STARTTLS, POP3+STARTTLS) encryption.
+Additionally, MailStore Gateway does not allow usernames or passwords to be transferred over an unencrypted connection. The remote server for proxied connections must support implicit (SMTPS, POP3S) or explicit (SMTP+STARTTLS, POP3+STARTTLS) encryption.

@@ Line 1: / Line 1: @@
-This article gives an high level overview of the basic concepts behind MailStore Gateway and should help to understand in which scenarios it can be beneficial to use MailStore Gateway in combination with MailStore Server or MailStore Gateway. In-depth instructions can be found in the corresponding articles of this help, or the help of MailStore Server and MailStore Service Provider Edition.
+This article gives an high level overview of the basic concepts behind MailStore Gateway. It should help to understand in which scenarios to use MailStore Gateway in combination with MailStore Server or MailStore Service Provider Edition. Further instructions can be found in the corresponding articles of this help or the help of MailStore Server and MailStore Service Provider Edition.
-MailStore Gateway has been designed primarily to serve two distinct purposes, which are:
+MailStore Gateway has been designed primarily for two distinct scenarios:
-# Being a journal or archiving target for other email servers, that themselves create copies of sent and received emails.
+# Serving as journal or archiving target for other email servers that themselves create copies of sent and received emails.
-# Being a SMTP and POP3 proxy that creates and stores copies of all emails, exchanged between email clients and email servers.
+# Serving as SMTP and POP3 proxy that creates and stores copies of all emails that are exchanged between email clients and email servers.
@@ Line 10: / Line 10: @@
 == MailStore Gateway as Server ==
-Many email servers allow the creation of copies of all in- and outbound emails for the purpose of archiving. While some allow to deliver these copies into local mailboxes, some others don't (e.g. Microsoft Office 365, Google G Suite). In the latter case, this means that third-party archiving solutions, such as MailStore Server and MailStore Service Provider Edition, must either pull these messages from other external mailboxes that have been used as a journal or archiving mailbox, or be able to receive emails directly via SMTP.
+Many email servers allow the creation of copies of all in- and outbound emails for the purpose of archiving. While on-premises email servers generally allow to deliver these copies into local mailboxes, most cloud based services (e.g. Microsoft Office 365, Google G Suite) do not, neither technically nor license-wise, and thus require external mailboxes to be used as a journal or archiving mailboxes. For those services, third-party archiving solutions, such as MailStore Server and MailStore Service Provider Edition, must either pull the emails from those external mailboxes, or, to circumvent that, be able to receive emails via SMTP directly.
-As direct SMTP archiving is generally preferred over using another third-party mailbox provider, but not supported by MailStore Server and MailStore Service Provider Edition, MailStore Gateway adds this functionality to these  products without changing their basic concept of pull-only archiving.
+As direct SMTP archiving is generally preferred over using yet another third-party mailbox provider, MailStore Gateway provides this functionality for MailStore Server and MailStore Service Provider Edition without changing their basic concept of pull-only archiving.
-Belows picture gives a good overview of how whole setup looks like.
+This chart gives a good overview of the whole setup.
 [[File:MailStore_Gateway_Overview_Server.png|550px|center]]
@@ Line 20: / Line 20: @@
 The typical workflow to set up this scenario looks as follows:
-# A MailStore Gateway [[Management Console#Create Mailbox|mailboxes is created]]. Each MailStore Gateway mailbox has its own, unique email address.
+# A MailStore Gateway [[Management Console#Create Mailbox|mailbox is created]]. Each MailStore Gateway mailbox has a unique email address.
-# On the email server, a new journal or archiving rule is created. This rule uses the email address of the previously created MailStore Gateway mailbox as target.
+# On the email server, a new journal or archiving rule is created. This rule uses the email address of a MailStore Gateway mailbox as target.
-# Once such a rule has been set up, copies of the messages to be archived are send to MailStore Gateway via SMTP. MailStore Gateway encrypts all email upon arrival with an encryption key unique to the mailbox.
+# Through the rule, copies of the emails to be archived are sent to MailStore Gateway via SMTP. Received emails are stored encrypted with an encryption key unique to each mailbox.
-# In the last step, MailStore Server and MailStore Service Provider Edition  will archive the messages from MailStore Gateway mailboxes via the corresponding email archiving profile.
+# MailStore Server or MailStore Service Provider Edition will then archive those emails from MailStore Gateway mailboxes via the corresponding archiving profile.
 == MailStore Gateway as Proxy ==
-Organisations without their own email server and without using an email service that allows to create journal or archiving rules as mentioned before, may use the combination of POP3/SMTP on their email client to receive and send emails.
+Organizations without their own email server and without using an email service that allows to create journal or archiving rules as described before, may use the combination of POP3/SMTP on their email clients to receive and send emails.
-To archive all in- and outbound emails in such a scenario, the communication between the email client and the email server must be recorded. This is what MailStore Gateway does when it is used as an email proxy.
+To archive all in- and outbound emails in such a scenario, MailStore Gateway can record the communication between the email client and the email server, effectively operating as an email proxy.
-Belows picture gives a good overview of how such a setup looks like.
+This chart gives a good overview of the whole setup.
 [[File:MailStore_Gateway_Overview_Proxy.png|550px|center]]
@@ Line 36: / Line 36: @@
 The typical workflow to set up this scenario looks as follows:
-# A MailStore Gateway [[Management Console#Create Mailbox|mailboxes is created]]. Each MailStore Gateway mailbox has its own unique identifier.
+# A MailStore Gateway [[Management Console#Create Mailbox|mailboxes is created]]. Each MailStore Gateway mailbox has a unique identifier.
-# On the email client, the in- (POP3) and outbound (SMTP) server must be replaced by the MailStore Gateway's IP address or host name. Additionally the username needs to be modified to '''remote_username%target_server%mailbox_id''' where
+# On the email client, the in- (POP3) and outbound (SMTP) server must be replaced by the MailStore Gateway's IP address or host name. Additionally, the user name needs to be modified to '''remote_username%target_server%mailbox_id''' where
-#* ''remote_username'' is the username (e.g. jdoe@google.com) to login to a mailbox on ''target_server''
+#* ''remote_username'' is the user name (e.g. jdoe@example.com) to login to a mailbox on ''target_server''
-#* ''target_server'' is the IP address or host name of the original email server (e.g. mail.google.com)
+#* ''target_server'' is the IP address or host name of the original email server (e.g. mail.example.com)
 #* ''mailbox_id'' is the unique identifier of the MailStore Gateway mailbox into which copies of the sent or received emails are to be stored.
 # Once such changes have been made, copies of all send and received emails on that particular client are stored in the given MailStore Gateway mailbox. MailStore Gateway encrypts all stored emails with a key unique to the mailbox.