https://www.redmine.org/https://www.redmine.org/favicon.ico?16793021292012-03-09T16:46:33ZRedmineRedmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=366992012-03-09T16:46:33ZJérôme BATAILLE
<ul></ul><p>The only case that seems odd is the table wiki_contents that as an updated_on field but no created_on one.</p>
<p>Anyway the patch as the original code always fallback on the existing field.<br />The patch just finds the more accurate information, updated_on.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=367002012-03-09T16:52:09ZEtienne Massip
<ul></ul><p>Isn't the message id the conversation id? If yes, it does not seem too weird to have the same id for every update of a specific issue?</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=367012012-03-09T17:01:40ZEtienne Massip
<ul><li><strong>Target version</strong> set to <i>Candidate for next minor release</i></li></ul><p>It is not.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=367022012-03-09T17:09:36ZJérôme BATAILLE
<ul></ul><p>That's it, the conversation id is called <strong>references</strong>.</p>
<p>Thanks to have integrated the patch in the next minor release.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=367052012-03-09T18:16:07ZEtienne Massip
<ul></ul><p>It's candidate =)</p>
<p>From what I've seen, it seems that <code>Original-Message-ID</code> header is more usable then <code>References</code> which should list all the ids of all the messages of the conversation.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=367092012-03-09T21:14:25ZJean-Philippe Langjp_lang@yahoo.fr
<ul></ul><blockquote>
<p>If a modification is made on the same issue the message Id can be the same</p>
</blockquote>
<p>How to reproduce? Because when an update is done on an issue, this is the timestamp of the journal that is used, not the issue timestamp.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=367542012-03-12T15:29:38ZJérôme BATAILLE
<ul></ul><p>In the main actual cases the created_on is reflecting the update time.</p>
<p>So there is no case for the moment were you can reproduce the bug because in the only table having the two fields (issues) the date is get through the journal table.</p>
<p>But I suppose it's sort of misleading (and we were mis leaded, lost a few days to understand why messages were not received) when adding new mailer methods, because we were sending mails reflecting changes in the issues, but not using the journal informations.</p>
<p>I suppose again that if other mailer methods are added, they can fall into this case, it's the reason why I proposed the patch.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=513222013-08-20T17:36:03ZJérôme BATAILLE
<ul><li><strong>Status</strong> changed from <i>New</i> to <i>Resolved</i></li></ul><p>After digging into the code, I realized the patch I proposed leads to an inconsistency :<br /><strong>references</strong> and <strong>message_id</strong> use the method that I proposed to patch.<br />It implies that the patch breaks the references for an issue update.</p>
<p>I now use message_id on a journal object, thus the message_id is always unique.</p>
<p>Sorry for ma bad understanding of the problem.<br />I close this issue</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=521802013-09-30T13:13:50ZJérôme BATAILLE
<ul></ul><p>You can remove it from <strong>Candidate for next minor release</strong></p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=522152013-10-01T10:53:05ZToshi MARUYAMA
<ul><li><strong>Status</strong> changed from <i>Resolved</i> to <i>Closed</i></li><li><strong>Target version</strong> deleted (<del><i>Candidate for next minor release</i></del>)</li></ul><p>Thanks.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=776462017-03-31T12:23:34ZJérôme BATAILLE
<ul></ul><p>Hi, you can indicate in the Resolution that's it's <strong>Invalid</strong>, if you have the time to, thanks a lot.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=776472017-03-31T12:35:44ZToshi MARUYAMA
<ul><li><strong>Resolution</strong> set to <i>Invalid</i></li></ul><p>Done.</p> Redmine - Defect #10414: Duplicated Message-Id in headers of mails send by Redminehttps://www.redmine.org/issues/10414?journal_id=776482017-03-31T12:36:33ZJérôme BATAILLE
<ul></ul><p>Thanks !</p>