infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (INFRA-15519) JIRA mails use incorrect In-Reply-To and References headers since Dec 2012
Date Fri, 24 Nov 2017 02:43:00 GMT

     [ https://issues.apache.org/jira/browse/INFRA-15519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Chris Lambertus updated INFRA-15519:
------------------------------------
    Status: Waiting for user  (was: Waiting for Infra)

Do  you have a suggested solution?

> JIRA mails use incorrect In-Reply-To and References headers since Dec 2012
> --------------------------------------------------------------------------
>
>                 Key: INFRA-15519
>                 URL: https://issues.apache.org/jira/browse/INFRA-15519
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>         Environment: commons issues mailing list
>            Reporter: Sebb
>            Priority: Minor
>
> Prior to Dec 2012, mails sent by JIRA used the same format for the Message-ID and the
In-Reply-To headers.
> For example:
> ===
> From issues-return-28886-apmail-commons-issues-archive=commons.apache.org@commons.apache.org
 Wed Aug 15 14:46:41 2012
>  Message-ID: <1572224473.13845.1345041998018.JavaMail.jiratomcat@arcas>
>  Subject: [jira] [Created] (OGNL-221) Map with String key that contains a non-word character
prevents value from being saved
> ===
> From issues-return-28887-apmail-commons-issues-archive=commons.apache.org@commons.apache.org
 Wed Aug 15 14:48:39 2012
> Message-ID: <952001715.13856.1345042118158.JavaMail.jiratomcat@arcas>
> In-Reply-To: <1572224473.13845.1345041998018.JavaMail.jiratomcat@arcas>
> Subject: [jira] [Updated] (OGNL-221) Map with String key that contains a non-word character
prevents value from being saved
> ===
> After that point, the Message-Ids changed, but the other headers did not.
> Also at that point, the [Create] mails started including IRT headers (which does not
make sense). The headers now look like this:
> ===
> From issues-return-31137-apmail-commons-issues-archive=commons.apache.org@commons.apache.org
 Fri Dec  7 16:51:28 2012
> Message-ID: <JIRA.12622926.1354898987453.4060.1354899080917@arcas>
> In-Reply-To: <JIRA.12622926.1354898987453@arcas>
> Subject: [jira] [Created] (DAEMON-271) No available JVMs when compiling against jdk1.7.0_09
> ===
> From issues-return-31137-apmail-commons-issues-archive=commons.apache.org@commons.apache.org
 Fri Dec  7 16:51:28 2012
>  Message-ID: <JIRA.12622926.1354898987453.4060.1354899080917@arcas>
>  In-Reply-To: <JIRA.12622926.1354898987453@arcas>
>  Subject: [jira] [Created] (DAEMON-271) No available JVMs when compiling against jdk1.7.0_09
> From issues-return-31138-apmail-commons-issues-archive=commons.apache.org@commons.apache.org
 Fri Dec  7 16:55:21 2012
> Message-ID: <JIRA.12622926.1354898987453.4076.1354899320999@arcas>
> In-Reply-To: <JIRA.12622926.1354898987453@arcas>
> Subject: [jira] [Updated] (DAEMON-271) No available JVMs when compiling against jdk1.7.0_09
> ===
> From issues-return-31154-apmail-commons-issues-archive=commons.apache.org@commons.apache.org
 Sun Dec  9 15:01:25 2012
> Message-ID: <JIRA.12622926.1354898987453.9349.1355065283019@arcas>
> In-Reply-To: <JIRA.12622926.1354898987453@arcas>
> Subject: [jira] [Resolved] (DAEMON-271) No available JVMs when compiling against jdk1.7.0_09
> ===
> Note that the Created mail has a spurious IRT.
> Also the IRT in the follow-up to the Create message does not match the original message.
The first two numbers after the JIRA prefix are the same, but the Message ID has two more
numbers which are missing from the IRT.
> Thus all the replies have the same IRT.
> They do have different Message Ids.
> It looks as though the first two numbers may be unique to the thread.
> However AFAIK the IRT values are supposed to be opaque, so the IRT will never match.
> This obviously messes up standard IRT processing.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message