Feature #41031
closedInclude project identifier in List-Id header field of notification emails
0%
Description
I propose adding the project identifier to the List-Id
header field of notification emails. Currently, the List-Id
is based on the emission email address (Setting.mail_from
). I want to change the List-Id to include both the project identifier and the emission email address.
The current notification email headers include the X-Redmine-Project
field, which contains the project identifier. However, widely used email services Gmail do not support filtering based on custom headers starting with X-
. This makes it difficult to create filters based on the project.
By including the project identifier in the List-Id
, users can utilize Gmail’s list
operator to create filters based on the project. This enhancement would improve the ability to organize and manage project-related emails in Gmail.
Current Implementation:
For an emission email address of redmine@example.net
, the current List-Id is:
List-Id: <redmine.example.net>
Proposed Implementation:
For an emission email address of redmine@example.net
and a project identifier of ecookbook
, the proposed List-Id is:
List-Id: <ecookbook.redmine.example.net>
Backward Compatibility:
Changing the List-Id
header field value will affect users who depend on the current format. To address this, we may need to add a new setting in Administration > Settings page allowing users to choose whether to include the project identifier in the List-Id. This ensures that existing workflows relying on the current List-Id format remain unaffected.
Files
Related issues