Redmine

h1. Receiving emails

As of r1572, Redmine can be configured to allow issue creation or comments via email.

h2. Setup

You can configure Redmine to receive emails in one of the following ways.

h3. Fetching emails from an IMAP server

A rake task (@redmine:email:receive_imap@) can be used to fetch incoming emails from an IMAP server.

It accepts the following options:

  * host      => IMAP server host (default: 127.0.0.1)

  * port      => IMAP server port (default: 143)

  * ssl       => Set this option to 1 to enable SSL (default: false)

  * username  => IMAP account

  * password  => IMAP password

  * folder    => IMAP folder to read (default: INBOX)

Other options:

  * project   => identifier of the project the issue should be added to

Example:

<pre>

rake redmine:email:receive_imap host=imap.domain \

                                username=redmine@domain \

                                password=xxx \

                                project=foo \              # => all issues will be added to project "foo"

                                RAILS_ENV="production"

</pre>

Emails that are ignored (unknown user, unknown project...) are marked as 'Seen' but are not deleted from the IMAP server.

h3. Reading emails from standard input

A rake task (@redmine:email:receive@) can be used to read a single raw email from the standard input.

Options:

  * project   => identifier of the project the issue should be added to

Postfix or Sendmail can be configured to forward incoming emails to this script.

See: http://wiki.rubyonrails.org/rails/pages/HowToReceiveEmailsWithActionMailer

Example of a Postfix alias:

  redmine: "|(cd /path/to/redmine && rake redmine:email:receive RAILS_ENV=production)" 

h2. How it works

When receiving an email, Redmine uses the From address of the email to find the corresponding user. Emails received from unknow or locked users are ignored.

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.

If you don't use the @project@ option when reading emails, 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"@.

Example (email body):

<pre>

This is a new ticket that will be added to project foo.

Here we have the ticket description

[...]

Project: foo

</pre>

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.