Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Add In-Reply-To header to email notifications #4183

Closed
wants to merge 1 commit into from

Conversation

fguillot
Copy link
Member

No description provided.

@fguillot fguillot changed the title Add In-Reply-To header to email notifications [WIP] Add In-Reply-To header to email notifications May 14, 2019
@lukasjuhrich
Copy link

I think this would be a great improvement!

To build on this: wouldn't it be possible to set a reasonable Message-ID? Otherwise, I'm not sure how this is supported with standard mail-clients.

For instance, github uses the following scheme for the Message-ID and In-Reply-To headers:

  • The „root event“ (creation) has a message-ID of the form <org/project/object_type/object_number@github.com> (think object_type=issue), so we could use something like <project-id/task-id@$kanboard_server>
  • Subsequent events set the (deterministic) Root-Event Message-ID Header in In-Reply-To and have Message-IDs of the form <org/project/object_type/object_number/event_type/event_number@github.com>. I don't think the distinction of event types is necessary here, and would propose to append the timestamp to get a unique value that still clearly relates to the root Message-ID.

@fguillot
Copy link
Member Author

fguillot commented Apr 3, 2020

Abandoning this PR. I never took the time to finish it.

@fguillot fguillot closed this Apr 3, 2020
@fguillot fguillot deleted the in_reply_to branch April 3, 2020 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants