Project

General

Profile

RedmineReceivingEmails » History » Version 49

Jean-Philippe Lang, 2012-06-20 20:57

1 40 Etienne Massip
h1. Receiving emails
2 1 Jean-Philippe Lang
3 4 Jean-Philippe Lang
{{>toc}}
4
5 40 Etienne Massip
As of 0.8.0, Redmine can be configured to allow issue creation or comments via email.
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
This script reads a raw email from the standard input and forward it to Redmine via a HTTP request.
30
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 26 Ian Smith-Heisters
Copy @rdm-mailhandler.rb@ to your mail server, make sure its permissions allow execution, and configure your MTA.
44 4 Jean-Philippe Lang
45 5 Jean-Philippe Lang
Usage:
46 4 Jean-Philippe Lang
47 1 Jean-Philippe Lang
<pre>
48 5 Jean-Philippe Lang
rdm-mailhandler [options] --url=<Redmine URL> --key=<API key>
49 1 Jean-Philippe Lang
50 5 Jean-Philippe Lang
Required:
51
  -u, --url                      URL of the Redmine server
52
  -k, --key                      Redmine API key
53
  
54
General options:
55
  -h, --help                     show this help
56
  -v, --verbose                  show extra information
57
  -V, --version                  show version information and exit
58 1 Jean-Philippe Lang
59 5 Jean-Philippe Lang
Issue attributes control options:
60
  -p, --project=PROJECT          identifier of the target project
61
  -t, --tracker=TRACKER          name of the target tracker
62
      --category=CATEGORY        name of the target category
63
      --priority=PRIORITY        name of the target priority
64
  -o, --allow-override=ATTRS     allow email content to override attributes
65
                                 specified by previous options
66
                                 ATTRS is a comma separated list of attributes
67 6 Jean-Philippe Lang
</pre>
68
69 1 Jean-Philippe Lang
Examples:
70 6 Jean-Philippe Lang
71
<pre>
72 5 Jean-Philippe Lang
  # No project specified. Emails MUST contain the 'Project' keyword:
73
  rdm-mailhandler --url http://redmine.domain.foo --key secret
74
  
75
  # Fixed project and default tracker specified, but emails can override
76
  # both tracker and priority attributes:
77
  rdm-mailhandler --url https://domain.foo/redmine --key secret \\
78
                  --project foo \\
79
                  --tracker bug \\
80
                  --allow-override tracker,priority
81
</pre>
82
83 35 Justin Clarke
Here is an example for a Postfix local alias (which is usually specified in @/etc/aliases@):
84 5 Jean-Philippe Lang
85
<pre>
86 1 Jean-Philippe Lang
foo: "|/path/to/rdm-mailhandler.rb --url http://redmine.domain --key secret --project foo"
87 35 Justin Clarke
</pre>
88
89
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:
90
91 36 Justin Clarke
* create a mapping in @/etc/virtual@ like: @ foo@example.org foo@
92 35 Justin Clarke
* modify @/etc/postfix/main.cf@ to specify a transport file: @transport_maps = hash:/etc/postfix/transport@
93 36 Justin Clarke
* within the transport file add a line like: @ foo@example.org local:@
94 35 Justin Clarke
95
*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.
96 1 Jean-Philippe Lang
97 34 Thomas Guyot-Sionnest
A front-end to rdm-mailhandler.rb has been written to allow specifying projects trough sub-addresses (name+project@example.com). See [[MailhandlerSubAddress]]
98
99 1 Jean-Philippe Lang
h3. Fetching emails from an IMAP server
100
101 20 Kurt Miebach
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:
102 1 Jean-Philippe Lang
103 21 Kurt Miebach
<code>
104
*/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 
105
</code>
106 20 Kurt Miebach
107 33 Jürgen Hörmann
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.
108
109
<code>
110
*/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 
111
</code>
112
113 22 Kurt Miebach
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. 
114 20 Kurt Miebach
115 25 Roland ...
For Windows as server "pycron":http://www.kalab.com/freeware/pycron/pycron.htm can be used to schedule a fetch task.
116 20 Kurt Miebach
117 6 Jean-Philippe Lang
It can be necessary that you open the firewall on the machine for outgoing TCP connections to IMAP port 143.
118 1 Jean-Philippe Lang
119 6 Jean-Philippe Lang
Available IMAP options:
120 20 Kurt Miebach
<pre>
121 6 Jean-Philippe Lang
  host=HOST                IMAP server host (default: 127.0.0.1)
122
  port=PORT                IMAP server port (default: 143)
123
  ssl=SSL                  Use SSL? (default: false)
