1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
|
## SMTP Email Setup
In product evaluation setups with single-container Docker instances, email is intentionally disabled. This allows account creation and system operation without having to set up email, but it also means email notification and password reset functionality aren't available.
### How to enable email
To enable email, configure an SMTP email service as follows:
1. **Set up an SMTP email sending service** (if you don't yet have an SMTP service with credentials)
1. Any SMTP email service can be used, you just need the following information: `Server Name`, `Port`, `SMTP Username`, and `SMTP Password`.
2. If you don't have an SMTP service, here are simple instructions to set one up with [Amazon Simple Email Service (SES)](https://aws.amazon.com/ses/):
2. Go to [Amazon SES console](https://console.aws.amazon.com/ses) then `SMTP Settings > Create My SMTP Credentials`
3. Copy the `Server Name`, `Port`, `SMTP Username`, and `SMTP Password` for Step 2 below.
4. From the `Domains` menu set up and verify a new domain, then enable `Generate DKIM Settings` for the domain.
5. Choose an sender address like `mattermost@example.com` and click `Send a Test Email` to verify setup is working correctly.
2. **Configure SMTP settings**
1. Open the **System Console** by logging into an existing team and accessing "System Console" from the main menu.
1. Alternatively, if a team doesn't yet exist, go to `http://dockerhost:8065/` in your browser, create a team, then from the main menu click **System Console**
2. Go to the **Email Settings** tab and configure the following:
1. **Allow Sign Up With Email:** `true`
2. **Send Email Notifications:** `true`
3. **Require Email Verification:** `true`
4. **Notification Display Name:** Display name on email account sending notifications
5. **Notification Email Address:** Email address displayed on email account used to send notifications
6. **SMTP Username**: `SMTP Username` from Step 1
7. **SMTP Password**: `SMTP Password` from Step 1
8. **SMTP Server**: `SMTP Server` from Step 1
9. **SMTP Port**: `SMTP Port` from Step 1
10. **Connection Security**: `TLS (Recommended)`
11. Then click **Save**
12. Then click **Test Connection**
13. If the test failed please look in **OTHER** > **Logs** for any errors that look like `[EROR] /api/v1/admin/test_email ...`
### Known Good Sample Settings
##### Amazon SES
* Set **SMTP Username** to **AKIASKLDSKDIWEOWE**
* Set **SMTP Password** to **AdskfjAKLSDJShflsdfjkakldADkjkjdfKAJDSlkjweiqQIWEOU**
* Set **SMTP Server** to **email-smtp.us-east-1.amazonaws.com**
* Set **SMTP Port** to **465**
* Set **Connection Security** to **TLS**
##### Postfix
* Make sure Postfix is installed on the machine where Mattermost is installed
* Set **SMTP Username** to **(empty)**
* Set **SMTP Password** to **(empty)**
* Set **SMTP Server** to **localhost**
* Set **SMTP Port** to **25**
* Set **Connection Security** to **(empty)**
##### Gmail
* Information needed
##### Office 365
* Information needed
##### Hotmail
* Information needed
### Troubleshooting SMTP
#### Tip 1
If you fill in **SMTP Username** and **SMTP Password** then you must set **Connection Security** to **TLS** or to **STARTTLS**
#### Tip 2
If you have issues with your SMTP install, from your Mattermost team site go to the main menu and open **System Console -> Logs** to look for error messages related to your setup. You can do a search for the error code to narrow down the issue. Sometimes ISPs require nuanced setups for SMTP and error codes can hint at how to make the proper adjustments.
For example, if **System Console -> Logs** has an error code reading:
```
Connection unsuccessful: Failed to add to email address - 554 5.7.1 <unknown[IP-ADDRESS]>: Client host rejected: Access denied
```
Search for `554 5.7.1 error` and `Client host rejected: Access denied`.
#### Tip 3
* Attempt to telnet to the email service to make sure the server is reachable.
* You must run the following commands from the same machine or virtual instance where `mattermost/bin/platform` is located. So if you're running Mattermost from docker you need to `docker exec -ti mattermost-dev /bin/bash`
* Telnet to the email server with `telnet mail.example.com 25`. If the command works you should see something like
```
Trying 24.121.12.143...
Connected to mail.example.com.
220 mail.example.com NO UCE ESMTP
```
* Then type something like `HELO <your mail server domain>`. If the command works you should see something like
```
250-mail.example.com NO UCE
250-STARTTLS
250-PIPELINING
250 8BITMIME
```
|
