Project

General

Profile

Actions

Feature #30820

closed

Drop setting "Blind carbon copy recipients (bcc)"

Added by Marius BĂLTEANU almost 6 years ago. Updated over 2 years ago.

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

0%

Estimated time:
Resolution:

Description

From #26791:

BCC recipients

Since each user gets their own mail, we can probably remove the setting to send mails with BCC completely. If plugins want to send mails to non-user recipients, we would have to make sure to either set the recipients manually on BCC or group them appropriately. It is not a required setting in Redmine core anymore though.

I agree, the setting doesn't make any sense now.


Files


Related issues

Related to Redmine - Feature #26791: Send individual notification mails per mail recipientClosedJean-Philippe Lang

Actions
Related to Redmine - Defect #30787: Other recipients are not listed in To field even if Setting.bcc_recipients is falseClosedGo MAEDA

Actions
Related to Redmine - Feature #8516: Email notifications without the recipient treated as attempted fraud by mail clientsClosed2011-06-03

Actions
Related to Redmine - Defect #35957: MessagesControllerTest#test_post_new test fails (trunk)ClosedMarius BĂLTEANU

Actions
Blocks Redmine - Patch #31035: Remove redefinition of ActionMailer::LogSubscriber#deliver which is no longer necessary because of the removal of Setting.bcc_recipientsClosedGo MAEDA

Actions
Actions #1

Updated by Marius BĂLTEANU almost 6 years ago

  • Related to Feature #26791: Send individual notification mails per mail recipient added
Actions #2

Updated by Marius BĂLTEANU almost 6 years ago

  • Related to Defect #30787: Other recipients are not listed in To field even if Setting.bcc_recipients is false added
Actions #3

Updated by Go MAEDA almost 6 years ago

  • Assignee set to Jean-Philippe Lang
  • Target version changed from Candidate for next major release to 4.0.2

+1
The setting has no effect since #26791 was implemented.

Actions #4

Updated by Go MAEDA almost 6 years ago

Probably the patch also resolves #8516 because Redmine with the patch applied does not remove To field.

Actions #5

Updated by Go MAEDA almost 6 years ago

  • Related to Feature #8516: Email notifications without the recipient treated as attempted fraud by mail clients added
Actions #6

Updated by Marius BĂLTEANU almost 6 years ago

Go MAEDA wrote:

Probably the patch also resolves #8516 because Redmine with the patch applied does not remove To field.

Agree. Also, #30787 can be closed now from my point of view if you don't refer to other problem.

Actions #7

Updated by Marius BĂLTEANU almost 6 years ago

  • File deleted (0001-Remove-setting-Blind-carbon-copy-recipients-bcc.patch)
Actions #9

Updated by Go MAEDA almost 6 years ago

  • Category set to Email notifications
  • Target version changed from 4.0.2 to 4.1.0

Since this patch adds a migration, I am changing the target version from 4.0.2 to 4.1.0.

Actions #10

Updated by Go MAEDA almost 6 years ago

  • Blocks Patch #31035: Remove redefinition of ActionMailer::LogSubscriber#deliver which is no longer necessary because of the removal of Setting.bcc_recipients added
Actions #11

Updated by Jean-Philippe Lang over 5 years ago

  • Target version changed from 4.1.0 to 5.0.0

Removing a setting may cause some plugins to error.
Setting it to a major release.

Actions #12

Updated by Marius BĂLTEANU over 3 years ago

  • Assignee changed from Jean-Philippe Lang to Marius BĂLTEANU
Actions #13

Updated by Marius BĂLTEANU over 3 years ago

I've rebased the branch for the current trunk

Actions #14

Updated by Marius BĂLTEANU over 3 years ago

Marius BALTEANU wrote:

I've rebased the patch for the current trunk

Actions #15

Updated by Holger Just over 3 years ago

If entirely removing the setting is unwanted in 4.3, maybe we can deprecate it there.

That is, we could remove any code which uses the setting but keep the setting itself available in code (possible with some deprecation warning if accessed)

Actions #16

Updated by Marius BĂLTEANU over 3 years ago

Holger Just wrote:

If entirely removing the setting is unwanted in 4.3, maybe we can deprecate it there.

That is, we could remove any code which uses the setting but keep the setting itself available in code (possible with some deprecation warning if accessed)

The next version is 5.0.0 which will contain other removals or breaking changes. I'm in favour of removing this and in the future, indeed, we can deprecate it few versions before.

Actions #17

Updated by Marius BĂLTEANU over 3 years ago

  • Status changed from New to Resolved
Actions #18

Updated by Marius BĂLTEANU over 3 years ago

Patch committed.

Plugins developers who are using bcc_recipients setting must add their own setting starting from Redmine 5.0.0.

Actions #19

Updated by Marius BĂLTEANU over 3 years ago

  • Status changed from Resolved to Closed
  • Assignee set to Marius BĂLTEANU
Actions #20

Updated by Go MAEDA about 3 years ago

  • Related to Defect #35957: MessagesControllerTest#test_post_new test fails (trunk) added
Actions #21

Updated by Go MAEDA over 2 years ago

  • Tracker changed from Patch to Feature
Actions

Also available in: Atom PDF