Project

General

Profile

RedmineReceivingEmails » History » Version 86

Go MAEDA, 2018-01-21 05:28
Added ".rb" extension in examples of rdm-mailhandler.rb

1 40 Etienne Massip
h1. Receiving emails
2 1 Jean-Philippe Lang
3 4 Jean-Philippe Lang
{{>toc}}
4
5 77 Go MAEDA
Redmine can be configured to allow issue creation or comments via email. It is also able to recognize and incorporate email replies to forum messages.
6 1 Jean-Philippe Lang
7 40 Etienne Massip
h2. Setup
8 1 Jean-Philippe Lang
9 40 Etienne Massip
You can configure Redmine to receive emails in one of the following ways:
10 7 Jean-Philippe Lang
11
* Forwarding emails from your email server:
12
13
  * Pros: works with a remote mail server, email are processed instantly, fast (no environment reloading)
14 10 Jean-Philippe Lang
  * Cons: needs some configuration on your mail transfer agent (eg. Postfix, Sendmail...)
15 7 Jean-Philippe Lang
16 29 Jean-Philippe Lang
* Fetching emails from an IMAP or POP3 server:
17 7 Jean-Philippe Lang
18
  * Pros: easy to setup, no need to configure your MTA, works with a remote mail server
19 9 Jean-Philippe Lang
  * Cons: emails are not processed instantly (a cron job needs to be added to read emails periodically)
20 7 Jean-Philippe Lang
21
* Reading emails from standard input:
22
23
  * Pros: fine for testing purpose
24
  * Cons: slow (the environment is reloaded each time an email is read), needs some configuration on your MTA
25 4 Jean-Philippe Lang
26
h3. Forwarding emails from your email server
27
28
A standalone script can be used to forward incoming emails from your mail server.
29 84 Go MAEDA
This script reads a raw email from the standard input and forwards it to Redmine via a HTTP request.
30 4 Jean-Philippe Lang
It can be found in your redmine directory: @extra/mail_handler/rdm-mailhandler.rb@.
31
32
In order to use it, you have to enable the API that receive emails:
33
Go to _Application settings_ -> _Incoming emails_, check *Enable WS for incoming emails* and enter or generate a secret key.
34
35 46 Jean-Philippe Lang
36
37
38
39
40
41
42
43 85 Go MAEDA
Copy @rdm-mailhandler.rb@ to your mail server, make sure its permissions allow execution (@chmod +x rdm-mailhandler.rb@), and configure your MTA (Mail Transport Agent).
44 4 Jean-Philippe Lang
45 5 Jean-Philippe Lang
Usage:
46 4 Jean-Philippe Lang
47 1 Jean-Philippe Lang
<pre>
48 78 Go MAEDA
Usage: rdm-mailhandler.rb [options] --url=<Redmine URL> --key=<API key>
49 1 Jean-Philippe Lang
50 82 Go MAEDA
Required arguments:
51
    -u, --url URL               URL of the Redmine server
52
    -k, --key KEY               Redmine API key
53
54
General options:
55
        --key-file FILE         full path to a file that contains your Redmine
56
                                API key (use this option instead of --key if
57
                                you don't want the key to appear in the command
58
                                line)
59
        --no-check-certificate  do not check server certificate
60
        --certificate-bundle FILE
61 78 Go MAEDA
                                certificate bundle to use
62 76 Jannik Lorenz
    -h, --help                  show this help
63
    -v, --verbose               show extra information
64
    -V, --version               show version information and exit
65 1 Jean-Philippe Lang
66 78 Go MAEDA
User and permissions options:
67 76 Jannik Lorenz
        --unknown-user ACTION   how to handle emails from an unknown user
68 1 Jean-Philippe Lang
                                ACTION can be one of the following values:
69
                                * ignore: email is ignored (default)
70 76 Jannik Lorenz
                                * accept: accept as anonymous user
71
                                * create: create a user account
72 1 Jean-Philippe Lang
        --no-permission-check   disable permission checking when receiving
73 78 Go MAEDA
                                the email
