Project

General

Profile

Actions

Feature #13340

closed

Mail handler: option to add created user to default group

Added by Daniel Black about 11 years ago. Updated almost 11 years ago.

Status:
Closed
Priority:
Normal
Category:
Email receiving
Target version:
Start date:
Due date:
% Done:

0%

Estimated time:
Resolution:
Fixed

Description

This patch creates the option --default-group to the mail hander.

The purpose is to put created users that are handled by the script into a default group.

With the associated permissions on this group, and a "Default notification option" conducive to a response for a new account, the objectives of responding to a issues in a private project without exposing all issues to the user is achievable as requested in #6069 and #8497.

The patch in #10178 would also compliment this nicely.

Other management functions, like identifying how the user account was created (e.g. --default-group=Email) are also made easier.


Files

mail_handler.patch (2.87 KB) mail_handler.patch Daniel Black, 2013-03-03 07:49

Related issues

Has duplicate Redmine - Feature #8643: Allow rdm-mailhandler with unknown-user=create to attach the user to a specific group instead of creating a "rightless" userClosed2011-06-17

Actions
Precedes Redmine - Defect #13712: Fix email rake tasks to also support no_account_notice and default_group optionsClosed

Actions
Actions #1

Updated by Jean-Philippe Lang about 11 years ago

  • Tracker changed from Patch to Feature
  • Subject changed from mail_handler can put created user into default group to Mail handler: option to add created user to default group
  • Status changed from New to Resolved
  • Assignee set to Jean-Philippe Lang
  • Target version set to 2.3.0
  • Resolution set to Fixed

Feature added in r11522. The patch was slightly refactored and a test was added. The --default-group option also accepts a comma separated list of names to add new users to several groups. Thanks.

Actions #2

Updated by Jean-Philippe Lang about 11 years ago

  • Status changed from Resolved to Closed

Merged.

Actions #3

Updated by Daniel Jones about 11 years ago

This doesn't seem to work when using redmine:email:receive_imap via Rake.

Specifying default_group=?? isn't passed through to the mail handler.

Can anyone help me understand how to use this with the rake task?

Actions #4

Updated by Arron Woods almost 11 years ago

+1 on this not working with the redmine:email:receive_imap rake

Is this only designed for the piped version? I have a group called "Clients", with this in my cron:
/usr/local/bin/rake -f /opt/apps/redmine/Rakefile redmine:email:receive_imap RAILS_ENV=production host=imap.gmail.com port=993 username=*** password=*** ssl=SSL folder=Redmine project=helpdesk tracker=Support category=Incoming unknown_user=create allow_override=project,assigned_to default_group=53

Actions #5

Updated by Jadranko Stjepanović almost 11 years ago

Daniel Jones wrote:

This doesn't seem to work when using redmine:email:receive_imap via Rake.

Specifying default_group=?? isn't passed through to the mail handler.

Can anyone help me understand how to use this with the rake task?

Right, lib/tasks/email.rake has not been patched, so it does not recognize new option.

Actions #6

Updated by Mischa The Evil almost 11 years ago

Jadranko Stjepanović wrote:

Right, lib/tasks/email.rake has not been patched, so it does not recognize new option.

Daniel J., Arron: Jadranko is right. Both --no-account-notice and --default-group options weren't supported for email fetching using the rake task (pop and imap) in Redmine 2.3.0.
This defect was reported via issue #13712, fixed in r11748 and released in Redmine 2.3.1.

Actions #7

Updated by Go MAEDA about 9 years ago

  • Has duplicate Feature #8643: Allow rdm-mailhandler with unknown-user=create to attach the user to a specific group instead of creating a "rightless" user added
Actions

Also available in: Atom PDF