Project

General

Profile

Actions

Feature #3003

open

Better handling of unknown and aliased email addresses when submitting issue via email

Added by simon b about 15 years ago. Updated over 12 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Email receiving
Target version:
-
Start date:
2009-03-18
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

Currently incoming emails from unknown addresses are not processed.

Some redmine users also like to submit tickets from alternative or personal email addresses, and an ideal enhancement to the email submission would be:

1) possibility to add email aliases in addition to the default email address that is used for sending notifications. this way, an email from the default address or the secondary alias address will be accepted.
2) possibility to allow ticket submission from a previously unknown address. this could be mapped to a default generic user, or a new username created from the email address (both options could be avaialable to the administrator).


Files

create_users_from_emails_patch (11.4 KB) create_users_from_emails_patch Marius Hächler, 2009-04-24 15:10
fixtures.rar (1.21 KB) fixtures.rar Marius Hächler, 2009-04-24 15:10
create_users_from_emails_patch.patch (17.1 KB) create_users_from_emails_patch.patch Marius Hächler, 2009-04-24 15:11
create-users-from-emails.patch (18.8 KB) create-users-from-emails.patch Tero Tilus, 2009-05-14 14:35

Related issues

Related to Redmine - Feature #2334: Autocreate user account when user submits email that creates new issueClosed2008-12-13

Actions
Follows Redmine - Feature #2230: Issue creation via email from anyone without a Redmine account using an Inbox projectNew2008-11-26

Actions
Actions #1

Updated by Marius Hächler about 15 years ago

I added some functionality that might be interesting. Basicly some more options for receiving e-mail, like what do to with unknown addresses. it's a little bit configurable like i thought it could be usefull.
A new user will be created from the email address:

email = from
firstname = from.split(@).split(.).first
lastname = from.split(@).split(.).last
password = generated

Tests included
Use as you like. (i suggest this would resolve point 2)

Actions #3

Updated by Tero Tilus about 15 years ago

Modified the patch a little. Role creation was broken against current trunk. Modified patch available at github, http://github.com/terotil/redmine/commit/458682467dc21a7cf0ad769fd5f351fbd96a468a

Actions #4

Updated by simon b about 15 years ago

Tero
Thankyou. How to implement your patch? The github gives a 1.2mb tar file of the a fork rather than a .patch diff file.
I am using the latest svn checkout.

Actions #6

Updated by Mischa The Evil over 14 years ago

  • Category set to Email notifications

Extracted from issue #2230:

Kolja K. wrote on 2009-11-20 17:46:

If you plan to put this issue in 0.9, it would be a really good idea to allow anonymous tickets with an email adress attached. This way, you are not forced to have every email to create an user only to know who has created the ticket. Kind of light users only with an email adress and unable to log in. Think of redirecting your into redmine... and btw: there is a patch to activate a permission called "view own issues" - perfect solution for inbox projects.

Jean-Philippe Lang replied on 2009-11-21 13:34:

Yes, this would be a really good idea. But time is missing for adding this in 0.9.

Actions #7

Updated by Jean-Philippe Lang over 14 years ago

  • Category changed from Email notifications to Email receiving
Actions #8

Updated by Stéphane Gourichon over 12 years ago

Some redmine users also like to submit tickets from alternative or personal email addresses

Solution implemented r2789:
  • deals with unknown e-mails very well (AFAIK, at least)
  • does not address need to associate to each user a collection of alternate e-mail adresses.

The one that bites hard here is people replying to existing issues with a different e-mail address... replies get lost.

That need of alternate e-mail addresses is de facto discussed in #4244, although the initial title and description are different.

If each issue is to be kept focused for clarity, should a separate dedicated issue be created ?

Actions

Also available in: Atom PDF