74
        --default-group GROUP   add created user to GROUP (none by default)
75 76 Jannik Lorenz
                                GROUP can be a comma separated list of groups
76
        --no-account-notice     don't send account information to the newly
77
                                created user
78
        --no-notification       disable email notifications for the created
79 1 Jean-Philippe Lang
                                user
80
81
Issue attributes control options:
82 76 Jannik Lorenz
        --project-from-subaddress ADDR
83 81 Go MAEDA
                                select project from subaddress of ADDR found
84 78 Go MAEDA
                                in To, Cc, Bcc headers
85 1 Jean-Philippe Lang
    -p, --project PROJECT       identifier of the target project
86
    -s, --status STATUS         name of the target status
87
    -t, --tracker TRACKER       name of the target tracker
88 76 Jannik Lorenz
        --category CATEGORY     name of the target category
89 1 Jean-Philippe Lang
        --priority PRIORITY     name of the target priority
90 78 Go MAEDA
        --assigned-to ASSIGNEE  assignee (username or group name)
91
        --fixed-version VERSION name of the target version
92
        --private               create new issues as private
93
    -o, --allow-override ATTRS  allow email content to set attributes values
94 76 Jannik Lorenz
                                ATTRS is a comma separated list of attributes
95 78 Go MAEDA
                                or 'all' to allow all attributes to be
96
                                overridable (see below for details)
