MailStore Gateway Help - User contributions [en]

Firewall Configuration

2022-03-22T16:33:16Z

Bmeyn:

__NOTOC__
It is highly recommended to protect any MailStore Gateway with appropriate firewall rules. This document should help with setting up the required rules.

'''Please note: '''On Windows, the installation process automatically creates an appropriate firewall rule. Therefore the below information is only applicable if other firewall solutions are used.

If MailStore Gateway computer is on a private network, refer to the manual of the router or firewall that connects the private network to the Internet to find out how to set up appropriate port forwarding rules in addition to the firewall rules described in this document.

The table below lists all TCP ports that need to be opened in the firewall when using MailStore Gateway. The following abbreviations are used in the source and target columns of that table:

* ANY = Any computer from private or public networks
* ADM = Computer or network used for administration
* GTW = Computer that hosts MailStore Gateway

{| class="wikitable sortable"
! width="80px" | Port
! width="80px" | Source
! width="80px" | Target
! class="unsortable"| Description
|-
| align="center" | 25
| align="center" | GTW
| align="center" | ANY
| Access to email servers via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 25
| align="center" | ANY
| align="center" | GTW
| Access from email servers to send emails to MailStore Gateway mailboxes. Access from email clients via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 80
| align="center" | ANY
| align="center" | GTW
| Access from Let's Encrypt for challenge requests. Required for the Let's Encrypt functionality.
|-
| align="center" | 110
| align="center" | GTW
| align="center" | ANY
| Access to email servers via POP3 needed by the POP3 proxy functionality.
|-
| align="center" | 110
| align="center" | ANY
| align="center" | GTW
| Access from email clients via POP3 needed by the POP3 proxy functionality.
|-
| align="center" | 8450
| align="center" | ADM
| align="center" | GTW
| Access to the Management Console by administrators.
|-
| align="center" | 465
| align="center" | GTW
| align="center" | ANY
| Access to email servers via SMTPS needed by the SMTP proxy functionality.
|-
| align="center" | 465
| align="center" | ANY
| align="center" | GTW
| Access from email clients via SMTPS needed by the SMTP proxy functionality.
|-
| align="center" | 587
| align="center" | GTW
| align="center" | ANY
| Access to email servers via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 587
| align="center" | ANY
| align="center" | GTW
| Access from email clients via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 995
| align="center" | GTW
| align="center" | ANY
|Access to email servers via POP3S needed by the POP3 proxy functionality.
|-
| align="center" | 995
| align="center" | ANY
| align="center" | GTW
|Access from email clients via POP3S needed by the POP3 proxy functionality.
|-
| align="center" | 995
| align="center" | MailStore
| align="center" | GTW
|Access from MailStore Server or MailStore Service Provider Edition to retrieve emails from MailStore Gateway mailboxes.
|}

[[de:Firewall-Konfiguration]]
[[en:Firewall Configuration]]

Using Let's Encrypt Certificates

2022-03-22T15:47:47Z

Bmeyn: /* About Let's Encrypt */

== About Let's Encrypt ==
Let's Encrypt is a free, automated, and open certificate authority, trusted by all major web browsers and operating systems. Many large, well known sponsors from the IT industry support Let's Encrypt's effort to help making the internet a safer place.

A fully automated certificate approval process eliminates email or phone verification of traditional certificate authorities that often take days.

Let's Encrypt certificates are only valid for 90 days and thus need to be renewed regularly. The MailStore Gateway service handles the automatic renewals once the initial configuration is done.

== Prerequisites ==
For the MailStore Gateway computer, a public DNS record (A or CNAME) must exist and point to a public IP address.
The MailStore Gateway computer must be accessible from the Internet on TCP port 80 (HTTP) for Let's Encrypt's automatic domain approval process. A port forwarding on your firewall or gateway might be necessary. Since Let's Encrypt validates from different IP addresses, such a firewall rule cannot be limited to certain source IP addresses.

== Scenario 1: MailStore Gateway on Local Area Network (LAN) ==
The most common scenario for a MailStore Gateway installation is on a local network inside the organization's premises. Typically, the MailStore Gateway computer has a private IP address (e.g. 192.168.0.10) and the Internet connection is established through a router which masks all internal IP addresses with its own external IP address assigned by the ISP. This is known as Network Address Translation (NAT).

For this scenario, we assume that MailStore Gateway is running on a new, dedicated computer.

# Ask your Internet access provider to assign a static, public IP address to the router.
# Assign an available static IP Address from your local network to the MailStore Gateway computer.
# Create a port forwarding rule on the router, that forwards all connections to TCP port 80 on the public IP address, which was assigned in step 1, to the internal IP address of your MailStore Gateway computer assigned in step 2. '''Note:''' In the MailStore Gateway Configuration, you can change the Let's Encrypt HTTP-01 Challenge Port on which the MailStore Gateway service listens on the internal IP address assigned in step 2. However, on the public IP address assigned to the router in step 1, TCP port 80 must be used because Let's Encrypt's certificate approval process only supports this HTTP standard TCP port. If you change Let's Encrypt HTTP-01 Challenge Port, you must update the port forwarding rule created in step 3 accordingly.
# Add an A or CNAME record to the DNS zone of your public domain, e.g. mailstore.example.com pointing to the public IP address that was assigned in step 1.
# Depending on how DNS resolution is handled in your local network, you need to add a corresponding DNS record on your internal DNS server or router as well. This record should point to the internal IP address of the MailStore Gateway computer.

