Edgewall Software
Modify

Opened 14 years ago

Last modified 5 years ago

#2619 new defect

Message-IDs generation should be a little more randomized

Reported by: jeremie.corbier@… Owned by:
Priority: low Milestone: unscheduled
Component: notification Version: 0.10.3
Severity: minor Keywords: notification email
Cc: Branch:
Release Notes:
API Changes:

Description

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 ?

Attachments (0)

Change History (10)

comment:1 by Matthew Good, 14 years ago

Milestone: 0.10
Resolution: wontfix
Status: newclosed

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.

comment:2 by anonymous, 14 years ago

Summary: Message-IDs generation should be a little more randomizedMessage-IDs generation should be a little more randomized1

comment:3 by anonymous, 14 years ago

Summary: Message-IDs generation should be a little more randomized1Message-IDs generation should be a little more randomized

comment:4 by Ulrich Eckhardt <eckhardt@…>, 12 years ago

Resolution: wontfix
Status: closedreopened
Version: 0.9.30.10.3

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.

in reply to:  4 comment:5 by Emmanuel Blot, 12 years ago

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.

comment:6 by Ulrich Eckhardt <eckhardt@…>, 12 years ago

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!

comment:7 by Remy Blank, 11 years ago

Milestone: 1.0
Type: enhancementdefect

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

comment:8 by Christian Boos, 10 years ago

Milestone: 1.0unscheduled

Milestone 1.0 deleted

comment:9 by Peter Suter, 7 years ago

Component: ticket systemnotification

comment:10 by Ryan J Ollos, 5 years ago

Owner: Jonas Borgström removed
Status: reopenednew

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The ticket will remain with no owner.
The ticket will be disowned. Next status will be 'new'.
as The resolution will be set. Next status will be 'closed'.
The owner will be changed from (none) to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.