Project

General

Profile

EmailConfiguration » History » Version 52

Go MAEDA, 2018-01-15 14:17
Slightly updated explanation of "async_smtp_settings"

1 1 Cyber Sprocket
h1. Email Configuration
2
3 7 Mischa The Evil
{{>toc}}
4
5 31 Miodrag Milic
6 1 Cyber Sprocket
h2. Configuration Directives
7
8 34 Anonymous
This page is a work in progress, the following configuration directives are only a partial list. Please consult "Action Mailer Configuration":http://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration
9
for detailed information.
10 1 Cyber Sprocket
11
h3. authentication
12
13
The type of authentication method expected by your service provider. 
14
15
Valid settings:
16 34 Anonymous
* @nil@ (or omit the key) for no authentication
17
* @:plain@
18
* @:login@
19
* @:cram_md5@
20 1 Cyber Sprocket
21 34 Anonymous
(note: if you set this to @nil@ or omit it, you must not include the @user_name@ and @password@ settings)
22 1 Cyber Sprocket
23
h3. delivery_method
24
25 6 Eric Davis
The mail transport method to be used.
26 1 Cyber Sprocket
27
Valid settings:
28 34 Anonymous
* @:smtp@
29
* :@sendmail@
30
* @:async_smtp@
31
* @:async_sendmail@
32 1 Cyber Sprocket
33 6 Eric Davis
h4. Asynchronous delivery_methods
34
35 52 Go MAEDA
The @:async_smtp@ and @:async_sendmail@ use asynchronous sends, which means Redmine does not wait for the email to be sent to display the next page.  See "Asynchronous Email Delivery":http://redmineblog.com/articles/asynchronous-email-delivery/ for more details. Some SMTP servers have delay period before processing takes place as an anti-spam feature, during which time synchronous method will block Redmine ("10 seconds":https://community.bitnami.com/t/updating-an-issue-in-redmine-takes-10-seconds/4421 could be a default value, see also #11376 for more information).
36 1 Cyber Sprocket
37 52 Go MAEDA
With this delivery method, smtp configuration is specified using @async_smtp_settings@ keyword instead of @smtp_settings@ keyword:
38 23 Miodrag Milic
39 47 Toshi MARUYAMA
<pre><code class="yml">
40 23 Miodrag Milic
development:
41 1 Cyber Sprocket
  email_delivery:
42
    delivery_method: :async_smtp
43 52 Go MAEDA
    async_smtp_settings:  # Don't use "smtp_settings"
44
      address: ...
45
      port: ...
46
      ...
47 47 Toshi MARUYAMA
</code></pre>
48 23 Miodrag Milic
49 11 Etienne Massip
h2. Example configuration.yml Configurations
50 1 Cyber Sprocket
51
h3. Simple Login Authentication (default settings)
52
53 47 Toshi MARUYAMA
<pre><code class="yml">
54 1 Cyber Sprocket
# Outgoing email settings
55
56
production:
57 12 Ross Wilson
  email_delivery:
58
    delivery_method: :smtp
59
    smtp_settings:
60
      address: smtp.example.net
61
      port: 25
62
      domain: example.net
63
      authentication: :login
64
      user_name: redmine@example.net
65
      password: redmine
66 1 Cyber Sprocket
  
67
development:
68 12 Ross Wilson
  email_delivery:
69
    delivery_method: :smtp
70
    smtp_settings:
71
      address: 127.0.0.1
72
      port: 25
73
      domain: example.net
74
      authentication: :login
75
      user_name: redmine@example.net
76
      password: redmine
77 47 Toshi MARUYAMA
</code></pre>
78 1 Cyber Sprocket
79 44 Holger Just
h3. GMail, Google Apps
80 1 Cyber Sprocket
81 44 Holger Just
If you want to use GMail/Google Apps and other TLS-requiring SMTP servers, you'll have to add some TLS-related settings:
82 8 Joël Lamotte
83 47 Toshi MARUYAMA
<pre><code class="yml">
84 8 Joël Lamotte
production:
85 12 Ross Wilson
  email_delivery:
86
    delivery_method: :smtp
87
    smtp_settings:
88
      enable_starttls_auto: true
89
      address: "smtp.gmail.com" 
90 51 Go MAEDA
      port: 587
91 12 Ross Wilson
      domain: "smtp.gmail.com" 
92
      authentication: :plain
93 1 Cyber Sprocket
      user_name: "your_email@gmail.com" 
94
      password: "your_password" 
95 47 Toshi MARUYAMA
</code></pre>
96 44 Holger Just
97 45 Maxim Krušina
When sending from G Suite (formerly Google Apps), it's good to use *SMTP relay* which has much larger sending limits.
98
More information and detailed guide how to enable SMTP relay is here: https://support.google.com/a/answer/2956491
99 46 Maxim Krušina
When configuring SMTP relay service use something like this:
100
* Name: Redmine
101
* 1. Allowed senders:
102
** Only registered Apps users in my domains - in case You have created dedicated G Suite user for Redmine
103
* 2. Authentication
104
** [x] Only accept mail from the specified IP addresses - IP address of your Redmine server
105
** [x] Require SMTP Authentication
106
* 3. Encryption
107
** [x] Require TLS encryption
108
109 45 Maxim Krušina
And config can be really simple:
110
111 47 Toshi MARUYAMA
<pre><code class="yml">
112 45 Maxim Krušina
production:
113
  email_delivery:
114
    delivery_method: :smtp
115
    smtp_settings:
116
      address: smtp-relay.gmail.com
117
      port: 587
118
      domain: smtp-relay.gmail.com
119
      authentication: :plain
120
      user_name: your_email@gmail.com
121
      password: your_password
122 47 Toshi MARUYAMA
</code></pre>
123 45 Maxim Krušina
124 44 Holger Just
h3. Office 365, Exchange Online
125 8 Joël Lamotte
126 41 Pierre Maigne
Here is an example for Office 365 users (Exchange online). The sender must have an account, or if you want to send from a shared mailbox, the account below must have authorization to "Send As" the sender which is defined in Redmine email notifications settings.
127
128 47 Toshi MARUYAMA
<pre><code class="yml">
129 41 Pierre Maigne
production:
130
  email_delivery:
131
    delivery_method: :smtp
132
    smtp_settings:
133
      enable_starttls_auto: true
134
      address: "smtp.office365.com"
135 51 Go MAEDA
      port: 587
136 41 Pierre Maigne
      domain: "your_domain.com"
137
      authentication: :login
138
      user_name: "email@your_domain.com"
139
      password: "password"
140 47 Toshi MARUYAMA
</code></pre>
141 41 Pierre Maigne
142 8 Joël Lamotte
143 1 Cyber Sprocket
h3. No Authentication
144
145 34 Anonymous
Example for an SMTP service provider with no authentication.
146 1 Cyber Sprocket
147 47 Toshi MARUYAMA
<pre><code class="yml">
148 13 Ross Wilson
production:
149
  email_delivery:
150
    delivery_method: :smtp
151
    smtp_settings:
152
      address: smtp.knology.net
153
      port: 25
154
      domain: cybersprocket.com
155 47 Toshi MARUYAMA
</code></pre>
156 1 Cyber Sprocket
157
h3. Using sendmail command
158 5 Eric Davis
159
Example for a unix system that uses the @/usr/sbin/sendmail@ command.
160
161 47 Toshi MARUYAMA
<pre><code class="yml">
162 5 Eric Davis
production:
163 13 Ross Wilson
  email_delivery:
164
    delivery_method: :sendmail
165 47 Toshi MARUYAMA
</code></pre>
166 1 Cyber Sprocket
167 35 Jean-Baptiste Barth
h2. Troubleshooting
168
169
h3. Error: "hostname was not match with the server certificate"
170
171
If you get this error, there's probably a problem verifying the SSL certificate of your smtp relay. As a temporary fix, you can set this option in the appropriate "email_delivery" section:
172
173 48 Toshi MARUYAMA
<pre><code class="yml">
174 35 Jean-Baptiste Barth
    enable_starttls_auto: false
175 48 Toshi MARUYAMA
</code></pre>
176 35 Jean-Baptiste Barth
177 36 Richard Gomes
h3. Error: "Mail failure - no recipient addresses"
178
179
When this error happens, the notification is not delivered to the destination address. Instead, you will probably receive a rejection message on your sender address, where you can see the header of the message sent, containing "From:" fields but not containing any "To:" fields.
180
181 39 Richard Gomes
This error is common on *Debian* boxes, due to the way _exim4_ is configured by default, which is @"-i -t"@. This configuration tells _exim4_ that the destination address is inside the header of the message. Instead, we need to configure _exim4_ so that the destination address will be retrieved from the command line.
182 36 Richard Gomes
183 37 Richard Gomes
The solution consists on editing your _config/configuration.yml_ and making sure you define @arguments@ containing the string @"-i"@, as shown below:
184 36 Richard Gomes
185 47 Toshi MARUYAMA
<pre><code class="yml">
186 36 Richard Gomes
# default configuration options for all environments
187
default:
188
  email_delivery:    
189
    delivery_method: :sendmail
190
    sendmail_settings:
191
      arguments: "-i" 
192 47 Toshi MARUYAMA
</code></pre>
193 36 Richard Gomes
194 40 Richard Gomes
The example above employs @:sendmail@ method, which employs @sendmail_settings@. In case you are using @:smtp@ or @:async_smtp@ methods, try @smtp_settings@ instead.
195 38 Richard Gomes
196 43 hongbo yang
h3. Error: "Timeout:Error" due to SSL SMTP server connection
197
198 1 Cyber Sprocket
add an ssl option to the configuration.yml #17239
199 43 hongbo yang
200 47 Toshi MARUYAMA
<pre><code class="yml">
201 42 hongbo yang
default:
202
  # Outgoing emails configuration (see examples above)
203
  email_delivery:
204
    delivery_method: :smtp
205
  smtp_settings:
206
    address: smtp.domain.com
207
    port: 465
208
    ssl: true
209
    enable_starttls_auto: true
210
    domain: domain.com
211
    authentication: :login
212
    user_name: redmine@domain.com
213
    password: xxxx
214 47 Toshi MARUYAMA
</code></pre>
215 42 hongbo yang
216 7 Mischa The Evil
h2. More information
217 5 Eric Davis
218
* "Action Mailer Configuration":http://guides.rubyonrails.org/action_mailer_basics.html#action-mailer-configuration