== Scenario 2: MailStore Gateway on External Network ==
If the MailStore Gateway computer is already on a network that uses public IP addresses, e.g. in a data center or a DMZ, it is much easier to fulfill the prerequisites.

For this scenario, we assume that MailStore Gateway is running on a new, dedicated computer.

# Assign an available public IP Address from your public network to the MailStore Gateway computer.
# If there is a firewall in place, create a firewall rule which allows all connections to TCP port 80 on the public IP address to pass through. '''Note:''' In the MailStore Gateway Configuration, you can change the Let's Encrypt HTTP-01 Challenge Port on which the MailStore Gateway service listens on the public IP address assigned in step 1. However, in the scenario described here, TCP port 80 must be used because Let's Encrypt's certificate approval process only supports this HTTP standard TCP port.
# Add an A or CNAME record to the DNS zone of your public domain, e.g. mailstore.example.com pointing to the public IP address that was assigned in step 1.

== Obtaining the Certificate ==
The MailStore Gateway tests the settings against Let's Encrypt's staging environment. If an issue occurs, MailStore Gateway will show a warning. Please review the log output, resolve the issue and try again.
If the test was successful, the MailStore Gateway will automatically request a certificate from Let's Encrypt's production system and confirm that setup was successful.
The automatic renewal of Let's Encrypt certificates every 60 days is active as long as no other certificate is selected manually.