97 6 Jean-Philippe Lang
</pre>
98 5 Jean-Philippe Lang
99
See [[RedmineReceivingEmails#Issue-attributes|Issue-attributes]] for a list of values that can be used for the @--allow-override@ option.
100
101
Examples:
102
103
<pre>
104
  # No project specified. Emails MUST contain the 'Project' keyword:
105 86 Go MAEDA
  rdm-mailhandler.rb --url http://redmine.domain.foo --key secret
106 5 Jean-Philippe Lang
  
107
  # Fixed project and default tracker specified, but emails can override
108
  # both tracker and priority attributes:
109 86 Go MAEDA
  rdm-mailhandler.rb --url https://domain.foo/redmine --key secret \\
110
                     --project foo \\
111
                     --tracker bug \\
112
                     --allow-override tracker,priority
113 1 Jean-Philippe Lang
</pre>
114 54 Art Kuo
115 55 Art Kuo
Here is an example for a Postfix local alias entry:
116 35 Justin Clarke
117
<pre>
118
foo: "|/path/to/rdm-mailhandler.rb --url http://redmine.domain --key secret --project foo"
119 36 Justin Clarke
</pre>
120 35 Justin Clarke
121 36 Justin Clarke
This line should go in the aliases file, which is usually specified in @/etc/aliases@. If the location is unknown, use the command @postconf alias_maps@ to find out. After updating the aliases file, be sure to run @newaliases@ to alert Postfix of the new entry.
122 35 Justin Clarke
123
If your domain is setup as a virtual mailbox map (so that you use /etc/postfix/virtual_mailbox_maps to do mappings in the form @ user@example.com /path/example.com/user@) you should:
124 1 Jean-Philippe Lang
125 75 Baz T.Miner
* create a mapping in @/etc/virtual@ like: @ foo@example.org foo@
126 34 Thomas Guyot-Sionnest
* modify @/etc/postfix/main.cf@ to specify a transport file: @transport_maps = hash:/etc/postfix/transport@
127 1 Jean-Philippe Lang
* within the transport file add a line like: @ foo@example.org local:@
128
129 20 Kurt Miebach
*Explanation:* - When you define virtual_mailbox_maps for a domain the default transport is virtual, which means specifying a local alias in @/etc/postfix/virtual@ will fail (with "unknown user"). To fix this, we override the default transport by specifying a local transport for the email address in question, which means the local alias will resolve correctly, and your script will be executed.
130 1 Jean-Philippe Lang
131 68 Denis Savitskiy
For versions before 3.2, a front-end to rdm-mailhandler.rb has been written to allow specifying projects trough sub-addresses (name+project@example.com). See [[MailhandlerSubAddress]]. This feature is now available for all email sources (ie @RAW@, @IMAP@ and @POP@) using the @project_from_subaddress@ feature see [[RedmineReceivingEmails#Target-Project-from-Email-Sub-Address|Target Project from Email Sub-Address]] below.
132 21 Kurt Miebach
133 68 Denis Savitskiy
h3. Fetching emails from an IMAP server
134 20 Kurt Miebach
135 33 Jürgen Hörmann
A rake task (@redmine:email:receive_imap@) can be used to fetch incoming emails from an IMAP server. When you run the rake command from a cron job you can include the switch @-f /path/to/redmine/appdir/Rakefile@ on the rake command, because otherwise the rakefile is not found. This is an example line for a cron file that fetches mails every 30 minutes:
136
137 68 Denis Savitskiy
<pre>
138 33 Jürgen Hörmann
*/30 * * * * redmineuser rake -f /path/to/redmine/appdir/Rakefile redmine:email:receive_imap RAILS_ENV="production" host=imap.foo.bar username=redmine@somenet.foo password=xxx 
139 68 Denis Savitskiy
</pre>
140 33 Jürgen Hörmann
141 22 Kurt Miebach
If your setup is working, but you receive mails from the cron daemon, you can suppress the output from the rake command by adding the --silent switch. That should stop cron sending mails on every execution of the command.
142 20 Kurt Miebach
143 25 Roland ...
<pre>
144 20 Kurt Miebach
*/30 * * * * redmineuser rake -f /path/to/redmine/appdir/Rakefile --silent redmine:email:receive_imap RAILS_ENV="production" host=imap.foo.bar username=redmine@somenet.foo password=xxx 
145 6 Jean-Philippe Lang
</pre>
146 1 Jean-Philippe Lang
147 6 Jean-Philippe Lang
The command has to go on a single line in your cronfile. Also see the other examples below, which only show the rake commands without the @-f@ option and without the cron part. 
148 20 Kurt Miebach
149 6 Jean-Philippe Lang
For Windows as server "pycron":http://www.kalab.com/freeware/pycron/pycron.htm can be used to schedule a fetch task.
150
151
It can be necessary that you open the firewall on the machine for outgoing TCP connections to IMAP port 143.
152 72 Sebastian Paluch
153 1 Jean-Philippe Lang
Available IMAP options:
154 6 Jean-Philippe Lang
<pre>
155 1 Jean-Philippe Lang
  host=HOST                IMAP server host (default: 127.0.0.1)
156 29 Jean-Philippe Lang
  port=PORT                IMAP server port (default: 143)
157
  ssl=SSL                  Use SSL? (default: false)
158
  starttls=STARTTLS        Use STARTTLS? (default: false)
159 1 Jean-Philippe Lang
  username=USERNAME        IMAP account
160 29 Jean-Philippe Lang
  password=PASSWORD        IMAP password
161 1 Jean-Philippe Lang
  folder=FOLDER            IMAP folder to read (default: INBOX)
162 20 Kurt Miebach
  move_on_success=MAILBOX  move emails that were successfully received
163 6 Jean-Philippe Lang
                           to MAILBOX instead of deleting them
164
  move_on_failure=MAILBOX  move emails that were ignored to MAILBOX
165
</pre>
166
167 18 Eric Davis
Issue attributes control options:
168 1 Jean-Philippe Lang
<pre>
169 18 Eric Davis
  project=PROJECT          identifier of the target project
170
  tracker=TRACKER          name of the target tracker
171
  category=CATEGORY        name of the target category
172 53 Jean-Philippe Lang
  priority=PRIORITY        name of the target priority
173 51 Jean-Philippe Lang
  allow_override=ATTRS     allow email content to override attributes
174 20 Kurt Miebach
                           specified by previous options
175 1 Jean-Philippe Lang
                           ATTRS is a comma separated list of attributes
176 6 Jean-Philippe Lang
</pre>
177
178
See [[RedmineReceivingEmails#Issue-attributes|Issue-attributes]] for a list of values that can be used for the @allow-override@ option.
179 11 Thomas Lecavelier
180 6 Jean-Philippe Lang
Examples for the rake command:
181 1 Jean-Philippe Lang
182
<pre>
183 6 Jean-Philippe Lang
  # No project specified. Emails MUST contain the 'Project' keyword:
184
  
185
  rake redmine:email:receive_imap RAILS_ENV="production" \\
186 11 Thomas Lecavelier
    host=imap.foo.bar username=redmine@somenet.foo password=xxx
187 6 Jean-Philippe Lang
188
189
  # Fixed project and default tracker specified, but emails can override
190
  # both tracker and priority attributes:
191 18 Eric Davis
  
192
  rake redmine:email:receive_imap RAILS_ENV="production" \\
193
    host=imap.foo.bar username=redmine@somenet.foo password=xxx ssl=1 \\
194
    project=foo \\
195 1 Jean-Philippe Lang
    tracker=bug \\
196
    allow_override=tracker,priority
197
198
  # Move successful emails to the 'read' mailbox and failed emails to
199
  # the 'failed' mailbox
200
  
201
  rake redmine:email:receive_imap RAILS_ENV="production" \\
202 37 Benjamin Haskell
    host=imap.foo.bar username=redmine@somenet.foo password=xxx \\
203 1 Jean-Philippe Lang
    move_on_success=read move_on_failure=failed
204 45 Mischa The Evil
205 29 Jean-Philippe Lang
</pre>
206
207
208
Ignored emails are marked as 'Seen' but are not deleted from the IMAP server--these include unknown user, unknown project and emails from the redmine emission account.
209
210
The option _allow_override_ is not only for overriding default values given to rake, but for every attribute in a mail. If you want to override the tracker in your mail you have to add _allow_override=tracker_ as a parameter.
211
212
h3. Fetching emails from a POP3 server
213
214
A rake task (@redmine:email:receive_pop3@) can be used to fetch incoming emails from a POP3 server.
215
216
Available POP3 options:
217
<pre>
218
  host=HOST                POP3 server host (default: 127.0.0.1)
219
  port=PORT                POP3 server port (default: 110)
220
  username=USERNAME        POP3 account
221
  password=PASSWORD        POP3 password
222
  apop=1                   use APOP authentication (default: false)
223 23 Roland ...
  delete_unprocessed=1     delete messages that could not be processed
224 1 Jean-Philippe Lang
                           successfully from the server (default
225
                           behaviour is to leave them on the server)
226
</pre>
227
228 6 Jean-Philippe Lang
See the IMAP rake task above for issue attributes control options.
229
230
h3. Reading emails from standard input
231
232
A rake task (@redmine:email:receive@) can be used to read a single raw email from the standard input.
233
234
<pre>
235
Issue attributes control options:
236
  project=PROJECT          identifier of the target project
237
  tracker=TRACKER          name of the target tracker
238 1 Jean-Philippe Lang
  category=CATEGORY        name of the target category
239 52 Jean-Philippe Lang
  priority=PRIORITY        name of the target priority
240
  allow_override=ATTRS     allow email content to override attributes
241 6 Jean-Philippe Lang
                           specified by previous options
242 1 Jean-Philippe Lang
                           ATTRS is a comma separated list of attributes
243 6 Jean-Philippe Lang
</pre>
244
245
See [[RedmineReceivingEmails#Issue-attributes|Issue-attributes]] for a list of values that can be used for the @allow-override@ option.
246 1 Jean-Philippe Lang
247 6 Jean-Philippe Lang
Examples:
248
249
<pre>
250
  # No project specified. Emails MUST contain the 'Project' keyword:
251
  rake redmine:email:read RAILS_ENV="production" < raw_email
252
253
  # Fixed project and default tracker specified, but emails can override
254 23 Roland ...
  # both tracker and priority attributes:
255 45 Mischa The Evil
  rake redmine:email:read RAILS_ENV="production" \\
256 1 Jean-Philippe Lang
                  project=foo \\
257 44 Mischa The Evil
                  tracker=bug \\
258 1 Jean-Philippe Lang
                  allow_override=tracker,priority < raw_email
259 44 Mischa The Evil
</pre>
260 1 Jean-Philippe Lang
261 61 Jean-Baptiste Barth
The option _allow_override_ is not only for overriding default values given to rake, but for every attribute in a mail. If you want to override the tracker in your mail you have to add _allow_override=tracker_ as a parameter.
262 44 Mischa The Evil
263
h3. Enabling unknown users to create issues by email
264
265
Redmine has a feature that provides the ability to accept incoming emails from unknown users. In order to use this feature, an extra parameter has to be included:
266 1 Jean-Philippe Lang
<pre>
267 44 Mischa The Evil
unknown_user=ACTION     how to handle emails from an unknown user where ACTION can be one of the following values:
268
                        ignore: the email is ignored (default)
269 60 Philipp erpel
                        accept: the sender is considered as an anonymous user and the email is accepted
270
                        create: a user account is created for the sender (username/password are sent back to the user) and the email is accepted
271
</pre>
272
273
Permissions have to be consistent with the chosen option. E.g. if you choose 'create', the 'Non member' role must have the 'Add issues' permission so that an issue can be created by an unknown user via email. If you choose 'accept', the 'Anonymous' role must have this permission.
274 45 Mischa The Evil
275 44 Mischa The Evil
If you receive emails via the rake task, the unknown-user option has to be written as:
276 1 Jean-Philippe Lang
<pre>
277
 unknown_user=[ignore|accept|create]
278
</pre>
279 57 Antoine Beaupré
280 44 Mischa The Evil
You can disable permission checking using the 'no_permission_check' option:
281 57 Antoine Beaupré
<pre>
282 44 Mischa The Evil
no_permission_check=1   disable permission checking when receiving the email
283
</pre>
284
285
This, together with the 'unknown-user', provides the ability to let anyone submit emails to a private project. For example:
286 45 Mischa The Evil
<pre>
287 86 Go MAEDA
rdm-mailhandler.rb --unknown-user accept --no-permission-check --project=foo
288 1 Jean-Philippe Lang
</pre>
289 58 Terence Mill
290
will let anyone submit emails to a private project 'foo'.
291
292
TODO: Is this true and is this related to the @no_permission_check@ option?:
293
> Since Redmine 0.9 the project doesn't have to be public, but authentication required in the Administration-> Settings->Authentication tab has to be unchecked.
294 70 Pierre Maigne
295
If you do not want an "new account notification email" sent to every newly created user by rdm-mailhandler you must add the option "--no-account-notice". Is implemneted with version#60 in issue #11498. Now an example:
296
<pre>
297 86 Go MAEDA
rdm-mailhandler.rb --unknown-user accept --no-permission-check --project=foo --no-account-notice
298 70 Pierre Maigne
</pre>
299
300
h3. Schedule email receiving with Rufus Scheduler
301
302
Instead of using a cron to trigger the Rake task to retrieve incoming email, you can use Rufus Scheduler which will run the Rake task in the same process as Redmine.
303 84 Go MAEDA
This is using less resources and faster than calling the Rake task from a cron (or from the Task Scheduler on Windows).
304 70 Pierre Maigne
305
To do that, install rufus-scheduler gem:
306
<pre>gem install rufus-scheduler</pre>
307
308
Create a what_you_want.rb file in /config/initializers/ and put the following content in your file. (Here for a POP3 account. Change it with your own parameters and own task.)
309
<pre>
310
require 'rubygems'
311
require 'rake'
312
require 'rufus-scheduler'
313
314
load File.join(Rails.root, 'Rakefile')
315
316
ENV['host']='pop.toto.com'
317
ENV['port']='110'
318
ENV['ssl']='SSL'
319
ENV['username']='redmine@toto.com'
320
ENV['password']='azerty123456'
321
322
scheduler = Rufus::Scheduler.new
323
# Check emails every 10 mins
324
scheduler.interval '10m' do
325
  task = Rake.application['redmine:email:receive_pop3']
326
  task.reenable
327
  task.invoke 
328
end
329 1 Jean-Philippe Lang
</pre>
330
331 12 Eric Davis
Restart your Redmine instance and your incoming emails will be retrieved on schedule.
332 1 Jean-Philippe Lang
333
You can check "Rufus-Scheduler":https://github.com/jmettraux/rufus-scheduler for scheduling syntax.
334 3 Jean-Philippe Lang
335 43 Mischa The Evil
h2. How it works
336 38 Dave Thomas
337 15 Jean-Philippe Lang
When receiving an email, Redmine uses the From address of the email to find the corresponding user. Emails received from unknown or locked users are ignored.
338
339 79 Go MAEDA
If the email subject contains something like "Re: *[xxxxxxx !#123]*" or "[!#123]", the email is processed as a reply and a note is added to issue !#123. Otherwise, a new issue is created.
340 1 Jean-Philippe Lang
341 16 Jean-Philippe Lang
Note that, in order to create an issue, all required custom fields must be provided. Without them, issue creation will fail. As an alternative you can ensure that every custom field has a default value which is then used during issue creation.
342
343 1 Jean-Philippe Lang
h3. Target project
344
345 84 Go MAEDA
The target project can be specified using the @project@ option when receiving emails.  This should be the identifier of the project and *not* the name.  You can easily find the identifier in the URL.
346 28 Ethan Fremen
347
If you don't use this option, users have to specify in the email body which project the issue should be added to. This can be done by inserting a line in the email body like this: @"Project: foo"@.
348 1 Jean-Philippe Lang
349
Example (email body):
350
351
<pre>
352
This is a new issue that will be added to project foo.
353 16 Jean-Philippe Lang
Here we have the issue description
354
[...]
355
356
Project: foo
357
</pre>
358
359
You can set a default project using the @project@ option and let users override this default project by using the @allow-override@ option when receiving emails.
360
Example:
361 14 Jean-Philippe Lang
362 1 Jean-Philippe Lang
<pre>
363 75 Baz T.Miner
  # Create issues on project foo by default
364
  rake redmine:email:receive_imap [...] project=foo allow_override=project
365
</pre>
366
367
Of course, user permissions are checked and this email would be ignored if the user who sent this email is not allowed to add issues to project foo.
368
Make sure that the target project doesn't use *required* custom fields with no default value for its issues, otherwise the creation of the issue will fail.
369
370
h3. Target Project from Email Sub-Address
371
372
This feature was introduced in ver 3.2.0 (SVN rev r14687). It may be preferable to have one mailbox for all incoming emails to a Redmine instance, instead of one per project. For some history of this feature see [[MailhandlerSubAddress]]. When receiving emails at redmine@somenet.foo, an email sent to redmine+foo@somenet.foo will cause the issue to be added to project with identifier foo.
373
374
To enable this feature add the @project_from_subaddress=redmine@somenet.foo@ to the command e.g.
375
376
<pre>
377
    rake redmine:email:receive_imap [...] project_from_subaddress=redmine@somenet.foo
378
</pre> 
379
380
If a project is included in the command-line then it becomes the default project that will be used for emails sent to @redmine@somenet.foo@. So with the command:
381
382
<pre>
383 15 Jean-Philippe Lang
    rake redmine:email:receive_imap [...] project=bar project_from_subaddress=redmine@somenet.foo
384
</pre> 
385 8 Jean-Philippe Lang
386 74 Deoren Moor
emails to @redmine@somenet.foo@ or @redmine+bar@somenet.foo@ will raise issues in project bar; emails to @redmine+foo@somenet.foo@ will go into project foo.
387
388
Some email providers include support for sub-addresses, as per RFCs 3598, 5233. Where this is not supported, forwarding mail addresses to the 'central' address, may work (it does in my case), ie set up an email address forwarding all mails to @redmine@somenet.foo@ from @redmine+foo@somenet.foo@, @redmine+bar@somenet.foo@ etc. This is easy to administer and does not require fetching emails from multiple accounts, each with its own account credentials.
389
390
h3. Issue attributes
391 1 Jean-Philippe Lang
392 66 Deoren Moor
Based on the options you use when receiving emails (see @allow-override@ option), users may be able to override some attributes when submitting an issue. 
393
394
Note: prior to Redmine version:"3.2.0" (#20543) some attributes were _always_ overridable, but this was not documented. This behavior has been changed and all attributes have to be explicitly listed with the @allow_override@ option to be overridable. For those who want all attributes to be overridable, @allow_override=all@ can now be used (#20543).
395
396
Once @allow_override@ has been configured, you can override those attributes by using the appropriate keywords in the email body.
397 1 Jean-Philippe Lang
398
Example keyword list:
399 69 Denis Savitskiy
400
* @Project@
401
* @Tracker@
402 80 Sören Weber
* @Status@
403 73 Mathieu Janson
* @Category@
404 1 Jean-Philippe Lang
* @Priority@
405 80 Sören Weber
* @Assigned to@
406 66 Deoren Moor
* @Start date@
407 71 Toshi MARUYAMA
* @Due date@
408 66 Deoren Moor
* @Target version@
409 8 Jean-Philippe Lang
* @Estimated hours@
410
* @Done ratio@
411 28 Ethan Fremen
* @<Custom field name>@
412 8 Jean-Philippe Lang
413
The values available are the ones of the context. E.g. @Status@ available (for this Tracker and this Project) are labels in the localized language, exactly as displayed in the user interface or system default language (even with spaces, without quoting).
414
415 1 Jean-Philippe Lang
Example (email body):
416 8 Jean-Philippe Lang
417 1 Jean-Philippe Lang
<pre>
418
This is a new issue that overrides a few attributes
419
[...]
420
421 66 Deoren Moor
Project: foo
422
Tracker: Bug
423
Priority: Urgent
424
Status: Resolved
425
</pre>
426
427
The format for keywords differs from the allowed attribute values for the @allow_override@ option:
428
429
* @project@
430
* @tracker@
431 1 Jean-Philippe Lang
* @status@
432 66 Deoren Moor
* @category@
433 80 Sören Weber
* @priority@
434 1 Jean-Philippe Lang
* @assigned_to@
435 66 Deoren Moor
* @start_date@
436
* @due_date@
437 80 Sören Weber
* @fixed_version@ (aka. Target version)
438 66 Deoren Moor
* @estimated_hours@
439
* @done_ratio@
440 80 Sören Weber
* @<custom_field_name>@
441 66 Deoren Moor
442
Multiple attribute values can be specified in order to allow only certain keywords to be used.
443
444 49 Jean-Philippe Lang
Example:
445 1 Jean-Philippe Lang
446
<pre>
447
  # Allow overriding project, tracker, status & priority
448 16 Jean-Philippe Lang
  rake redmine:email:receive_imap [...] allow_override=project,tracker,status,priority
449 42 Mischa The Evil
</pre>
450 41 Miguel Filho
451 16 Jean-Philippe Lang
h3. Watchers
452
453
If the user who sends the email has the 'Add issue watchers' permission, users that are in To or Cc field of the email are automatically added as watchers of the created issue.
454
455 1 Jean-Philippe Lang
Watchers are added only when the issue is created. To or Cc fields are ignored on replies. See #7017 and #8009.
456 55 Art Kuo
457
h3. Email format and attachments
458
459 1 Jean-Philippe Lang
Redmine tries to use the plain text part of the email to fill the description of the issue.
460 65 Toshi MARUYAMA
If a HTML-only email is received, HTML tags are removed from its body.
461 1 Jean-Philippe Lang
462
Email attachments are automatically attached to the issue, unless their size exceeds the [[RedmineSettings#Attachment-max-size|maximum attachment size]] defined in the application settings.
463
464
h3. Truncate emails
465
466 83 Go MAEDA
The Administrator's settings may be used to automatically truncate emails, for example to eliminate quoted messages in forum replies. To do this, set the outgoing email header to something like @--Reply above this line--@ in the Email notifications settings. Then in the Incoming emails settings, enter the same line into the box "Truncate emails after one of these lines." (It is also possible to allow regex to be truncated)