124 1 Jean-Philippe Lang
  username=USERNAME        IMAP account
125 6 Jean-Philippe Lang
  password=PASSWORD        IMAP password
126 1 Jean-Philippe Lang
  folder=FOLDER            IMAP folder to read (default: INBOX)
127 29 Jean-Philippe Lang
  move_on_success=MAILBOX  move emails that were successfully received
128
                           to MAILBOX instead of deleting them
129
  move_on_failure=MAILBOX  move emails that were ignored to MAILBOX
130 1 Jean-Philippe Lang
</pre>
131 29 Jean-Philippe Lang
132 1 Jean-Philippe Lang
Issue attributes control options:
133 20 Kurt Miebach
<pre>
134 6 Jean-Philippe Lang
  project=PROJECT          identifier of the target project
135
  tracker=TRACKER          name of the target tracker
136
  category=CATEGORY        name of the target category
137
  priority=PRIORITY        name of the target priority
138 18 Eric Davis
  allow_override=ATTRS     allow email content to override attributes
139 1 Jean-Philippe Lang
                           specified by previous options
140 18 Eric Davis
                           ATTRS is a comma separated list of attributes
141
</pre>
142
143 20 Kurt Miebach
Examples for the rake command:
144 1 Jean-Philippe Lang
145 6 Jean-Philippe Lang
<pre>
146
  # No project specified. Emails MUST contain the 'Project' keyword:
147
  
148 11 Thomas Lecavelier
  rake redmine:email:receive_imap RAILS_ENV="production" \\
149 6 Jean-Philippe Lang
    host=imap.foo.bar username=redmine@somenet.foo password=xxx
150 1 Jean-Philippe Lang
151
152 6 Jean-Philippe Lang
  # Fixed project and default tracker specified, but emails can override
153
  # both tracker and priority attributes:
154
  
155 11 Thomas Lecavelier
  rake redmine:email:receive_imap RAILS_ENV="production" \\
156 6 Jean-Philippe Lang
    host=imap.foo.bar username=redmine@somenet.foo password=xxx ssl=1 \\
157
    project=foo \\
158
    tracker=bug \\
159
    allow_override=tracker,priority
160 18 Eric Davis
161
  # Move successful emails to the 'read' mailbox and failed emails to
162
  # the 'failed' mailbox
163
  
164 1 Jean-Philippe Lang
  rake redmine:email:receive_imap RAILS_ENV="production" \\
165
    host=imap.foo.bar username=redmine@somenet.foo password=xxx \\
166
    move_on_success=read move_on_failure=failed
167
168
</pre>
169
170
171 37 Benjamin Haskell
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.
172 1 Jean-Philippe Lang
173 45 Mischa The Evil
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.
174 29 Jean-Philippe Lang
175
h3. Fetching emails from a POP3 server
176
177
_Only available in trunk and future 1.0._
178
179
A rake task (@redmine:email:receive_pop3@) can be used to fetch incoming emails from a POP3 server.
180
181
Available POP3 options:
182
<pre>
183
  host=HOST                POP3 server host (default: 127.0.0.1)
184
  port=PORT                POP3 server port (default: 110)
185
  username=USERNAME        POP3 account
186
  password=PASSWORD        POP3 password
187
  apop=1                   use APOP authentication (default: false)
188
  delete_unprocessed=1     delete messages that could not be processed
189
                           successfully from the server (default
190
                           behaviour is to leave them on the server)
191
</pre>
192
193
See the IMAP rake task above for issue attributes control options.
194 23 Roland ...
195 1 Jean-Philippe Lang
h3. Reading emails from standard input
196
197
A rake task (@redmine:email:receive@) can be used to read a single raw email from the standard input.
198
199 6 Jean-Philippe Lang
<pre>
200
Issue attributes control options:
201
  project=PROJECT          identifier of the target project
202
  tracker=TRACKER          name of the target tracker
203
  category=CATEGORY        name of the target category
204
  priority=PRIORITY        name of the target priority
205
  allow_override=ATTRS     allow email content to override attributes
206
                           specified by previous options
207
                           ATTRS is a comma separated list of attributes
208
</pre>
209 1 Jean-Philippe Lang
210 6 Jean-Philippe Lang
Examples:
211 1 Jean-Philippe Lang
212 6 Jean-Philippe Lang
<pre>
213
  # No project specified. Emails MUST contain the 'Project' keyword:
214
  rake redmine:email:read RAILS_ENV="production" < raw_email
215 1 Jean-Philippe Lang
216 6 Jean-Philippe Lang
  # Fixed project and default tracker specified, but emails can override