[[de:Verwendung von Let's Encrypt Zertifikaten]]
[[en:Using Let's Encrypt Certificates]]

Using Let's Encrypt Certificates

2022-03-22T15:47:14Z

Bmeyn: /* Obtaining the Certificate */

== About Let's Encrypt ==
Let's Encrypt is a free, automated, and open certificate authority, trusted by all major web browsers and operating systems. Many large, well known sponsors from the IT industry support Let's Encrypt's effort to help making the internet a safer place.

A fully automated certificate approval process eliminates email or phone verification of traditional certificate authorities that often take days.

Let's Encrypt certificates are only valid for 90 days and thus need to be renewed regularly. The MailStore Server service handles the automatic renewals once the initial configuration is done.

== Prerequisites ==
For the MailStore Gateway computer, a public DNS record (A or CNAME) must exist and point to a public IP address.
The MailStore Gateway computer must be accessible from the Internet on TCP port 80 (HTTP) for Let's Encrypt's automatic domain approval process. A port forwarding on your firewall or gateway might be necessary. Since Let's Encrypt validates from different IP addresses, such a firewall rule cannot be limited to certain source IP addresses.

== Scenario 1: MailStore Gateway on Local Area Network (LAN) ==
The most common scenario for a MailStore Gateway installation is on a local network inside the organization's premises. Typically, the MailStore Gateway computer has a private IP address (e.g. 192.168.0.10) and the Internet connection is established through a router which masks all internal IP addresses with its own external IP address assigned by the ISP. This is known as Network Address Translation (NAT).

For this scenario, we assume that MailStore Gateway is running on a new, dedicated computer.

# Ask your Internet access provider to assign a static, public IP address to the router.
# Assign an available static IP Address from your local network to the MailStore Gateway computer.
# Create a port forwarding rule on the router, that forwards all connections to TCP port 80 on the public IP address, which was assigned in step 1, to the internal IP address of your MailStore Gateway computer assigned in step 2. '''Note:''' In the MailStore Gateway Configuration, you can change the Let's Encrypt HTTP-01 Challenge Port on which the MailStore Gateway service listens on the internal IP address assigned in step 2. However, on the public IP address assigned to the router in step 1, TCP port 80 must be used because Let's Encrypt's certificate approval process only supports this HTTP standard TCP port. If you change Let's Encrypt HTTP-01 Challenge Port, you must update the port forwarding rule created in step 3 accordingly.
# Add an A or CNAME record to the DNS zone of your public domain, e.g. mailstore.example.com pointing to the public IP address that was assigned in step 1.
# Depending on how DNS resolution is handled in your local network, you need to add a corresponding DNS record on your internal DNS server or router as well. This record should point to the internal IP address of the MailStore Gateway computer.

== Scenario 2: MailStore Gateway on External Network ==
If the MailStore Gateway computer is already on a network that uses public IP addresses, e.g. in a data center or a DMZ, it is much easier to fulfill the prerequisites.

For this scenario, we assume that MailStore Gateway is running on a new, dedicated computer.

# Assign an available public IP Address from your public network to the MailStore Gateway computer.
# If there is a firewall in place, create a firewall rule which allows all connections to TCP port 80 on the public IP address to pass through. '''Note:''' In the MailStore Gateway Configuration, you can change the Let's Encrypt HTTP-01 Challenge Port on which the MailStore Gateway service listens on the public IP address assigned in step 1. However, in the scenario described here, TCP port 80 must be used because Let's Encrypt's certificate approval process only supports this HTTP standard TCP port.
# Add an A or CNAME record to the DNS zone of your public domain, e.g. mailstore.example.com pointing to the public IP address that was assigned in step 1.

== Obtaining the Certificate ==
The MailStore Gateway tests the settings against Let's Encrypt's staging environment. If an issue occurs, MailStore Gateway will show a warning. Please review the log output, resolve the issue and try again.
If the test was successful, the MailStore Gateway will automatically request a certificate from Let's Encrypt's production system and confirm that setup was successful.
The automatic renewal of Let's Encrypt certificates every 60 days is active as long as no other certificate is selected manually.

[[de:Verwendung von Let's Encrypt Zertifikaten]]
[[en:Using Let's Encrypt Certificates]]

Using Let's Encrypt Certificates

2022-03-22T15:46:18Z

Bmeyn: /* Scenario 2: MailStore Gateway on External Network */

== About Let's Encrypt ==
Let's Encrypt is a free, automated, and open certificate authority, trusted by all major web browsers and operating systems. Many large, well known sponsors from the IT industry support Let's Encrypt's effort to help making the internet a safer place.

A fully automated certificate approval process eliminates email or phone verification of traditional certificate authorities that often take days.

Let's Encrypt certificates are only valid for 90 days and thus need to be renewed regularly. The MailStore Server service handles the automatic renewals once the initial configuration is done.

== Prerequisites ==
For the MailStore Gateway computer, a public DNS record (A or CNAME) must exist and point to a public IP address.
The MailStore Gateway computer must be accessible from the Internet on TCP port 80 (HTTP) for Let's Encrypt's automatic domain approval process. A port forwarding on your firewall or gateway might be necessary. Since Let's Encrypt validates from different IP addresses, such a firewall rule cannot be limited to certain source IP addresses.

== Scenario 1: MailStore Gateway on Local Area Network (LAN) ==
The most common scenario for a MailStore Gateway installation is on a local network inside the organization's premises. Typically, the MailStore Gateway computer has a private IP address (e.g. 192.168.0.10) and the Internet connection is established through a router which masks all internal IP addresses with its own external IP address assigned by the ISP. This is known as Network Address Translation (NAT).

For this scenario, we assume that MailStore Gateway is running on a new, dedicated computer.

# Ask your Internet access provider to assign a static, public IP address to the router.
# Assign an available static IP Address from your local network to the MailStore Gateway computer.
# Create a port forwarding rule on the router, that forwards all connections to TCP port 80 on the public IP address, which was assigned in step 1, to the internal IP address of your MailStore Gateway computer assigned in step 2. '''Note:''' In the MailStore Gateway Configuration, you can change the Let's Encrypt HTTP-01 Challenge Port on which the MailStore Gateway service listens on the internal IP address assigned in step 2. However, on the public IP address assigned to the router in step 1, TCP port 80 must be used because Let's Encrypt's certificate approval process only supports this HTTP standard TCP port. If you change Let's Encrypt HTTP-01 Challenge Port, you must update the port forwarding rule created in step 3 accordingly.
# Add an A or CNAME record to the DNS zone of your public domain, e.g. mailstore.example.com pointing to the public IP address that was assigned in step 1.
# Depending on how DNS resolution is handled in your local network, you need to add a corresponding DNS record on your internal DNS server or router as well. This record should point to the internal IP address of the MailStore Gateway computer.

== Scenario 2: MailStore Gateway on External Network ==
If the MailStore Gateway computer is already on a network that uses public IP addresses, e.g. in a data center or a DMZ, it is much easier to fulfill the prerequisites.

For this scenario, we assume that MailStore Gateway is running on a new, dedicated computer.

# Assign an available public IP Address from your public network to the MailStore Gateway computer.
# If there is a firewall in place, create a firewall rule which allows all connections to TCP port 80 on the public IP address to pass through. '''Note:''' In the MailStore Gateway Configuration, you can change the Let's Encrypt HTTP-01 Challenge Port on which the MailStore Gateway service listens on the public IP address assigned in step 1. However, in the scenario described here, TCP port 80 must be used because Let's Encrypt's certificate approval process only supports this HTTP standard TCP port.
# Add an A or CNAME record to the DNS zone of your public domain, e.g. mailstore.example.com pointing to the public IP address that was assigned in step 1.

== Obtaining the Certificate ==
The MailStore Gateway tests the settings against Let's Encrypt's staging environment. If an issue occurs, the Gateway will show a warning. Please review the log output, resolve the issue and try again.
If the test was successful, the MailStore Gateway will automatically request a certificate from Let's Encrypt's production system and confirm that setup was successful.
The automatic renewal of Let's Encrypt certificates every 60 days is active as long as no other certificate is selected manually.

[[de:Verwendung von Let's Encrypt Zertifikaten]]
[[en:Using Let's Encrypt Certificates]]

System Requirements

2022-03-22T13:58:54Z

Bmeyn: /* Web Browsers */

__NOTOC__
Before beginning the installation of MailStore Gateway, all system requirements must be met.

== Hardware Requirements ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
=== Operating System ===
MailStore Gateway is supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
The TCP SMTP ports 25, 465 and 587, the TCP POP3 ports 110 and 995, and the TCP HTTPS port 8450 must not be used by any other program, such as an email server.

=== Web Browsers ===
The following web browsers in their respective current version are supported by the Management Console:
* Microsoft Edge (based on Chromium)
* Google Chrome
* Mozilla Firefox

=== Other Software ===
The following other software is required:
* [https://dotnet.microsoft.com/en-us/download/dotnet/6.0 Microsoft .NET 6 Runtime]
[[de:Systemanforderungen]]
[[en:System Requirements]]

System Requirements

2022-03-22T13:53:41Z

Bmeyn:

__NOTOC__
Before beginning the installation of MailStore Gateway, all system requirements must be met.

== Hardware Requirements ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
=== Operating System ===
MailStore Gateway is supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
The TCP SMTP ports 25, 465 and 587, the TCP POP3 ports 110 and 995, and the TCP HTTPS port 8450 must not be used by any other program, such as an email server.

=== Web Browsers ===
The following web browsers are supported by the Management Console:
* Microsoft Edge (based on Chromium)
* Google Chrome
* Mozilla Firefox

=== Other Software ===
The following other software is required:
* [https://dotnet.microsoft.com/en-us/download/dotnet/6.0 Microsoft .NET 6 Runtime]
[[de:Systemanforderungen]]
[[en:System Requirements]]

System Requirements

2022-03-22T13:52:20Z

Bmeyn: /* Operating System */

__NOTOC__
Before beginning the installation of MailStore Gateway all system requirements must be met.

== Hardware Requirements ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
=== Operating System ===
MailStore Gateway is supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
The TCP SMTP ports 25, 465 and 587, the TCP POP3 ports 110 and 995, and the TCP HTTPS port 8450 must not be used by any other program, such as an email server.

=== Web Browsers ===
The following web browsers are supported by the Management Console:
* Microsoft Edge (based on Chromium)
* Google Chrome
* Mozilla Firefox

=== Other Software ===
The following other software is required:
* [https://dotnet.microsoft.com/en-us/download/dotnet/6.0 Microsoft .NET 6 Runtime]
[[de:Systemanforderungen]]
[[en:System Requirements]]

System Requirements

2022-03-22T13:51:41Z

Bmeyn: /* Operating System */

__NOTOC__
Before beginning the installation of MailStore Gateway all system requirements must be met.

== Hardware Requirements ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
=== Operating System ===
MailStore Gateway will be supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
The TCP SMTP ports 25, 465 and 587, the TCP POP3 ports 110 and 995, and the TCP HTTPS port 8450 must not be used by any other program, such as an email server.

=== Web Browsers ===
The following web browsers are supported by the Management Console:
* Microsoft Edge (based on Chromium)
* Google Chrome
* Mozilla Firefox

=== Other Software ===
The following other software is required:
* [https://dotnet.microsoft.com/en-us/download/dotnet/6.0 Microsoft .NET 6 Runtime]
[[de:Systemanforderungen]]
[[en:System Requirements]]

System Requirements

2022-03-22T13:51:13Z

Bmeyn: /* Software Requirements */

__NOTOC__
Before beginning the installation of MailStore Gateway all system requirements must be met.

== Hardware Requirements ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
=== Operating System ===
MailStore Gateway will be supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Small Business Server 2011 SP1
* Microsoft Windows Server 2008 R2 SP1 (Foundation, Standard, Enterprise, Datacenter)
The TCP SMTP ports 25, 465 and 587, the TCP POP3 ports 110 and 995, and the TCP HTTPS port 8450 must not be used by any other program, such as an email server.

=== Web Browsers ===
The following web browsers are supported by the Management Console:
* Microsoft Edge (based on Chromium)
* Google Chrome
* Mozilla Firefox

=== Other Software ===
The following other software is required:
* [https://dotnet.microsoft.com/en-us/download/dotnet/6.0 Microsoft .NET 6 Runtime]
[[de:Systemanforderungen]]
[[en:System Requirements]]

Monitoring

2019-03-08T16:23:06Z

Bmeyn:

Monitoring the MailStore Gateway can be done on various levels. While monitoring the underlying infrastructure, which typically includes network components, hardware usage or the status of security updates, is a common task for administrators, setting up further monitoring checks for the MailStore Gateway is recommended to ensure permanent service availability for end users.

This article provides generic information about what should be monitored to help administrators setting up additional checks in their monitoring solution.

{| class="wikitable"
| width="150px" | '''Network Ports'''
| TCP 25 (SMTP) TCP 110 (POP3) TCP 465 (SMTPS) TCP 587 (SMTP) TCP 995 (POP3S) TCP 8450 (HTTPS)
|-
| '''TLS Certificate Lifetime'''
| TCP 25 (SMTP) TCP 110 (POP3) TCP 465 (SMTPS) TCP 587 (SMTP) TCP 995 (POP3S) TCP 8450 (HTTPS)
|-
| '''Windows Service'''
| MailStoreGateway
|}

[[de:Überwachung]]
[[en:Monitoring]]

Backup and Restore

2019-03-08T16:13:38Z

Bmeyn:

Although emails typically reside in MailStore Gateway mailboxes only for a short period of time, it is highly recommended to protect the content of these mailboxes as well as the configuration files by implementing a decent backup plan.

If not the whole computer is backed up anyway, the following path should at least be included in the backup set of you backup solution:

%PROGRAMDATA%\MailStore\Gateway

As no files are kept open while the MailStore Gateway service is running, stopping the service prior to creating the backup is not necessary.

[[de:Datensicherung und Wiederherstellung]]
[[en:Backup and Restore]]

Management Console

2019-03-08T16:10:11Z

Bmeyn:

__NOTOC__

The MailStore Gateway Management Console is the primary tool for administrators to manage MailStore Gateway, and mailboxes in particular.

[[File:MailStore_Gateway_Management_Console.png|center|550px]]

== Create Mailbox ==
* [[Login]] to the Management Console.
* Click on ''Create Mailbox''.
* Type a name in the ''Name'' field, i.e. ''Office 365 Journal''.
* ''Optional: '' Enter a description that helps to identify the purpose of the mailbox, e.g. ''Target for journal emails from Office 365 domain example.com''.
* Click ''OK''.
* A strong, random password is generated and displayed.
*: [[File:MailStore_Gateway_Create_Mailbox.png|center|350px]]
* Carefully read the warning, and afterwards tick the checkbox ''I've read and understood the above warning''.
* Click ''OK'' to finish the mailbox creation. 
*; '''Important notice:''' Make sure to store the password in a safe place as it is not stored in MailStore Gateway. The password is needed to decrypt the content of the mailbox. If the password is lost, there is no way to access emails that are still in the mailbox ever again; a lost password cannot be retrieved. For MailStore Server customers we recommend to use an enterprise password manager to store such critical passwords. For MSPs using MailStore Service Provider Edition we do not recommend to store these passwords but instead ensure that when providing them to end customers, add a note about the importance of keeping the password safe.

== Edit Mailbox ==
* [[Login]] to the Management Console.
* Select a mailbox from the table.
* Click ''Edit Mailbox''.
*: [[File:MailStore_Gateway_Edit_Mailbox.png|center|350px]]
* The following mailbox properties can be changed:
** '''Name''' The name of the mailbox, e.g. G Suite Archiving.
** '''Description''' The description helps to identify the purpose of the mailbox e.g. ''Destination for G Suite Archiving''.
** '''Status''' The status can have the following values:
*** ''Active'' Active mailboxes accept new messages, which can be archived.
*** ''Suspended'' Suspended mailboxes do not accept new messages but archiving from them is still possible. Typically this is needed when a mailbox is to be deleted, but still contains unarchived emails. A temporary error is thrown if an attempt is made to deliver an email to a suspended mailbox.
* Click ''OK'' to confirm the changes, or ''Cancel'' to abort.

== Delete Mailbox ==
To delete a mailbox, it must meet the following prerequisites:

* The mailbox must be empty.
* Its status must be set to ''Suspended''.

If these prerequisites are met, a mailbox can be deleted by the following procedure:

* [[Login]] to the Management Console.
* Select a mailbox from the table.
* Click ''Delete Mailbox''.
*: [[File:MailStore_Gateway_Delete_Mailbox.png|center|350px]]
* Click ''Yes'' to confirm deleting the mailbox, or ''No'' to abort the deletion.

== Reset Mailbox Password ==
To reset a mailbox password, the mailbox must meet the following prerequisites:

* The mailbox must be empty.
* Its status must be set to ''Suspended''.

If these prerequisites are met, a mailbox password can be reset by the following procedure:

* [[Login]] to the Management Console.
* Select a mailbox from the table.
* Click ''Reset Password''.
*: [[File:MailStore_Gateway_Reset_Mailbox_Password.png|center|350px]]
* Click ''Yes'' to confirm resetting the mailbox password, or ''No'' to abort the password reset.
* After clicking ''Yes'', a new password is generated and displayed.
* Proceed as detailed in the above section [[#Create Mailbox|Create Mailbox]].

== Change Language ==
* [[Login]] to the Management Console.
* Click on the username in the upper right corner.
* Select ''Settings''.
* Select the intended language from the ''Language'' drop-down. The console is updated immediately when selecting an other language.
* Click ''OK'' to close the settings.

== Reset Own Password ==
* [[Login]] to the Management Console.
* Click on the username in the upper right corner.
* Select ''Settings''.
* Click on the ''Reset own password'' link next to the ''Password'' label.
* Type in your current password to confirm the password change.
* A new, random password is displayed. Make sure to keep it in a safe place.
* Click ''OK'' to save changes.

== Sign Out ==
* Click on the username in the upper right corner.
* Select ''Sign out''.

[[de:Management Console]]
[[en:Management Console]]

Management Console

2019-03-08T15:46:21Z

Bmeyn:

__NOTOC__

The MailStore Gateway Management Console is the primary tool for administrators to manage MailStore Gateway, and mailboxes in particular.

[[File:MailStore_Gateway_Management_Console.png|center|550px]]

== Create Mailbox ==
* [[Login]] to the Management Console.
* Click on ''Create Mailbox''
* Type a name in the ''Name'' field, i.e. ''Office 365 Journal''
* ''Optional: '' Enter a description that helps to identify the purpose of the mailbox, e.g. ''Target for journal emails from Office 365 domain example.com''
* Click ''OK''
* A strong, random password is generated and displayed.
*: [[File:MailStore_Gateway_Create_Mailbox.png|center|350px]]
* Carefully read the warning, and afterwards tick the checkbox ''I've read and understood the above warning''.
* Click ''OK'' to finish the mailbox creation. 
*; '''Important notice:''' Make sure to store the password in a safe place as it is not stored in MailStore Gateway. The password is needed to decrypt the content of the mailbox. If the password is lost, there is no way to access emails that are still in the mailbox ever again; a lost password cannot be retrieved. For MailStore Server customers we recommend to use an enterprise password manager to store such critical passwords. For MSPs using MailStore Service Provider Edition we do not recommend to store these passwords but instead ensure that when providing them to end customers, add a note about the importance of keeping the password safe.

== Edit Mailbox ==
* [[Login]] to the Management Console.
* Select a mailbox from the table.
* Click ''Edit Mailbox''.
*: [[File:MailStore_Gateway_Edit_Mailbox.png|center|350px]]
* The following mailbox properties can be changed:
** '''Name''' The name of the mailbox, e.g. G Suite Archiving
** '''Description''' The description helps to identify the purpose of the mailbox e.g. ''Destination for G Suite Archiving''
** '''Status''' The status can have the following values:
*** ''Active'' Active mailboxes accept new messages, which can be archived.
*** ''Suspended'' Suspended mailboxes do not accept new messages but archiving from them is still possible. Typically this is needed when a mailbox is to be deleted, but still contains unarchived emails. A temporary error is thrown if an attempt is made to deliver an email to a suspended mailbox.
* Click ''OK'' to confirm the changes, or ''Cancel'' to abort.

== Delete Mailbox ==
To delete a mailbox, it must meet the following prerequisites:

* The mailbox must be empty.
* Its status must be set to ''Suspended''.

If these prerequisites are met, a mailbox can be deleted by the following procedure:

* [[Login]] to the Management Console.
* Select a mailbox from the table.
* Click ''Delete Mailbox''.
*: [[File:MailStore_Gateway_Delete_Mailbox.png|center|350px]]
* Click ''Yes'' to confirm deleting the mailbox, or ''No'' to abort the deletion.

== Reset Mailbox Password ==
To reset a mailbox password, the mailbox must meet the following prerequisites:

* The mailbox must be empty.
* Its status must be set to ''Suspended''.

If these prerequisites are met, a mailbox password can be reset by the following procedure:

* [[Login]] to the Management Console.
* Select a mailbox from the table.
* Click ''Reset Password''.
*: [[File:MailStore_Gateway_Reset_Mailbox_Password.png|center|350px]]
* Click ''Yes'' to confirm resetting the mailbox password, or ''No'' to abort the password reset.
* After clicking ''Yes'', a new password is generated and displayed.
* Proceed as detailed in the above section [[#Create Mailbox|Create Mailbox]].

== Change Language ==
* [[Login]] to the Management Console.
* Click on the username in the upper right corner.
* Select ''Settings''.
* Select the intended language from the ''Language'' drop-down. The console is updated immediately when selecting an other language.
* Click ''OK'' to close the settings.

== Reset Own Password ==
* [[Login]] to the Management Console.
* Click on the username in the upper right corner.
* Select ''Settings''.
* Click on the ''Reset own password'' link next to the ''Password'' label.
* Type in your current password to confirm the password change.
* A new, random password is displayed. Make sure to keep it in a safe place.
* Click ''OK'' to save changes.

== Sign Out ==
* Click on the username in the upper right corner.
* Select ''Sign out''.

[[de:Management Console]]
[[en:Management Console]]

Configuration Tool

2019-03-08T13:02:34Z

Bmeyn:

__NOTOC__
[[File:MailStore_Gateway_Configuration.png|right|300px]]

With the MailStore Gateway Configuration tool administrators can configure basic settings of the MailStore Gateway service.

The tool is started automatically during the initial installation process; it can be started manually through the corresponding desktop icon or start menu link.

{{clear}}

== E-Mail Domain ==
This value specifies the domain part of each MailStore Gateway mailbox email address (i.e. ''<mailbox-id>@'''<e-mail domain>'' ''').

If MailStore Gateway should receive emails from other email servers (e.g. Microsoft Office 365, Google G Suite, etc.), the configured e-mail domain must be resolvable through DNS.

'''Example: ''' If the primary domain is ''example.com'' and MailStore Gateway should receive emails, a DNS record like ''msgw.example.com'' needs to be created in the DNS zone ''example.com''. The record must point to a public IP address on which MailStore Gateway is reachable. In MailStore Gateway the value of ''E-Mail Domain'' would be set to <tt>msgw.example.com</tt>.
If MailStore Gateway is located behind a NAT router or firewall, additional configuration may be needed. Refer to [[Firewall Configuration]] for further details.

== Certificate ==
MailStore Gateway uses TLS certificates to establish encrypted communication channels with clients and other servers.

Administrators can choose from the following options which certificate MailStore Gateway should use:

* '''Select from Certificate Store''' A certificate can be selected from the Windows certificate store. Please note that the ''Personal'' certificate store of the computer account is used, not the store of the current Windows user.
* '''Create Self-Signed Certificate''' A new self-signed certificate can be created and is automatically selected afterwards. Please note that self-signed certificates are neither trusted by other clients, which may lead to warnings on client computers, nor other servers. Therefore, self-signed certificates are suitable for testing purposes only and should be replaced once a system is used in a productions environment.
* '''Import from File''' With this option certificates can be imported from ''Private Information Exchange (*.p12;*.pfx)'' files. The configuration tool will automatically import the certificates into the correct Windows certificate store. Since Private Information Exchange files are password protected, a password must be entered to start the import process.

== Log Level ==
The ''Log Level'' defines how much information MailStore Gateway logs into its log files. The default settings is ''Information'' which should not be changed unless troubleshooting is required.

== Apply Configuration Changes ==
After the configuration of MailStore Gateway has been changed, the changes must be written to the configuration file by clicking on ''Apply''. Otherwise the changed settings will not be used when starting the MailStore Gateway service.

== Starting the MailStore Gateway Service ==
By clicking the ''Start Service'' button, the MailStore Gateway service will be started. Changes to the configuration must be applied first, otherwise a warning is issued. This button is only available if the service is currently stopped.

== Stopping the MailStore Gateway Service ==
By clicking the ''Stop Service'' button, the MailStore Gateway service will be stopped. Changes to the configuration can only be made while the service is stopped. This button is only available if the service is currently running.

[[de:Konfigurationswerkzeug]]
[[en:Configuration Tool]]

Overview

2019-03-08T12:58:04Z

Bmeyn:

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 for two distinct scenarios:

# Serving as journal or archiving target for other email servers that themselves create copies of sent and received emails.
# Serving as SMTP and POP3 proxy that creates and stores copies of all emails that are exchanged between email clients and email servers.

Both scenarios are explained more detailed in the following sections.

== 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.

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.

This chart gives a good overview of the whole setup.

[[File:MailStore_Gateway_Overview_Server.png|550px|center]]

The typical workflow to set up this scenario looks as follows:

# 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 a MailStore Gateway mailbox as target.
# 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.
# 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 ==
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, MailStore Gateway can record the communication between the email client and the email server, effectively operating as an email proxy.

This chart gives a good overview of the whole setup.

[[File:MailStore_Gateway_Overview_Proxy.png|550px|center]]

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 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
#* ''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)
#* ''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.
# Repeat step 2 for all email clients where the users' emails should be archived.
# 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 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. The remote server for proxied connections must support implicit (SMTPS, POP3S) or explicit (SMTP+STARTTLS, POP3+STARTTLS) encryption.

[[de:Übersicht]]
[[en:Overview]]

Login

2019-03-08T12:50:44Z

Bmeyn:

To log on to the MailStore Gateway Management Console follow these instructions:

* Open a [[System_Requirements|supported web browser]].
* Navigate to <tt><nowiki>https://<hostname-or-ip-address-of-mailstore-gateway-server>:8450</nowiki></tt>.
* Accept possible certificate warnings from your web browser when using a self-signed certificate.
*: [[File:MailStore_Gateway_Login.png|center|450px]]
* In the ''User Name'' field enter ''admin''.
* In the ''Password'' field enter the corresponding password of the admin user. For the first time login, the password is ''admin''. After the first login, a random, secure password is created automatically.
* Click ''Sign in'' to proceed.

[[de:Anmelden]]
[[en:Login]]

Login

2019-03-08T12:47:23Z

Bmeyn:

Firewall Configuration

2019-03-08T12:24:47Z

Bmeyn:

__NOTOC__
It is highly recommended to protect any MailStore Gateway with appropriate firewall rules. This document should help with setting up the required rules.

'''Please note: '''On Windows, the installation process automatically creates an appropriate firewall rule. Therefore the below information is only applicable if other firewall solutions are used.

If MailStore Gateway computer is on a private network, refer to the manual of the router or firewall that connects the private network to the Internet to find out how to set up appropriate port forwarding rules in addition to the firewall rules described in this document.

The table below lists all TCP ports that need to be opened in the firewall when using MailStore Gateway. The following abbreviations are used in the source and target columns of that table:

* ANY = Any computer from private or public networks
* ADM = Computer or network used for administration
* GTW = Computer that hosts MailStore Gateway

{| class="wikitable sortable"
! width="80px" | Port
! width="80px" | Source
! width="80px" | Target
! class="unsortable"| Description
|-
| align="center" | 25
| align="center" | GTW
| align="center" | ANY
| Access to email servers via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 25
| align="center" | ANY
| align="center" | GTW
| Access from email servers to send emails to MailStore Gateway mailboxes. Access from email clients via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 110
| align="center" | GTW
| align="center" | ANY
| Access to email servers via POP3 needed by the POP3 proxy functionality.
|-
| align="center" | 110
| align="center" | ANY
| align="center" | GTW
| Access from email clients via POP3 needed by the POP3 proxy functionality. Access from MailStore Server or MailStore Service Provider Edition to retrieve emails from MailStore Gateway mailboxes.
|-
| align="center" | 8450
| align="center" | ADM
| align="center" | GTW
| Access to the Management Console by administrators.
|-
| align="center" | 465
| align="center" | GTW
| align="center" | ANY
| Access to email servers via SMTPS needed by the SMTP proxy functionality.
|-
| align="center" | 465
| align="center" | ANY
| align="center" | GTW
| Access from email clients via SMTPS needed by the SMTP proxy functionality.
|-
| align="center" | 587
| align="center" | GTW
| align="center" | ANY
| Access to email servers via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 587
| align="center" | ANY
| align="center" | GTW
| Access from email clients via SMTP needed by the SMTP proxy functionality.
|-
| align="center" | 995
| align="center" | GTW
| align="center" | ANY
|Access to email servers via POP3S needed by the POP3 proxy functionality.
|-
| align="center" | 995
| align="center" | ANY
| align="center" | GTW
|Access from email clients via POP3S needed by the POP3 proxy functionality.
|}

[[de:Firewall-Konfiguration]]
[[en:Firewall Configuration]]

Configuration Tool

2019-03-07T14:53:04Z

Bmeyn:

Privacy policy

2019-03-07T14:10:53Z

Bmeyn: Bmeyn moved page MailStore Gateway Help:Privacy policy to Privacy policy without leaving a redirect

Click [https://www.mailstore.com/en/imprint/legal-privacy-policy/ here] for privacy policy on our official website.

MediaWiki:Privacypage

2019-03-07T14:10:07Z

Bmeyn: Created page with "Privacy policy"

Trademarks

2019-03-07T14:01:06Z

Bmeyn: Created page with "Click [https://www.mailstore.com/en/imprint/legal-trademarks/ here] for trademark information on our official website."

Click [https://www.mailstore.com/en/imprint/legal-trademarks/ here] for trademark information on our official website.

Privacy policy

2019-03-07T14:00:01Z

Bmeyn: Created page with "Click [https://www.mailstore.com/en/imprint/legal-privacy-policy/ here] for privacy policy on our official website."

Click [https://www.mailstore.com/en/imprint/legal-privacy-policy/ here] for privacy policy on our official website.

Imprint

2019-03-07T13:59:03Z

Bmeyn: Created page with "Click [https://www.mailstore.com/en/imprint/ here] for imprint on our official website."

Click [https://www.mailstore.com/en/imprint/ here] for imprint on our official website.

System Requirements

2019-03-07T11:12:46Z

Bmeyn:

__NOTOC__
Before beginning the installation of MailStore Gateway all system requirements must be met.

== Hardware Requirements ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
MailStore Gateway will be supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Small Business Server 2011 SP1
* Microsoft Windows Server 2008 R2 SP1 (Foundation, Standard, Enterprise, Datacenter)

The following web browsers are supported by the Management Console:
* Microsoft Edge
* Microsoft Internet Explorer 10 or higher
* Google Chrome
* Mozilla Firefox

[[de:Systemanforderungen]]
[[en:System Requirements]]

System Requirements

2019-03-07T11:06:42Z

Bmeyn:

__NOTOC__
Before beginning the installation of MailStore Gateway all system requirements must be met.

== Hardware ==
{| class="wikitable" width="100%"
! width="150" scope="row" | '''Processor'''
| Any x64 compatible CPU
|-
! width="150" scope="row" | '''Main Memory'''
| 512 MB
|-
! width="150" scope="row" | '''Hard Disk'''
| 150 MB available disk space + enough disk space to store expected email volume.
|-
! width="150" scope="row" | '''Network Bandwidth'''
| 100 MBit/s
|}

== Software Requirements ==
MailStore Gateway will be supported on the following operating systems:
* Microsoft Windows 10 (1607 or higher)
* Microsoft Windows 8.1
* Microsoft Windows 7 SP1
* Microsoft Windows Server 2019 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2016 (Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 R2 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Server 2012 (Foundation, Essentials, Standard, Datacenter)
* Microsoft Windows Small Business Server 2011 SP1
* Microsoft Windows Server 2008 R2 SP1 (Foundation, Standard, Enterprise, Datacenter)

The following web browsers are supported by the Management Console:
* Microsoft Edge
* Microsoft Internet Explorer 10 or higher
* Google Chrome
* Mozilla Firefox

[[de:Systemanforderungen]]
[[en:System Requirements]]

Overview

2019-03-07T10:51:28Z

Bmeyn:

Overview

2019-02-26T16:35:17Z

Bmeyn:

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 for two distinct scenarios:

# Serving as journal or archiving target for other email servers that themselves create copies of sent and received emails.
# Serving as SMTP and POP3 proxy that creates and stores copies of all emails that are exchanged between email clients and email servers.

Both scenarios are explained more detailed in the following sections.

== 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.

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.

This chart gives a good overview of the whole setup.

[[File:MailStore_Gateway_Overview_Server.png|550px|center]]

The typical workflow to set up this scenario looks as follows:

# 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 a MailStore Gateway mailbox as target.
# 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.
# 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 ==
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, MailStore Gateway can record the communication between the email client and the email server, effectively operating as an email proxy.

This chart gives a good overview of the whole setup.

[[File:MailStore_Gateway_Overview_Proxy.png|550px|center]]

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 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
#* ''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)
#* ''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.
# Repeat step 2 in all email clients where the user's 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.

== 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).

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.

Main Page

2019-02-26T10:34:22Z

Bmeyn:

__NOTOC__
{{DISPLAYTITLE:MailStore Gateway Help}}

MailStore Gateway is a free, complementary tool for MailStore's email archiving solutions MailStore Server and MailStore Service Provider Edition.

It provides SMTP and POP3 proxy functionality, as well as simple mail server functionality to receive and store emails from Microsoft Office 365, Google G Suite or other email servers that are capable of sending emails to external archiving solutions via SMTP.

The following provides a walk-though of the essential steps to get the MailStore Gateway up and running, as well as some background information.

== Before You Start ==
{|
| style="vertical-align: top; width: 200px" | [[Overview]]
| Learn more about the scenarios in which MailStore Gateway is the right solution for common challenges.
|-
| [[System Requirements]]
| Before installing MailStore Gateway, ensure that the system requirements are met.
|}

== Installation and Setup ==
{|
| style="vertical-align: top; width: 200px" | [[Installing MailStore Gateway|Installation]]
| Irrespective of the projected scenario, it all begins with the installation of the software itself.
|-
| [[Configuration Tool|Basic Configuration]]
| After successful installation, some basic configuration settings should be reviewed and adjusted where needed.
|-
| [[Firewall Configuration|Firewall Configuration]]
| To access MailStore Gateway from remote systems, appropriate firewall rules may have to be set up.
|}

== Using MailStore Gateway ==
{|
| style="vertical-align: top; width: 200px" | [[Login|Logging On]]
| Learn how to login to MailStore Gateway's Management Console.
|-
| [[Management Console|Create and Manage Mailboxes]]
| MailStore Gateway mailboxes contain the emails that are to be archived by MailStore Server or MailStore Service Provider Edition.
|}

== Post Installation Tasks ==
{|
| style="vertical-align: top; width: 200px" | [[Backup and Restore]]
| Although emails typically reside in MailStore Gateway mailboxes for a quite short period of time, it is highly recommended to protect the content of the mailboxes from hardware or software failure by implementing a decent backup plan.
|-
| [[Monitoring]]
| This article gives an overview of what services and parameters to proactively monitor with a suitable monitoring solution to always provide users the best possible experience.
|}

[[de:Hauptseite]]
[[en:Main_Page]]