Message-IDs generation should be a little more randomized

[jeremie.corbier@…]

The way message-ids of notification emails are generated is a little too simple to my mind. Maybe, you could add a little more randomness with the random module ?

[Matthew Good]

Message ids cannot be random since they need to be reproducable for the "In-Reply-To" and "References" headers for further emails related to the ticket.

[Ulrich Eckhardt <eckhardt@…>]

I have the concrete case that different tickets generate notifications with the same message ID, which breaks the association between related and unrelated messages and is obviously not the idea of an "ID". I took a look at the code, and I think it would help if you mangled the project into the ID, too.

[Emmanuel Blot]

Replying to Ulrich Eckhardt <eckhardt@satorlaser.com>:

I have the concrete case that different tickets generate notifications with the same message ID, which breaks the association between related and unrelated messages and is obviously not the idea of an "ID". I took a look at the code, and I think it would help if you mangled the project into the ID, too.

The project URL is already mangled into the message ID, however as this setting is not mandatory, it may be left blank… You're right here.

[Ulrich Eckhardt <eckhardt@…>]

Under 'project' in the configfile, I have different 'name' entries but equal 'url' entries (both point to the server running tracd). So, just using different 'url' entries I should be able to get this working, but I would also break existing relations, right?

Just one suggestion how I would do it: create a UID for every environment when it is initialised (trac-admin … initenv) and document that it is used to identify messages originating from this environment. That way, if a user changes or duplicates it, they are at least warned.

Cheers & thanks!

[Remy Blank]

I'm not sure this is still an issue. At any rate, it would be a defect, not an enhancement.

[Christian Boos]

Milestone 1.0 deleted