Defect #13851
closed
Unthreade new mail message
Added by pasquale [:dedalus] about 11 years ago.
Updated about 5 years ago.
Description
I have updated redmine from previous (old) 1.4.0 to new 2.3.0.
With new release, I have a problem with emails thread view: if I have old mail threaded (for example per bug [A]) and now someone update the bug [A], the new mail is orphaned and not threaded with others (old mails).
This happens per a changed creation of message-id in email source.
For the previous redmine release, when the bts send a mail for example from
Date: Tue, 23 Apr 2013 11:23:09 +0200,
I see that message-id is created as
<redmine.journal-22140.20130423112308@XXX.it>
Now message-id is created as 22140.20130423092308 (-2 hours)
and also references is created as 22140.20130423092308 (-2 hours) and cannot find originale message-id that is 22140.20130423112308 (+ 2 hours)
Is this intentional or is a new behavior of timestamp.strftime routine?
The issue is related to new application.rb per option config.active_record.time_zone_aware_attributes;
If i set config.active_record.time_zone_aware_attributes = false all work fine.
This is a major bug because in this situation, a message for the same bug posted the day after the daylight savings off isn't in the same thread of message sended for the same bug the day before!
STRs (steps to reproduce):
- move pc time to 30 march 2013, 10 AM
- create a new bug: the first mail is sended to you
- move pc time to 31 march 2013, 10 AM (when Europe starts Daylight Saving Time)
- update the previusly created bug: redmine sends a mail to you but the two mails are unthreaded
- Related to deleted (Defect #13888: Daylight savings causes inconsistency of Message-Id in emails)
- Is duplicate of Defect #13888: Daylight savings causes inconsistency of Message-Id in emails added
- Status changed from New to Closed
- Priority changed from High to Normal
- Resolution set to Duplicate
Also available in: Atom
PDF
Updated by 
Updated by