217
  # both tracker and priority attributes:
218
  rake redmine:email:read RAILS_ENV="production" \\
219
                  project=foo \\
220
                  tracker=bug \\
221
                  allow_override=tracker,priority < raw_email
222
</pre>
223 23 Roland ...
224 45 Mischa The Evil
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.
225 1 Jean-Philippe Lang
226 44 Mischa The Evil
h3. Enabling unknown users to create issues by email
227 1 Jean-Philippe Lang
228 44 Mischa The Evil
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:
229 1 Jean-Philippe Lang
<pre>
230 44 Mischa The Evil
unknown_user=ACTION     how to handle emails from an unknown user where ACTION can be one of the following values:
231
                        ignore: the email is ignored (default)
232
                        accept: the sender is considered as an anonymous user and the email is accepted
233
                        create: a user account is created for the sender (username/password are sent back to the user) and the email is accepted
234
</pre>
235 1 Jean-Philippe Lang
236 44 Mischa The Evil
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.
237
238 45 Mischa The Evil
You can disable permission checking using the 'no_permission_check' option:
239 44 Mischa The Evil
<pre>
240 1 Jean-Philippe Lang
no_permission_check=1   disable permission checking when receiving the email
241
</pre>
242
243 44 Mischa The Evil
This, together with the 'unknown_user', provides the ability to let anyone submit emails to a private project. For example:
244
<pre>
245
rdm-mailhandler --unknown_user accept --no-permission-check --project=foo
246
</pre>
247
248
will let anyone submit emails to a private project 'foo'.
249
250 45 Mischa The Evil
TODO: Is this true and is this related to the @no_permission_check@ option?:
251 47 Brett Zamir
> 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.
252 1 Jean-Philippe Lang
253
h2. How it works
254
255 12 Eric Davis
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.
256 1 Jean-Philippe Lang
257
If the email subject contains something like "Re: *[xxxxxxx !#123]*", the email is processed as a reply and a note is added to issue !#123. Otherwise, a new issue is created.
258 3 Jean-Philippe Lang
259 43 Mischa The Evil
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.
260 38 Dave Thomas
261 15 Jean-Philippe Lang
h3. Target project
262
263 27 Eric Davis
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.
264 1 Jean-Philippe Lang
265 16 Jean-Philippe Lang
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"@.
266
267 1 Jean-Philippe Lang
Example (email body):
268
269
<pre>
270 28 Ethan Fremen
This is a new issue that will be added to project foo.
271
Here we have the issue description
272 1 Jean-Philippe Lang
[...]
273
274
Project: foo
275
</pre>
276
277 16 Jean-Philippe Lang
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.
278
Example:
279
280
<pre>
281
  # Create issues on project foo by default
282
  rake redmine:email:receive_imap [...] project=foo allow_override=project
283
</pre>
284
285 14 Jean-Philippe Lang
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.
286 16 Jean-Philippe Lang
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.
287 15 Jean-Philippe Lang
288
h3. Issue attributes
289 8 Jean-Philippe Lang
290 1 Jean-Philippe Lang
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.
291 48 Daniel Caillibaud
This can be done by using the following keywords in the email body : @Project@, @Tracker@, @Category@, @Priority@, @Status@.
292
293
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 (even with spaces, without quoting).
294 8 Jean-Philippe Lang
295 16 Jean-Philippe Lang
Example (email body):
296 8 Jean-Philippe Lang
297
<pre>
298 28 Ethan Fremen
This is a new issue that overrides a few attributes
299 8 Jean-Philippe Lang
[...]
300
301
Project: foo
302 1 Jean-Philippe Lang
Tracker: Bug
303 8 Jean-Philippe Lang
Priority: Urgent
304 12 Eric Davis
Status: Resolved
305 8 Jean-Philippe Lang
</pre>
306 15 Jean-Philippe Lang
307 49 Jean-Philippe Lang
Valid attribute values that can used with the @allow-override@ option are:@ project, tracker, status, priority, category, assigned_to, fixed_version@ (aka. Target version),@ start_date, due_date, estimated_hours, done_ratio@.
308
309 1 Jean-Philippe Lang
h3. Watchers
310
311
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.
312 16 Jean-Philippe Lang
313 42 Mischa The Evil
Watchers are added only when the issue is created. To or Cc fields are ignored on replies. See #7017 and #8009.
314 41 Miguel Filho
315 16 Jean-Philippe Lang
h3. Email format and attachments
316
317
Redmine tries to use the plain text part of the email to fill the description of the issue.
318
If a HTML-only email is received, HTML tags are removed from its body.
319
320
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.